Windows 10: Boot configuration completely borked

When I upgraded to Windows 11 it set up my old Win10 install on a separate drive as a boot option in the boot loader. I decided to finally get rid of that so I used Macrorit Partition Expert to merge the partitions on that drive, thinking that it would also handle any boot configuration issues GPT, MBR, BCD. Once the volumes were merged everything seemed fine so I reformatted the drive with Macrorit. When it finished, it errored with "3810 err_is_volume_mounted" and on reboot I was stuck in a BIOS boot loop and could not get to Windows.So I created a recovery USB drive with Macrium Refl

:)

 

is there any demand for a system configurator?

Processor(V) <--drop down arrow
-AMD(V)
--Socket(V)
---AM2(V)
----List of cpu's
---939(V)
----List of CPU's
-Intel(V)
--Socket(V)
---775(V)
----List of cpu's
---771(V)
----List of CPU's


etc etc.

 

Windows Updated(16299.309).KB4088776 Restart is required to complete.

Hi dalchina. Good news, I followed your suggestion and reinstalled the update and now it appears as "installed correctly" *Biggrin Maybe it was not necessary to run the Windows Update Troubleshooter or maybe if necessary. But using it I do not think it could have worsened something. The installation was very fast, unlike the first time it showed step 1 and step 2 completed.

Thanks for the suggestions and for the time to respond Best regards.


And thanks for the tip of that program, I'll have it on my list.

 

Recovery image not working - Windows could not update the boot configuration

Hi Paulie,

This issue might occur due to the damaged/corrupted boot records. We suggest that you recreate the boot configuration manually. Follow the steps below:

• Boot into System Recovery Options, and select the Command prompt entry (It will open the
  Command Prompt at boot).
• Select your admin account, and enter your account password to continue.
• Type the command chkdsk /r.
• After the check disk is completed, you may try booting the computer and check if that resolves the issue. If the issue still persists; then, try running the
  SFC scan using SFC /SCANNOW command to rebuild/recover the corrupted system files on the computer.

We would appreciate it if you could get back to us and provide us your feedback.