Event Error 10010

Hi Noel

I agree with you !  I haven't found any Issues, it appears to be cosmetic. BUT Event Errors are annoying to see them, I'm sure Microsoft knows that that the problem exist and it seem many people on the web with the same issue.  I bet if there was errors with the Windows Store there would be a fix  the next day.

I had my SSD brick on me so I reinstalled on my replacement SSD yesterday now instead  of the 2 that I had now i got 4 now, twins of each of what I had before

I tried several  things but only to find the settings are in order, so I guess we have to wait and see what happens..

Tuco

Hey Ronnie,

No disrespect intended, but your answer is insufficient.  People should NOT be advised to just ignore errors!

There are those of us who would prefer our event logs to be clear of all errors, which would indicate the system is running entirely properly.  It has been possible to accomplish this in the past!

There's some evidence that the error message "

The server {

BF6C1E47-86EC-4194-9CE5-13C15DCB2001

} did not register with DCOM within the required timeout." is related to SkyDrive (specifically, "Automatic Maintenance task to enable SkyDrive file sync to make progress while in Connected Standby")

On the system on which I see this message I don't use nor want SkyDrive support.  It is set up with a local account.  The above message implies some part of the SkyDrive software is still trying to run.

What do I have to disable to stop these events from happening once a day?

-Noel

Hi,

Some info to add to Ronnie's good tips :

MyEventViewer - Free - a simple alternative to the standard event viewer of Windows.

TIP - Options - Advanced Filter allows you to see a time frame instead of the whole file -

set it to a bit before and after the time of the EVENT.

http://www.nirsoft.net/utils/my\_event\_viewer.html

This utility also allows you to easily clear (remove) one, several, or all of the Event Viewer logs. Only

real reason to clear them would be to make it easier to read any new Events - those recorded after

clearing.

TechNet - Event Viewer

http://technet.microsoft.com/en-us/library/cc766042.aspx

TechNet - Clear an Event Log

http://technet.microsoft.com/en-us/library/cc722318.aspx

Hope this helps.

Rob Brown - Microsoft MVP <- profile - Windows Expert - Consumer : Bicycle <- Mark Twain said it right.

Ronnie  Thanks

Hi

Sometimes the way the Event Viewer works can be incomprehensible to someone looking at it for the first time.

You did mention that "There seems to be no operational problem other then the Errors showing up in the Event Viewer".

This was the reason why I mentioned that these timing errors are usually noted in Milliseconds. This time period is usually so short that the end user will not even notice any effects in the software.

The Event Viewer is designed to report these events as errors, even though the event may not create any error messages or noticeable effects in the UI.

The errors may be created when Windows Defender runs, but the exact cause would require running special developer testing tools to pinpoint the exact problem. It could be anything, such as another software program or driver that may be using a large amount of resources.

This is why I recommended that this error can be safely ignored.

I also recommend that you spend some time looking through the Event Viewer and note the errors that you find. You will probably be surprised to find thousands of these errors in a typical system.

Regards