Display MMC Error Message

  • Thread starter Thread starter DaffyD®
  • Start date Start date
D

DaffyD®

While using Diskeeper, I got the error message:
"MMC has detected an error in a snap-in. It is recommended that you shut
down and restart MMC." It gave me 3 options and I chose
Continue running and always ignore errors with this snap-in, regardless of
user or session.

However, I would like to be able to see this message again because I plan to
do more troubleshooting and I want to see if it works. How do I reverse my
action--is there a place in the MMC I would go or is there a registry key I
need to edit? I'm running Windows XP SP3.
--
DaffyD® ( : []=

If I knew where I was I'd be there now.



__________ Information from ESET NOD32 Antivirus, version of virus signature database 4784 (20100118) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com
 
DaffyD® said:
While using Diskeeper, I got the error message:
"MMC has detected an error in a snap-in. It is recommended that you shut
down and restart MMC." It gave me 3 options and I chose
Continue running and always ignore errors with this snap-in, regardless of
user or session.

However, I would like to be able to see this message again because I plan
to
do more troubleshooting and I want to see if it works. How do I reverse
my
action--is there a place in the MMC I would go or is there a registry key
I
need to edit?
Click to expand...

Either there, or in an ini or cfg file in its Pgm Files or its Application
Data directory, but I'd bet it's in the registry. You could try hunting
for it (and then the appropriate setting) in the registry using regedit.

Or, if you've been using ERUNT, use a previous backup to restore the
registry to before you made that change.
 
I don't have ERUNT but you gave me the idea to try using System Restore,
which worked. But thanks for the tip on ERUNT, I just downloaded it.


Bill in Co. said:
Either there, or in an ini or cfg file in its Pgm Files or its Application
Data directory, but I'd bet it's in the registry. You could try hunting
for it (and then the appropriate setting) in the registry using regedit.

Or, if you've been using ERUNT, use a previous backup to restore the
registry to before you made that change.


__________ Information from ESET NOD32 Antivirus, version of virus
signature database 4784 (20100118) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com
Click to expand...



__________ Information from ESET NOD32 Antivirus, version of virus signature database 4785 (20100119) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com
 
DaffyD® said:
I don't have ERUNT but you gave me the idea to try using System Restore,
which worked.
Click to expand...

And that is a fine example of why you should not disable System Restore,
it can be a very useful tool at times. Erunt is a fine tool but System
Restore does more than just the registry.

John
 
Back
Top