Try making WinPE, getting error `Driver [WofAdk] supports maximum target build [10240], while this OS is build [26200]; skipping install`

Shimi 1 Reputation point

I'm using the latest version on the link below, and it always shows the same error in the title.

What do I do?

https://learn.microsoft.com/en-us/windows-hardware/get-started/adk-install?source=docs

0 comments No comments
Sign in to comment

3 answers

  1. Jason Nguyen Tran 20,115 Reputation points • Independent Advisor

    Hi Shimi,

    I’m following up to check whether the issue has been resolved. Feel free to reply if you need further information. If the information provided was helpful, please click "Accept Answer" to help others in the community. Thank you!

    1. Shimi 1 Reputation point

      No, it hasn't. I'm still stuck on the same problem.To make sure, I tried again just now. I ran Windows Update, installed the full ADK, and copy-pasted the commands from the instructions.

      Still the same error on copype amd64 C:\WinPE_amd64

    Sign in to comment
  2. Jason Nguyen Tran 20,115 Reputation points • Independent Advisor

    Hi Shimi,

    The message you’re seeing, indicates that the driver in question was compiled for much older Windows builds and isn’t compatible with the current ADK/OS version you’re targeting. The good news is that this isn’t a fatal error, it simply means that the outdated driver is being skipped. WinPE itself should still build correctly, but you won’t have that legacy driver included.

    To resolve this, make sure you’re using the Windows 11 ADK and WinPE add‑on that matches your OS build (for example, ADK for Windows 11, version 24H2 if your system is on build 26200). Installing both the ADK and the separate WinPE add‑on package is required; otherwise, you’ll run into missing or mismatched components.

    If you’ve already installed the latest ADK, I recommend uninstalling any older ADK versions and re‑installing only the current release from Microsoft’s site. Also, check that your build environment is pointing to the correct WinPE image folder (usually under C:\\Program Files (x86)\\Windows Kits\\10\\Assessment and Deployment Kit\\Windows Preinstallation Environment).

    In short, the error is just telling you that an old driver isn’t compatible, and the fix is to use the matching ADK + WinPE add‑on for your OS build and remove any legacy kits. Once that’s done, your WinPE build should complete without issues.

    I hope the response provided some helpful insight. If it addressed your issue, please consider marking it as Accept Answer so others facing the same problem can easily find the solution. If you need any further assistance, feel free to leave a comment.

    Jason.

    1. Shimi 1 Reputation point

      It's Windows 11 Education 10.0.26200 that runs on Hyper-V so I can just revert back to before I installed the ADK.
      What do I need to do?

    2. Jason Nguyen Tran 20,115 Reputation points • Independent Advisor

      Since you mentioned you can revert the VM back to before the ADK install, that’s a good safety net. What you’ll want to do is make sure you’re using the matching ADK and WinPE add‑on for Windows 11, version 24H2 (build 26200). The error you saw earlier is simply because the legacy WofAdk driver doesn’t support newer builds, so reverting and reinstalling with the correct kit will save you headaches.

      Here’s the recommended path:

      1. Revert your VM snapshot to the clean state before ADK was installed.
      2. Download and install the latest Windows ADK for Windows 11, version 24H2.
      3. Install the WinPE add‑on for the same version (this is a separate package).
      4. Confirm that no older ADK versions are present, mixing components causes compatibility errors.
      5. Build your WinPE image again, pointing to the correct WinPE folder under the new ADK installation.

      Once you’ve done this, the WofAdk driver warning should disappear, and your WinPE build will complete successfully.

      If you find this answer helpful, please consider clicking Accept Answer so others can benefit too. Thank you.

      Let me know if you need further information.

    3. Shimi 1 Reputation point

      That's exactly what I did!

      Unless there's a command line way to verify the installation (or even better - the download, like from pip or something like that).

    Sign in to comment

  3. AI answer

    The error indicates that the WofAdk.sys filter driver from the installed ADK/WinPE add-on only supports Windows builds up to 10240, while the current OS is build 26200. This happens when using an older DISM/WofAdk driver combination than the Windows build being targeted.

    To resolve this, use the DISM and WofAdk.sys driver from the matching, current Windows ADK/WinPE version for the Windows build being deployed, and ensure that this newer DISM is what runs inside WinPE:

    1. Install the latest Windows ADK and Windows PE add-on that correspond to the Windows 10/11 version being deployed. The WofAdk.sys filter driver required by Windows 10+ DISM is included in the Windows 10/11 ADK.
    2. On the technician PC, use the ADK tools to copy the current Deployment and Imaging Tools (including DISM and WofAdk.sys) to external media: 
       CopyDandI.cmd amd64 E:\ADKTools\amd64
    3. Boot the target PC into WinPE.
    4. In WinPE, install and configure the newer DISM’s required drivers (including WofAdk.sys) from that external location each time WinPE boots, for example: 
       W:\ADKTools\amd64\wimmountadksetupAmd64.exe /Install /q
    5. Run DISM from that updated toolset path (do not overwrite the DISM in the WinPE image): 
       W:\ADKTools\amd64\DISM.exe /?
      Confirm that the version shown matches the Windows 10/11 ADK version.
    6. Use this updated DISM to apply or service the Windows image. This combination (Windows 10/11 DISM + WofAdk.sys from the matching ADK) is required to correctly handle Compact OS and newer image formats and to avoid version/build mismatch errors like the one seen.

    If the host OS or WinPE environment is older than the Windows build being deployed, always rely on the DISM and drivers from the matching ADK version rather than the in-box DISM.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.
Sign in to answer

Your answer