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

  3. Anonymous
    2015-05-13T12:29:55+00:00

    Right click on Windows logo in the bottom left corner, then select "run" and type "regedit" (without quotes). Click "OK". Regedit will open. Now go to "Edit" (it's in the top left corner of regedit window next to "File"), click on it, and then click on "Find...". Type "DeviceMetadataServiceURL" (again without quotes) then click "Find next". Wait a few seconds and you can now see "DeviceMetadataServiceURL" in the right panel. Right click on "DeviceMetadataServiceURL" and select "Modify...". Copy and paste the new address "http://dmd.metaservices.microsoft.com/dms/metadata.svc" (always without quotes) in place of the old one. Before executing this last passage, you may want to copy the old address and save it in the notepad, in case you should experience any problems (there shouldn't be any at all) and you'd like to revert back to your previous setting. Now close the registry and you are done. Restart system. Event viewer and everything else should be finally fine.

    Blessings and all the best 

    This worked great for me. Now whether I plug a new USB peripheral in or start the PC, I no longer get this 131 Event Error. Thanks Marcus!

    This is merely a temporary fix, we used these in September when the url was malfunctioning.  The main objective here is to get the forwarding url fixed.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2015-05-13T18:02:58+00:00

    This is not an answer to the malfunctioning url sorry - all you are doing is tampering with the registry and putting in a direct link.  This is a temporary fix and when the correct url is repaired you will have future issues with your operating systems-  this is merely a temporary fix and should be quoted as an 'answer'

    Was this answer helpful?

    0 comments