New
#1
Inaccessible_Boot_Device & Error code 0xc0000001
Hi Guys,
I had a pretty much faultless Win 10 setup with all the latest patches installed then this morning I connected an external USB hard drive which I had used several times before but this time Windows said it needed to install a new driver. I let the driver install and then Windows stated it needed a restart to complete the installation. When restarting I received the "Inaccessible_Boot_Device error message - Windows will restart for you" message. On restarting again I got: "Your PC couldn't start properly. Error code 0xc0000001." Windows tried to automatically repair itself displaying the Diagnosing message first and then Attempting Repair message, and finally reporting it could not fix the problem. I'm not sure if the new driver being installed created the problem or whether it was just a coincidence and something else has caused the fault.
I was able to boot to Recovery using a USB stick created with Microsoft's MediaCreationTool. Safe boot and all the other startup options didn't do anything apart from resulting in yet another failed boot. Getting to the command line, I was able to view the file that Windows creates when it tries to repair itself: c:\windows\system32\logfiles\srt\srttail.txt. That file shows that all tests were completed successfully until:
"Root cause found
A patch is preventing the system from starting
Repair action system files integrity check and repair
Result failed error code 0x490"
I tried: sfc /scannow
and got:
"Verification 100% complete
Windows resource protection could not perform the requested operation"
I then tried sfc /verifyonly
and got:
"Windows resource protection found integrity violations. Details are included in the cbs.log. Note that logging is currently not supported in offline servicing scenarios."
As the message suggested, no cbs.log files were created.
I have tried:
bootrec /fixmbr
bootrec /fixboot
bootrec /rebuildbcd
which all complete successfully but doesn't help.
Also tried chkdsk which didn't find any errors and:
bootsect /nt60 ALL
which again seems to complete successfully but doesn't help.
Any ideas?
Thanks,
Bob
Last edited by BobN; 28 Nov 2015 at 16:07. Reason: Added additional info