New
#1
BSOD updating to 1607, Inaccessible Boot Device, sfc/scannow corrupt
Hey there, computer overlords,
Thanks for checking this out.
TL;DR—BSOD, "INACCESSIBLE_BOOT_DEVICE" when updating to 1607. Restored from backup and tried again. Ran chkdsk. sfc /scannow fails (see log link). Drivers updated.
I let Windows do its normal updating routine/schedule, and everything appears to download and update fine. When updating to 1607, though, it updated, shut down, restarted, did more updating, restarted, and tried to boot. Then I got the BSOD, "INACCESSIBLE_BOOT_DEVICE." It restarted and tried again, getting the same BSOD. So, it gives up and restores back to the previous version of Windows, with no memory of the update (I'm one of the lucky ones who can still get into Windows).
Still, it continues to try to push the update through. I get the same results every time I allowed it. At first, I was like, "Oh, poop—I screwed up by installing something that's interfering with Windows" and restored to my handy-dandy backup, but the problem came back when it tried to update to 1607 again.
Pretty sure I ran a successful chkdsk on both my SSD (OS) and HDD. When running Windows Resource Protection (sfc /scannow), it says it "found corrupt files but was unable to fix some of them." The log file is too big to upload, so here's the link: Dropbox - CBS.log. Interestingly, I think I had that same problem with a computer I used a while ago (it's beyond dead now). Perhaps I'm cursed, or just make really poor decisions with my software choices?
I updated all my drivers and then ran the update again. No bean dip.
I'm pretty sure I can just stop Windows from updating to 1607, but if I can get a successful update going and resolve this, that's probably preferred.
Blah, blah, blah, "I shoulda stuck to Windows 7!" and all that tripe. This one's a head-scratcher for me; perhaps fixing those corrupt files will work?
Last edited by Hank R Chief; 20 Feb 2017 at 18:06.