locked
Cannot Enable .Net Framework 3.5 on Windows 10 RRS feed

  • Question

  • Hi,

    I can't install .Net framework 3.5 on windows 10, I've tried all ways but all end with this error

    Error: 0x8000ffff

    DISM failed. No operation was performed.

    I've the log file if needed

    Wednesday, August 5, 2015 12:46 PM

Answers

  • I managed to solve that error by following this solution:

      • Open the Registry Editor by clicking the Start button Picture of the Start button, typing regedit into the Search box, and then pressing ENTER. Administrator permission required If you are prompted for an administrator password or confirmation, type the password or provide confirmation.
      • In the left pane, find and double-click HKEY_LOCAL_MACHINE, and then click COMPONENTS.

      • Right-click COMPONENTS, and then click Export. By default, this file is saved to your desktop, but you can choose any folder.

      • In the File Name text box, type COMPONENTS. You have now created a back up copy of the registry values you're going to be removing.

      • In the right pane, search for PendingXmlIdentifier, right-click it, and then click Delete. PendingXmlIdentifier might not be listed.

      • In the right pane, search for NextQueueEntryIndex, right-click it, and then click Delete. NextQueueEntryIndex might not be listed.

      • In the right pane, search for AdvancedInstallersNeedResolving, right-click it, and then click Delete. AdvancedInstallersNeedResolving might not be listed.

    1. Restart your computer and then run Windows Update again

    Friday, August 7, 2015 3:55 PM

All replies

  • Just to make sure you have your windows 10 installation media (usb/iso)

    and you started a command promp as admin.

    you ran this : Dism /online /enable-feature /featurename:NetFX3 /All /Source:D:\sources\sxs /LimitAccess

    D being the iso you mounted or the USB key.

    This should work

    If not you could do it like this

    Press “Windows Logo” + “R” keys on the keyboard.

    b) Type “appwiz.cpl” in the “Run” command box and press “ENTER”.

    c) In the “Programs and Features” window, click on the link “Turn Windows features on or off”.

    d) Check if the “.NET Framework 3.5 (includes .NET 2.0 and 3.0)” option is available in it.

    e) If yes, then enable it and then click on “OK”.

    f) Follow the on-screen instructions to complete the installation and restart the computer, if prompted.

    you might need to specified the location of the source or access to internet.

    Wednesday, August 5, 2015 12:51 PM
  • Just to make sure you have your windows 10 installation media (usb/iso)

    and you started a command promp as admin.

    you ran this : Dism /online /enable-feature /featurename:NetFX3 /All /Source:D:\sources\sxs /LimitAccess

    D being the iso you mounted or the USB key.

    This should work

    If not you could do it like this

    Press “Windows Logo” + “R” keys on the keyboard.

    b) Type “appwiz.cpl” in the “Run” command box and press “ENTER”.

    c) In the “Programs and Features” window, click on the link “Turn Windows features on or off”.

    d) Check if the “.NET Framework 3.5 (includes .NET 2.0 and 3.0)” option is available in it.

    e) If yes, then enable it and then click on “OK”.

    f) Follow the on-screen instructions to complete the installation and restart the computer, if prompted.

    you might need to specified the location of the source or access to internet.

    For Windows 10, you may need to go through the Settings App (it's very confusing, figuring out which method: Control Panel vs Settings App, to use)  Try Settings - System - Apps and Features - Manage Optional Features - Add a Feature - .Net Framework 3.5 if Frederick's way doesn't work  

    Hope that helps!


    • Edited by Q-Tech Wednesday, August 5, 2015 3:43 PM grammar
    Wednesday, August 5, 2015 3:43 PM
  • Just to make sure you have your windows 10 installation media (usb/iso)

    and you started a command promp as admin.

    you ran this : Dism /online /enable-feature /featurename:NetFX3 /All /Source:D:\sources\sxs /LimitAccess

    D being the iso you mounted or the USB key.

    This should work

    If not you could do it like this

    Press “Windows Logo” + “R” keys on the keyboard.

    b) Type “appwiz.cpl” in the “Run” command box and press “ENTER”.

    c) In the “Programs and Features” window, click on the link “Turn Windows features on or off”.

    d) Check if the “.NET Framework 3.5 (includes .NET 2.0 and 3.0)” option is available in it.

    e) If yes, then enable it and then click on “OK”.

    f) Follow the on-screen instructions to complete the installation and restart the computer, if prompted.

    you might need to specified the location of the source or access to internet.

    For Windows 10, you may need to go through the Settings App (it's very confusing, figuring out which method: Control Panel vs Settings App, to use)  Try Settings - System - Apps and Features - Manage Optional Features - Add a Feature - .Net Framework 3.5 if Frederick's way doesn't work  

    Hope that helps!


    I have the same problem, cannot install .net 3.5 Framework on Windows 10 clean install.

    I have tried appwiz.cpl -> Turn Windows features on or off, fails with error 0x8000FFFF

    I have tried Dism /online /enable-feature /featurename:NetFX3 /All /Source:H:\sources\sxs /LimitAccess, where H:\ is the Windows 10 iso image mounted.

    I have tried  Settings - System - Apps and Features - Manage Optional Features - Add a Feature - .Net Framework 3.5 per the above poster, .net 3.5 is not listed as a feature, only languages + handwriting/Cortana/typing/speech recognition, etc...

    Dism CLI and results below:

    C:\Windows\system32>Dism /online /enable-feature /featurename:NetFX3 /All /Source:H:\sources\sxs /LimitAccess

    Deployment Image Servicing and Management tool
    Version: 10.0.10240.16384

    Image Version: 10.0.10240.16384

    Enabling feature(s)
    [==========================100.0%==========================]

    Error: 0x8000ffff

    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

    dism.log contents:

    2015-08-05 18:23:41, Info                  DISM   DISM Package Manager: PID=5140 TID=7548  Error in operation: (null) (CBS HRESULT=0x8000ffff) - CCbsConUIHandler::Error
    2015-08-05 18:23:41, Error                 DISM   DISM Package Manager: PID=5140 TID=8416 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x8000ffff)
    2015-08-05 18:23:41, Error                 DISM   DISM Package Manager: PID=5140 TID=8416 Failed processing package changes with session options - CDISMPackageManager::ProcessChangesWithOptions(hr:0x8000ffff)
    2015-08-05 18:23:41, Error                 DISM   DISM Package Manager: PID=5140 TID=8416 Failed ProcessChanges. - CPackageManagerCLIHandler::Private_ProcessFeatureChange(hr:0x8000ffff)
    2015-08-05 18:23:41, Error                 DISM   DISM Package Manager: PID=5140 TID=8416 Failed while processing command enable-feature. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x8000ffff)
    2015-08-05 18:23:41, Info                  DISM   DISM Package Manager: PID=5140 TID=8416 Further logs for online package and feature related operations can be found at %WINDIR%\logs\CBS\cbs.log - CPackageManagerCLIHandler::ExecuteCmdLine
    2015-08-05 18:23:41, Error                 DISM   DISM.EXE: DISM Package Manager processed the command line but failed. HRESULT=8000FFFF
    2015-08-05 18:23:41, Info                  DISM   DISM Provider Store: PID=5140 TID=8416 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
    2015-08-05 18:23:41, Info                  DISM   DISM Provider Store: PID=5140 TID=8416 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
    2015-08-05 18:23:41, Info                  DISM   DISM Provider Store: PID=5140 TID=8416 Found the PE Provider.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
    2015-08-05 18:23:41, Info                  DISM   DISM Provider Store: PID=5140 TID=8416 Finalizing the servicing provider(DISM Package Manager) - CDISMProviderStore::Internal_DisconnectProvider
    2015-08-05 18:23:41, Info                  DISM   DISM Package Manager: PID=5140 TID=8416 Finalizing CBS core. - CDISMPackageManager::Finalize
    2015-08-05 18:23:41, Info                  DISM   DISM Provider Store: PID=5140 TID=8416 Disconnecting Provider: DISM Package Manager - CDISMProviderStore::Internal_DisconnectProvider
    2015-08-05 18:23:41, Info                  DISM   DISM Provider Store: PID=5140 TID=8416 Finalizing the servicing provider(MsiManager) - CDISMProviderStore::Internal_DisconnectProvider
    2015-08-05 18:23:41, Info                  DISM   DISM Provider Store: PID=5140 TID=8416 Disconnecting Provider: MsiManager - CDISMProviderStore::Internal_DisconnectProvider
    2015-08-05 18:23:41, Info                  DISM   DISM Provider Store: PID=5140 TID=8416 Finalizing the servicing provider(IntlManager) - CDISMProviderStore::Internal_DisconnectProvider
    2015-08-05 18:23:41, Info                  DISM   DISM Provider Store: PID=5140 TID=8416 Disconnecting Provider: IntlManager - CDISMProviderStore::Internal_DisconnectProvider
    2015-08-05 18:23:41, Info                  DISM   DISM Provider Store: PID=5140 TID=8416 Finalizing the servicing provider(IBSManager) - CDISMProviderStore::Internal_DisconnectProvider
    2015-08-05 18:23:41, Info                  DISM   DISM Provider Store: PID=5140 TID=8416 Disconnecting Provider: IBSManager - CDISMProviderStore::Internal_DisconnectProvider
    2015-08-05 18:23:41, Info                  DISM   DISM Provider Store: PID=5140 TID=8416 Finalizing the servicing provider(DriverManager) - CDISMProviderStore::Internal_DisconnectProvider
    2015-08-05 18:23:41, Info                  DISM   DISM Provider Store: PID=5140 TID=8416 Disconnecting Provider: DriverManager - CDISMProviderStore::Internal_DisconnectProvider
    2015-08-05 18:23:41, Info                  DISM   DISM Provider Store: PID=5140 TID=8416 Finalizing the servicing provider(DISM Unattend Manager) - CDISMProviderStore::Internal_DisconnectProvider
    2015-08-05 18:23:41, Info                  DISM   DISM Provider Store: PID=5140 TID=8416 Disconnecting Provider: DISM Unattend Manager - CDISMProviderStore::Internal_DisconnectProvider
    2015-08-05 18:23:41, Info                  DISM   DISM Provider Store: PID=5140 TID=8416 Finalizing the servicing provider(SmiManager) - CDISMProviderStore::Internal_DisconnectProvider
    2015-08-05 18:23:41, Info                  DISM   DISM Provider Store: PID=5140 TID=8416 Disconnecting Provider: SmiManager - CDISMProviderStore::Internal_DisconnectProvider
    2015-08-05 18:23:41, Info                  DISM   DISM Provider Store: PID=5140 TID=8416 Finalizing the servicing provider(AppxManager) - CDISMProviderStore::Internal_DisconnectProvider
    2015-08-05 18:23:41, Info                  DISM   DISM Provider Store: PID=5140 TID=8416 Disconnecting Provider: AppxManager - CDISMProviderStore::Internal_DisconnectProvider
    2015-08-05 18:23:41, Info                  DISM   DISM Provider Store: PID=5140 TID=8416 Finalizing the servicing provider(ProvManager) - CDISMProviderStore::Internal_DisconnectProvider
    2015-08-05 18:23:41, Info                  DISM   DISM Provider Store: PID=5140 TID=8416 Disconnecting Provider: ProvManager - CDISMProviderStore::Internal_DisconnectProvider
    2015-08-05 18:23:41, Info                  DISM   DISM Provider Store: PID=5140 TID=8416 Finalizing the servicing provider(AssocManager) - CDISMProviderStore::Internal_DisconnectProvider
    2015-08-05 18:23:41, Info                  DISM   DISM Provider Store: PID=5140 TID=8416 Disconnecting Provider: AssocManager - CDISMProviderStore::Internal_DisconnectProvider
    2015-08-05 18:23:41, Info                  DISM   DISM Provider Store: PID=5140 TID=8416 Finalizing the servicing provider(GenericManager) - CDISMProviderStore::Internal_DisconnectProvider
    2015-08-05 18:23:41, Info                  DISM   DISM Provider Store: PID=5140 TID=8416 Disconnecting Provider: GenericManager - CDISMProviderStore::Internal_DisconnectProvider
    2015-08-05 18:23:41, Info                  DISM   DISM Provider Store: PID=5140 TID=8416 Finalizing the servicing provider(OfflineSetupManager) - CDISMProviderStore::Internal_DisconnectProvider
    2015-08-05 18:23:41, Info                  DISM   DISM Provider Store: PID=5140 TID=8416 Disconnecting Provider: OfflineSetupManager - CDISMProviderStore::Internal_DisconnectProvider
    2015-08-05 18:23:41, Info                  DISM   DISM Provider Store: PID=5140 TID=8416 Finalizing the servicing provider(Edition Manager) - CDISMProviderStore::Internal_DisconnectProvider
    2015-08-05 18:23:41, Info                  DISM   DISM Provider Store: PID=5140 TID=8416 Disconnecting Provider: Edition Manager - CDISMProviderStore::Internal_DisconnectProvider
    2015-08-05 18:23:41, Info                  DISM   DISM Provider Store: PID=5140 TID=8416 Releasing the local reference to OSServices. - CDISMProviderStore::Internal_DisconnectProvider
    2015-08-05 18:23:41, Info                  DISM   DISM Provider Store: PID=5140 TID=8416 Disconnecting Provider: OSServices - CDISMProviderStore::Internal_DisconnectProvider
    2015-08-05 18:23:41, Info                  DISM   DISM Provider Store: PID=5140 TID=8416 Releasing the local reference to DISMLogger.  Stop logging. - CDISMProviderStore::Internal_DisconnectProvider
    2015-08-05 18:23:42, Info                  DISM   DISM Manager: PID=10592 TID=8772 Closing session event handle 0x198 - CDISMManager::CloseImageSession
    2015-08-05 18:23:42, Info                  DISM   DISM.EXE: Image session has been closed. Reboot required=no.
    2015-08-05 18:23:42, Info                  DISM   DISM.EXE: 
    2015-08-05 18:23:42, Info                  DISM   DISM.EXE: <----- Ending Dism.exe session ----->
    2015-08-05 18:23:42, Info                  DISM   DISM.EXE: 
    2015-08-05 18:23:42, Info                  DISM   DISM Provider Store: PID=10592 TID=8772 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
    2015-08-05 18:23:42, Info                  DISM   DISM Provider Store: PID=10592 TID=8772 Disconnecting Provider: FolderManager - CDISMProviderStore::Internal_DisconnectProvider
    2015-08-05 18:23:42, Info                  DISM   DISM Provider Store: PID=10592 TID=8772 Releasing the local reference to DISMLogger.  Stop logging. - CDISMProviderStore::Internal_DisconnectProvider

    Clean install, fully patched, cannot install .net 3.5. Any ideas?

    Wednesday, August 5, 2015 10:26 PM
  • What have work for a lot of people is REMOVE .net 4.6 install .net 3.5 and install .net 4.6 back
    Thursday, August 6, 2015 9:37 AM
  • I Tried all of the tips above with no luck, Same errors....What's new is the "Cumulative Update for Windows 10 for x64-based Systems (KB3081424)" Ends with Error  0x8000fff 
    Friday, August 7, 2015 12:26 PM
  • I managed to solve that error by following this solution:

      • Open the Registry Editor by clicking the Start button Picture of the Start button, typing regedit into the Search box, and then pressing ENTER. Administrator permission required If you are prompted for an administrator password or confirmation, type the password or provide confirmation.
      • In the left pane, find and double-click HKEY_LOCAL_MACHINE, and then click COMPONENTS.

      • Right-click COMPONENTS, and then click Export. By default, this file is saved to your desktop, but you can choose any folder.

      • In the File Name text box, type COMPONENTS. You have now created a back up copy of the registry values you're going to be removing.

      • In the right pane, search for PendingXmlIdentifier, right-click it, and then click Delete. PendingXmlIdentifier might not be listed.

      • In the right pane, search for NextQueueEntryIndex, right-click it, and then click Delete. NextQueueEntryIndex might not be listed.

      • In the right pane, search for AdvancedInstallersNeedResolving, right-click it, and then click Delete. AdvancedInstallersNeedResolving might not be listed.

    1. Restart your computer and then run Windows Update again

    Friday, August 7, 2015 3:55 PM
  • Hi Khaled,

    I am glad the issue has been resolved and thanks for updating. It will be very useful as a reference for the person who will come across the similar issue in the future.

    Best regards


    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Saturday, August 8, 2015 6:21 AM
  • There is no Components Key under HKLM. Can you be more specific?
    Thursday, August 27, 2015 3:43 PM
  • Hi Jeff,

    Same issue could be caused by various reasons. To understand the issue more clearly and get a better support, it is recommended to open a new case.
    It would attract other experts in this forum to join in the thread and it is easy to follow up the case. Thanks for your understanding and cooperation.

    Best regards


    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.


    Monday, August 31, 2015 1:55 AM
  • I had this same problem. We have System Center in our environment and so I don't go out to Windows Update and get redirected to our internal WSUS Server. In Group Policy, you have a lot of options to get around such a configuration as long as your IT department hasn't blocked you.

    Fire off the Local Group Policy Editor on Windows 10. You can find it easily from the Start Menu by typing group policy. Select Computer Configuration, Administrative Templates, System, Specify settings for optional component installation and component repair. You'll have several options available if you enable the policy. I specified the alternative source path since I have Windows 10 sources on a USB stick. I selected the \sources\sxs directory and I was able to then add support for .Net 3.5 and 2.0 so I could install the AD Map Tool.

    I hope this helps someone.

    Friday, November 20, 2015 5:05 PM
  • I ran into this same exact problem with the last Windows 10 insider build (14986 RS), but I found an easier workaround. I copied the entire SXS directory to my system drive and ran the DISM command, and .Net 3.5 installed without error

    For whatever reason Windows didn't want to install .net from the DVD mounted media. I think this may be an actual bug in the OS or perhaps PowerShell with the way it handles or trusts mounted media.

    • Proposed as answer by Robert_IT Wednesday, December 14, 2016 5:54 AM
    Wednesday, December 14, 2016 5:54 AM
  • I don't have components under Local Machine?
    Tuesday, August 1, 2017 12:24 AM
  • Took me an age to track this down but after trying all the other methods, this one worked.  In an elevated command prompt, type the following (replacing the drive letter for your media)

    dism /online /add-package /packagepath:D:\sources\sxs\microsoft-windows-netfx3-ondemand-package.cab
    Sunday, October 15, 2017 9:05 PM
  • Took me an age to track this down but after trying all the other methods, this one worked.  In an elevated command prompt, type the following (replacing the drive letter for your media)

    dism /online /add-package /packagepath:D:\sources\sxs\microsoft-windows-netfx3-ondemand-package.cab

    Hi Richadoodledoo,
    this worked for me too, thank you very much for sharing this help advice!

    Tuesday, October 31, 2017 5:42 PM
  • Hi,

    I used the following method that worked for me. I have posted the method below.

    https://social.technet.microsoft.com/Forums/en-US/20b47518-00cd-4896-8d54-090e54cf5126/can-not-install-net-framework-35-on-windows-server-2012?forum=w8itproinstall

    Thursday, November 16, 2017 4:11 PM
  • Wednesday, February 6, 2019 1:50 PM
  • This is the only thing that solved my issue, thank you.
    Wednesday, September 11, 2019 10:27 PM
  • There is no HKLM->COMPONENTS in my Windows 10 Pro Registry
    Thursday, March 12, 2020 7:07 PM