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: Newest
Most helpful Newest Oldest
  1. Anonymous
    2015-08-22T14:34:41+00:00

    So this is pretty annoying, but is it at least harmless?

    I can't believe this issue has been in Windows for YEARS now without getting fixed!

    Was this answer helpful?

    0 comments
  2. Anonymous
    2015-08-08T04:13:08+00:00

    Hi Harkanwar Singh,

    I have this problem to on W 10.0 TH1 SR1 10240 and have had this problem throughout the history of 10240. I have file this Trouble Report.

    I hope somebody can figure it out.

    Best Regards,

    Crysta

    Was this answer helpful?

    0 comments
  3. Anonymous
    2015-08-07T17:30:29+00:00

    " After six weeks they recommended I wait for Windows 10 and all would be well"

    Welcome to the club! That's exactly how I wound up buying this

    'Vista like failure' that is w8p64.

    Now I'm suposed to do that again & waste another year of my productivity.

    I think not, even if it's "free for life."     I hear Linux just works.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2015-08-07T11:56:47+00:00

    For what is worth I'm seeing these errors on Windows 10 (public release version), so Microsoft hasn't addressed this problem.

    I was searching for information about it, and ran across this thread.

    I just knew this would happen.  I worked closely with Microsoft Level 3 support for six weeks from May onwards trying to get them to fix this issue.  They assured me they were acknowledging this as a serious issue.  After six weeks they recommended I wait for Windows 10 and all would be well.

    I refused the upgrade, I knew it would not resolve, all versions of Windows connect to the Microsoft server and they did acknowledge it was a server issue.

    I am going to get back to them know and suggest that once again they look for a fix.

    Cheers

    Was this answer helpful?

    0 comments