Important Notice: On February 29th, this community was put into read-only mode. All existing posts will remain but customers are unable to add new posts or comment on existing. Please feel to join our Community Discord for any questions and discussions.

Troubles with built-in "Microsoft .NET 3.5 (Workstations) 3.5.1 (Updated 2009)" Package.

Hello, we've recently started rolling out Windows 10 Enterprise 2H20 (x64) this week and are have a Base software package that we have a few nested packages in, .NET 3.5 is one of them.  The .NET 3.5 is an Auto Download package so it always appears to be up-to-date with the latest versions released by PDQ.

We seem to be having problems with it timing out when it comes to Step 11 of that package and never finishes, resulting it failure so the rest of the package stops at that point (this is intended).  Step 11 points to the install file of: $(Repository)\Microsoft\NETFramework\3.5\2009\64\NetFx3-10-64.bat

The contents of the BAT file include the following, which looks pretty typical:

%SYSTEMROOT%\System32\dism.exe /online /Get-Featureinfo /FeatureName:NetFx3 | findstr Enabled
ECHO .NET 3.5 is already enabled
) ELSE (
%SYSTEMROOT%\system32\DISM.exe /online /enable-feature /featurename:NetFx3 /All /Source:.\sxs /LimitAccess


What log file location can I check to see what's happening that this package is timing out?  The strange thing is that our PC Support Techs are saying if they retry the package from failed step, it then works as expected.  As with all new OS versions and PDQ package versions, I'm just working out the kinks.  Any insight would be helpful.

Thank you.