Windows 10: Windows 10 fails to update

Hi tybee,

It looks like your OS is heavily corrupted, IF SFC & DISM can fix it then it will be very difficult.
The corruption includes features as Cortana, preinstalled apps, drivers and many other things.

I would advice a clean reinstallation of your OS, meaning that you need to backup your important data so all current partitions can be deleted. After the reinstallation is done you'll need to run Windows Update again, I would ask that you also perform a few tests to see if the memory and/or hard drive may be causing problems that may cause this size of corruption.

 

For what it's worth, I recently created another profile (I'm in it now) and it shows an active Cortana and Edge. I know Edge is working because I've used it but I don't know how to test Cortana. Is any of that meaningful? Also, I recently performed a successful CHKDSK and Windows 10 memory test and used Acronis 2016 to make an image of my hdd. Is any of that useful for doing the reinstall or should I do them again. At this point,with some guidance, I'm certainly ready to it.

 

Please upload the chkdsk log *Arrow Chkdsk Log in Event Viewer - Read in Windows 10 - Windows 10 Forums

The built-in memory test isn't very reliable, it finds nothing when there are problems, of course no software is perfect when testing hardware but the test we suggest is certainly better than the built-in.

 

I still think my post #44 of a repair install using an in-place upgrade *might* fix things, but you need to use the media creation tool to have it saved to USB, and you need to choose the correct ISO for your system. But axe0 is right - your sfc log is riddled with problems, and not just hash mismatches. There is a lot of corruption in your system. *Sad

 

Filter current log was greyed out so I'm thinking the CHKDSK event log is not there. In any event I'll do it again and post when it's complete.

 

Please make sure that you run following chkdsk command from an admin command prompt
Code: chkdsk C: /r[/quote] Change the letter C to the letter of the partition on which you ran chkdsk.

 

I had already started chkdsk using one of your tutorials calling for chkdsk c: /f /r /x. It's really slow, after ~2hrs it's only 11%. When it completes I'll post the event log and start the mem test. Is there a tutorial for the test you mentioned?

 

It can be indeed very slow, just let it run and it'll finish *Smile

The /f command doesn't need to be included, /x is also unnecessary as the partition needs to be unmounted with /r to fix problems. /r & /x include /f feature but /r also includes /x feature indirectly.

 

Do you recommend memtest86 in lieu of the built-in memory test?

 

chkdsk finally finished. chkdsk results.txt

 

MemTest86+ would be better *Smile

Run MemTest86+ - Test RAM - Windows 10 Forums



Note



MemTest86+ needs to be run for at least 8 complete passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

Make a photo of the result and post it.

Addition:
If errors show up you can stop the test, remove all sticks but 1 and test this single stick in each slot for 8 passes or until errors show, switch sticks and repeat.
If errors show up and you see them a lot later, no problem, the errors don't affect the test.

 

The memtest86+ finally finished with no errors. See attched photo:

 

I tried post 44 again: I downloaded the media creation tool, saved it to desktop, ran the tool selecting create installation media for another pc, selected options English, Windows 10, and 64-bit, checked 'use the recommended options for this PC', dotted 'USB flash drive', it identified the USB stick I wanted to use and installed it. Then I opened the flash drive (left click), right clicked setup and selected run as administrator. The result was the same as before: "Windows" icon appeared for 30 sec and then I got the same message that Setup couldn't properly start.... reboot and try again. I noted a message in the first part of this instruction about disabling secure boot​?? Would that be an issue??

 

That all sounds perfectly correct, except for running setup.exe with run as administrator. I've never had to do that - I've always been in an administrative account when trying to do the repair install and just double-click setup.exe. I don't think secure boot would have any effect (can't understand how it would), but I guess you could try turning it off - we've tried just about everything else.

 

I did not try disabling secureboot , not yet anyway, I found myself guessing at too many settings and decided against it until I've learned a little more about it. So, I guess I'm hold for now.