Windows 11 23H2 (February 2024 Update) not finding Appx List

[The1andONLYTLC]

I just downloaded the Windows 11 23H2 February Update. Everything works fine (so far) until I get to the point to remove apps.

Expected Behavior

When you Enable App Removal and hit the select button, it's supposed to populate a list of apps to select to remove.

Current Behavior

When I enable App removal and hit select I see the following in the PowerShell window:
02/29/2024 13:58:13 Information - Looking for Appx list file D:\WimWitchFK\Private\Assets\appxWin11_Unknown Version.txt
WARNING: No matching Appx list file found for build Unknown Version.

I noticed on the Source WIM tab, the version is "Unknown Version" instead of 23H2.

Now if I make a copy of the "appxWin11_23H2" text file located in the \Private\Assets folder and name it "appxWin11_Unknown Version", it will then populate the list for me. To me this is only a workaround, so I wanted to bring it to your attention with the latest ISO from the Microsoft 365 Admin Center.

Your Environment

• Module version used: 4.01
• Operating System and PowerShell version: Windows 11 23H2 and PS version 5.1

[bast92]

Hello, thank you for this version of wimwith.
I have the same problem with the 23H2 French version, for wimwithcFK it is an unknown version that prevents me from customizing it, idem for the international English version recognized in 22H2, is it possible to manually modify the version field to unblock the situation ?
Thanks

[silvanetgmcs]

I am having a similar issue. I looked at the Source WIM tab and it shows the version as "Unknown Version".

I think in previous versions of Wimwitch, when I imported, it asked me for the Edition (which this version does), but it also asked for the version. For me, the issue is that it does not inject the updates. It says, "Warning. C:...\Unknown Version..." does not exist. There are not updates of this class to apply."

[bondurantdt]

That build number does not match any of the version checking functions in WWFunctions.ps1. Adding checks to look for that build version should resolve the issue.