Solved How to do a Repair install with inaccessible boot device issue

Jorgen E · Oct 29, 2025

chris1234 said:
I am using bootable USB for winRE, the winRE on the local drive does load up but the kbd and mouse don't work.

You don’t specify your motherboard, but if you have a PS/2 connector it might work for mouse or keyboard. (could be diabled in BIOS) USB is the problem.

chris1234 · Oct 29, 2025

tried these commands along with selecting the correct EFI drive
bcdboot F:\Windows /s W: /f UEFI
dir W:\EFI\Microsoft\Boot
See attached in case Im missing something important
I have not tried formatting the EFI partition yet

chris1234 · Oct 30, 2025

Motherboard has no PS/2 ports
Only thing that works is to use a winRE that is on the local system

Stigg · Oct 30, 2025

chris1234 said:
Motherboard has no PS/2 ports
Only thing that works is to use a winRE that is on the local system

Have you been into the BIOS to look at your boot order?

chris1234 · Oct 30, 2025

Seatool long generic test passed
Have not checked boot order yet

Stigg · Oct 30, 2025

chris1234 said:
Have not checked boot order yet

When I have an inaccessible boot device error, going into the BIOS and checking the boot order settings is the first thing I check.

chris1234 · Oct 30, 2025

There appears to be two, I've tried both

Can I restore my primary drive backup image to a USB drive and boot from it?

BTW thanks to everyone so far for your efforts even though I still haven't managed to fix my PC

chris1234 · Oct 30, 2025

So the iDrive mirror restore image works, its all online and I can choose individual drives to restore such as just the c drive, to any backup version I have, with the latest being last Monday.
I ordered a new wifi dongle that'll arrive tomorrow cause the one I currently have it old and seems a bit flaky.
If it cant be fixed by then that's what I'll be trying.

BTW thanx for everyone's effort so far

zbook · Oct 30, 2025

In another thread problems were reported that were not seen in this thread.

Are these different or the same computer?

Windows 11 Boot with Inaccessible boot device blue screen error

I ran the command as suggested and it completes 60.2% then returns with: Error: 3017 The requested operation failed. A system reboot is required to roll back changes made. The DISM log file can be found ..... Ran sfc /scannow it completes 20% and returns the following: Windows Resource...

www.elevenforum.com

Did this computer have both an update and scannow problem?

jimbo45 · Oct 30, 2025

chris1234 said:
I've going through some threads on this forum trying to solve an inaccessible boot device issue.
None of the suggestions seem to work and the common fix is a Repair install.
Trouble is when I tried this all I get two options, either install and wipe everything or run winRE
If I can boot into a recovery system and see that everything appears to exist, I'd assume the problem some minor corrupt but critical file.
But Im kinda stuck now,
As I cant boot into windows I'm guessing the build and trying an iso from uupdump and see what happens
Does she wipe everything wipe just the C drive?
If so can I just wipe c, install win11 and copy over everything on c with my iDrive backup?
What would happen if I just overwrite the windows directory with my backup?

Why not from the iso boot / usb device boot into "repair system" -> -- then choose command mode and simply try bcdboot.exe to fix / re-install the boot loader. Should work every time unless your whole OS is hosed up.

Cheers
jimbo

zbook · Oct 30, 2025

Please detach the non-Windows drive(s).
Boot using a Windows 11 MCT (iso) > run startup repair > post a share link with LogFiles\Srt\SrtTrail.txt results

Open command prompt > type or copy and paste
bcdedit | find "osdevice"
Dism /Image:C:\ /Get-Packages /format:list
(change C to the applicable partition drive letter)
Post a share link.

Post share links for
C:\windows\logs\CBS\CBS.log
C:\windows\logs\CBS\CbsPersist
C:\windows\minidump
C:\windows\memory.dmp

Celery · Oct 30, 2025

Windows normally boots from the EFI\Microsoft\Boot\bootmgfw.efi file, which corresponds to the “Windows Boot Manager” entry in the UEFI settings. If there’s no “Windows Boot Manager” entry, Windows will boot from EFI\Boot\bootx64.efi — the UEFI fallback boot mechanism.

If you want to update the firmware entry in NVRAM, you must run the bcdboot command without the /s and /f options.

BCDBoot Command-Line Options - Microsoft Learn

On UEFI PCs, BCDBoot can update the firmware entries in the device’s NVRAM: BCDBoot adds a firmware entry in the NVRAM to point to the Windows Boot Manager.

By default, BCDBoot creates a Windows Boot Manager entry in the NVRAM on the firmware to identify the boot files on the system partition. If the /s option is used, then this entry is not created.

If you specify the /f option, you must also specify the /s option to identify the volume letter of the system partition.

Boot from the Windows USB stick in UEFI mode (select the USB stick with a UEFI prefix), and run the following commands at the Windows Recovery Environment command prompt.

On a GPT disk, the bcdboot command below will not work if the USB stick is booted in BIOS mode. In that case, you’ll see the error:

Failure when attempting to copy boot files.

You’ll get the same error:

if you enter the wrong volume letter for the Windows partition, or
if the EFI system partition is missing or not formatted as FAT32.

diskpart
list volume (check the volume letter of your Windows partition)
exit

bcdboot x:\windows

Replace "x" with the volume letter of your Windows partition.

The bcdboot command automatically identifies the FAT32-formatted EFI system partition, copies the necessary boot files from the Windows partition to it, and creates a Boot Configuration Data (BCD) store on that partition. It also creates a Windows Boot Manager entry in the NVRAM.

edit: The /s option is used when you need to override bcdboot's default choice and target a non-default EFI system partition. When you boot your USB stick in UEFI mode, the firmware type /f uefi is not required.

chris1234 said:
There appears to be two, I've tried both

You can remove the extra "Windows Boot Manager" entry, if your Gigabyte BIOS version supports it, by selecting the unwanted entry and selecting Remove or Disable Boot Option.

cereberus · Oct 30, 2025

chris1234 said:
I've going through some threads on this forum trying to solve an inaccessible boot device issue.
None of the suggestions seem to work and the common fix is a Repair install.
Trouble is when I tried this all I get two options, either install and wipe everything or run winRE
If I can boot into a recovery system and see that everything appears to exist, I'd assume the problem some minor corrupt but critical file.
But Im kinda stuck now,
As I cant boot into windows I'm guessing the build and trying an iso from uupdump and see what happens
Does she wipe everything wipe just the C drive?
If so can I just wipe c, install win11 and copy over everything on c with my iDrive backup?
What would happen if I just overwrite the windows directory with my backup?

On another pc, install Macrium Reflect (trial is ok) and create a usb flash recovery drive.

Add the storage drivers for old pc.

Boot from it and select to fix windows boot problems.

chris1234 · Oct 30, 2025

bcdboot x:\windows
command worked but I still get the same error

chris1234 · Oct 30, 2025

zbook said:
Please detach the non-Windows drive(s).
Boot using a Windows 11 MCT (iso) > run startup repair > post a share link with LogFiles\Srt\SrtTrail.txt results

Open command prompt > type or copy and paste
bcdedit | find "osdevice"
Dism /Image:C:\ /Get-Packages /format:list
(change C to the applicable partition drive letter)
Post a share link.

Post share links for
C:\windows\logs\CBS\CBS.log
C:\windows\logs\CBS\CbsPersist
C:\windows\minidump
C:\windows\memory.dmp

link to files

I have also tried the macrium reflect fix boot issues too

Megahertz · Oct 30, 2025

The problem can be on the EFI partition and not on the Windows partition.
I gave you a possible solution on post #16 but you just ignored

Celery · Oct 30, 2025

Megahertz said:
The problem can be on the EFI partition and not on the Windows partition.
I gave you a possible solution on post #16 but you just ignored

The bcdboot command (bcdboot X:\Windows) has already been run, but it did not fix the problem.

bcdboot X:\Windows

The bcdboot command automatically identifies the FAT32-formatted EFI system partition, copies the necessary boot files from the Windows partition to it, and creates a Boot Configuration Data (BCD) store on that partition. It also creates a Windows Boot Manager entry in the NVRAM.

bcdboot X:\Windows /s W: /f UEFI

The bcdboot command copies the necessary boot files from the Windows partition to the specified EFI system partition, and creates a Boot Configuration Data (BCD) store on that partition. When the /s option is used, bcdboot does not create a Windows Boot Manager entry in the NVRAM.

Megahertz · Oct 30, 2025

aubergine said:
The bcdboot command (bcdboot X:\Windows) has already been run, but it did not fix the problem.

bcdboot X:\Windows

The bcdboot command automatically identifies the FAT32-formatted EFI system partition, copies the necessary boot files from the Windows partition to it, and creates a Boot Configuration Data (BCD) store on that partition. It also creates a Windows Boot Manager entry in the NVRAM.

bcdboot X:\Windows /s W: /f UEFI

The bcdboot command copies the necessary boot files from the Windows partition to the specified EFI system partition, and creates a Boot Configuration Data (BCD) store on that partition. When the /s option is used, bcdboot does not create a Windows Boot Manager entry in the NVRAM.

Did you cleaned the partition previously?
A EFI partition may have more than one boot manager. If you create a new but don't set BIOS to load the new it can be loading the old corrupted boot manager.

Celery · Oct 30, 2025

Megahertz said:
Did you cleaned the partition previously?
A EFI partition may have more than one boot manager. If you create a new but don't set BIOS to load the new it can be loading the old corrupted boot manager.

BCDBoot Command-Line Options - Microsoft Learn

On UEFI PCs, BCDBoot can update the firmware entries in the device’s NVRAM:

BCDBoot adds a firmware entry in the NVRAM to point to the Windows Boot Manager. By default, this entry is placed as the first item in the boot list. Use the /p option to preserve the existing UEFI boot order. Use /addlast to add it to the bottom of the boot order list.

But you could try formatting the EFI system partition before running the bcdboot command to see if that helps.

Boot from the Windows USB stick in UEFI mode (select the USB stick with a UEFI prefix), and run the following commands at the Windows Recovery Environment (WinRE) command prompt:

diskpart
list volume (check your EFI system partition number)
select volume # (replace # with your EFI system partition number)
format quick fs=fat32
list volume (check the volume letter of your Windows partition)
exit

bcdboot x:\windows

Replace "x" with the volume letter of your Windows partition.

The bcdboot command automatically identifies the FAT32-formatted EFI system partition, copies the necessary boot files from the Windows partition to it, and creates a Boot Configuration Data (BCD) store on that partition. It also creates a Windows Boot Manager entry in the NVRAM.

zbook · Oct 30, 2025

Some findings:

a) Root cause found: A recently serviced boot binary is corrupt.

b) Multiple BSODs Feb, Sept, Oct 2025:
Misbehaving driver seen in three mini dump files:
SoftPerfect RAMDisk Driver
spvve.sys Thu May 1 03:36:35 2025 (68133293)

c) Out of date BIOS: 2021

What were the status:
a) Restore points
b) Backup images

Continue with the earlier post steps.

Consider a custom install.

Possible trial and error steps:
a) Uninstall RAM disk driver
b) Upgrade the BIOS
c) Windows Updates: Revert pending actions
d) Test RAM unless replaced in 2025

https://www.gigabyte.com/Motherboard/X470-AORUS-ULTRA-GAMING-rev-10/support#dl

Code:

Wed Oct  8 19:00:52.324 2025 (UTC - 5:00)
Bugcheck code 1000007E

Code:

Wed Sep 10 09:35:41.340 2025 (UTC - 5:00)
Bugcheck code 0000001E
SoftPerfect RAMDisk Driver
spvve.sys    Thu May  1 03:36:35 2025 (68133293)

Code:

Mon Sep  8 18:38:48.526 2025 (UTC - 5:00)
Bugcheck code 0000004E

Code:

Tue Sep  9 07:31:13.986 2025 (UTC - 5:00)
Bugcheck code 0000001E
SoftPerfect RAMDisk Driver
spvve.sys    Thu May  1 03:36:35 2025 (68133293)

Code:

Thu Aug 28 01:21:56.106 2025 (UTC - 5:00)
Bugcheck code 1000007E
AMD AHCI Virtual Storage driver
envirtahci.sys Thu Sep 19 20:29:18 2019 (5D842B6E)
SoftPerfect RAMDisk Driver
spvve.sys    Thu May  1 03:36:35 2025 (68133293)

Code:

Mon Feb 24 18:14:51.460 2025 (UTC - 5:00)
Bugcheck code 0000012B

Code:

Sat Feb  1 22:16:12.376 2025 (UTC - 5:00)
Bugcheck code 00000154

Code:

Gigabyte Technology Co., Ltd.
X470 AORUS ULTRA GAMING
BIOS Version                  F62d
BIOS Release Date             10/13/2021

Code:

Package Identity : Package_for_RollupFix~31bf3856ad364e35~amd64~~26100.6584.1.20
State : Uninstall Pending
Release Type : Security Update
Install Time : 10/19/2025 11:57 AM

Package Identity : Package_for_RollupFix~31bf3856ad364e35~amd64~~26100.6899.1.25
State : Install Pending
Release Type : Security Update
Install Time : 10/28/2025 4:52 PM


Package Identity : OpenSSH-Client-Package~31bf3856ad364e35~amd64~~10.0.26100.6584
State : Uninstall Pending
Release Type : OnDemand Pack
Install Time : 10/19/2025 11:57 AM

Package Identity : OpenSSH-Client-Package~31bf3856ad364e35~amd64~~10.0.26100.6899
State : Install Pending
Release Type : OnDemand Pack
Install Time : 10/28/2025 4:52 PM


Package Identity : Microsoft-Windows-Xps-Xps-Viewer-Opt-Package~31bf3856ad364e35~amd64~~10.0.26100.6584
State : Uninstall Pending
Release Type : OnDemand Pack
Install Time : 10/19/2025 11:57 AM

Package Identity : Microsoft-Windows-Xps-Xps-Viewer-Opt-Package~31bf3856ad364e35~amd64~~10.0.26100.6899
State : Install Pending
Release Type : OnDemand Pack
Install Time : 10/28/2025 4:52 PM


Package Identity : Microsoft-Windows-WMIC-FoD-Package~31bf3856ad364e35~wow64~~10.0.26100.6584
State : Uninstall Pending
Release Type : OnDemand Pack
Install Time : 10/19/2025 11:57 AM

Package Identity : Microsoft-Windows-WMIC-FoD-Package~31bf3856ad364e35~wow64~~10.0.26100.6899
State : Install Pending
Release Type : OnDemand Pack
Install Time : 10/28/2025 4:52 PM


Package Identity : Microsoft-Windows-WMIC-FoD-Package~31bf3856ad364e35~amd64~~10.0.26100.6584
State : Uninstall Pending
Release Type : OnDemand Pack
Install Time : 10/19/2025 11:57 AM

Package Identity : Microsoft-Windows-WMIC-FoD-Package~31bf3856ad364e35~amd64~~10.0.26100.6899
State : Install Pending
Release Type : OnDemand Pack
Install Time : 10/28/2025 4:52 PM


Package Identity : Microsoft-Windows-WMIC-FoD-Package~31bf3856ad364e35~amd64~en-US~10.0.26100.6584
State : Uninstall Pending
Release Type : OnDemand Pack
Install Time : 10/19/2025 11:57 AM

Package Identity : Microsoft-Windows-WMIC-FoD-Package~31bf3856ad364e35~amd64~en-US~10.0.26100.6899
State : Install Pending
Release Type : OnDemand Pack
Install Time : 10/28/2025 4:52 PM


Package Identity : Microsoft-Windows-WMIC-FoD-Package~31bf3856ad364e35~amd64~en-GB~10.0.26100.6584
State : Uninstall Pending
Release Type : OnDemand Pack
Install Time : 10/19/2025 11:57 AM

Package Identity : Microsoft-Windows-WMIC-FoD-Package~31bf3856ad364e35~amd64~en-GB~10.0.26100.6899
State : Install Pending
Release Type : OnDemand Pack
Install Time : 10/28/2025 4:52 PM

Solved How to do a Repair install with inaccessible boot device issue

Active member

My Computer

Active member

Attachments

My Computers

Active member

My Computers

Well-known member

My Computers

Active member

Attachments

My Computers

Well-known member

My Computers

Active member

Attachments

My Computers

Active member

My Computers

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computers

Well-known member

My Computer

Active member

My Computers

Active member

My Computers

Wish to be flying

My Computers

Well-known member

My Computers

Wish to be flying

My Computers

Well-known member

My Computers

Well-known member

My Computer

Similar threads