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: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2015-10-09T13:40:55+00:00

    got 123 error hour ago:

    The DSM service was delayed by 30 seconds for a driver query/download/install on device 'SCSI\CDROM&VEN_MSFT&PROD_VIRTUAL_DVD-ROM\2&1F4ADFFE&1&000002'

    will wait for 131, etc and then try turn on time sync ...

    Was this answer helpful?

    0 comments
  2. Anonymous
    2015-10-09T13:09:09+00:00

    Microsoft time server check often doesn't work the first time.. takes a long time to time out compared to actually checking time.     

    Maybe its during that hang time is when 131 metadata and the #200 201 etc errors processes are checking home.

    But then again, why would the alternative address not have the same errors ? 

    I'm using the alternative url and no errors ever.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2015-10-09T12:21:05+00:00

    didn't change time server; (change time automaticaly is disabled years at my PC)

    reverted link to old one;

    try refresh several times still no error;

    will try to reproduce 131 and then try time trik to be sure;

    Was this answer helpful?

    0 comments
  4. Anonymous
    2015-10-09T12:01:44+00:00

    Worked a treat, thank you:

    To test:

    Control Panel

    Harware and Devices

    Click with mouse on any blank space

    Click refresh

    You should no longer get event ID 131 Metadata staging failed.

    Amazing! thanks amtino

    Was this answer helpful?

    0 comments