You may find yourself in a situation where an MMC snap-in errors out, and doesn’t allow you to reconfigure, fix, or use it. It becomes unusable.
In my case, this occurred on a system where I was trying to use the WSUS (Windows Server Update Services) snap-in, and it was configured for an old server that didn’t exist anymore.
When opening the WSUS MMC snap-in, it would report an error, give me the option to unload (which didn’t work), and do nothing else. There was no way to use or reconfigure it.
The Fix
To resolve this, you need to clear your local configuration for the snap-in. Your user profile contains all MMC snap-in information and configuration in the following directory:
C:\Users\USERNAME\AppData\Roaming\Microsoft\MMC
When browsing, here’s what it looks like on my system:
In my case, deleting the “wsus” file, reset the MMC snap-in, and allowed me to use it again and configure it for a new server.
Let me know if this helped you!
It worked perfectly for me! Clean and clear explanation.
Thank you!
Worked a charm, thanks! Would not have expected that the WSUS config was stored per user.
AWESOME! This problem has been bugging me for months. Thank you so much!
Thanks a lot!!!
Did not work for me, slightly different error and setup. Event viewer declaring snap-in error.
Windows 8.1, not a domain PC, files not existing in said folder: wsus, dsa, dnsmgmt.
Possible snap-in, re-install error trying to fix other errors on PC.