Windows 11 23H2 - No matching Appx list file found for build Unknown Version

[seantdavidson]

Expected Behavior

When you select the Enable app removal button it launches a window to select the apps you want to remove.

Current Behavior

When I click the select button I get an error that says WARNING: No matching Appx list file found for build Unknown Version

Steps to Reproduce (for bugs)

1. Imported ISO from Volume License site, shows as Edition: Windows 11 Pro Arch: x64 Build: 10.0.22621.3155 Patch Level: 3155 Languages: en-US Index: 5 Version: Unknown Version
2. Clicked on App Removal Tab
3. Checked box for Enable App Removal
4. Click Select button and get error message.

Context

Brand new version of WimWitch installed on a Fresh Windows 11 install.

Your Environment

• Module version used: 4.0.1 version of the module installed
• Operating System and PowerShell version: Running Windows 11 23H2 Volume License with PowerShell version 5.1.22621.2506

[seantdavidson]

I spun up a Windows 10 VM and I get the same error when using the recently download ISO from the Volume License Center.

[seantdavidson]

[NytSong]

Seeing that this is still Open it's still being worked on but figured I'd just add my note that I'm in the same boat.

[JasonCioffi]

I am also having the same issue for Build 3155 of Windows 11. The version reported on the 'Source WIM' tab is coming back with 'Unknown Version', which is causing App Removal to fail because it won't resolve to one of the available txt files in "C:\Program Files\WindowsPowerShell\Modules\WimWitchFK\4.0.1\Private\Assets". I'm also seeing image creation errors after I hit 'Make it so!'.

I was able to modify WWFunctions.ps1 to get it to report version 23H2, but I'm encountering the following error when I'm building my image:

03/27/2024 16:45:51 Warning - ISO Binaries are not present for Windows 11 23H2 03/27/2024 16:45:51 Warning - Import ISO Binaries from an ISO or disable ISO/Upgrade Package creation 03/27/2024 16:45:51 Error - Discarding WIM and not making it so

[seantdavidson]

@JasonCioffi thanks I will test that on Friday when I go back to the office.

[seantdavidson]

@JasonCioffi this worked for me I was able to get a new install.wim setup. Hopefully it will be fixed in newer version but good for now.

[dan-hughes]

@JasonCioffi , @seantdavidson I have PR #29 to fix this, just waiting for it to be merged.

[JasonCioffi]

@dan-hughes , I applied your changes from PR #29 into my copy of WWFunctions.ps1.

The Source Wim tab is reporting the ISO I downloaded today with a description of "Windows 11, version 23H2 (updated Mar 2024) x64 English" as 22H2 (v10.0.22621.3296). Is this correct?

In addition, my iso and DotNet imports are applying '22H2' to the file path. This is the same behavior I was seeing with v10.0.2261.3296.

[dan-hughes]

@JasonCioffi, build 22621 is 22H2 according to this.

[j-gustin]

Any ideas on when a new version will be coming out? I am also having the same issue with the March 2024 VLSC Windows 11 ISO reporting as "Unknown Version" in WIM Witch 4.01. This then prevents the App Removal process from working as others above have reported.

[henrybelk]

Having the same issue on v4.0.1 and March 2024 Win 11 23H2 Enterprise from VLSC.

[alaurie]

There's an on going issue with labelling the release in the UI based on the build number from the WIM. Initially caused by the Windows 10 and 11 having a build that started with the same build number causing issue. So I changed it to hard coded build numbers in 4.x which Server is not in. I'm looking into either just adding all the build numbers from wikipedia into the module. Or setting up a Github action to scrape wikipedia weekly to generate a JSON file of all build numbers for Win 10, 11 and Server and then calling that in the module. Not sure which way to go as of yet.

[CheezWizTN]

This is 100% a Microsoft caused issue, right? The Wim I extracted from the 23H2 media identifies as: However, installed it shows:

To get around this, I just spun up a fresh copy of WimWitchFK and created the folders imports\iso\Windows 11\Unknown Version and \imports\DotNet\Windows 11\Unknown Version and copied the extracted contents to those locations.

It seems this would be a rough problem to fix programmatically when Microsoft cannot ensure its own media self-identifies properly.

[dan-hughes]

Does anyone know the revision numbers on the 22621 build where the changeover happens? Or are MS still pumping out WIM's with incorrect versions?

E.g. does a 22621.3000 = 23H2 and 22H2 = 22621.2000?

[CheezWizTN]

This is directly from the Install.Wim from the 23H2 ISO I downloaded yesterday:

Let me grab the latest 22H2 ISO and see how it identifies.

[CheezWizTN]

This is from the latest 22H2 ISO: Other than the file count, you would assume them to be the same.

[dan-hughes]

Hmm, all I can think of right now is ignoring 22H2 and defaulting the 22621 build to 23H2 so the rest of it will work until MS fix the WIM's.

[alaurie]

I'm thinking of just adding a manual drop down to select the Feature Update version (e.g. 21H2, 22H2, 23H2 etc) at least in the short term while I figure out a way to reliably match the WIM build numbers.

[alaurie]

I have a new download of Win 11 23H2 with April 2024 updates and it shows as 22H2 Build.

[dan-hughes]

I'm assuming if you install, the OS will show 23H2?

Taking your idea, if the W11 22H2/23H2 case hits then use your dropdown idea otherwise fill in automatically everything is correct?

[CheezWizTN]

@alaurie The menu idea sounds like the best option. I doubt M$ will ever fix this.

[leonastas]

@CheezWizTN @alaurie I had a ticket with Microsoft about this issue, it is by design that the 23H2 ISO WIM shows the 22H2 build number. They said it is because it shares a codebase. They also stated this is the same behavior as seen in the 21H2 and 22H2 ISOs for Windows 10. So this is likely something that won't be auto-detectable going forward and will need the menu as @alaurie mentioned creating.

[henrybelk]

Good afternoon. Any update on getting this to work with current feature release?

[Volidon]

Any update on this issue?