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 No 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 No comments

139 additional answers

Sort by: Most helpful
  1. Anonymous
    2015-10-09T10:53:41+00:00

    A new resolution to the issue without changing the url in the registry or touching anything we shouldn't really:

    Click on time and date at bottom right of screen.

    select Internet time

    change the server in the drop down list from windows time to nist.gov.   Update the time.

    Your system should now be error free:  I have tested this by refreshing all hardware devices etc.  all OK.

    The nist.gov time server is obviously correct to the millisecond and the window time server is not! 

    hard to belive that ms do such bugs;

    will try to reproduce 131 and change time server;

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2015-10-08T18:52:08+00:00

    A new resolution to the issue without changing the url in the registry or touching anything we shouldn't really:

    Click on time and date at bottom right of screen.

    select Internet time

    change the server in the drop down list from windows time to nist.gov.   Update the time.

    Your system should now be error free:  I have tested this by refreshing all hardware devices etc.  all OK.

    The nist.gov time server is obviously correct to the millisecond and the window time server is not!

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2015-09-15T06:04:34+00:00

    this one solution - "In reply to Marcus_83's post on September 15, 2014"

    ["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 "]

    • is good and fixed inner ms issue that not allow redirected URLS; it fix most of issues;

    also I had remove all inactive devices via devicemanager (view->show hidden devices); and remove all hidden/inactive devices with drivers;

    3)

    then found that USB3.0 use ms driver; so reinstalled eaton drivers from gigabyte site, still wrong ms driver, so reinstalled in cimpatibility with win 8 and all installed fine;

    MS not able to retest and keep fresh DB of all drivers, etc; and sometimes older driver work more better under 8 or 10 windows; sometimes ms provide very bad and unusable drivers (for example under win10 I installed beta driver for AMD hd7870 because updated driver by ms was wrong and had terrible perfomance in apps with hardware acceleration; and it's wide ms issue, that often appears in win7 and for other VGA card AMD and NVIDIA);

    so my advice:

    • manually update drivers from offsite of MB manufacturers and from AMD/NVIDIA/intel sites;
    • if device old and had not driver for win 10(or 8 etc) setup it in compatibility mode...

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2015-09-15T00:42:42+00:00

    fwiw..

    I started having a 131 error and had a good idea what it was..  I just fresh installed again the 10532 build a few days ago.

    Realtek card reader here.  Microsoft gives a driver  with the install that's not quite right - I had changed it to an older driver then remembered that realtek has a newer driver so installed it.     I imagine that's when 131 error started.

    I uninstalled its driver .. refreshed device manager a couple times ,, so I could uninstall the other two versions completely & following a restart to make sure it had no drivers...  installed the newest and haven't had a 131 since.    So just uninstalling all the 'other' drivers that were not being used anyhow - seems to have gotten rid of that error here.

    Hi there and thanks for sharing your findings:

    If you wish to check that you have resolved your issue there is a quick way:

    Control Panel

    Hardware and Devices

    Select Devices and Printers

    Right Click on a Blank Space and Select Refresh

    Now check your event viewer for event ID 131 - are you still error free?

    I have tried your method and many many others since May and as yet it remains a Microsoft server error with a timing issue.

    I would welcome your results

    Was this answer helpful?

    0 comments No comments