Maybe this works: Go into safe mode and delete the whole "C:\Windows\SoftwareDistribution\" folder, reboot into normal mode and try again.
I guess I wasn't clear. Loading Windows ends up in a BSOD (INACCESSIBLE_BOOT_DEVICE) and on next startup it tries to repair itself for no effect. Loading safe mode also ends up in the same BSOD. Of course I can rename the folder from command line, but I strongly doubt SoftwareDistribution is the culprit. I have feeling it is easier to reset Windows instead on trying to fix this.
Funny you should mention this. I noticed my HP laptop rebooted twice yesterday while it was trying to download/install updates on Windows 10. After the smoke cleared and the dust settled, I checked the update history and found that KB890830, KB4022715, KB4022730, and KB4023834 all failed to install on the first attempt but somehow succeeded on the second try. Looks like I dodged a bullet without even being aware of it.
I took the CU on last night everything went smooth 15063.413 i assume this is what u guys are talking about. my update is KB4022405.... unless is a update 14393
kb4022405 = 1703 servicing stack (https://forums.mydigitallife.net/threads/windows-10-hotfix-repository.57050/page-202#post-1352410)
Thanks for the tip! I hadthe same issue with KB4022727. After deleting SoftwareDistribution folder, then re-installing KB4022727, it work. Thanks. I wasn't aware you could remove the entire folder. I always removed downloads folder only.
Thankfully no issues here; both the Servicing Stack update and the 15063.413 CU installed without incident, along with a bunch of other updates including for Office 2016. No details as far as I can tell regarding the Servicing Stack update though...
hi i am having a similar issue. i reinstalled 1703 about 3-4 times with a BSOD voming up after the last windows update it grabbed. almost everytime it BSOD with Memory_management or something related to the kernel. i turned off the ability for windows to download drivers as i thought it could be the issue. can you guys tell me exactly what do i need to do in order get windows fully updated with no BSOD ? thanks
If you're running 1607 mount the 1703 ISO and let Setup download critical updates right away when you're prompted instead of letting 1703 download and install them later. This reportedly worked for at least one person I know with a similar issue to yours.
If you're clean installing/upgrading windows why not first integrate the three updates and install using the pre-updated ISO?
I'm using one of the isos that is titled as Generation2 Windows 10 RS2 + Office. it installs fine but as soon as WU installs the mention KB , everything crashes. 1607 worked fine before and as well as CU until up to that weird KB that crashed it
After trying that homebrew ISO multiple times why not try a clean install with the untouched 1703 ISO once in the manner I suggested? Either that, or you can try untouched 1703 + latest CU slipstreamed as Enthousiast mentioned.
so i did try reinstalling but this time in MBR mode with rufus and so far i managed to get it working but however i hidden the bad KB until MS fixes it