Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Sunday, June 9, 2019 2:33 PM
I am trying to enable .NET 3.5 for an application that is used across our company and I am trying to do this offline to the .WIM file. Following some instructions I got, this is what I am doing:
Open a command prompt as the administrator
Navigate to the location of the Windows 10 ADK DISM folder
Execute the following:
DISM /Mount-Wim /WimFile:"E:\Sources\OS\Capture\New_Dell_Win10x64.wim" /Index:1 /MountDir:"E:\Sources\OS\Mount"
Then:
DISM /Image:"E:\Sources\OS\Mount" /Enable-Feature /FeatureName:NetFx3 /All /LimitAccess /Source:"E:\Sources\OS\Win10_1809\sources\sxs"
These two work fine. The problem starts with the next command:
DISM /Unmount-Wim /MountDir:"E:\Sources\OS\Mount" /Commit
The following error is received:
Error: 161
The specified path is invalid
The DISM log file can be found at C:\windows\Logs\DISM\dism.log
When I look at the log file, I see hundreds of lines like this:
2019-06-08 22:20:00, Warning DISM DISM WIM Provider: PID=14804 [AllocNode:(701) -> GetFileStorageTierClass failed] E:\Sources\OS\Mount\Program Files\WindowsApps\Microsoft.MicrosoftOfficeHub_17.8918.5926.0_x64__8wekyb3d8bbwe\VFS (HRESULT=0x80070001) - CWimManager::WimProviderMsgLogCallback
Lots and lots of warnings until I get to the error on this line:
The DISM log file can be found at C:\windows\Logs\DISM\dism.log DISM WIM Provider: PID=14804 [AllocNode:(701) -> GetFileStorageTierClass failed] E:\Sources\OS\Mount\Program Files\WindowsApps\Microsoft.MicrosoftOfficeHub_17.8918.5926.0_x64__8wekyb3d8bbwe\VFS\ProgramFilesCommonX64 (HRESULT=0x80070001) - CWimManager::WimProviderMsgLogCallback
This line throws the 161 error. I tried to navigate to the folder listed (E:\Sources\OS\Mount\Program Files\..\VFS\ProgramFilesCommonX64) and I get the following Windows error: "<directory name> is not accessible. The file cannot be accessed by the system."
The .WIM was created through an SCCM build and capture task sequence. We are at build 1810 on SCCM and for the image I am using the May 16th version of Win 10 1809. I have successfully deployed the task sequence prior to this problem.
Thoughts?
All replies (3)
Monday, June 10, 2019 4:08 PM ✅Answered
Thank you for the reply.
I still want to inject this into the .WIM file, but I may modify on my next build by pausing in between BUILD and CAPTURE to enable .NET 3.5.
For now, though, I went ahead and cracked open the .WIM, copied the sxs folder to the mounted C:\ drive and buttoned it back up. I then added a step in the task sequence to run the following command:
C:\Windows\System32\Dism.exe /online /enable-feature /featurename:NetFx3 /All /Source:C:\Apps\sxs\ /LimitAccess
This works for now.
Thanks again!
Monday, June 10, 2019 2:00 AM
Your deduce is reasonable, DISM steps should be correct, I also suspect the media you are using.
You may the original wim from Microsoft website rather than captured from SCCM for install .NET Framework.
I always using original image(wim or iso)’s sxs folder for installation, works fine.
Regards
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
Tuesday, October 29, 2019 8:36 PM
Since Windows 10, the command should be:
For Offline:
DISM /Image:"C:\WIM\Mounted" /Add-Package /PackagePath:"C:\WIM\NetFx3\Microsoft-Windows-NetFx3-OnDemand-Package.cab"
For Online:
DISM.EXE /Online /Add-Package /PackagePath:"Microsoft-Windows-NetFx3-OnDemand-Package.cab"
*** If you use Windows 10 1809, ensure tu use NetFx3 package from 1809 source.