yes, the first thing I did was put the Microsoft-Windows-NetFx3-OnDemand-Package~31bf3856ad364e35~amd64~~.cab file in the NTLITE folder, but it still doesn't work, after installing the iso compiled by ntlite, 3.5 was still disabled.
- Messages
- 1,327
- Reaction score
- 281
You have to put the .cab file in the ISO, in the Sources\Sxs directory
And not in the NTLite directory
This .cab already comes on the iso originally(Win11_24H2_BrazilianPortuguese_x64\sources\sxs\Microsoft-Windows-NetFx3-OnDemand-Package~31bf3856ad364e35~amd64~~.cab), I normally did it the other way around, as NTlite requested the .cab, so as usual I copied it to the Cache\Updates\11.24H2.x64 and Cache\Updates\11.24H2.x64.FOD folders, but it still didn't activate.
- Messages
- 1,327
- Reaction score
- 281
The file just needs to be in the Sources\Sxs directory, then from NTLite, on the Updates page.
Toolbar - Add - Template - .NET 3.5
I apologize, I actually tested it now and 3.5 is active in this latest version.
Thanks.
- Messages
- 4,062
- Reaction score
- 1,704
To confirm if .NET 3.5 is installed use this command from an elevated command-line:
Should return Install REG_DWORD 0x1 if all good.
Worked in my tests, tried both 26100.1 and the official 26100.1742 image.
Just make sure as tistou77 said to add it to the Updates page.
Doesn't matter where the package is before insertion to the updates page, only for that template command which is handy - each ISO has the .NET package in it as is.
(just saw your result after posting this, will leave it for others how to test)
Code:
reg query "HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v3.5" /v InstallWorked in my tests, tried both 26100.1 and the official 26100.1742 image.
Just make sure as tistou77 said to add it to the Updates page.
Doesn't matter where the package is before insertion to the updates page, only for that template command which is handy - each ISO has the .NET package in it as is.
(just saw your result after posting this, will leave it for others how to test)
Yes, this is correct, it returned Install REG_DWORD 0x1, thank you very much.
peter_58_ha
New Member
- Messages
- 11
- Reaction score
- 3
Hello from Germany!
I walked through all the steps to add the wmic files to the correct folders and now this shows up:
What to do in this case?
Im runninhg the free version of NTLite and to remove the OOBEFodSetup I need the premium feature :-(
Best regards
Peter
I walked through all the steps to add the wmic files to the correct folders and now this shows up:
What to do in this case?
Im runninhg the free version of NTLite and to remove the OOBEFodSetup I need the premium feature :-(
Best regards
Peter
Last edited:
I get an error message when I try to add WMIC "remove one of the following"
Obviously, I did remove both "OOBEFodSetup" from scheduled task and components.
I did "process" after removing but I still get the same error message.
Please help.
Attachments
I am running the premium feature and I still get the same error message. I have removed those two and I still get the error message.
I did remove it and I still get the same error message.
Hi, I tried that and option is deactivated. Operation requires missing files. Will try by manually adding the file but most often something like this crashes the unattended installation
nuhi are you able to automate this? allow the user to select the ISO, then all mounting, unmounting, copying of files, correct region etc, is done automatically?
This process seems tedious and vulnerable to user error if manual. But do appreciate the guide provide by garlin.
Currently I am stuck on a box that wont let me tick WMIC, it says to enable this feature either remove oobefodsetup scheduled task or oobe fod setup component. Removing the scheduled task has no effect. Cant find the component to remove, but the standard OOBE is greyed out, which isnt surprising as I thought this is critical.
This process seems tedious and vulnerable to user error if manual. But do appreciate the guide provide by garlin.
Currently I am stuck on a box that wont let me tick WMIC, it says to enable this feature either remove oobefodsetup scheduled task or oobe fod setup component. Removing the scheduled task has no effect. Cant find the component to remove, but the standard OOBE is greyed out, which isnt surprising as I thought this is critical.
Last edited:
Ok an update, as I came back here forgetting what I did, will reference this post.
Simply need to disable the OOBEFodSetup task, and I have actually still done it as is in my preset.
Simply need to disable the OOBEFodSetup task, and I have actually still done it as is in my preset.
Last edited:
Unfortunately, I didn't feel safe disabling OOBEFodSetup; to temporarily resolve the issue, I created a startup batch file with the following command. It takes a while to install, but it was the solution I found so far.
powershell -Command "Start-Process powershell -ArgumentList 'DISM /Online /Add-Capability /CapabilityName:WMIC~~~~' -Verb RunAs"
The task only exists for one reason: to disable WMIC right before your first logon.
Windows keeps WMIC enabled (by default) on a clean install, so legacy setup tools that depend on WMIC can work. But once you're past the specialize and audit phases, MS thinks it's a great time to secretly remove WMIC since the dependency is over.
Therefore, disabling or removing this task poses no risk.