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
    2016-01-06T07:42:13+00:00

    Fix for Event ID: 131 Metadata staging failed Error:

    This error is occurring in Windows 10 (and probably previous versions of Windows) because of an incorrect URL in the Registry for the key:  HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Device Metadata. The URL should be: http://dmd.metaservices.microsoft.com/dms/metadata.svc .

    Fix:

    1.  Open Registry Editor (Run*>regedit>*Enter or type regedit in the search box and press Enter).

    2.  Go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Device Metadata by just opening the folders sequentially or going to Edit>Find and typing in DeviceMetadataServiceURL and then pressing Enter.

    3.  On the right side of the screen, right click on DeviceMetadataServiceURL and click Modify. Highlight or delete the current URL and paste the following URL in: http://dmd.metaservices.microsoft.com/dms/metadata.svc. Press OK and close the Registry Editor.

    4.  Reboot and these Metadata errors should be gone.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2015-12-06T09:51:03+00:00

    To reassure you, the event id 131 is not caused by turning off windows updates for device drivers.  It is caused by a timing issue on the Microsoft server.  Microsoft are aware of this. 

    Turning this off will only raise more errors because as you say you are blocking the updates.

    If updates are turned on they do actually run but a few milliseconds too late to prevent id 131 being logged.

    If they are turned off then you will see more errors such as 'Windows Update has been blocked by Policy'  

    You may also see event id 200, 201 and 202.  In this instance the process doesn't complete at all because you have blocked it.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2015-12-06T07:28:06+00:00

    I have found that it's caused by blocking windows from checking for drivers on the windows update site 

    Access to drivers on Windows Update was blocked by policy

    I have 256 event ID: 131's in the last 7 days and that ^^^ msg is for all of them 

    It happens because I don't want MS messing with my device drivers like replacing the new AMD Catalyst driver 15.11.1 with an older version  which it quite happily does if left unchecked and I don't know why it keeps trying to check when it been told not to

    Was this answer helpful?

    0 comments
  4. Anonymous
    2015-12-02T16:44:56+00:00

    The NIST  server gave me a problem too, now I use the North American Pool in the US.

    pool.ntp.org so far so good.

    UPDATE: Actually that one is timing out now after many weeks of working fine.

    Was this answer helpful?

    0 comments