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-05-29T09:44:07+00:00

    Hello Robert,

    Would like to add that when look into the Event Viewer - Application and Services - Microsoft - Windows - DeviceSeptupManager - Admin. there are listed the errors Metadata staging failed reg. seperate device and after there is the information that the same device has been served. So it looks as there is a delay in this service - firstly some errors are generated but finally the devices are served.                                        

    Such issues in the Event Viewer have found when open the laptop and also after regular maintenence done.

    The same result -errors have found after done following operation :

    in Task Scheduler -> Microsoft -> Windows -> Device setup have run the Metadata Refresh task

    and after this have checked the Event Viewer - get the same result errors as before.

    What can be the reason of this erors - delays in service and how to fix it. There were some suggesions of register modification but not sure if it is so safety.

    Such errors have benn found since May 5th-6th and not earlier.

    Would appreciate for you comments.suggestions.

    Best regards,

    Ewa

    Was this answer helpful?

    0 comments
  2. Anonymous
    2015-05-29T08:46:01+00:00

    Related Content

    https://social.technet.microsoft.com/Forums/en-US/03ec3890-702e-46dc-b112-607346e5db0e/serious-broken-url-on-microsoft-server-event-id-131-metadata-staging-failed?forum=ieitprocurrentver

    <quote>

    A redirect:

    http://go.microsoft.com/fwlink/?LinkID=252669&clcid={BF363439-5478-BCF0-01D9-12B8F31CEEBC}

    http://dmd.metaservices.microsoft.com/dms/metadata.svc

    Now all we need to do is figure out what the parameter name for the return code should be and then append that and the 0x490 and I bet we will get something instead of an HTTP 400.

    </quote>

    Well I will keep exploring, if you find a resolve before any one else, do post back, and I appreciate all your assistance, advice, suggestions and comments.

    Thank you

    Was this answer helpful?

    0 comments
  3. Anonymous
    2015-05-29T02:51:46+00:00

    Related Content

    https://social.technet.microsoft.com/Forums/en-US/03ec3890-702e-46dc-b112-607346e5db0e/serious-broken-url-on-microsoft-server-event-id-131-metadata-staging-failed?forum=ieitprocurrentver

    <quote>

    A redirect:

    http://go.microsoft.com/fwlink/?LinkID=252669&clcid={BF363439-5478-BCF0-01D9-12B8F31CEEBC}

    http://dmd.metaservices.microsoft.com/dms/metadata.svc

    Now all we need to do is figure out what the parameter name for the return code should be and then append that and the 0x490 and I bet we will get something instead of an HTTP 400.

    </quote>

    Was this answer helpful?

    0 comments
  4. Anonymous
    2015-05-26T13:01:44+00:00

    Hello,

    Have the same issue in the Event Viewer started since May 5th. Have not modified the register yet

    suggested in one of the reply as still expect the solution you mentioned.

    Would appreciate if you get the reply from the Microsoft engineer as promised and post the information me as well.

    Thanks in advance, Ewa

    Will do, no problem.

    Was this answer helpful?

    0 comments