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

2014-09-20T17:42:55+00:00

Hi

I can also confirm that I restored my Laptop today and everything is working correctly with the original url:

Thanks to everyone who contributed to the thread and used the temporary fix.
Was this answer helpful?

0 comments No comments
Anonymous

2014-09-20T10:01:16+00:00

ah ty..no it was set to automatic.
Was this answer helpful?

0 comments No comments
Anonymous

2014-09-20T09:35:40+00:00

The Device Setup Manager is supposed to be set to Manual (Trigger Start). It is supposed to be started by Windows when Windows needs it (see more here) so by default it's not running.

Do you have the service set to Manual (Trigger Start)?
Was this answer helpful?

0 comments No comments
Anonymous

2014-09-20T09:21:32+00:00

I mean the device manager setup service. I turned it off to get rid of the metadata errors.
Was this answer helpful?

0 comments No comments