Error in MMC snap-in

[blockie]

I right click "Computer" and then left click "Manage" and I get the error:
"MMC has detected an arror in a snap-in and will unload it"
I clicked on "UNLOAD THE SNAP-IN and continue" and got the attached dialog which I then clicked on OK.
1. I don't know what a snap-in is. What is the difference between snap-in and plug-in?
2. Can I recover from this?

 

[gregrocker]

Try rebooting.

Run SFC /SCANNOW Command.

 

[blockie]

Ran sfc /scannow and found some errors that were fixed. Rebooted and still had problem.
Ran sfc /snannow again an did not find any errors. Rebooted and checked again. Still had the problem.
What next?

 

[A Guy]

Hello blockie, try this:

Start> In search box type Turn Windows features on or off> When the list loads, scroll down to Microsoft .NET Framework 3.5.1 and uncheck it> Click on OK and reboot> See if Computer management will open now

If so you have an issue with .NET, and we can try and tackle that

You might also try booting to Safe Mode and see if it launches OK there. If so, try a clean start to see if there is a conflict.

http://www.sevenforums.com/tutorials/69585-safe-mode.html

http://www.sevenforums.com/tutorial...ation-conflicts-performing-clean-startup.html

A Guy

 

[UsernameIssues]

Minor note regarding A Guy's instructions. The default W7 install makes the box to the left of Microsoft .NET Framework 3.5.1 look like this:



You will want to click one time on that colored box to clear it - then carry on with the steps that A Guy mentioned.



>What is the difference between snap-in and plug-in?
I do not know why MS called these applets snap-ins.
After completing A Guy instructions, please test opening snap-ins via:

Start > search for and run mmc.exe

Once the MMC window opens, use File > Open:




Then navigate to C:\Windows\System32 and scroll down until you see file with the .msc extension.



1) Let us know if you can open both of the snap-ins highlighted in the image above will open using the steps mentioned above.


Note: you can open services.msc via Start > search for and run services.msc, but that is a slightly different test that the steps mentioned above. I want to see if the mmc app will even start correctly.



2) The error image in your original post mentions, "Access to the path..." but we cannot see the full path. If you can make that error happen again, please press Ctrl+c while the error window has focus (on top of other windows and is selected). The will try and copy/paste/post the error text to the Windows clipboard - but it does not work for all error windows :-(

If the clipboard thing does not happen to work, please see if you can reshape/resize that error window. I'm just looking for ways to see the full path to the item in that error. Might have to look in the event logs.

 

[A Guy]

I am assuming the path is AppData\Local\Microsoft\Event Viewer\Settings.Xml . Shame on me if I am wrong

A Guy

P.S. If you have x64 version of 7, try the 32 bit console and see if that will work via UsernameIssues instructions

Start> In search box type Run> Enter> in Run box type mmc.exe /32> Enter

 

[NoelDP]

Let's go back to the SFC scan results - they may tell us more than just the pass/fail.
There may also be other things we can check...

Please follow the Windows Update Posting Instructions and post the requested data - it also applies here, and could give us some valuable information to work on.

 

[blockie]

First thing first/. I followed "The Guy" instructions with the following results:
Got the error msg trying all of the instructions.
Also ran the Safe mode and the trouble shooting instruction. Got the error.
ON my own I ran the trouble shooting with the Hide Microsoft........... unchecked and Disabled all services.Still got the error.

UsernameIssues

Open compmgmt.msc as instructed. NO error msg.
Open services.msc as instructed. Got error msg

Access to the path 'C:\Users\William\AppData\Local\Microsoft\Event Viewer\Settings.Xml' is denied.


Your right, GUY !!

The text above "is denied" gave me a clue. So I went to each folder in the path to see which one denied access. It turns out that the file "Settings.XML" is the one that did not give me access so I took ownership of that file and then went to "My Computer.......Manage" and the error did not show up.

If there is nothing further I consider the problem solved.
Thanks for all the help.
Bill

 

[A Guy]

Excellent detective work! Sometimes we need to remember to KISS. Good on ya

A Guy

 

[UsernameIssues]

Good job.

~~~
If there is nothing further I consider the problem solved.
Thanks for all the help.
Bill

I would suggest doing the things mentioned in post #7.

 

[blockie]

Items on post #7


SURP Ran it and installed one update.

sfc /scannow Ran it and NO bad files.

Windows Updates Ran it and installed one update. No errors.

Log Collection Following logs attached: CBS.zip

 

[A Guy]

I don't see the log attached

A Guy

 

[blockie]

I don't see the log attached

A Guy

Here it is again.

 

[NoelDP]

Here's the summary of your CheckSUR log..

Summary:
Seconds executed: 423
 Found 596 errors
  CSI Missing Deployment Key Total count: 82
  CBS Watchlist Package Missing Total count: 416
  CBS Watchlist Component Missing Total count: 98

There is no way we can attempt to repair this number of errors and hope to get a good result - you're going to have to do a repair install.
See this tutorial for guidelines....
http://www.sevenforums.com/tutorials/3413-repair-install.html?ltr=R

 

[blockie]

I went to the site recommended. Went to the appropiate page for W7 Ultimate SP1 32bit and it (the page) was not available.
I remember saome months, or a year, ago I did a repair install. I found the DVD that I put the ISO on. The name of the disk I found is GSP1RMCVLFRER_EN_DVD. If that is the correct disk I will use it for the repair install.
I'll wait for an answer from you experts before I do anything else.

 

[gregrocker]

If that is the same version of the one you installed then you can use it for the Repair Install. Does it have SP1? If you're not sure then try it to see.

Be sure you have a readable PRoduct Key on the COA sticker, or audit it if retail using Belarc Advisor . Read all of the other warnings and steps in the Repair Install tutorial above.

It may be awhile before the ISO links are back up, or they may never be. So I would hold onto the disk.

 

[blockie]

I did the repair install. Went fine.
I ran sfc /scannow.
Then I copied the cbs log to the desktop. zipped it and included in this post.
I'm not sure on how to read it. How does it look?
Bill

 

[NoelDP]

There was one minor error present which SFC has corrected - should be fine now.

Good luck with the new install - don't forget all the updates!