XP Pro x64

[DasFox]

In x64 I have a Event ID 10016:

http://img143.imageshack.us/my.php?image=screenshot3md.jpg

Microsoft gives two soloutions to this problem:

http://support.microsoft.com/?kbid=899965

I did Grant the user permissions to start the COM component

But after rebooting I still got this error message and it did not solve it.

Here is what I did, to make sure this was correct.

By the screenshot I showed above, I went to the key:

HKEY_CLASSES_ROOT\CLSID\CLSID\{555F3418-D99E-4E51-800A-6E89CFD8B1D7}

Under the AppID it gives this key ----> http://img225.imageshack.us/my.php?image=screenshot1lm.jpg

{B1B9CBB2-B198-47E2-8260-9FD629A2B2EC}

Then under the "Component Services" - "DCOM Config" at the bottom I located the key, {B1B9CBB2-B198-47E2-8260-9FD629A2B2EC}

http://img156.imageshack.us/my.php?image=screenshot8sj.jpg

Then did the following steps, outlined by Microsoft:

If the AppGUID identifier is listed instead of the friendly name, locate the program by using this identifier.
7. Right-click the program, and then click Properties.
8. Click the Security tab.
9. In the Launch and Activation Permissions area, click Customize, and then click Edit.
10. Click Add, type the user's account name, and then click OK.
11. While the user is selected, click to select the Allow check boxes for the following items:
? Local Launch
? Remote Launch
? Local Activation
? Remote Activation
12. Click OK two times.
13. Quit Registry Editor.

When I completed this and rebooted, well I still ended up with the error message still in the Computer Manager, WHY? Microsoft says this is the fix, I have read others did the samething and it worked, but it did not for me, what's wrong here?

THANKS

 

[DasFox]

ok HANG TIGHT it seems like it's taking now. Possibly a service I disabled affected this, but this time from something I read that .NET Framework 1.1 is needed which I did not do before, and I have a few more services running, but I can't see how any of these would effect it.

Anyhow it's looking good at the moment.

If it craps I'll let you all know, hehe.

THANKS

 

[stash]

I don't know what kind of help you expect to get around here with all these questions you've been asking. You've obviously modified the OS in some unsupported manner, so there's no telling what the OS will do. There's no way for anyone to know.

Guess what the easiest way to get rid of these problems is? Reinstall the OS and leave all the services and whatever else you changed alone.

 

[DasFox]

I did not modify the OS at all. Once you have installed x64 from the get go, it has this issue, here is a screenshot showing DCOM error:

http://img314.imageshack.us/my.php?image=screenshot7jc.jpg

Anyhow I think I have it fixed using the first solution and then installing the .NET Framework, seems to do it for me, because just trying both of the solutions and not adding in the .NET framework, they don't work.

By the way this is on a fresh install of the OS and this happens as well, I've been running Windows 20 years I know what I am doing, but I don't know evereything that is why I ask questions. 😉

So no a fresh install with nothing touched does not get rid of the problem, because this is on a clean install with nothing touched. I always troubleshoot the OS once it is a clean fresh install, to see if there are any issues before moving on, especially with x64 given it's track record and it does have a few bugs that need cleaning up and this is one of them that I have found along with a few others.

THANKS