New
#31
Just one question. Is that stuff that is running on disk 0 (C:) the problem disk that gave you the boot failure and is running now?
I don't need reagentc any more.
The answer please! A good cooperation looks different
Edit:
cmd
mkdir D:\BCD_Backup
bcdedit /store \\?\GLOBALROOT\device\harddisk0\partition1\EFI\Microsoft\Boot\BCD /export D:\BCD_Backup\BCD1
and buy a new CMOS-Battery!
- - - Updated - - -
And no (!) further changes till the CMOS Battery is replaced.
After Replacement boot into BIOS and in
Settings > General >Date/Time correct the time
Last edited by Pentagon; 2 Weeks Ago at 12:51.
No, the OS on Disk 0 (C:) the one that fails to boot.
I currently running Windows PE OS installed on Disk 2.
I am really sorry about this, but I had 09:00 PM in my local time and was asked to leave the site.
cmd
mkdir D:\BCD_Backup
bcdedit /store \\?\GLOBALROOT\device\harddisk0\partition1\EFI\Microsoft\Boot\BCD /export D:\BCD_Backup\BCD1
The store export command is invalid.
Run "bcdedit /?" for command line assistance.
The parameter is incorrect.
OK, let me purchase the part and confirm here.
OK, that's correct. The /export command is valid only for the active system-bcd and not for a store-bcd.
Sorry for the confusion.
I see that you boot from (F:) but what happens if you doubleclick on the desktop icon "My PC"
or you open the explorer? Try to run a Program that you start from C:\Program Files
OK, final step now:
run cmd (admin)
sfc /scannow
Attention: Only when the above command finds problems, that couldn't be fixed, come back here. When problems have been fixed you continue.
Shutdown PC and remove USB disk 2+3
Boot into BIOS <F2>
Settings>General>Boot Sequence ==> Windows Boot Manager
>Boot List option> UEFI
OK and shut down
Boot into Boot Start <F12>
Select >Windows Boot Manager >OK
Cross you fingers and start the engine
What we did till now:
Back to UEFI
The Diskette Drive was the 1st Boot Device. Now its on the last position
In bootorder the {bootmgr} was on the last position. Now it’s on position 1 again
modified and deleted some wrong BCD-Entries.
What to do in future:
Your Disk 0 Partition 4 needs an attrib-treatment
Good Luck
sfc /scannow /offbootdir=c:\ /offwindir=c:\windows
X:\Windows\System32>sfc /scannow /offbootdir=c:\ /offwindir=c:\windows
Beginning system scan. This process will take some time.
Windows Resource Protection did not find any integrity violations.
I will proceed with the next steps...
- - - Updated - - -
Shutdown PC and remove USB disk 2+3
done
Boot into BIOS <F2>
Settings>General>Boot Sequence ==> Windows Boot Manager
done
>Boot List option> UEFI
done
OK and shut down
done
Boot into Boot Start <F12>
Select >Windows Boot Manager >OK
done
Got BSOD with the error code INACCESSIBLE BOOT DEVICE...
Have we missed something?
How to do this?
OK
go back to the (F:)-Boot Option (first change UEFI to BIOS) again and do that what is explained in #34
Everything looks like a typical Dual-Boot arrangement. You run Windows (C:) and boot successfully from (F:)
Machines that do not support NVMe boot often run Windows (C:) perfectly, but need the bootmanager on a SATA Disk.
But do that what is mentioned in #34 first. And I do not tell that again. When it is what I believe now, your RAID-Controller-Update changed UEFI bootsettings.
BIOS: \Windows\system32\winload.exe ==> is working
UEFI: \Windows\system32\winload.efi ==> not working
Instead of a USB-Disk you could try a SATA-Disk as well. But keep your (F:)-Disk safe.
Then the cmd command
diskpart
sel disk 0
sel par 1
assign letter=S
exit
allows you to explore the boot-partition using Explorer++ running in Admin-Mode
But your BCD is OK!
It should look like that.
when finished
run cmd
diskpart
sel disk 0
sel par 1
remove
exit
But your feedback has to be faster!
Last edited by Pentagon; 1 Week Ago at 12:32.