Windows could not update the computer's boot configuration

I thought I would share my experience with this problem.

I've been struggling with the "Windows could not update the computer's boot configuration" issue all day. Somehow, a couple of days ago, I created a successful installation USB, but that was while I was experimenting and learning NTLite. I decided yesterday to start from scratch, using what I've learned, and aim toward creating the ISO that I want. This is for Windows 10 Pro 22H2.

After downloading the updates (I thought) I wanted, I processed the image. One of the updates (KB5040427 - Cumulative) would not process, so I accepted the error and just assumed it would be caught by Windows Update and installed later (it was, BTW).

All day I have been changing settings in the BIOS (Secure boot, legacy, etc), changing options in Rufus, re-creating the ISO - all to no avail. Each time I recreated the ISO, I kept getting the same error about the update. Wondering if that had anything to do with it, I started investigating and also noticed that one of the updates (KB4052623 - Microsoft Defender Antivirus update (Platform)) actually had "amd64" within the filename. The machine I am creating the ISOs on is indeed an AMD, but my target machines are Intel.

Hmmm, does NTLite look at the host machine to determine what updates may or may not be needed? Is this the issue, or could it be the other failed update. I decided to create another fresh ISO, this time with NO updates loaded. I reset the BIOS on the target PC to default (secure boot on, uefi boot). This time, it worked flawlessly.

I've got about 50 machines to set up with this ISO, and planned on checking for updates anyway, so I'll just let Windows decide which ones it needs.

Russ
 
"amd64" is a common PC term referring to any 64-bit CPU based on the AMD 64-bit ISA (instruction set).

When Intel & HP proposed their IA-64 architecture, it wasn't popular because it didn't keep backwards compatibility with x86. AMD used this opportunity to propose a 64-bit version of the IA-32, with a few extensions added. Microsoft and the PC industry eventually supported AMD's model. Intel grudgingly adopted the AMD64 ISA, and later added some of their own CPU extensions.

There's still old versions of Windows built for IA-64, but they're rarely seen today.

NTLite only cares whether the loaded image is a 32-bit or 64-bit "Intel", or ARM. Components or package names will always refer to the 64-bit version as amd64 or arm64, depending on the architecture.

Boot configuration issues during install are related to:
- missing driver support for storage or USB controllers​
- conflicts due to BCDedit finding another bootable system drive, and picking the wrong one to update​
 
Thanks for the insight, garlin .

Boot configuration issues during install are related to:
- missing driver support for storage or USB controllers
- conflicts due to BCDedit finding another bootable system drive, and picking the wrong one to update
Click to expand...

I'm not sure if any of those issues were a factor, but what I do know is that in my final test , the only thing I changed was to omit any Windows updates from the ISO build and that made a difference between a "Windows could not update the computer's boot configuration" error and a working installation.

Russ
 
You must log in or register to reply here.
Back
Top