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

Anonymous
2014-09-14T08:35:45+00:00

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?

Windows for home | Previous Windows versions | Performance and system failures

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
2014-09-19T22:34:49+00:00

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

Was this answer helpful?

0 comments

139 additional answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2014-09-19T19:07:29+00:00

    It appears that all is fine for me today (I did not make any registry changes so all is as it was before the issue had surfaced).

    It seems that now the Microsoft servers respond with HTTP 302 status code instead of HTTP 301 which might contriubte to solving the issue.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2014-09-20T07:39:16+00:00

    Something is not working for me,  I turned the service back on since people said it is fixed.

    but now the service  hangs on every system start and reboot.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2014-09-20T07:45:24+00:00

    To what service do you refer to? Do you mean Metadata Refresh in \Microsoft\Windows\Device Setup scheduled task?

    Was this answer helpful?

    0 comments
  4. 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