Update bootloader in Win10 Iot Ent LTSC (21H2) applied images?
The product I work on uses Windows 10 IoT Enterprise LTSC (21H2). I am trying to update the bootloader in the extracted and applied images to the version signed in 2023, to work around the issue with the default bootloader signatures expiring in 2026 (see KB5012170). KB5012170 updates the bootloader on an installed system. I can apply this hotfix to an installed device, and the bootloader on the hidden partition indeed gets updated. However, if I sysprep and extract the image from this machine, and apply it to a new machine, after using bcdboot to set the boot image, the new machine ends up with the old expiring bootloader installed. It seems KB5012170 only updates the "live" version of the bootloader on the hidden partition. It does not update the bootloader that ends up in the extracted image? Updating to Windows 10 IoT 22H2 or Windows 11 IoT is not an option for us for now. I do not want to have to require users to always install KB5012170 every time they install our product moving forward. I would like newly created images of our product to contain the updated bootloader by default. But I cannot find a way to do this. KB5012170 seems to be the only way to get the updated bootloader for our edition of Windows. Is there another way to get the updated bootloader I am missing? Is there a tool or trick that I am missing that would allow us to update the bootloader in the extracted, applied image without requiring a subsequent install of KB5012170?Integrate Dynamic Disk Booting into windows #DynamicDisk #BootLoader #DevelopmentIdeas
**Subject:** Proposal to Enable Windows Boot Support for Dynamic Disks **Dear Microsoft Windows Engineering Team,** I am writing to respectfully propose the implementation of a long-requested feature: enabling Windows to install and boot from dynamic disks. As a dedicated user and system enthusiast, I find the current limitation both technically unnecessary and strategically misaligned with the evolving needs of advanced users. Outlined below are ten compelling reasons why enabling boot support for dynamic disks would be a valuable enhancement to the Windows platform: --- ### ✅ 1. Technically Straightforward to Implement - Integrating the Logical Disk Manager (`libdm`) into the bootloader would require approximately 200 KB of additional code, plus minimal integration logic. - The Windows bootloader already supports modular driver loading; incorporating LDM parsing would be a lightweight extension rather than a fundamental architectural change. - Windows Setup could similarly be enhanced with LDM support at negligible cost, given the existing size and modularity of setup components. --- ### 🔐 2. Proven Compatibility with Security Features - BitLocker encryption operates reliably on dynamic disks, demonstrating their stability and suitability for secure environments — including system volumes. --- ### 🧠 3. Advanced Storage Capabilities - Dynamic disks support spanned, striped, and mirrored volumes, making them ideal for: - High-performance workstations - Redundant storage configurations - Power users and IT professionals - Enabling boot from these configurations would unlock powerful new use cases. --- ### 🧱 4. Continued Presence in Windows 11 - Dynamic disks remain a supported feature in Windows 11. If they were truly obsolete, they would have been deprecated. - Maintaining support without enabling boot functionality represents an artificial and unnecessary limitation. --- ### 💾 5. Basic Disks Are Older and More Constrained - Basic disks rely on MBR and GPT partitioning schemes, which date back to the 1980s and 1990s. - Dynamic disks are a more modern and flexible alternative. Allowing boot from basic disks while disallowing it for dynamic disks is inconsistent. --- ### ☁️ 6. Alignment with Modern Storage Strategies - Dynamic disks can be formatted with ReFS, encrypted with BitLocker, and integrated into cloud-based backup workflows. - They are fully compatible with Microsoft’s broader vision for resilient, scalable, and cloud-integrated storage. --- ### 🧪 7. Improved Recovery from Accidental Conversion - Currently, if a system volume is inadvertently converted to dynamic, users are locked out of installation and recovery. - Boot support would make dynamic disks more forgiving and accessible, reducing data loss and support incidents. --- ### 💡 8. Empowerment for Advanced Users - Developers, IT professionals, and power users seek greater control over their storage configurations. - Supporting dynamic disk booting would reinforce Windows’ reputation for flexibility and technical depth. --- ### 💰 9. High Impact, Low Cost - The engineering effort required is modest relative to the potential benefits. - Microsoft already supports more complex features (e.g., ReFS, Storage Spaces, Secure Boot); this enhancement would be a logical and cost-effective addition. --- ### 🗣️ 10. Clear Community Demand - The request to boot from dynamic disks has persisted for years among technical users. - Implementing this feature would demonstrate Microsoft’s responsiveness to its most engaged and knowledgeable user base. --- ### 🛠️ Proposed Enhancements to Windows Setup To support this functionality, I respectfully suggest the following updates to the Windows Setup and boot process: 1. Integrate LDM support into Windows PE (`libdm`, `dmio.sys`, `dmboot.sys`, `dmload.sys`) 2. Update disk enumeration logic to recognize dynamic volumes as valid installation targets 3. Enable formatting with NTFS or ReFS and support BitLocker encryption 4. Modify BCD generation to accommodate dynamic boot volumes 5. Extend WinRE and recovery tools to support dynamic disk environments 6. Validate compatibility across BIOS/MBR and UEFI/GPT configurations --- I sincerely hope this proposal is given due consideration. Enabling boot support for dynamic disks would be a meaningful improvement for advanced users and professionals alike, and it aligns with Microsoft’s legacy of empowering users through innovation and flexibility. Thank you for your time and for your continued commitment to advancing the Windows platform. **Respectfully,** **Adheesh**
