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
    2016-03-12T02:00:00+00:00

    AM, do you know if that "finish" includes 8.1 Pro as well as 8 ?

    Maybe that's why MS level 3 TS abandoned me.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2016-03-12T10:28:13+00:00

    Happens with win10 too, so its .. just one of those things.

    sometimes changing in device manager the hard drive controller driver version can fix it here in win10.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2016-03-13T04:34:04+00:00

    To the best of my knowledge Windows 8.1 will continue to receive updates and support.  IE11 will continue to receive updates.  Windows 8 runs on IE 10 and will not receive any further security updates or support.

    If anyone knows any different I will stand corrected.

    Kind Regards

    Was this answer helpful?

    0 comments
  4. Anonymous
    2016-03-30T16:05:14+00:00

    Not seen the 131 error since the change to British Summer Time - what is also interesting is that the 200 to 203 errors on starting Windows 10 have also disappeared since the time change - are they connected? Anyone else seeing this?

    Was this answer helpful?

    0 comments