Answered by:
.net framework 3.5 installation fails w/ error code: 0x800F0954

Question
-
Answers
-
Title. Downloads for about 2 seconds then fails. Tried the DISM command
Dism /online /enable-feature /featurename:NetFX3 /All /Source:D:\sources\sxs
Get the same error code.
Windows 10 1709
Used the powershell command
Add-WindowsCapability –Online -Name NetFx3~~~~ –Source D:\sources\sxs
which worked.
- Marked as answer by CFFraser Friday, December 8, 2017 8:37 PM
All replies
-
Title. Downloads for about 2 seconds then fails. Tried the DISM command
Dism /online /enable-feature /featurename:NetFX3 /All /Source:D:\sources\sxs
Get the same error code.
Windows 10 1709
Used the powershell command
Add-WindowsCapability –Online -Name NetFx3~~~~ –Source D:\sources\sxs
which worked.
- Marked as answer by CFFraser Friday, December 8, 2017 8:37 PM
-
Hi CFFraser,
Adding features (including .NET 3.5) to Windows 10
DISM.EXE /Online /Get-Capabilities
Get-WindowsCapability -Online
Glad to hear that you have solved it and thank you for sharing it here, it will be helpful to other community members who have same questions.
Regards,
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.- Proposed as answer by Eric0502 Thursday, December 14, 2017 12:40 PM
-
I get the same error in the Powershell window (running as admin):
PS C:\Windows\system32> Add-WindowsCapability –Online -Name NetFx3~~~~ –Source D:\sources\sxs
Add-WindowsCapability : Add-WindowsCapability failed. Error code = 0x800f0954
At line:1 char:1
+ Add-WindowsCapability –Online -Name NetFx3~~~~ –Source D:\sources\sxs
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Add-WindowsCapability], COMException
+ FullyQualifiedErrorId : Microsoft.Dism.Commands.AddWindowsCapabilityCommandI also tried inserting the original Windows 10 DVD, which is the R: drive, and changed the D: to R: in the command above. Same result.
Any further suggestions?
Colin
- Edited by GraniteStateColin Friday, January 19, 2018 1:16 PM added info about also trying from DVD
- Proposed as answer by Joaquin H Monday, January 22, 2018 6:06 PM
-
For me, the solution was to use the full name of the source file, instead of just the path. Not sure why that was needed, but I had found a post that suggested it (don't recall where now, sorry), tried it, and sure enough it solved my problem with very similar symptoms:
Instead of using this (which did not work for me): Dism /online /enable-feature /featurename:NetFX3 /All /Source:R:\sources\sxs
I used this, which did work for me: dism /online /add-package /packagepath:R:\sources\sxs\microsoft-windows-netfx3-ondemand-package.cab
Where R is the drive letter for my Blu-Ray/DVD-ROM drive. Prior to finding the solution, I had tried many variants on the command, which all failed, because Windows couldn't find the source file. I believe the key difference is inclusion of the filename, not the other differences from the command above.
Colin
- Edited by GraniteStateColin Monday, January 22, 2018 7:46 PM
- Proposed as answer by WayneMorgan Saturday, October 20, 2018 8:34 PM
-
Is the source correct?
DISM /Online /Enable-Feature /FeatureName:NetFx3 /All /LimitAccess /Source:"d:\sources\sxs"
- Edited by JoseEspitia Monday, January 22, 2018 7:55 PM
-
-
-
You may receive this error when trying to install DotNet (.net) on Windows 10 and you are using a WSUS server. This error may occur of the .net installer is not approved in WSUS.
As a temporary workaround, change the registry key “UseWUServer” to 0. It is located at:
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU
After the registry change, restart the Windows Update service. You should be able to install .net at this time. Once done you should change this key back to its original value (or wait and allow Group Policy to do it for you.)
Source => https://www.westechs.com/error-0x800f0954-when-installing-dot-net-on-windows-10/
- Proposed as answer by DGooose Monday, March 19, 2018 8:04 PM
-
-
-
-
-
Here's what worked for me. I saw something about CBS in the dism log so I cleaned up CBS logs.
net stop trustedinstaller
Delete all files from C:\Windows\Logs\CBS
net start trustedinstaller
Then I ran Dism.exe /online /enable-feature /featurename:NetFX3 /source:C:\
I had already copied the sxs files to the root of C: based on someone else's post here, but it probably would work with the source in other locations.
Thanks everyone.
- Proposed as answer by Jamieweeman Tuesday, October 16, 2018 8:13 AM
-
-
-
-
You may receive this error when trying to install DotNet (.net) on Windows 10 and you are using a WSUS server. This error may occur of the .net installer is not approved in WSUS.
As a temporary workaround, change the registry key “UseWUServer” to 0. It is located at:
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU
After the registry change, restart the Windows Update service. You should be able to install .net at this time. Once done you should change this key back to its original value (or wait and allow Group Policy to do it for you.)
Source => https://www.westechs.com/error-0x800f0954-when-installing-dot-net-on-windows-10/
- Proposed as answer by goonerwhelan Wednesday, May 9, 2018 2:22 PM
-
-
Thanks.
<snip
Here's what worked for me. I saw something about CBS in the dism log so I cleaned up CBS logs.
net stop trustedinstaller
Delete all files from C:\Windows\Logs\CBS
net start trustedinstaller
Then I ran Dism.exe /online /enable-feature /featurename:NetFX3 /source:C:\
I had already copied the sxs files to the root of C: based on someone else's post here, but it probably would work with the source in other locations.
</snip>
This worked for me as well.
- Edited by Vinayak Sonmale Tuesday, April 3, 2018 5:24 AM
-
Hi,
I got an answer that worked from another post
Dism.exe /online /enable-feature /featurename:NetFX3 /source:C:\ /LimitAccess
Copy first the CAB files from media locally to the root of C:\ drive and 100% success!
-
You may receive this error when trying to install DotNet (.net) on Windows 10 and you are using a WSUS server. This error may occur of the .net installer is not approved in WSUS.
As a temporary workaround, change the registry key “UseWUServer” to 0. It is located at:
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU
After the registry change, restart the Windows Update service. You should be able to install .net at this time. Once done you should change this key back to its original value (or wait and allow Group Policy to do it for you.)
Source => https://www.westechs.com/error-0x800f0954-when-installing-dot-net-on-windows-10/
I tried everything above, and this finally fixed my issue!
Thanks.
-
You may receive this error when trying to install DotNet (.net) on Windows 10 and you are using a WSUS server. This error may occur of the .net installer is not approved in WSUS.
As a temporary workaround, change the registry key “UseWUServer” to 0. It is located at:
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU
After the registry change, restart the Windows Update service. You should be able to install .net at this time. Once done you should change this key back to its original value (or wait and allow Group Policy to do it for you.)
Source => https://www.westechs.com/error-0x800f0954-when-installing-dot-net-on-windows-10/
Thankssssssssssssssssssssssssssssssss -
-
-
One thing I have noticed - If you have the window open that says installation failed when trying to add it through "Turn Windows features on and off" and you try to run the scripts, they will still give the 0x800f0954 error. Closing that window and then rerunning the script worked fine. Guessing it was locking a file that was needed.
-
Thank you @GranteStateColin for this! I kept running the PowerShell commands above and it kept erroring out for me, so I finally came across your fix with using the full name of the source file and it worked! Yaaaaay! If only I could get those 4 hours of my life back.
-Jessica
- Edited by Jessica Levy Thursday, June 21, 2018 6:36 PM
-
-
-
-
-
You may receive this error when trying to install DotNet (.net) on Windows 10 and you are using a WSUS server. This error may occur of the .net installer is not approved in WSUS.
As a temporary workaround, change the registry key “UseWUServer” to 0. It is located at:
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU
After the registry change, restart the Windows Update service. You should be able to install .net at this time. Once done you should change this key back to its original value (or wait and allow Group Policy to do it for you.)
Source => https://www.westechs.com/error-0x800f0954-when-installing-dot-net-on-windows-10/
worked, thanks. -
-
-
-
-
-
I got the same problem when I tried to add .NET 3.5 by go to "Turn Windows features on or off", got Error code 0x800F0954. Tried run
DISM.EXE /Online /Add-Capability /CapabilityName:NetFx3~~~~
Still the same error, now it is possible to read error log in C:\Windows\Logs\DISM\dism.log:
xxxx, Info DISM DISM Package Manager: PID=12956 TID=12296 Further logs for online package and feature related operations can be found at %WINDIR%\logs\CBS\cbs.log - CPackageManagerCLIHandler::ExecuteCmdLine xxxx, Error DISM DISM.EXE: DISM Package Manager processed the command line but failed. HRESULT=800F0954
Go to C:\Windows\Logs\CBS\CBS.log, found
xxxx, Info CBS DWLD:Failed to do Windows update search [HRESULT = 0x800f0954 - CBS_E_INVALID_WINDOWS_UPDATE_COUNT_WSUS] xxxx, Info CBS FC: WindowsUpdateDownloadFromUUP returns. [0x800F0954]
Now search for "CBS_E_INVALID_WINDOWS_UPDATE_COUNT_WSUS" will lead to solution that change "HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU the key UseWUServer to 0".
-
-
-
-
-
-
-
-
For me, the solution was to use the full name of the source file, instead of just the path. Not sure why that was needed, but I had found a post that suggested it (don't recall where now, sorry), tried it, and sure enough it solved my problem with very similar symptoms:
Instead of using this (which did not work for me): Dism /online /enable-feature /featurename:NetFX3 /All /Source:R:\sources\sxs
I used this, which did work for me: dism /online /add-package /packagepath:R:\sources\sxs\microsoft-windows-netfx3-ondemand-package.cab
Where R is the drive letter for my Blu-Ray/DVD-ROM drive. Prior to finding the solution, I had tried many variants on the command, which all failed, because Windows couldn't find the source file. I believe the key difference is inclusion of the filename, not the other differences from the command above.
Colin
-
-
Thanks for the workaround by disabling WSUS. I've inherited a legacy environment and I'm building myself a Windows 10 VM so I don't have to touch their existing systems. Wondered why I couldn't install .NET v3.5 which I need for vSphere. Saved me a lot of hassle!
-
-
-
-
-
-
You may receive this error when trying to install DotNet (.net) on Windows 10 and you are using a WSUS server. This error may occur of the .net installer is not approved in WSUS.
As a temporary workaround, change the registry key “UseWUServer” to 0. It is located at:
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU
After the registry change, restart the Windows Update service. You should be able to install .net at this time. Once done you should change this key back to its original value (or wait and allow Group Policy to do it for you.)
Source => https://www.westechs.com/error-0x800f0954-when-installing-dot-net-on-windows-10/
-
You may receive this error when trying to install DotNet (.net) on Windows 10 and you are using a WSUS server. This error may occur of the .net installer is not approved in WSUS.
As a temporary workaround, change the registry key “UseWUServer” to 0. It is located at:
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU
After the registry change, restart the Windows Update service. You should be able to install .net at this time. Once done you should change this key back to its original value (or wait and allow Group Policy to do it for you.)
Source => https://www.westechs.com/error-0x800f0954-when-installing-dot-net-on-windows-10/
-
-
-
I found another solution that may be easier for some (a GUI solution, rather than a PS solution) and works for installing all Windows components, not just the .NET Framework: IF you run into this on a computer getting updates through WSUS, instead of directly from MS, then:
change the registry key “UseWUServer” to 0
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU
This will let you install any of the Windows Optional features from the GUI.
After you're done, be sure to run gpupdate /force or manually restore that key to 1 after you have finished your installs so you can resume getting updates from the WSUS server.
Colin
-
-
-
-
I am trying to install Skylight by Sierra Wireless on a new Dell Rugged Extreme Tablet with M$ Win 10, so I can use the WWAN card & SIM I installed, but I cannot get it to work. I read through other posts about this error, but I cannot get their resolutions to work. I've changed the Registry Key for UseWUServer to "0". Where can I get the necessary .NET 3.5 setup files without the DISM (I don't have access to it)?
-
Ok, I'm a newbie here. I just read that I could try running...
I deleted all files in C:\Windows\Logs\CBS
I ran Windows PowerShell as admin
PS C:\Users\JD_S>net start trustedinstaller
PS C:\Users\JD_S>Dism.exe /online /enable-feature /featurename:NetFX /source:C:\
The response was...
Deployment Image Servicing and Management tool
Version: 10.0.17763.1
Image Version: 10.0.17763.379
Enabling feature(s)
[==================100.0%===============]
Error: 0x800f0950
DISM failed. No operation was performed.
For more information, review the log file.
The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log
So, apparently, I have access to DISM, but I do not have access to the CAB files referred to above. I guess I should have asked that instead. Anyone know where I can find and download them to drop onto my C:\ root drive?
-
-
-
Thank you!! Thank you!! Thank you!!
Such a simple, intuitive solution. This should win an award.
Trashed a computer trying to add .netFramework3.5 back after a user removed this feature. Tried all of the other DISM BS, which worked for previous builds, but not 1809. Wish I would have found this a lot sooner. Now the trick is to remember it for the next time:)
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Flávio Campelo thank you this worked!