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
    2016-03-10T19:51:25+00:00

    Yes I have spent many months working with Microsoft on this issue, so rest assured they are aware of it and yes they did fix it in October a coupe of weeks before daylight saving but then it went by the wayside again shortly after.  Like you, I am waiting to see what happens when daylight saving changes this month but I am not holding out much hope of a [permanent fix as recently the message from Microsoft was 'support for Windows 7 and Windows 8 finished on'12th January 2016, so I guess that says 'tough' what isn't fixed wont be fixed for all users of these 2 operating systems.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2016-03-10T11:43:07+00:00

    I had this issue on Windows 8.1 and after upgrade still have it on Windows 10

    This issue was fixed until we came off of British Summer Time last year - it will be interesting to see what happens at the end of March when we go back to British Summer Time. Wonder if it will be "fixed" again

    for me any auto time servers changes never helped

    (it appears rare based on devices and drivers that you use)

    as upper people post only reg trick with direct URL resolve issue;

    Was this answer helpful?

    0 comments
  3. Anonymous
    2016-03-10T11:14:05+00:00

    I had this issue on Windows 8.1 and after upgrade still have it on Windows 10

    This issue was fixed until we came off of British Summer Time last year - it will be interesting to see what happens at the end of March when we go back to British Summer Time. Wonder if it will be "fixed" again

    Was this answer helpful?

    0 comments
  4. Anonymous
    2016-02-26T16:21:29+00:00

    Thank you kindly - this worked as a charm.

    Nick B.

    Was this answer helpful?

    0 comments