Multiple errors in Event Viewer: EventID 131 from DeviceSetupManager since September 12, 2014

Anonymous

Hello,

Since September 12, 2014 I receive multple errors in Event Viewer from DeviceSetupManager.

Sample error looks like this:

Metadata staging failed, result={E9031C57-C25D-8227-E390-3662BD05D0CB} for container '0x80070490'

This error occurs when the Metadata Refresh in \Microsoft\Windows\Device Setup scheduled task is run or when accessing Control Panel -> Devices and Printers when Device Installation Settings are set to "Recommended" or are set to "Automatically get the device app and info provided by your device manufacturer".

What I believe happens is Windows attempts to contact a Microsoft web server to obtain additional information about a device (custom icon for example) and this process had started to fail for me since September 12, 2014. More details on it can be found on this page.

Looking at the Debug logs of Microsoft-Windows-DeviceSetupManager I can see the following error:

Job (13) has completed for device container '{3c7878f1-bc70-523d-b17c-7aaf5253f81a}', status=Hard Error

Looking at the network traffic, I can see communication using HTTP protocol with Microsoft server which returns HTTP 301 (page has been moved).

SFC /scannow returns no errors. All the latest Windows Updates are installed. I've already tried to remove %PROGRAMDATA%\Microsoft\Windows\DeviceMetadataCache folder to no avail.

Does anybody else see this error message and what can I do to fix the problem?

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

Answer accepted by question author

Anonymous

I just checked ... seems the original url works fine now. Thanks Emkay1001 !

0 comments

139 additional answers

Anonymous

2015-11-20T21:24:53+00:00

I changed the time server, but not to any of the nist.gov ones. None of them worked properly for me here in the UK. Hardly surprising if they are across the pond. So I googled internet time servers here and added this to the server list, ntppub.le.ac.uk. Leicester University internet time server.

No more event ID 131.
Was this answer helpful?

0 comments No comments
Anonymous

2015-12-02T12:08:23+00:00

I changed the time server, but not to any of the nist.gov ones. None of them worked properly for me here in the UK. Hardly surprising if they are across the pond. So I googled internet time servers here and added this to the server list, ntppub.le.ac.uk. Leicester University internet time server.

No more event ID 131.

I am in the UK, but changing the time server to ntppub.le.ac.uk does not work for me.

However, I do believe this is a timing issue that users will be permanently chasing around in circles to fix.

It requires fixing in the Operating System, by Microsoft.
Was this answer helpful?

0 comments No comments
Anonymous

2015-12-02T14:24:53+00:00

This is indeed a timing issue on the Microsoft Server, the only successful fix at present is the alternative Url alteration in the registry.

Microsoft are fully aware of this issue and have been since May. I have been communicating with them at Level 3 and a few weeks ago they fixed it prior to daylight saving. Unfortunately one week later it went behind time again and reproduced event ID 131.

The task does actually complete but it does so a few milliseconds too late to stop the event being registered in the event log.

I guess it is a case of using the alternative Url or sitting back and waiting for the next attempt Microsoft may r may not make to fix it.

I am staying in touch with them.
Was this answer helpful?

0 comments No comments
Anonymous

2015-12-02T16:44:56+00:00

The NIST server gave me a problem too, now I use the North American Pool in the US.

pool.ntp.org so far so good.

UPDATE: Actually that one is timing out now after many weeks of working fine.
Was this answer helpful?

0 comments No comments