WMIC missing on Windows 11 24H2

[nuhi]

I'm only using packages from the CLIENT ISO, both ISO versions are downloaded from the same base URL (except with a different ISO filename).

My testing started with using DISM, outside of NTLite, to understand what the missing dependency was. I haven't retested with the latest 24H2 build, which might have later SSU fixes. Maybe later today if I have time.

Oh, this WMIC issue started on 24H2 as they disabled it via CU.
NTLite handles capabilities, unless there is some issue I don't know about, just copy FOD ISO to FOD cache.

 

[jlsupremo]

Oh, this WMIC issue started on 24H2 as they disabled it via CU.
NTLite handles capabilities, unless there is some issue I don't know about, just copy FOD ISO to FOD cache.

I downloaded the iso, copied the .cab files to C:\Program Files\NTLite\Cache\Updates\11.24H2.x64.FOD and C:\Program Files\NTLite\Cache\Updates\Common.FOD, but Ntlite gives the following error when I check the WMIC option in Features > On Demand >
WMIC - The operation requires missing files.

 

[nuhi]

I downloaded the iso, copied the .cab files to C:\Program Files\NTLite\Cache\Updates\11.24H2.x64.FOD and C:\Program Files\NTLite\Cache\Updates\Common.FOD, but Ntlite gives the following error when I check the WMIC option in Features > On Demand >
WMIC - The operation requires missing files.

Yes, same here for that feature. DISM log error listed few posts above here.
Will see these days if anything can be done or it's locked, maybe someone figures it out.

 

[Alex Corretor Do Brasil]

1. Download the 24H2 LP & FOD ISO using this script:
PowerShell GUI for Downloading Windows ADK, WinPE, LP & FOD ISO's - W10_11ADK_WinPE_LP_FOD.ps1

2. Load your 24H2 install image.

3. From Features on Demand, search for WMIC and enable the checkbox.
NTLite will ask you to copy the required FOD package files into "C:\Program Files\NTLite\Cache\Updates\11.24H2.x64.FOD".

View attachment 13060

4. Mount the FOD ISO in Explorer, copy the following CAB files from "LanguagesAndOptionalFeatures" to NTLite's 11.24H2.x64.FOD folder:

Microsoft-Windows-WMIC-FoD-Package~31bf3856ad364e35~amd64~en-US~.cab
Microsoft-Windows-WMIC-FoD-Package~31bf3856ad364e35~amd64~~.cab
Microsoft-Windows-WMIC-FoD-Package~31bf3856ad364e35~wow64~en-US~.cab
Microsoft-Windows-WMIC-FoD-Package~31bf3856ad364e35~wow64~~.cab

Replace en-US with your preferred language version.

View attachment 13062

5. Create a new subfolder inside the 11.24H2.x64.FOD folder:

mkdir C:\Program Files\NTLite\Cache\Updates\11.24H2.x64.FOD\metadata

6. Copy the the following CAB files from the ISO's "LanguagesAndOptionalFeatures\metadata" folder into NTLite's FOD\metadata folder:

DesktopTargetCompDBForISO_FOD_en-us.xml.cab
DesktopTargetCompDB_FOD_Neutral.xml.cab

Replace en-US with your preferred language version.

View attachment 13063

7. Unmount the FOD ISO.

8. Apply your changes to the image.

View attachment 13065

---

NTLite currently has no process for adding FOD metadata (which is now required to enable 24H2's WMIC and VBScript features), but you can manually create a new subfolder under the FOD cache folder.

DISM expects to find both the FOD CAB's, and the DesktopTargetCompDB reference packages under the source path's metadata subfolder.

I did this whole process on Windows 11 23H2.V2 and it worked for the problem I was having with the on-demand feature "TPM Diagnostics"

I believe it works for all on-demand resources that are giving this "missing file" error.

 

[nuhi]

For 23H2 there is no issue with NTLite as is, it's just 24H2 which has WMIC disabled by the cumulative update.

Tested 23H2 now just in case, and it worked without any errors:

- Enabling "TPM Diagnostics" prompted me to fill [UpdateCacheDir]\11.23H2.x64.FOD with the FOD ISO content.
- Did so, extracted 22621.1.220506-1250.ni_release_amd64fre_CLIENT_LOF_PACKAGES_OEM.iso
into it - no further steps necessary with the files.
- Enabled the feature - Applied, no issues.

If you have missing files during applying after the steps listed here, please let me know.
Thanks.

 

[Alex Corretor Do Brasil]

For 23H2 there is no issue with NTLite as is, it's just 24H2 which has WMIC disabled by the cumulative update.

Tested 23H2 now just in case, and it worked without any errors:

- Enabling "TPM Diagnostics" prompted me to fill [UpdateCacheDir]\11.23H2.x64.FOD with the FOD ISO content.
- Did so, extracted 22621.1.220506-1250.ni_release_amd64fre_CLIENT_LOF_PACKAGES_OEM.iso
into it - no further steps necessary with the files.
- Enabled the feature - Applied, no issues.

If you have missing files during applying after the steps listed here, please let me know.
Thanks.

For me it only worked using Garlin's "metadata" folder method.

Just placing the .cab files without the aforementioned folder above didn't work for me.

Just to point out, I used the .cab files from the FOD 23H2.

 

[nuhi]

For me it only worked using Garlin's "metadata" folder method.

Just placing the .cab files without the aforementioned folder above didn't work for me.

Just to point out, I used the .cab files from the FOD 23H2.

I haven't said add just CABs, I said extract the whole FOD ISO (with its subfolders as is) to the FOD cache dir.
Metadata is in there in the subfolders already, no need to tamper.

 

[garlin]

I haven't said add just CABs, I said extract the whole FOD ISO (with its subfolders as is) to the FOD cache dir.
Metadata is in there in the subfolders already, no need to tamper.

It's kinda inconvenient to copy the whole FOD ISO, unless you're using a large number of packages on a regular basis. The way I tested it (before using NTLite), was to figure the minimum number of files DISM needed to do the same task.

If you only needed WMIC, then only two metadata CAB's are required and DISM has to find them in a relative subfolder. Unless you're bypassing DISM and doing your own magic, that's how DISM appears to work.

 

[nuhi]

It's kinda inconvenient to copy the whole FOD ISO, unless you're using a large number of packages on a regular basis. The way I tested it (before using NTLite), was to figure the minimum number of files DISM needed to do the same task.

If you only needed WMIC, then only two metadata CAB's are required and DISM has to find them in a relative subfolder. Unless you're bypassing DISM and doing your own magic, that's how DISM appears to work.

Topic is about WMIC 24H2 block, we got sidetracked on how FOD cache is supposed to work due to your rebuilding of FOD ISO.
That is commendable that you can get it file by file, not really an issue and it works via FOD ISO miles simpler.

What I would like us to figure out how to workaround the 24H2 CU uninstalling WMIC during Windows setup, FOD cache works as expected but it does not help in this case.

 

[abbodi86]

What I would like us to figure out how to workaround the 24H2 CU uninstalling WMIC during Windows setup, FOD cache works as expected but it does not help in this case.

OOBEFodSetup.exe executed by schedule task "Microsoft\Windows\Servicing\OOBEFodSetup", triggered by WNF_SHEL_LOGON_COMPLETE

since the task mostly not created offline prior installation, add this registry value which OOBEFodSetup.exe checks to skip disabling wmic

[HKEY_LOCAL_MACHINE\SYSTEM\Setup]
"Upgrade"=dword:00000001

 

[nuhi]

OOBEFodSetup.exe executed by schedule task "Microsoft\Windows\Servicing\OOBEFodSetup", triggered by WNF_SHEL_LOGON_COMPLETE

since the task mostly not created offline prior installation, add this registry value which OOBEFodSetup.exe checks to skip disabling wmic

[HKEY_LOCAL_MACHINE\SYSTEM\Setup]
"Upgrade"=dword:00000001

Thanks for the info. Before considering that direction, do you know what else does that Upgrade switch entail, are there any downsides?
What I mean is, I doubt that it skips only FoD disabling, could be other FoD processing and obvious by the name puts the setup into Upgrade mode, which can mean anything.

 

[nuhi]

Wow, well done abbodi86, OOBEFodSetup task was the key.

jlsupremo, removed OOBEFodSetup scheduled task with NTLite (it has the option to remove any task on the Scheduled Tasks page) and WMIC is there after setup, without touching/re-enabling WMIC FoD, leave it on Features page as is.

abbodi86, this should have much less sideeffects than switching to the Upgrade mode?
Don't see any other capability mentioned in the OOBEFodSetup.exe, should be isolated effect for now.

Will also add this as a component split from full OOBE.

 

[abbodi86]

abbodi86, this should have much less sideeffects than switching to the Upgrade mode?
Don't see any other capability mentioned in the OOBEFodSetup.exe, should be isolated effect for now.

Will also add this as a component split from full OOBE.

Yes, disabling the task is more "supported" way

OOBEFodSetup.exe doesn't actually check the "Upgrade" value data, it only query its presence
so it can be set to 0

 

[jlsupremo]

Wow, well done abbodi86, OOBEFodSetup task was the key.

jlsupremo, removed OOBEFodSetup scheduled task with NTLite (it has the option to remove any task on the Scheduled Tasks page) and WMIC is there after setup, without touching/re-enabling WMIC FoD, leave it on Features page as is.

abbodi86, this should have much less sideeffects than switching to the Upgrade mode?
Don't see any other capability mentioned in the OOBEFodSetup.exe, should be isolated effect for now.

Will also add this as a component split from full OOBE.

I apologize, I'm not that experienced, could you explain to me how to do this step, which from what I understand is to remove the OOBEFodSetup scheduled task with NTLite, how to do this procedure? remembering that I'm using a 24h2 iso to customize the original iso.

 

[nuhi]

I apologize, I'm not that experienced, could you explain to me how to do this step, which from what I understand is to remove the OOBEFodSetup scheduled task with NTLite, how to do this procedure? remembering that I'm using a 24h2 iso to customize the original iso.

Sure.

After loading an image, don't change WMIC feature state if it's Win11 24H2.
If you had an auto-loaded preset which enables it, go back to the Features page and uncheck WMIC (goal is not to have the change pending on the Apply page).

Instead go to the Scheduled Tasks page and paste OOBEFodSetup into its filter row, first empty row on the page.
That will filter the task list to have only one option shown.
On the right of that OOBEFodSetup row set to Remove.

Apply as usual.

 

[jlsupremo]

Sure.

After loading an image, don't change WMIC feature state if it's Win11 24H2.
If you had an auto-loaded preset which enables it, go back to the Features page and uncheck WMIC (goal is not to have the change pending on the Apply page).

Instead go to the Scheduled Tasks page and paste OOBEFodSetup into its filter row, first empty row on the page.
That will filter the task list to have only one option shown.
On the right of that OOBEFodSetup row set to Remove.

Apply as usual.

Thank you very much, I'll do the test, do you think this will solve the issue of NetFX3 not working either?

 

[nuhi]

Thank you very much, I'll do the test, do you think this will solve the issue of NetFX3 not working either?

Haven't tested that.
To enable .NET 3.5 add it on the Updates page.
Toolbar - Add - Template - .NET 3.5
That worked for me as usual.

 

[jlsupremo]

Haven't tested that.
To enable .NET 3.5 add it on the Updates page.
Toolbar - Add - Template - .NET 3.5
That worked for me as usual.

I haven't tested this latest version of NTLITE, but even the previous ones don't work even in the update.

J

Post in thread 'Win 11 24H2 NetFx3.5 no longer appears'

Oct 3, 2024

This looks like a .10073 bug, where NTLite isn't picking up NetFX3.5's correct package name:

View attachment 12929

+nuhi

In this case, how can I report this bug to ntlite? Or is it just a matter of waiting for a new version?

• jlsupremo

 

[tistou77]

I haven't tested this latest version of NTLITE, but even the previous ones don't work even in the update.

Work for me and Image 26100.1

See EDIT

Post in thread 'How to insert NET Framework 3.5?'

Oct 4, 2024

Surely a link, the .Net 3.5 feature is no longer listed in the Features list either
To see with nuhi if that's it

Or test by adding the file manually from NTLite, maybe it works
I have never tested, I remove .Net 2.0, 3.0 and 3.5 components

EDIT : tested with full ISO (26100.1) and it's good though (the file is present in sources\sxs)

View attachment 12947 View attachment 12948

If not present in the following ISOs, recover the file and add it to this directory

• tistou77

• 

 

[jlsupremo]

Work for me and Image 26100.1

See EDIT

Post in thread 'How to insert NET Framework 3.5?'

Oct 4, 2024

Surely a link, the .Net 3.5 feature is no longer listed in the Features list either
To see with nuhi if that's it

Or test by adding the file manually from NTLite, maybe it works
I have never tested, I remove .Net 2.0, 3.0 and 3.5 components

EDIT : tested with full ISO (26100.1) and it's good though (the file is present in sources\sxs)

View attachment 12947 View attachment 12948

If not present in the following ISOs, recover the file and add it to this directory

• tistou77

• 

As soon as possible I will test this latest version of NTLITE but as I said before this option did not work when I did it with the previous version of NTLITE, Windows even using this feature was not activating 3.5.

remembering that this only happens in Windows 11 24h2.