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
    2015-08-29T13:49:48+00:00

    As I stated above, my machine seems to have no ill effects from this error.

    The issues I have all seem to be "engineered into w8pro64" like insomnia.

    My box is 95% stable, only blue-screening once every few months or less.

    Also I will not risk trying w10 as I need the 95% stable box to run my company,

    unless I could dual-boot upgrade - which AFAIK, MS will not allow.   j.Post

    at corporate PC updated on 29 after update came, fixed most of issues; (issue with start menu appeared after I tried move/delete windows.old folder); all work stable and perfect; (no blue screen yet);

    issue discribed here is same for both win8 and win10, maybe 7 too effected;

    (at home still win8 same issue; will update soon when appear free time);

    About dual-boot upgrade  ms do not have such feature, but they can't disable it, use third party tools you able to do this; I am sure it's legetible because you don't use both windows simultaniously....

    Was this answer helpful?

    0 comments
  2. Anonymous
    2015-08-29T13:20:15+00:00

    As I stated above, my machine seems to have no ill effects from this error.

    The issues I have all seem to be "engineered into w8pro64" like insomnia.

    My box is 95% stable, only blue-screening once every few months or less.

    Also I will not risk trying w10 as I need the 95% stable box to run my company,

    unless I could dual-boot upgrade - which AFAIK, MS will not allow.   j.Post

    Was this answer helpful?

    0 comments
  3. Anonymous
    2015-08-26T10:22:34+00:00

    Hi

    There is a temporary fix for this issue if you wish to change the forwarding url in your registry.

    You will find the details in this post.  Microsoft have been aware of this issue and have promised a fix several weeks ago.  I am trying to keep in touch with them but to be honest, communication appears to have broken down since the release of Windows 10 I have stopped getting responses to my emails which is very annoying.

    The temporary fix will stop your event log from filling up with this error.

    If you need further assistance please post back. 

    already changed DeviceMetadataServiceURL to http://dmd.metaservices.microsoft.com/dms/metadata.svc

    few days work good; then appears 200-202 event some time (maybe bad internet or that link don't have all needed for win 10 web or wcf api functions)

    yesterday 131 appers again Metadata staging failed, result={F9D342C3-51D8-5838-B433-76CC9B5BB016} for container '0x80072EFE'

    maybe ms again change link?

    Was this answer helpful?

    0 comments
  4. Anonymous
    2015-08-26T09:33:11+00:00

    Hi

    There is a temporary fix for this issue if you wish to change the forwarding url in your registry.

    You will find the details in this post.  Microsoft have been aware of this issue and have promised a fix several weeks ago.  I am trying to keep in touch with them but to be honest, communication appears to have broken down since the release of Windows 10 I have stopped getting responses to my emails which is very annoying.

    The temporary fix will stop your event log from filling up with this error.

    If you need further assistance please post back.

    Was this answer helpful?

    0 comments