A few people are getting the 0x800f0954 error code when trying to install the .NET Framework 3.5 or a diverse optional feature on the Win 10 system. Most people are saying that this issue takes place while they were attempting to install the package through the Win Features, but others are receiving it while utilizing the DISM (Deployment Image Servicing and Management) command-line tool. The issue does not seem to be exclusive to a particular version of Windows since it is confirmed to happen on Windows 7, 8.1 and 10.
Solution#1: Clean Your CBS (Component Based Servicing) Logs
A few people who are facing the 0x800f0954 error code have stated that they managed to fix the problem after deleting the Component Based Servicing (CBS) logs related to DISM (Deployment Image Servicing and Management). After doing so and rerunning the DISM command, a few affected people have stated that the issue was no longer happening. Here is what you have to carry out:
- First of all, open the File Explorer > go to the ‘C:\Windows\Logs\CBS’ location.
- Once you are in the CBS folder, choose everything there, and select Delete.
- After each file .cab and .log file is deleted, close the folder.
- Hit Win + R keys for opening up the Run dialog box > CMD > hit Shift + Ctrl + Enter for opening up the elevated CMD. When you see the User Account Control (UAC), simply hit Yes for granting the admin privileges.
- Now, inside this elevated CMD, enter the ‘Dism.exe /online /enable-feature /featurename:NetFX3 /source:C:\’ command > hit Enter for rerunning your DISM command.
- After pressing Enter, your .NET Framework ought to install without giving the error code 0x800f0954.
- If you are still facing this same issue or this solution was not applicable to the present scenario, then simply go down to the next solution.
Solution#2: Utilizing The PowerShell For Installing The .NET Framework 3.5 To Fix The 0x800f0954 Error Code
If you are facing the error code 0x800f0954 while attempting to install the .NET Framework 3.5 by utilizing the DISM, you may be capable of circumventing the issue by utilizing the PowerShell. Numerous affected people have stated that the problem was no longer happening after they ran the powershell command that ended up resolving the issue. Here is what you have to carry out:
- Hit Win + R keys for opening up the Run > enter powershell > hit Shift + Ctrl + Enter for opening up the elevated PowerShell prompt. When asked by the User Account Control, simply click on Yes for granting the admin privileges.
- Then inside that elevated PowerShell, enter the ‘Add-WindowsCapability –Online -Name NetFx3~~~~ –Source D:\sources\sxs’ command > hit Enter for executing it.
- Now, close that prompt and reboot the system.
- At the next startup, try installing your .NET Framework 3.5 again and check if the problem has been fixed.
Solution#3: Utilizing Your Group Policy Editor
If you receive the error code 0x800f0954 while attempting to append the RSAT Toolset, odds are you will have to make a few changes utilizing your Group Policy Editor tool. Numerous people have managed to fix this problem by running the Gpedit tool for modifying a few settings related to the Component Repair and Component Installation.
After allowing a certain local policy and permitting the operating system to download the optional features and repair content directly from the WU, numerous people have stated that the problem was gone. If you have your Group Policy Editor on the Win version, here is how you can make the necessary edits:
- Hit Win + R buttons for opening up the Run dialog box > enter gpedit.msc > hit Enter for opening up your system’s Local Group Policy Editor. If you are asked by the UAC, simply hit Yes for granting the admin privileges.
- Once you are inside your system’s Local Group Policy Editor, utilize the left-hand pane for going to the ‘Computer Configuration\Administrative Templates\System’ location.
- Then, with System chosen, go into to your right-hand pane > double-click Specify settings for the optional component repair and component installation.
- Now, set policy to Enabled and ensure to tick the checkbox that says something like Download optional features and repair content directly from the Win Update in place of USUS (Windows Server Update Services).
- Click on Apply for saving all the configurations > close your Local Group Policy Editor > reboot the system.
- At the next startup, the issue ought to no longer happen.