win10 1809 to 1909 "inaccessible boot device" 0xC1900101 0x30017

Joel S.

Member
Joined
Feb 17, 2020
Posts
16
Trying to update win10 from 1809 to 1909, the error is "inaccessible boot device" 0xC1900101 0x30017 the update gets to 27%, reboots, and blue screen.

The system has been up and running for many years, if i recall it was a clean install, on a different hdd, now on a sdd for several years.

Bios are now using uefi, before the error was regular legacy, this made no change, except now I have a boot entry, Microsoft Windows, that crashes with an instant blue screen “File :\bcd error”. The entry Windows boot manager works just fine. Not sure if any of this is related to the issue. I have unplugged my multifunction printer, and extra usb hub as well, no change. My OS SSD is on channel 1 not zero, I have attached a screenshot of disk management from win10.

Step #2 - Run SFC Scan

sfc /scannow

Beginning verification phase of system scan.

Verification 70% complete.

Windows Resource Protection could not perform the requested operation.


Step #4 - Run SFCFix

crashes right away,

SFCFix version 3.0.2.1 by niemiro.
Start time: 2020-02-19 06:55:34.958
Microsoft Windows 10 Build 17763 - amd64
Not using a script file.

SFCFix version 3.0.2.1 by niemiro has encountered an unhandled exception.
Currently storing 0 datablocks.
Finish time: 2020-02-19 06:56:06.793

Chkdsk /f from event viewer Windows has scanned the file system and found no problems. No further action is required.

FRST Scan run as administrator, and included logs, with additional checked.

Tried windows repair aio in safe mode repairing only windows update, reran the update and it failed. (Might have had my usb hub installed, but printer still disconnected)

I have tried from the thumb drive, dvd, and iso all 1909, 1 image downloaded from a link posted here, the rest using media creation 1909.


These are included also in the zip file CBS zipped, frst and addition txt, disk management screenshot, drive health screenshot,

c:\$WINDOWS.~BT\Sources\Panther\setupact.log and c:\$WINDOWS.~BT\Sources\Panther\setuperr.log


Please let me know what the next steps are, and thank you so much for your time.

Joel
 

Attachments

Last edited:
strange, i tried the version before 1909, 1903 v2 ?? results were the same, but after the first reboot, got to 30%, vs 27%, then my computer shut off. had me a bit concerned for sure, but it restarted hitting the power button, continued to blue screen with the same error a couple times, then rolled back. (the first screen with the counter in the top left gets to 100%, then boots again, with the progress in the middle of the screen, or bottom 1/3 this is the one where at 27 or 30%, it reboots, and crashes after a bit with the error.

thought i would try something different, but still no luck.
still on 17763.1039 x64 1809
 
Hi!

Please do the following:

GSmartControl
Follow the instructions below to check your SMART status with GSmartControl:


  • Download the portable version of GSmartControl and save it on your Desktop;
  • Extract the zip file to your Desktop. Open the folder gsmartcontrol-1.1.3-win64 which should be located on your Desktop and double-click gsmartcontrol.exe to launch the program.
  • Identify your drive in the list (if recognized by the tool), and hover your mouse over it.
  • You should see something called: SMART status. It will either read: Enabled, in which case you should do the following:
  • Double-click on it to bring up its window (usually you'll find your drive by its size or its brand name);
  • Go to the Self-Tests tab, then select Extended Self-test in the Test type drop-down list and click on Execute (this test can take a few hours to complete);
  • Once the test is over, the results will be displayed at the bottom of the window. Please copy and paste these results in your next reply or take a screenshot;
  • Also, go in the Attributes tab and if you have any entries highlighted in red or pink, take a screenshot of the GSmartControl window and attach it in your next reply;
  • Please note: If the SMART Status reads: Unsupported, stop and let me know.
    info_failing.png
 
thank you for your response, i will run that now.
I was able to do a repair/over the top with 1809 and that fixed the sfc, but 1909 failed again, i might have got lax at the usb adapter, don't recall.
For some reason, the first part of the 1809 and 1909 my monitor turned off, and i lost signal, the monitor and hdmi had zero signal, i did have it check for updates during the install, not sure if that was the issue. I let the update run, since my HDD light was showing activity, the screen eventually came back on, not sure if it tried updating a driver or something. 1809 added an additional partition at the end, like 800mb, 1909 gave the same blue screen error.

i posted on tenforums as well, jumped through a ton of hoops there with results posted, i stopped with driver verifier, made my system wonky, added 9, then went up some more, and it wasn't good. looked like it wouldn't boot, i shut it down, then started getting post codes and other things, reset bios a few times,
(i did update my z77 extreme 6 bios to the latest, its a beta for nvme to boot from.
BSOD "inaccessible boot device" 0xC1900101 0x30017 during 1909/1903 - Windows 10 Help Forums

I am not sure if the bcd or efi has anything to do with it. these drives have been configured a few different ways over the years. i have listings that will blue screen in my boot menu,
thank you again for your time, i will report the findings from that tool.
 
progress is sitting at 90%, time remaining says 0, HDD light showing a tic of activity..... i'll let it keep doing what it wants, if it is still doing something. per task manager it is not doing much of anything, still at 90% and 0 disk activity ... Attributes are good, no red or pink,

my system was rolled back to before installing 1809 over the top, i had a backup of the complete drive with Macrium Reflect. i did this after the last failed 1909 update.
 
no, never had a hard drive fail
cloned from a HDD to SDD possibly, or win10 was a clean install dual boot , trying to remember, it was many years ago

as far as the clone it is on now, that was done the other day. same sdd, just before 1809 repair inplace, and a second one after that before 1909, so i had 3 versions,
old school norton ghost user, way back in the day,
 
Okay. Please do the following:

SFC Scan


  1. Click on the Start button and in the search box, type Command Prompt
  2. When you see Command Prompt on the list, right-click on it and select Run as administrator
  3. When command prompt opens, copy and paste the following commands into it, press enter after each

    sfc /scannow


    Wait for this to finish before you continue

    copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
  4. This will create a file, cbs.txt on your Desktop. Please attach this to your next post.
 
SFCFix Script

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.


  1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
  5. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.



SFC Scan


  1. Click on the Start button and in the search box, type Command Prompt
  2. When you see Command Prompt on the list, right-click on it and select Run as administrator
  3. When command prompt opens, copy and paste the following commands into it, press enter after each

    sfc /scannow


    Wait for this to finish before you continue

    copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
  4. This will create a file, cbs.txt on your Desktop. Please attach this to your next post.
 

Attachments

i zipped the cbs, because the txt was too large to upload, 9.9 MB
i can rerun, rezip it, split it in 2, and post both halves, or something else , but the forum will not let me upload the cbs.txt



Code:
 SFCFix version 3.0.2.1 by niemiro.
Start time: 2020-02-26 07:52:18.336
Microsoft Windows 10 Build 17763 - amd64
Using .zip script file at C:\Users\JAS\Desktop\SFCFix.zip [0]




PowerCopy::
Successfully took permissions for file or folder C:\WINDOWS\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\Defender.psd1
Successfully took permissions for file or folder C:\WINDOWS\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpComputerStatus.cdxml
Successfully took permissions for file or folder C:\WINDOWS\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpPreference.cdxml
Successfully took permissions for file or folder C:\WINDOWS\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpScan.cdxml
Successfully took permissions for file or folder C:\WINDOWS\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpSignature.cdxml
Successfully took permissions for file or folder C:\WINDOWS\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpThreat.cdxml
Successfully took permissions for file or folder C:\WINDOWS\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpThreatCatalog.cdxml
Successfully took permissions for file or folder C:\WINDOWS\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpThreatDetection.cdxml
Successfully took permissions for file or folder C:\WINDOWS\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpWDOScan.cdxml

Successfully copied file C:\Users\JAS\AppData\Local\niemiro\Archive\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\Defender.psd1 to C:\WINDOWS\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\Defender.psd1.
Successfully copied file C:\Users\JAS\AppData\Local\niemiro\Archive\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpComputerStatus.cdxml to C:\WINDOWS\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpComputerStatus.cdxml.
Successfully copied file C:\Users\JAS\AppData\Local\niemiro\Archive\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpPreference.cdxml to C:\WINDOWS\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpPreference.cdxml.
Successfully copied file C:\Users\JAS\AppData\Local\niemiro\Archive\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpScan.cdxml to C:\WINDOWS\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpScan.cdxml.
Successfully copied file C:\Users\JAS\AppData\Local\niemiro\Archive\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpSignature.cdxml to C:\WINDOWS\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpSignature.cdxml.
Successfully copied file C:\Users\JAS\AppData\Local\niemiro\Archive\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpThreat.cdxml to C:\WINDOWS\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpThreat.cdxml.
Successfully copied file C:\Users\JAS\AppData\Local\niemiro\Archive\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpThreatCatalog.cdxml to C:\WINDOWS\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpThreatCatalog.cdxml.
Successfully copied file C:\Users\JAS\AppData\Local\niemiro\Archive\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpThreatDetection.cdxml to C:\WINDOWS\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpThreatDetection.cdxml.
Successfully copied file C:\Users\JAS\AppData\Local\niemiro\Archive\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpWDOScan.cdxml to C:\WINDOWS\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpWDOScan.cdxml.

Successfully restored ownership for C:\WINDOWS\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\Defender.psd1
Successfully restored permissions on C:\WINDOWS\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\Defender.psd1
Successfully restored ownership for C:\WINDOWS\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpComputerStatus.cdxml
Successfully restored permissions on C:\WINDOWS\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpComputerStatus.cdxml
Successfully restored ownership for C:\WINDOWS\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpPreference.cdxml
Successfully restored permissions on C:\WINDOWS\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpPreference.cdxml
Successfully restored ownership for C:\WINDOWS\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpScan.cdxml
Successfully restored permissions on C:\WINDOWS\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpScan.cdxml
Successfully restored ownership for C:\WINDOWS\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpSignature.cdxml
Successfully restored permissions on C:\WINDOWS\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpSignature.cdxml
Successfully restored ownership for C:\WINDOWS\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpThreat.cdxml
Successfully restored permissions on C:\WINDOWS\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpThreat.cdxml
Successfully restored ownership for C:\WINDOWS\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpThreatCatalog.cdxml
Successfully restored permissions on C:\WINDOWS\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpThreatCatalog.cdxml
Successfully restored ownership for C:\WINDOWS\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpThreatDetection.cdxml
Successfully restored permissions on C:\WINDOWS\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpThreatDetection.cdxml
Successfully restored ownership for C:\WINDOWS\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpWDOScan.cdxml
Successfully restored permissions on C:\WINDOWS\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpWDOScan.cdxml
PowerCopy:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 9 datablocks.
Finish time: 2020-02-26 07:52:20.079
Script hash: 5hcBxtLGKNbwYykh3rzXDwVDLGiWWmTKFa7kA2EqUVk=
----------------------EOF-----------------------
 
Step#1 - Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Try running SFC just like you have in the past.
3. Stop Process Monitor as soon as it fails. You can simply do this by clicking the magnifying glass on the toolbar as shown below.
i3yiUac.png


4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine.
5. Zip up and provide the link to the LogFile.PML file as well as your CBS.log Examples of services to upload to are Dropbox or OneDrive or SendSpace.
 
Last edited:
so update 1909 till the blue screen inaccessible boot device??
it happens after the 2nd or 3rd reboot, not in windows, ??
not sure how it would stay running, or i would stop it at that point

or stop it once the update rolls back to previous, if it does ??
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top