Windows 10: INACCESSIBLE BOOT DEVICE after Win10 Update

Page 3 of 4 FirstFirst 1234 LastLast
  1.    21 Jan 2018 #21

    i was able to do that before i did something wrong with the bcd, because then after restart from ”inaccessible boot” i was taken to a recovery screen, however i cannot get there anymore as after inaccessible boot bsod restart i now get a bcd bsod.

    i can only choose options from my USB, my only options are ”system restore” (doesnt work) ”command prompt”, ”system image recovery”, ”go back to previous version” (doesnt work) and ”startup repair”.

    how ****ed am i? can i no longer repair my C drive without total loss of data?

    im guessing i could access that data if i hooked it up to another pc, sadly I do not have one

    thanks a lot for trying to help, all i really have to say is **** microsoft and **** intel. its a joke intel can ignore a security problem and microsoft can push a forced update that bricks your pc and there is no punishment for them. shitty companies with awful morals, despicable :@
      My ComputerSystem Spec

  2.    21 Jan 2018 #22

    Let try below troubleshooting option.


    Windows Vista/ 7/8/8.1/10 keep a regular backup of the registry handy in case you need to overwrite a corrupted registry. By default, the RegIdleBackup task runs every 10 days, so that’s as far back as you would lose if you replaced the current registry with the automatically backed-up files. You can find the backed-up registry files in \Windows\System32\config\RegBack folder.


    Please boot your computer with Windows Setup Media and from Windows Recovery Environment start the Command Prompt.

    Please type below command into Command Prompt and press Enter key.

    Code:
     Dir C:\Windows\System32\config\RegBack

    Above command will list files stored within RegBack folder and there file size, make sure files are not zero size if they are do not follow below instructions.



    Please replace partition letter C: with Windows installed partition letter. When computer boots into Windows Recovery Environment (WinRE) environment the drive letter assign to Windows partition may not be C: drive letter because Windows 7, 8 , 8.1 and 10 creates a separate system partition when it's installed from scratch. The system partition contains boot files WinRE assigns the system partition the C: drive letter and the Windows installed partition will be assign any other drive letter usually D: drive letter is assign to Windows installed partition. The Bcdedit /enum | find "osdevice" command can be use to find out the drive letter of the Windows installed partition the output of the Bcdedit command is similar to this osdevice partition=D:. The drive letter after partition= is the drive letter of the Windows partition.

    Please type below commands into Command Prompt and for each command you have typed press Enter key.



    Code:
    Ren  C:\windows\system32\config\SAM         SAM.BAK
    
    Ren  C:\windows\system32\config\SYSTEM      SYSTEM.BAK
    
    Ren  C:\windows\system32\config\SECURITY    SECURITY.BAK
    
    Ren  C:\windows\system32\config\DEFAULT     DEFAULT.BAK
    
    Ren  C:\windows\system32\config\SOFTWARE    SOFTWARE.BAK
    
     
    
    Copy  C:\Windows\System32\config\RegBack\SAM         C:\windows\system32\config
    
    Copy  C:\Windows\System32\config\RegBack\SYSTEM      C:\windows\system32\config
    
    Copy  C:\Windows\System32\config\RegBack\SECURITY    C:\windows\system32\config
    
    Copy  C:\Windows\System32\config\RegBack\DEFAULT     C:\windows\system32\config
    
    Copy  C:\Windows\System32\config\RegBack\SOFTWARE    C:\windows\system32\config

    This procedure assumes that Windows Vista/7/8/8.1/10 is installed to the C:\ partition. Make sure to replace C:\ drive letter to the appropriate Windows OS installed partition drive letter if it is a different location.


    Above commands renames the registry files at their existing location, and then copies the registry files from the RegBack folder to the C:\Windows\System32\Config folder.
      My ComputerSystem Spec

  3.    21 Jan 2018 #23

    FreeBooter said: View Post
    Let try below troubleshooting option.


    Windows Vista/ 7/8/8.1/10 keep a regular backup of the registry handy in case you need to overwrite a corrupted registry. By default, the RegIdleBackup task runs every 10 days, so that’s as far back as you would lose if you replaced the current registry with the automatically backed-up files. You can find the backed-up registry files in \Windows\System32\config\RegBack folder.


    Please boot your computer with Windows Setup Media and from Windows Recovery Environment start the Command Prompt.

    Please type below command into Command Prompt and press Enter key.

    Code:
     Dir C:\Windows\System32\config\RegBack

    Above command will list files stored within RegBack folder and there file size, make sure files are not zero size if they are do not follow below instructions.



    Please replace partition letter C: with Windows installed partition letter. When computer boots into Windows Recovery Environment (WinRE) environment the drive letter assign to Windows partition may not be C: drive letter because Windows 7, 8 , 8.1 and 10 creates a separate system partition when it's installed from scratch. The system partition contains boot files WinRE assigns the system partition the C: drive letter and the Windows installed partition will be assign any other drive letter usually D: drive letter is assign to Windows installed partition. The Bcdedit /enum | find "osdevice" command can be use to find out the drive letter of the Windows installed partition the output of the Bcdedit command is similar to this osdevice partition=D:. The drive letter after partition= is the drive letter of the Windows partition.

    Please type below commands into Command Prompt and for each command you have typed press Enter key.



    Code:
    Ren  C:\windows\system32\config\SAM         SAM.BAK
    
    Ren  C:\windows\system32\config\SYSTEM      SYSTEM.BAK
    
    Ren  C:\windows\system32\config\SECURITY    SECURITY.BAK
    
    Ren  C:\windows\system32\config\DEFAULT     DEFAULT.BAK
    
    Ren  C:\windows\system32\config\SOFTWARE    SOFTWARE.BAK
    
     
    
    Copy  C:\Windows\System32\config\RegBack\SAM         C:\windows\system32\config
    
    Copy  C:\Windows\System32\config\RegBack\SYSTEM      C:\windows\system32\config
    
    Copy  C:\Windows\System32\config\RegBack\SECURITY    C:\windows\system32\config
    
    Copy  C:\Windows\System32\config\RegBack\DEFAULT     C:\windows\system32\config
    
    Copy  C:\Windows\System32\config\RegBack\SOFTWARE    C:\windows\system32\config

    This procedure assumes that Windows Vista/7/8/8.1/10 is installed to the C:\ partition. Make sure to replace C:\ drive letter to the appropriate Windows OS installed partition drive letter if it is a different location.


    Above commands renames the registry files at their existing location, and then copies the registry files from the RegBack folder to the C:\Windows\System32\Config folder.
    i will try this in the morning, either way i want to thank you so much for trying to help me, youre a great guy/gal and i will wish you the best possible life.

    if i try to boot into recovery options from my os i get this bsod:

    Imgur: The magic of the Internet

    i did not get this until i ****ed up the bcd stuff trying to solve the inaccessible boot issue on my own.

    is it possible maybe to repair that error so i can access recovery options and perform a reset?
      My ComputerSystem Spec

  4.    21 Jan 2018 #24

    If you cannot access Windows Recovery Environment and use Command Prompt there is no way we can repair the BCD data store error sorry.

    You were able to access the Windows Recovery Environment before enabling UEFI you have disabled UEFI and Secure Boot modes haven't you?
      My ComputerSystem Spec

  5.    21 Jan 2018 #25

    FreeBooter said: View Post
    If you cannot access Windows Recovery Environment and use Command Prompt there is no way we can repair the BCD data store error sorry.

    You were able to access the Windows Recovery Environment before enabling UEFI you have disabled UEFI and Secure Boot modes haven't you?
    i can reach it via the USB, however that way only gives me access to cmd, i cannot use the ”reset windows but save files” option, that option only exists if i can reach the recovery environment via my ssd with windows on it.

    is it possible to use cmd on the usb to copy files from my windows volume disk to another drive in case i need to completely reinstall windows on my sysdisk?

    it would be nice to be able to keep the files on it even if id need to completely reinstall all apps on it, re-configure windows and the various applications i had there.
      My ComputerSystem Spec

  6.    21 Jan 2018 #26

    Yes you can copy your personal files to any other attached storage drive from Command Prompt type Notepad and click File menu from Notepad and select Save this will open a File Explorer you can use this File Explorer to copy your personal files to any other storage drive.
      My ComputerSystem Spec

  7.    22 Jan 2018 #27

    Hi folks

    @fullofdespair

    There's an old bug in Windows install -- you will have problems if Windows AT INSTALL TIME sees more than 4 existing partitions on HDD's -- disconnect all possible HDD's and or make offline or HIDE partitions if you have a partition manager.

    Now install Windows -- after boot you can re-enable the HDD's again -- this was an old defect that I believe was never really addressed as people have different HDD's these days and laptops generally don't have 4 HDD's. !!!!

    Cheers
    jimbo
    Last edited by jimbo45; 22 Jan 2018 at 04:34.
      My ComputerSystem Spec

  8.    22 Jan 2018 #28

    You could try the Fix Windows Boot Option on the Macrium Repair Disk if you have one ? it has saved me a few times from BCD Boot issues.

    KB.
      My ComputerSystem Spec

  9.    22 Jan 2018 #29

    Kbird said: View Post
    You could try the Fix Windows Boot Option on the Macrium Repair Disk if you have one ? it has saved me a few times from BCD Boot issues.

    KB.
    Hi there
    @Kbird

    Just tested trying to install Windows on device with > 4 partitions -- system wouldn't install (message on each partition selected for installation -- system cannot be installed to this partition !!) so I'd suggest the OP wipes his HDD first and then tries again -- also allowing legacy boot and disabling secure boot in BIOS. (Shows I'm not to busy today !!!)

    If HDD is < 2 TB I wouldn't bother with GPT - simply split HDD into say 2 physical partitions C and D - make C say 100 GB for Windows and D the rest for data. Now try and install Windows on "C".

    If computer only has UEFI still disable secure boot and ensure that when the install media was created it was created on a computer that was UEFI capable or again system won't boot after install !!!!!. You'll also need to make the HDD a GPT one in this case.

    Rufus is the best tool for creating bootable media once you have the iso downloaded.

    Cheers
    jimbo
      My ComputerSystem Spec

  10.    22 Jan 2018 #30

    Sorry Jimbo , I didn't mean to infer your advice was wrong at all , I just see People trying all these complicated fixes without trying the simple stuff like checking the Boot Order in the Bios (Windows Memory Mananger 1st still?) or the Macrium Fix Boot Option 1st.

    I believe there was (is?) an old limit which was 4 Primary Partitions on One disk (MBR?), ( which could be 4 Disks too) you could have as many logical partitions as you wanted ( inside an Extended Partition), if I remember correctly.

    found this at Aomei.....

    The Rules of Partitioning a Hard Drive

    A hard disk drive must be partitioned before you can use it. There are some rules as follows:

    • A maximum of four primary partitions can be created on any MBR hard disk. The limitation of four primary partitions is that when one primary partition is applied to the system the master boot record is structured.
    • There is only one primary partition can be designated as active partition and this partition is used to boot system.
    • BIOS will only recognize the active partition for loading operating system. Other partitions can’t be recognized.
    • To break the limitation of at most 4 primary partitions, you have to create 3 or less primary partitions plus an extended partition and there is only one extend partition.



    You don't really need Rufus these days , Window's Explorer will open any .iso ( right click> open with.... or Mount ) and will mount it so it appears like a DVD Drive and from there you can copy everything to a Fat32 Formatted USB Drive ( I find USB2 Drives work best as bootable drives ) mark the Drive Active if it is to be a booted on a legacy Bios , UEEFI Bios dont require this.

    KB
      My ComputerSystem Spec


 
Page 3 of 4 FirstFirst 1234 LastLast

Related Threads
Having problems updating 17046 to either 17063 and 17074. Update seems to work up until it reboots I then get a GSOD inaccessible boot device, it reboots and the same happens (GSOD). The System then reverts to my old version (17046). Thanks Brian
Inaccessible boot device in BSOD Crashes and Debugging
Just finished this build Wednesday night. Finished all software installs Thursday night and did some gaming Friday night. I played Doom 2016 on Ultra settings @2k 144hz for about an hour. System ran beautifully. All hardware is at factory spec. ...
Sorry, I read through the posting instructions, but due to the nature of the problem, I can not provide a crash log or a screen shot because I can not get past the Repair/Diagnose loop. My Windows 10 pro has been running just fine until yesterday...
Inaccessible Boot Device in Installation and Upgrade
Sir, I had upgraded my Acer Aspire Laptop (CORE i5 - 4GB RAM) from Windows 8.1 to Windows 10 recently. As it was running very slow, I decided to do a 'clean reset'. By mistake, the recovery partition also cleaned. It then went to a blue screen...
Inaccessible Boot Device in General Support
I ran into a problem this evening with my laptop, Lenovo B575. The laptop kept restarting because of inaccessible boot_device. I am not sure how to fix this problem. I know it's too new for everyone with Windows 10. Mine is Windows 10 64X Home...
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 08:28.
Find Us