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. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more

  2. Anonymous
    2015-09-13T16:05:50+00:00

    In regards to the event id 131 for Windows 10, I went to control panel, devices and printers, right click your pc icon, click device installation settings, click no let me choose what to do, uncheck box automatically get the device app and info provided by your device manufacturer. After that I did not get any more 131 errors.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2015-09-13T21:11:55+00:00

    In regards to the event id 131 for Windows 10, I went to control panel, devices and printers, right click your pc icon, click device installation settings, click no let me choose what to do, uncheck box automatically get the device app and info provided by your device manufacturer. After that I did not get any more 131 errors.

    Thank You 

    BR

    brclblnc,

    I have restarted twice and I have seen the same result. I am going to pass this on to TechNet's Allen Wang to see what he has to say about this solution. See that here:

    https://social.technet.microsoft.com/Forums/en-US/04e31d9e-90ec-4d05-94ab-d2b53b026453/metadata-staging-failed-device-setup-manager-eventid-131-0x80070490

    Best Regards,

    Crysta

    Was this answer helpful?

    0 comments
  4. Anonymous
    2015-09-13T22:53:07+00:00

    Thank you for passing on your findings to us all but note we have been using this temporary resolution since September 2014 after which Microsoft fixed the issue and then it resurfaced in May 2016.

    Turning off the automatic device set-up does temporarily resolve the event id 131 but turning off hardware updates permanently in this manner is not a good idea.  Your system will miss important updates and driver updates.  Please note this is not a fix.

    Please see all notes in this forum in particular pages 2 and 3 dating back as I say to last year.  http://www.eightforums.com/bsod-crashes-debugging/53670-continues-errors-startup-metadata-staging-failed-2.html

    You will note this has already been used as a 'temporary' fix.

    Hope this helps.  I am still working with Microsoft on a permanent resolution to the timing issue which causing this error, the timing issue is on their own servers.  This has already been confirmed.

    Was this answer helpful?

    0 comments