SOLVED Windows 10 1909 - OSD and .NET3.5

[Daptonic]

Anyone testing/playing with W10 1909 yet?

When attempting to deploy the image with .NET3.5 pre-configured I am getting the following error:

---
The task sequence execution engine failed executing the action (DotNET_3.5) in the group (Setup Operating System) with the error code 2148468767
Action output: ... MSPKG$/TAP00174/sccm?/InstallNetFx3.ps1 to C:\_SMSTaskSequence\Packages\TAP00174\InstallNetFx3.ps1
Downloading file /SMS_DP_SMSPKG$/TAP00174/sccm?/microsoft-windows-netfx3-ondemand-package~31bf3856ad364e35~amd64~~.cab range 0-72729052
Downloaded file from http://SERVERNAME.DOMAIN:80/SMS_DP_...ondemand-package~31bf3856ad364e35~amd64~~.cab to C:\_SMSTaskSequence\Packages\TAP00174\microsoft-windows-netfx3-ondemand-package~31bf3856ad364e35~amd64~~.cb
VerifyContentHash: Hash algorithm is 32780
Content successfully downloaded at C:\_SMSTaskSequence\Packages\TAP00174.
Resolved source to 'C:\_SMSTaskSequence\Packages\TAP00174'
Command line for extension .exe is "%1" %*
Set command line: Run command line
Working dir 'C:\_SMSTaskSequence\Packages\TAP00174'
Executing command line: Run command line with options (0, 4)

Deployment Image Servicing and Management tool
Version: 10.0.18362.1

Image Version: 10.0.18363.418

Enabling feature(s)
P.
---

I am using the same file / package / code from my 1809 and 1903 Deployments and those work without an issue.

I have verified that the cab file name has not changed between 1809/1903/1909.





Even trying to install .NET 3.5 on 1909 in the OS via System Center after the OS boots fails with this error:


---

Contents of the InstallNetFx3.ps1 file referenced above.

$currentLocation = Split-Path -Parent $MyInvocation.MyCommand.Path;
Enable-WindowsOptionalFeature -Online -FeatureName NetFx3 -Source $currentLocation -LimitAccess -All

 

[Sam Banford]

So a manual DISM install of 3.5 pointing to that package works? I'm thinking it won't and it doesn't matter if the file name is the same, if it's not the actual file the OS wants it won't work, hence your "The source files could not be found." issue.

I gave up on using the 3.5 OnDemand package back in the 17xx's, just snag the source data straight from the ISO's and invoke DISM via PowerShell.

 

[Daptonic]

I compared the 2 files and there is a minute difference in size despite the identical name. Created a 1909 specific .NET package and everything works as intended now.

 

[m0rph]

For the newer builds of Windows 10 we had to download the "Feature on Demand" ISO to get the correct CAB files. There I use an application: Content location is the folder containing the unpacked ISO, and a powershell script installs the features:

 

[Fruby]

Where can i get the net framework cab for 1909?