Thank you for being a valued part of the CNET community. As of December 1, 2020, the forums are in read-only format. In early 2021, CNET Forums will no longer be available. We are grateful for the participation and advice you have provided to one another over the years.

Thanks,

CNET Support

General discussion

Can't run eventvwr.msc

Oct 4, 2008 4:13AM PDT

Hello everybody.
I got a DELL XPS M1530 runing Windows Vista Home Premium SP1.
Yesterday i found out that the computer had a log(eventvwr.msc).
Today i wanted to open it again, but no matter how i try to run it or open it i get following message:

"MMC can't open the file C:\Windows\System32\eventvwr.msc

This may be because the file does not exist, it is not an MMC console, or was created by a later version of MMC. This may also be because you do not have sufficient access rights to the file."

I really need help, please somone answer soon!

Discussion is locked

- Collapse -
To run Event Viewer:
Oct 4, 2008 4:43AM PDT

"To run Event Viewer:

1. Open Computer Management by right-clicking the Computer icon on the start menu (or on the Desktop if you have it enabled) and select Manage. Navigate to the Event Viewer. "

More at http://www.petri.co.il/vista-event-viewer.htm

- Collapse -
But why can't i run it by runing eventvwr.msc?
Oct 4, 2008 5:05AM PDT

Yes, i found that out too, but why cant i run it anymore? what is the problem? how do i make it good again?

- Collapse -
Wish I was there.
Oct 4, 2008 5:14AM PDT

It could be UAC, a change in a patch to stop you from doing that. Glad you could still get to the logs the way Microsoft (forcibly?) wanted you to.

Frankly I'm in a very foul mood over Vista today. A simple batch file failed. It was UAC (again.)

For your part you could open the command line, and cd to where this eventvwr is to check your work. But I do not offer classes in command line use. That's something for you to read the books and build up your skills.
Bob

- Collapse -
Re: event viewer
Oct 4, 2008 5:12AM PDT

Does the file exist?
What are the creation and modification date?
What happens if you doubleclick it in Computer or Windows Explorer?

Kees

- Collapse -
Can anyone please atell me how to repair the error?
Oct 4, 2008 8:01AM PDT

the file exist but doesnt run. I can see the log but not by runing that program. I wuld wish to know how to repair the program, so i dont get the same error message all time!

- Collapse -
Try a command window.
Oct 4, 2008 8:09AM PDT

regsvr32 msxml3.dll

Research if that needs something different for Vista and did anyone run a registry cleaner?
Bob

- Collapse -
Article link
Oct 4, 2008 8:13AM PDT
- Collapse -
I managed somthing but didnt fix the problem
Oct 4, 2008 8:04PM PDT

ok, with administrator priviligies i managed to do what u described before(type regsvr32 C:\Windows\system32\msxml3.dll in the command prompt). But no solution to the problem =( it still cant open the eventviewer... =(((

BTW, does anyone know the service name of eventviewer?

- Collapse -
It's not a service issue.
Oct 4, 2008 11:41PM PDT

That much I can share. It's a registry issue or a dll that has become unregistered due to the registry cleaner.

-> ASK THE MAKER OF THE REGISTRY CLEANER HOW TO FIX THIS ONE.
Bob

- Collapse -
The mail has been sent
Oct 5, 2008 12:17AM PDT

I sent them the mail. Really hope they can come up with a solution, becuase this problem seems to be very strange =\
Anyways, thanks for the help until now Bob

- Collapse -
If you want to explore SERVICES
Oct 5, 2008 12:34AM PDT
- Collapse -
i did a registry clean up
Oct 4, 2008 8:53AM PDT

yes i did make a registry clean up =\

- Collapse -
That's the usual cause.
Oct 4, 2008 9:02AM PDT

If the above fixes it, break it again to retest it.

But it does point to a flawed registry cleaner.
Bob

- Collapse -
more errors
Oct 4, 2008 9:03AM PDT

i get the error 0x80070005 when i proceed to do that =(

- Collapse -
Sounds like UAC or "other" security.
Oct 4, 2008 9:04AM PDT

At least we know why it died.
Bob

- Collapse -
...
Oct 4, 2008 9:06AM PDT

is there anyway how to make it appear again? i hope somthing ist wrong with my computer =(

- Collapse -
I'll be blunt.
Oct 4, 2008 9:15AM PDT

UAC or other protection software causes the 8xxx 0005 code to show up. The reason for the failure is now quite clear, you shot up the OS with a registry cleaner.

Recovery can be as simple as turning off what is protecting the machine from being fixed. UAC, Norton or OTHER!!! I can't guess what you run. It's all up to you to share such details.
Bob

- Collapse -
Now reboted computer,
Oct 4, 2008 10:06AM PDT

I rebooted the computer, but for no help =( i rebppted it to before i installed the registry cleaner, so i cant understand what the problem could be :S

- Collapse -
registry cleaner type
Oct 4, 2008 10:08AM PDT

I was running a registry cleaner called Tune Up Utilities 2008

- Collapse -
what do u mean by turning of
Oct 4, 2008 10:10AM PDT

which program should i turn off u say? because yestreday i could run it perfectly, but now i have to shut down a program (UAC?) to run it?

- Collapse -
About UAC.
Oct 4, 2008 10:22AM PDT

I never write what UAC is. You could google that. But it and other PROTECTION SOFTWARE may have to be turned off to allow the DLL registration to succeed.

I'll also write you could use an VISTA ELEVATED COMMAND PROMPT but will not tell how. You can google that.

As to the registry cleaner. You've convinced me it's junk.
Bob

- Collapse -
Event Viewer
Oct 6, 2008 5:23PM PDT

capibarbaroja: I'm not quite sure why you're trying to run eventvwr.msc but I am wondering what happens when you click Start and type in Event Viewer in the Search box. Do you see Event Viewer listed in the results that come up? If so, press Enter and the Event Viewer should start. Keep in mind that TuneUp Utilities is a 30-day trial version.

R. Proffitt: I had to smile a little bit when I read your assessment of TuneUp Utilities 2008 as being junk because Download.com (part of CNet) gave it an editor's rating of 5/5. Happy Or perhaps you were just talking about the registry cleaner part of it. I prefer not to have programs messing with my registry myself so in a way I agree with you that the registry cleaner is junk. Wink

- Collapse -
I have tried everything, and it doesn't open
Oct 6, 2008 7:03PM PDT

yes it do appear in my search box, but, when i press enter, same error message appears. BTW im both contacting DELL(my computer manufacturer), and TuneUp Utilities, to see if any of them know about a solution. I just hope the registry cleaner didnt mess up with anything else :\

- Collapse -
In my first reply
Oct 6, 2008 10:26PM PDT
- Collapse -
Event Viewer
Oct 7, 2008 12:08AM PDT

capibarbaroja: I want to see if I can get on the same page here. You did do a search for "eventvwr" in Windows Explorer, correct? Is this how you were able to get the log to appear? I'm guessing that you were able to double-click on the "eventvwr" that has a type of Microsoft Common Console Document but when you double-click on the "eventvwr" that has a type of Application you get the error message, is that correct? Or is it only when you try to access the Event Viewer using the method that R. Proffitt suggested in the second post of this thread (an alternative method to what I suggested in my last post)? Also, are you logged in under an Administrator account?

I'm thinking that a System Restore may correct the issue. The only questions would be how far you would have to go back to solve it and what other changes would a Sys Restore make to your system. So I'm not suggesting that you do a System Restore at this time. Happy Since you are dealing with a software issue you may find that tech support guidance may not be free when you contact them. One last question: if you type in Event Viewer as I suggested but instead of hitting Enter right-click on the result that pops up and choose Properties you should see a target for that link. Go ahead and post that target here.

- Collapse -
I have tried everything out already =\
Oct 7, 2008 12:45AM PDT

Yes, I'm administrator!
Don't matter where I open it, wheter it is using command prompt(even running command prompt as administrator), or running it, or trying to open it from it file location, from the shortcut location, or the search result. The location is:

This is what is typed in properties:

Target:%SystemRoot%\system32\eventvwr.msc /s

and this is the actually location:

C:\Windows\System32\eventvwr.msc

I already rebooted my computer, but not so long back in time, so I might need to reboot it to longer back even. DELL answered saying they can't help me with the problem since the hardware doesn't have any ERROR, it is a software related problem(i did a hardware search yesterday). As R. Profitt says it might be a registry related problem. Is there any way to restore the registry, maybe? I don't want to make Dell Factory Image Restore, which is what DELL recommend since they can't help. Maybe I should contact Microsoft also? BTW waiting for the mail answer from TuneUp Utilities.

- Collapse -
Hint: Read above.
Oct 7, 2008 12:52AM PDT

The registry cleaner wiped out some dll registration. I noted a few but there are probably more. Sadly it is not as simple an issue as the path or whether the file exists.

- Collapse -
System Restore
Oct 7, 2008 5:41AM PDT

capibarbaroja: First I need to clear up some terminology. When you are saying "reboot" I am assuming that you mean doing a "system restore" and not just restarting the computer, which is the typical usage for "reboot." You asked whether there was any way to restore the registry and there are two ways: System Restore and the Dell Factory Image Restore (that's the case for both you and I as I have a Dell also). The Windows System Restore restores your settings to a previously saved point (a restore point). That includes the Registry settings but does not affect any data that you have saved such as pictures, e-mail, etc. The Factory Image Restore is a last resort option when nothing else works. It reformats your hard drive and restores it to the condition it was in when you received it from Dell. There is actually a third way but that is a possibility only if you made a backup of the registry first.

You also asked whether you should contact Microsoft. I would say that you will get the same response from them that you did from Dell, that is that they won't troubleshoot it for free. The good thing is that you have the two Restore options to work with.

I think we all agree that the Registry needs to be fixed so the Windows System Restore seems to be the best option unless you get a better response on your e-mail to TuneUp Utilities, which I'm not sure that you will. When you run System Restore you will see a handful of restore points to choose from when you first run it. There is a checkbox to "Show restore points older than 5 days" and you should probably click that. Under the descriptions for the restore points most of them will probably say "System: Scheduled Checkpoint" if you have Windows Update set to automatic. You can look through the descriptions to see if one of them mentions a program installation but the tactic I would use would be to go back through one by one, do a restore and then test to see if the event viewer is working again. This way you don't make a bunch of changes to the system all at one time. You can pick a random one but it's hard to tell what will happen sometimes. However if you do a week or two of the System Restores and it doesn't fix it, you may end up having to do the Factory Image Restore. It isn't terrible (I did it quite a few times myself trying to troubleshoot a weird issue) but you have to make sure that all of your data (pictures, e-mail, documents, etc.) is backed up first and that can be a job trying to make sure that you don't miss something.

So, just to make sure that you are using the System Restore here are the steps. Click Start => Control Panel => System and Maintenance => Backup and Restore Center => then click on the link that starts with "Use System Restore..." => click Continue if the UAC box pops up and Next on the first page of the System Restore Wizard => there you will see the restore points, choose one, click Next and then follow the wizard until the end.

If you find that the System Restore doesn't work or you have any questions, let us know. I can get you started if you need to do the Factory Image Restore. Like I said I've had some practice using it. Happy

- Collapse -
MSXML
Oct 7, 2008 5:48AM PDT

R. Proffitt: There are three MSXML versions that are used in Vista: 3, 4 and 6. Four if you include using version 5 which is used for Office 2007. Also, I had the same error code trying to reregister the MSXML dll's and found some good articles that point to that error code being a permissions issue inside the registry. However, I only saw a complete rundown for XP and not for Vista. They do differ somewhat and I didn't feel like messing with it for too long. Happy

- Collapse -
Yes there are.
Oct 7, 2008 8:03AM PDT

Oh what a tangled contraption Microsoft created here. The permissions issue is a non-issue. You know about UAC, elevated command prompt and more by now.
Bob