I've got a tricky situation happening with a group of computers we upgraded from Ryzen 2400G to Ryzen 5 5400s, which are compatible with Windows 11. A few weeks ago, four out of the five machines started throwing a 0xc0000034 error. I attempted various fixes including MBR and BCD repairs, but nothing worked. When I booted using a Windows 11 ISO and attempted an auto repair, it would initially boot into Windows but then would always hit that same reboot error. I also tried running SFC and DISM; they allowed it to boot once but then the error returned on the next restart. I had success with four machines by restoring their original images and updating drivers, but I'm stumped on the fifth one since it was imaged over a year ago. Any advice from you tech wizards?
3 Answers
It sounds like there might be an issue with the way you cloned the drives. Cloning multiple machines on the same network can sometimes create conflicts, but if you've already tested with the fifth machine being isolated, you might need to try a different approach altogether. Maybe booting it up without the internet could help?
You might want to be careful when making changes to your BIOS or disk configuration since it can lead to data loss. Always ensure you have your data backed up before you start messing with any settings. If you haven't already, check out the FAQ threads for some general advice.
Consider booting using a WinPE environment where you can access certain utilities for rebuilding the EFI partition and addressing BCD issues. Tools like Hasleo's EasyUEFI could help, but you might need to completely delete the existing EFI partition first using diskpart for this to work successfully.
I've tried Hasleo’s EasyUEFI, but it doesn’t recognize any existing EFI partition. The rebuild option remains greyed out. Using BCDEDIT to tackle the BCD errors has also led to messages saying that C:boot doesn’t exist, and I got access denied errors while trying to execute bootrec commands. It worked once but failed again on reboot.
I’m not sure how that would help, as my main focus is fixing the boot error, not cloning. But I did try booting without the internet, and the error still occurred.