Fionarms

New Member
Joined
May 17, 2022
Messages
1
I did a system restore to another date and my computer now won’t work properly.

It only allows me to limited options like start-up repair which doesn’t work.

I got the blue screen with a qr code which led me here but I didn’t have any luck - Troubleshoot blue screen errors

I also got this error message - C:\Windows\System32\Logfiles\Srt\SrtTrail.txt

I found another website with some advice and I opened command prompt. I successfully did rebuildbcd and fixmbr. I tried fixboot but got access denied.

I don’t have any windows disks to this pc.

I also tried to restore to factory settings but this didn’t work also.

Any ideas please?
Thanks in advance
 


Solution
If most of the Advanced Options in the Recovery Environment are missing, this is caused by faulty Boot Configuration Data. If the blue screen lead you to use those commands, it is probably SYSTEM_THREAD_EXCEPTION_NOT_HANDLED caused by CPU core and memory limits in the Boot Configuration Data.

If it's a UEFI system, Bootrec /FixMBR and Bootrec /FixBoot are irrelevant as the UEFI firmware directly reads the partition table and filesystem to run Windows Boot Manager without using bootsectors. Even if it's legacy BIOS, the bootsectors are static unless corrupt or overwritten by something like a Linux installer. It is the BCD.

Bootrec /RebuildBCD only locates Windows installations that are not already in the BCD, and adds...
If most of the Advanced Options in the Recovery Environment are missing, this is caused by faulty Boot Configuration Data. If the blue screen lead you to use those commands, it is probably SYSTEM_THREAD_EXCEPTION_NOT_HANDLED caused by CPU core and memory limits in the Boot Configuration Data.

If it's a UEFI system, Bootrec /FixMBR and Bootrec /FixBoot are irrelevant as the UEFI firmware directly reads the partition table and filesystem to run Windows Boot Manager without using bootsectors. Even if it's legacy BIOS, the bootsectors are static unless corrupt or overwritten by something like a Linux installer. It is the BCD.

Bootrec /RebuildBCD only locates Windows installations that are not already in the BCD, and adds them. No installations already in the BCD are changed by Bootrec /RebuildBCD unless the existing BCD file is renamed (which can only be done in the Recovery Environment, which may be missing Command Prompt because the BCD), or unless the existing Windows entry is deleted from the BCD with bcdedit /delete {default} which can be inside Windows, immediately before using Bootrec /RebuildBCD to add it back. The BCD file should be backed up before doing that, in case Bootrec /RebuildBCD fails somehow. Windows should not be restarted between bcdedit /delete {current} and Bootrec /RebuildBCD success.

So, in Command Prompt from inside Windows (like Safe Mode) or Recovery Environment, use
bcdedit /export C:\Temp\BCDold && bcdedit /delete {default}
Bootrec /RebuildBCD || bcdedit /import C:\Temp\BCDold
Input A when asked
This way, the existing entry is only deleted if the BCD is successfully backed up.
The backup is automatically restored if a new entry isn't successfully added back.
 


Solution
Back
Top