get-windowsfeature : The given key was not present in the dictionary

When you run the get-windowsfeature cmdlet in PowerShell on Windows Server 2012 you may see the following error

get-windowsfeature : The given key was not present in the dictionary.

At line:1 char:1
+ get-windowsfeature
+ ~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Get-WindowsFeature], KeyNotFoundException
    + FullyQualifiedErrorId : System.Collections.Generic.KeyNotFoundException,Microsoft.Windows.ServerManager.Commands
   .GetWindowsFeatureCommand

This seems to occur if there is a problem in the following registry key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ServerManager\ServicingStorage\ServerComponentCache

As this is just a cache registry key you can try renaming the key to ServerComponentCache.old and then re-running the PowerShell command or refreshing the view in server manager.

This recreates the key and rebuilds the server feature information.


- While you're here -
Why not check out our Windows Server Documentation and Audit Tool?


Comments

  1. Oldboy19 October 2015 at 08:12

    Thank you very much. I tried this and it fixed my issue. Amazing!

    ReplyDelete
  2. Unknown22 June 2016 at 08:48

    Same here, thanks man!

    ReplyDelete
  3. Francisco Javier Cintrón Olguín2 June 2017 at 12:38

    Thank you very much man!!.This solved my issue

    ReplyDelete
  4. Chris13 June 2017 at 03:50

    Thank you solved my issue

    ReplyDelete
  5. Unknown14 September 2017 at 12:33

    Ace - this is going in my personal list of useful tips that REALLY fix issues..

    ReplyDelete
  6. Ian Murphy24 January 2018 at 08:00

    Thank you. I don't think I would ever have found this particular one.

    ReplyDelete
    Replies
    1. David Homer24 January 2018 at 08:10

      No problems, feel free to check out our network documentation tool :)

      https://www.centrel-solutions.com/xiaconfiguration/network-documentation-tool.aspx?referrer=dblogad

      Delete
  7. Unknown13 March 2018 at 04:09

    Thanks, worked.

    ReplyDelete
  8. Anonymous16 May 2018 at 09:52

    It works! Brilliant, thank you.

    ReplyDelete
  9. Luis Miguel16 May 2018 at 12:50

    It helped me as well, thank you!

    ReplyDelete
  10. Unknown9 July 2018 at 00:23

    Thanks a lot,

    ReplyDelete
  11. Anonymous23 July 2018 at 21:43

    Such a simple fix to repair a big mess. Thanks for the post. It worked.

    ReplyDelete
  12. Unknown16 October 2018 at 15:24

    Thank you very much! You made my day!!!!

    ReplyDelete
  13. Onji18 October 2018 at 10:36

    You're helping people 5 years later! Worked perfectly. Thanks David!

    ReplyDelete
  14. Jeremy3 December 2018 at 09:03

    This helped me today. Thank you! :-)

    ReplyDelete
  15. Lead-lynx.com5 December 2018 at 10:20

    Worked for me as well. Thanks!
    -Server 2016 STD



    Error received (prior to reg fix):
    ****************************************************************
    get-windowsfeature : The given key was not present in the dictionary.
    At line:1 char:1
    + get-windowsfeature
    + ~~~~~~~~~~~~~~~~~~
    + CategoryInfo : NotSpecified: (:) [Get-WindowsFeature], KeyNotFoundException
    + FullyQualifiedErrorId : System.Collections.Generic.KeyNotFoundException,Microsoft.Windows.ServerManager.Commands
    .GetWindowsFeatureCommand

    ****************************************************************

    ReplyDelete
  16. Unknown29 March 2019 at 07:48

    Don't know if this was the same for everyone else or not but I had to make sure I exited out of Regedit before it would rebuild the key. So if, after you rename the key, it still doesn't work. Make sure that you've exited out of Regedit then try again

    ReplyDelete
  17. Unknown3 April 2019 at 01:25

    HI
    I resolved the issue with help of this post. Thank you

    ReplyDelete
  18. Unknown11 December 2019 at 03:44

    Thnks a lot...:)

    ReplyDelete
  19. Sosuke14 January 2020 at 08:15

    This allowed mt to continue working in a normal manner

    ReplyDelete
  20. BxN8822 September 2020 at 05:30

    Work! Thanks

    ReplyDelete
  21. Ivo Kruusamäe13 October 2021 at 07:39

    Thanks! Works!
    W2016

    ReplyDelete
  22. Unknown13 October 2021 at 14:14

    Worked for me on Server 2019. Thank you for this!

    ReplyDelete

Post a Comment

Popular posts from this blog

Windows Server 2016, 2019, 2022, Windows 10 and Windows 11: Date and time "Some settings are managed by your organization".

Image
When you're using the new "Modern" date and time settings in Windows Server 2016, 2019, 2022, Windows 10 and Windows 11 you may find that you can't set the correct date and time and the value "Some settings are managed by your organization". - While you're here - Why not check out our Windows Server Documentation and Audit Tool? The simplest way around this is to go back to the proper control panel using Start, Run, "Control.exe" and searching for "Set the date".  Within here you can set the date and time manually as required If you try and click the Change time zone button you may again get access denied... To resolve this open an elevated command prompt by right clicking the command prompt and selecting Run as Administrator  From there run the command rundll32.exe shell32.dll,Control_RunDLL timedate.cpl This will open the Data and Time control panel app elevated as an Administrator.
Read more

TFTPD32 or TFTPD64 reports Bind error 10013 An attempt was made to access a socket in a way forbidden by its access permissions.

Image
When you start the trivial FTP (TFTP) server application TFTPD32 or TDTPD64 you may see the following error Bind error 10013 An attempt was made to access a socket in a way forbidden by its access permissions. This can be because another application is using this port. The easiest way to check if (and which) application is using the port is as administrator run an elevated command prompt and enter netstat -anb > ports.txt Then open ports.txt in Notepad and search for :69, you'll quickly be able to see the process using the required port - While you're here - Why not check out our Windows Server Documentation and Audit Tool?
Read more

Windows Server 2019 desktop icons such as My Computer, Windows cannot access the specified device, path, or file.

Image
In Windows Server 2019 you may notice that the desktop icons such as My Computer are missing, however when you goto Personalization > Themes > Desktop icon settings You see the error Windows cannot access the specified device, path, or file. You may not have the appropriate permissions to access the item. The quickest way to resolve this is to ignore the modern UI and desk.cpl ,5 From here you can easily add the My Computer icon - While you're here - Why not check out our Windows Server Documentation and Audit Tool?
Read more