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-05-26T13:01:44+00:00

    Hello,

    Have the same issue in the Event Viewer started since May 5th. Have not modified the register yet

    suggested in one of the reply as still expect the solution you mentioned.

    Would appreciate if you get the reply from the Microsoft engineer as promised and post the information me as well.

    Thanks in advance, Ewa

    Will do, no problem.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2015-05-26T10:21:11+00:00

    Hello,

    Have the same issue in the Event Viewer started since May 5th. Have not modified the register yet

    suggested in one of the reply as still expect the solution you mentioned.

    Would appreciate if you get the reply from the Microsoft engineer as promised and post the information me as well.

    Thanks in advance, Ewa

    Was this answer helpful?

    0 comments
  3. Anonymous
    2015-05-22T08:23:10+00:00

    thanks a lot Markus for your suggestion

    the post by Saammy in eightforums (modification of the registry) solved my event ID 131 multiple errors, now I have 0 errors.

    ciao, Fabio

    This will resolve your issue but modifying the registry is merely a temporary fix which hides the real issue of the malfunctioning url on the Microsoft server. 

    Microsoft are currently investigating this issue and I am awaiting a response from them regarding their investigation.

    Kind Regards 

    Yes this is a temporary fix, this issue is widespread and affecting most operating systems.  Not everyone checks their event logs so they will not be aware of the issue.  I am informed Microsoft are working on a resolution.  Redirecting the url manually merely stops the logging of event ID 131 ' metadata staging failed'.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2015-05-22T08:17:18+00:00

    thanks a lot Markus for your suggestion

    the post by Saammy in eightforums (modification of the registry) solved my event ID 131 multiple errors, now I have 0 errors.

    ciao, Fabio

    This will resolve your issue but modifying the registry is merely a temporary fix which hides the real issue of the malfunctioning url on the Microsoft server. 

    Microsoft are currently investigating this issue and I am awaiting a response from them regarding their investigation.

    Kind Regards

    Was this answer helpful?

    0 comments