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
Friday, October 5, 2018 2:50 PM
Howdy,
With previous Windows installations, for example 1803, I would made a Folder and copy:
Microsoft-Windows-NetFX3-OnDemand-Package.cab
Microsoft-Windows-NetFX3-OnDemand-Package-en-us.cab
To the folder plus a batch file to install manually & offline:
DISM /Online /Enable-Feature /FeatureName:NetFX3 /All /LimitAccess /Source:%~dp0
Unfortunately with release of Windows 10 1809 x64 the file names are changed and the code also does not work:
Win 10 x64 1809 :: sources \ sxs \
microsoft-windows-netfx3-ondemand-package~31bf3856ad364e35~amd64~~.cab
Microsoft-Windows-NetFx3-OnDemand-Package~31bf3856ad364e35~amd64~en-US~.cab
1st you notice the file name changes in both files.
2nd the code does not work:
Error: 87
DISM doesn't recognize the command-line option "1809"\.
...
Please advise,
Cheers.
All replies (16)
Sunday, October 7, 2018 1:39 AM
Uninstall Windows 10 Version 1809 aka October Update.
Microsoft paused the rollout of the Windows 10 October 2018 Update (version 1809). Please don’t install it and wait until new media is available.
Microsoft will provide an update when they resume rolling out the Windows 10 October 2018 Update to customers.
S.Sengupta,Microsoft MVP Windows and Devices for IT, Windows Insider MVP
Sunday, October 7, 2018 8:15 AM
Thanks buddy,
After masterpieces of Windows 10 Updates! I install every new update on Virtual Machine for some days before my real environment.
October 2018 update was the worst one as there were many bugs to list, so I already ignored it.
Thanks for your confirmation however :)
Monday, October 8, 2018 8:52 AM
Hi，
Thank you for your understanding and support. We will notify you as soon as possible after the update is launched.
Please feel free to contact us if you have any issue.
Best
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Wednesday, October 10, 2018 7:57 AM
I heard finally a patch is released, KB4464330:
http://www.catalog.update.microsoft.com/Search.aspx?q=KB4464330
But is there new ISOs released for build 1809 or I just need to install & apply the above patch?
Tuesday, October 16, 2018 8:47 AM
Hi，
New ISO hasn't been released. You can install KB4464330 first.
Thanks for your understanding.
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Wednesday, November 14, 2018 10:40 PM
Now that 1809 is released I am having the same issue during testing of our "old" method of installing .net 3.5 (same method as person who made this thread) - is there a fix or alternative method?
Friday, November 16, 2018 12:28 PM
I am use package from Win2019 server iso - working fine
Microsoft-Windows-NetFx3-OnDemand-Package~31bf3856ad364e35~amd64~en-US~.cab
Friday, November 16, 2018 8:36 PM
Uninstall Windows 10 Version 1809 aka October Update.
Microsoft paused the rollout of the Windows 10 October 2018 Update (version 1809). Please don’t install it and wait until new media is available.
Microsoft will provide an update when they resume rolling out the Windows 10 October 2018 Update to customers.
S.Sengupta,Microsoft MVP Windows and Devices for IT, Windows Insider MVP
Will MS release the new media for 1809?
Monday, November 19, 2018 3:34 PM
It has been re-released on Volume Licensing Center now
Roger G CH - thanks I found a similar solution that worked for me that I forgot to post on here.
Monday, January 28, 2019 11:07 PM | 11 votes
How to fix.
Download the Windows 10 1809 .iso file using the Microsoft media creation tool
https://www.microsoft.com/en-gb/software-download/windows10
Sign in as admin, run that tool, create media for another PC, download iso.
Once you have the .iso mount the iso (double click on it)
Open the command prompt as admin
Run this command
Dism /online /enable-feature /featurename:NetFx3 /All /Source:d:\sources\sxs /LimitAccess
(d:\sources\sxs = use whatever the drive letter for the mounted .iso is)
This should work.
You MUST MUST MUST use the .iso for the version of Windows you are using... Microsoft checks. Version mismatch between the .iso and your PC and it will fail with some bogus error message and you will spend 3 days pulling your hair out and yelling at people on the internet trying to get a core feature of Windows working because Microsoft wants to play .net version Nazi.
-RW
Saturday, February 23, 2019 9:21 PM
@Redwizard001 Thank you so much! I have tried every weird way to install that. Disabling WU in registry, uninstalling newer .NET, safe mode, switching language to English. But this was it. The cab has to be from the VERY SAME windows build.
Wednesday, February 27, 2019 7:08 PM
Awesome! Worked!
Wednesday, May 15, 2019 12:40 PM | 1 vote
How to fix.
Download the Windows 10 1809 .iso file using the Microsoft media creation tool
https://www.microsoft.com/en-gb/software-download/windows10
Sign in as admin, run that tool, create media for another PC, download iso.
Once you have the .iso mount the iso (double click on it)
Open the command prompt as admin
Run this command
Dism /online /enable-feature /featurename:NetFx3 /All /Source:d:\sources\sxs /LimitAccess
(d:\sources\sxs = use whatever the drive letter for the mounted .iso is)
This should work.
You MUST MUST MUST use the .iso for the version of Windows you are using... Microsoft checks. Version mismatch between the .iso and your PC and it will fail with some bogus error message and you will spend 3 days pulling your hair out and yelling at people on the internet trying to get a core feature of Windows working because Microsoft wants to play .net version Nazi.
-RW
Bro, dude - after spending too many hours on this sht, i luckily stumbled upon your reply. The "MUST MUST MUST" part helped me spot on. Cheers!
*Copying my original error in here in case it helps people searching to find it- Error: 0x800F081F The source files could not be found.“"
Thursday, June 13, 2019 6:51 PM | 1 vote
Dism /online /enable-feature /featurename:NetFx3 /All /Source:d:\sources\sxs /LimitAccess
THIS ^ WORKED
You're a god-damn hero. You helped save me some time and my customer money :)
Thursday, August 1, 2019 10:43 AM | 1 vote
Howdy,
I had the same issue with one of our customers.
I made the mistake to remove the suffixe after "package" to shorten the filenames. Apparently these are needed to check against the operating system.
So with each new build of "Windows 10" you will have to update the content of the package you will use to deploy your .Net3.x.
So my script is this:
MD C:\TEMP\Sources
xcopy *.* C:\TEMP\Sources\ /E/Y
start /wait DISM.exe /Online /Enable-Feature /FeatureName:NetFx3 /All /LimitAccess /Source:C:\Temp\Sources
rd /s /q C:\TEMP\Sources
It works like a charm.
By the way we use Quest Kace System Deployment Appliance and System Management Appliance
Tuesday, November 19, 2019 9:34 AM
You are a genious!