Share via

Windows ADK 26H1 Build 28000

avi kroparo 0 Reputation points
2026-01-06T09:35:37.6433333+00:00

this build has problem injecting drivers both to boot.wim and install.wim.

Windows for business | Windows Client for IT Pros | Devices and deployment | Other
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Chen Tran 9,005 Reputation points Independent Advisor
    2026-01-07T10:59:18.0866667+00:00

    Hello Avi,

    Thank you for posting question on Microsoft Windows Forum.

    Well! Windows ADK for Windows 11 26H1 (Build 28000) which was, while technically including tools for x64, primarily optimized and released for Windows on ARM64. There are reports of that this specific ADK build has "poor driver handling," specifically failing when attempting to inject drivers via DISM into both boot.wim and install.wim.

    The possible explanation to this is probably of architecture mismatch. Build 28000 is the first ADK where several components are strictly architecture-specific. If you are running the tools on an x64 host to service x64 images, the DISM version included in this kit often returns errors or fails to recognize valid .inf files during the injection phase. Also, it might relate to WIM mounting registry issues. The ADK fails to properly track the driver store path within the mounted image, leading to a failure in the "Processing 1 of 1" stage of driver addition.

    The potential temporary workaround is to use the Drvload method. While DISM injection fails during the image prep phase, you can still load drivers manually once WinPE is booted. Then run drvload path_to_driver.inf .This is only a temporary fix for a single boot session and will not help with install.wim. Otherwise, revert to ADK 24H2 (Build 26100).

    Hope the above information is helpful! If it is. Free feel to hit "Accepted" for benefitting others in community having the same query too.

  2. Q&A Assist
    2026-01-06T09:35:47.24+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    The context does not provide specific information regarding issues with injecting drivers into boot.wim and install.wim for the Windows ADK 26H1 Build 28000. However, it does mention general limitations and methods for injecting drivers into WinPE and the operating system. If you are experiencing problems, it may be beneficial to ensure that you are using compatible driver versions and follow the recommended methods for driver injection, such as using DISM.exe or the $WinPEDriver$ folder method.

    If you encounter specific error messages or behavior, those details could help in diagnosing the issue further.

    References:

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.