Link to home
Start Free TrialLog in
Avatar of jrslim
jrslim

asked on

"MMC has detected an error in a snap-in." When trying to manage Local Users and Groups.

MMC 3.0 v6.1 build 7600
Windows 2008 R2 Standard

In the "Computer Management" console when attempting to access user properties, or when attempting to add the "Local Users and Groups" snap-in  to a generic MMC  the following error occurs.

"MMC has detected an error in a snap-in. It is recommended that you shut down and restart MMC."

Giving two options:
1) Report this error to Microsoft, and then shut down MMC.
2) Ignore this error and continue running.
Avatar of Lukasz Chmielewski
Lukasz Chmielewski
Flag of Poland image

Or replace mmc.exe from the running machine.
Avatar of jrslim
jrslim

ASKER

Thanks,

"Try this hotfix
http://support.microsoft.com/kb/915797"

This hotfix is for 2003 pre sp2 and reates to the GP snap-in.


"Or replace mmc.exe from the running machine. "

The file is a protected system file with only "Trusted Installer" having delete rights.  Any thoughts on the repercussions of takling ownership or any other method of replacing this file?
Yes, I saw the 2003 after posting.
It might be a risk regarding the taking ownership. I'd try it.
If you click continue, the error is still ther, right ?
Avatar of jrslim

ASKER

The error clears and MMC stays open. The error recurs each time I attempt any user operation.
Avatar of johnb6767
Try renaming the following file related to lusrmgr.....

"%appdata%\Microsoft\MMC\"
Avatar of jrslim

ASKER

"%appdata%\Microsoft\MMC\"

The only file in that path is for server manager.
ASKER CERTIFIED SOLUTION
Avatar of Glen Knight
Glen Knight
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of jrslim

ASKER

Thanks Dem,  I will try that with the March patches.  Stay tuned.
Avatar of jrslim

ASKER

This solution has not been confirmed, due to scheduling issues for implimentation of the proposed fix.  I am closing the question and awarding full points on the presumption that the solution will work.