search

jmclaren7 / windows-setup-helper

GUI for Windows Installer to access tools and select installer automations from WinPE
Other
55 stars 8 forks source link

ADK PE Addon packages cannot be installed to an existing boot.wim - The specified package is not applicable to this image #1

Open bezik46 opened 5 days ago

bezik46 commented 5 days ago

en-us_windows_11_consumer_editions_version_23h2_updated_april_2024_x64_dvd_d986680b.iso = 22631.3447 Matching ADK/PE Addon from https://learn.microsoft.com/en-us/windows-hardware/get-started/adk-install

One CANNOT add ADK PE Addon packages to an existing boot.wim

That can only be done to winpe.wim So batch script needs to be adjusted accordingly & that wipe.wim file to be copied instead of the original boot.wim from iso

But the above file replacement also requires FULL sources folder from original boot.wim (in the source en-us_windows_11_consumer_editions_version_23h2_updated_april_2024_x64_dvd_d986680b.iso to be copy/replace the one in winpe.wim from ADK - without this replacement all sort of errors during install would happen - seems that ADK 10.1.26100.1 (May 2024) does not "play" nicely with 22631.3447 even the readme states: supports Windows 11, version 24H2 and all earlier supported versions of Windows 10 and 11

If the winpe.wim is not used then batch will fail:

Adding packages to mounted image

Packages From: C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs

Deployment Image Servicing and Management tool
Version: 10.0.22621.2792

Image Version: 10.0.22621.3447

Processing 1 of 28 - Adding package WinPE-WMI-Package~31bf3856ad364e35~amd64~~10.0.26100.1
[==========================100.0%==========================]
Processing 2 of 28 - Adding package WinPE-WMI-Package~31bf3856ad364e35~amd64~en-US~10.0.26100.1
[==========================100.0%==========================]
Processing 3 of 28 - Adding package WinPE-NetFx-Package~31bf3856ad364e35~amd64~~10.0.26100.1
[==========================100.0%==========================]
Processing 4 of 28 - Adding package WinPE-NetFx-Package~31bf3856ad364e35~amd64~en-US~10.0.26100.1
[==========================100.0%==========================]
Processing 5 of 28 - Adding package WinPE-Scripting-Package~31bf3856ad364e35~amd64~~10.0.26100.1
[==========================100.0%==========================]
Processing 6 of 28 - Adding package WinPE-Scripting-Package~31bf3856ad364e35~amd64~en-US~10.0.26100.1
[==========================100.0%==========================]
Processing 7 of 28 - Adding package WinPE-PowerShell-Package~31bf3856ad364e35~amd64~~10.0.26100.1
[==========================100.0%==========================]
Processing 8 of 28 - Adding package WinPE-PowerShell-Package~31bf3856ad364e35~amd64~en-US~10.0.26100.1
[==========================100.0%==========================]
Processing 9 of 28 - Adding package WinPE-StorageWMI-Package~31bf3856ad364e35~amd64~~10.0.26100.1
[==========================100.0%==========================]
Processing 10 of 28 - Adding package WinPE-StorageWMI-Package~31bf3856ad364e35~amd64~en-US~10.0.26100.1
[==========================100.0%==========================]
Processing 11 of 28 - Adding package WinPE-SecureBootCmdlets-Package~31bf3856ad364e35~amd64~~10.0.26100.1
[==========================100.0%==========================]
Processing 12 of 28 - Adding package WinPE-SecureStartup-Package~31bf3856ad364e35~amd64~~10.0.26100.1
[==========================100.0%==========================]
Processing 13 of 28 - Adding package WinPE-SecureStartup-Package~31bf3856ad364e35~amd64~en-US~10.0.26100.1
[==========================100.0%==========================]
Processing 14 of 28 - Adding package WinPE-DismCmdlets-Package~31bf3856ad364e35~amd64~~10.0.26100.1
[==========================100.0%==========================]
Processing 15 of 28 - Adding package WinPE-DismCmdlets-Package~31bf3856ad364e35~amd64~en-US~10.0.26100.1
[==========================100.0%==========================]
Processing 16 of 28 - Adding package WinPE-EnhancedStorage-Package~31bf3856ad364e35~amd64~~10.0.26100.1
[==========================100.0%==========================]
Processing 17 of 28 - Adding package WinPE-EnhancedStorage-Package~31bf3856ad364e35~amd64~en-US~10.0.26100.1
[==========================100.0%==========================]
Processing 18 of 28 - Adding package WinPE-Dot3Svc-Package~31bf3856ad364e35~amd64~~10.0.26100.1
[==========================100.0%==========================]
Processing 19 of 28 - Adding package WinPE-Dot3Svc-Package~31bf3856ad364e35~amd64~en-US~10.0.26100.1
[==========================100.0%==========================]
Processing 20 of 28 - Adding package WinPE-FMAPI-Package~31bf3856ad364e35~amd64~~10.0.26100.1
[==========================100.0%==========================]
Processing 21 of 28 - Adding package Microsoft-Windows-WinPE-FontSupport-WinRE-Package~31bf3856ad364e35~amd64~~10.0.26100.1
[==========================100.0%==========================]
Processing 22 of 28 - Adding package WinPE-PlatformId-Package~31bf3856ad364e35~amd64~~10.0.26100.1
[==========================100.0%==========================]
Processing 23 of 28 - Adding package WinPE-WDS-Tools-Package~31bf3856ad364e35~amd64~~10.0.26100.1
[==========================100.0%==========================]
Processing 24 of 28 - Adding package WinPE-WDS-Tools-Package~31bf3856ad364e35~amd64~en-US~10.0.26100.1
[==========================100.0%==========================]
Processing 25 of 28 - Adding package WinPE-HTA-Package~31bf3856ad364e35~amd64~~10.0.26100.1
[==========================100.0%==========================]
Processing 26 of 28 - Adding package WinPE-HTA-Package~31bf3856ad364e35~amd64~en-US~10.0.26100.1
[==========================100.0%==========================]
Processing 27 of 28 - Adding package WinPE-WinReCfg-Package~31bf3856ad364e35~amd64~~10.0.26100.1
[==========================100.0%==========================]
Processing 28 of 28 - Adding package WinPE-WinReCfg-Package~31bf3856ad364e35~amd64~en-US~10.0.26100.1
[==========================100.0%==========================]

Error: 0x800f081e

The specified package is not applicable to this image.
The specified package is not applicable to this image.
The specified package is not applicable to this image.
The specified package is not applicable to this image.
The specified package is not applicable to this image.
The specified package is not applicable to this image.
The specified package is not applicable to this image.
The specified package is not applicable to this image.
The specified package is not applicable to this image.
The specified package is not applicable to this image.
The specified package is not applicable to this image.
The specified package is not applicable to this image.
The specified package is not applicable to this image.
The specified package is not applicable to this image.
The specified package is not applicable to this image.
The specified package is not applicable to this image.
The specified package is not applicable to this image.
The specified package is not applicable to this image.
The specified package is not applicable to this image.
The specified package is not applicable to this image.
The specified package is not applicable to this image.
The specified package is not applicable to this image.
The specified package is not applicable to this image.
The specified package is not applicable to this image.
The specified package is not applicable to this image.
The specified package is not applicable to this image.
The specified package is not applicable to this image.
The command completed with errors.
For more information, refer to the log file.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

and dism.log shows:

2024-09-21 13:52:32, Info                  CBS    Appl: detect Parent, Package: WinPE-WinReCfg-Package~31bf3856ad364e35~amd64~en-US~10.0.26100.1, Parent: WinPE-WinReCfg-Package~31bf3856ad364e35~amd64~~10.0.26100.1, Disposition = Detect, VersionComp: EQ, BuildComp: EQ, RevisionComp: GE, Exist: present
2024-09-21 13:52:32, Info                  CBS    Appl: detectParent: parent found: WinPE-WinReCfg-Package~31bf3856ad364e35~amd64~~10.0.26100.1, state: Absent
2024-09-21 13:52:32, Info                  CBS    Appl: Evaluating package applicability for package WinPE-WinReCfg-Package~31bf3856ad364e35~amd64~en-US~10.0.26100.1, applicable state: Absent
2024-09-21 13:52:32, Info                  DISM   DISM Package Manager: PID=2064 TID=13036  Error in operation: the package is not applicable. (CBS HRESULT=0x800f081e) - CCbsConUIHandler::Error
2024-09-21 13:52:32, Info                  CBS    Plan: Skipping package since its start state and target state are both absent for package: WinPE-WinReCfg-Package~31bf3856ad364e35~amd64~en-US~10.0.26100.1, current: Absent, pending: Default, start: Absent, applicable: Absent, targeted: Absent, limit: Installed
2024-09-21 13:52:32, Info                  CBS    No Edition family found
jmclaren7 commented 4 days ago

Packages can certainly be added to an existing boot.wim but the version of the ADK must be right and it seems like newer versions of the ADK that "support" older versions isn't sufficient. I'll need to do more testing but when I use ADK 22621 with the ISO downloaded by the Media Creation Tool which is also 22621, everything works. I'm not able to find any official sources for 22631 so I haven't been able to test that yet.

It does seem like using the winpe.wim from the ADK could be a safer bet though, not because it's required but because it sidesteps the entire version compatibility issue. I was avoiding this because I didn't want any more dependency on the ADK than what was necessary but I'm going to start testing this. I'll leave this issue open so I can update it with what I find and any changes I make.

Edit: Not sure what this is about but the latest Windows 11 23H2 ISO has a version of 22621 for both boot.wim AND the install images even though 22621 is supposed to be 22H2

bezik46 commented 4 days ago

https://www.windows11forums.com/threads/windows-11-mvs-isos-april-released-22631-3447.2287/

It also did NOT work with ADK 10.1.25398.1 (September 2023)

Did not test ADK for Windows 11, version 22H2