Forum Discussion
Update bootloader in Win10 Iot Ent LTSC (21H2) applied images?
Hi, I think the key detail here is that the boot files you are seeing are coming from the EFI/System partition and from what `bcdboot` lays down, not just from the captured Windows partition.
If the image capture only contains the OS volume, it can easily miss the updated boot files that KB5012170 placed on the live system partition. Then when you apply the image and run `bcdboot`, Windows may rebuild the boot files from the older source files that are still present in the image.
I would check whether your capture process includes all required partitions, especially the EFI System Partition. If you are intentionally deploying only the Windows partition, the safer supported route may be to include KB5012170 as a required post-apply step before the device is considered ready. Manually copying bootloader files can get risky with Secure Boot, servicing, and supportability, so I would avoid making that the production process unless Microsoft/OEM support confirms the exact offline-servicing method for Windows 10 IoT Enterprise LTSC.
Earlier in our development we had problems copying the EFI system partition. It may be worth another try as a long shot.
The "emergency fallback backup plan" we have is exactly as you suggest: include installation of the KB as a post-install step. I was hoping to avoid that b/c it extends our installation time by ~10 mins.
Thank you Jamony!