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
    2014-09-15T00:14:28+00:00

    I too was afraid to change the registry, but just did it and now all is finally working fine. Basically what you're doing is just changing the address devices metadata are stored to (from go.microsoft.com/fwlink/?LinkID=252669&clcid=0x409 to *http://dmd.metaservices.microsoft.com/dms/metadata.svc*), for Windows to go and check for them. As Saammy found out about the domain, what happened I think is Microsoft changed this address but forgot to update systems accordingly

    http://www.eightforums.com/bsod-crashes-debugging/53670-continues-errors-startup-metadata-staging-failed-3.html#post427682

    Was this answer helpful?

    0 comments
  2. Anonymous
    2014-09-14T23:43:15+00:00

    It would appear this is a global issue.

    Started on my HP Laptop on Thursday 11/09.

    Tried everything, even system restore and reinstalling OS from CD.  On boot I get intermittent errors from 2 to 7.  On re-boot I get 7 errors all the same meta data related as yours.

    I spent over an hour on the phone with Microsoft on Friday who stated that I was unable to connect to the WMIS server and to try again in 24 hours when MSDN  ( Microsoft Developers had finihsed working on the server)

    Issue still persists today and I have checked 3 other Laptops in the household and I Desktop PC and they all have this issue.

    Relieved to eventually see I am not an isolated case who has several trashed PCS or some mad virus.

    Keep the post up-dated if the event goes away or you find a sensible resolution.  I do not think changing the registry is the answer here.

    The registry should not be changed manually it can have on going consequences.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2014-09-14T22:35:38+00:00

    Please look up this thread on Eightforums for a possible solution, especially post by Saammy on page 3 http://www.eightforums.com/bsod-crashes-debugging/53670-continues-errors-startup-metadata-staging-failed-3.html

    Hope it helps

    Was this answer helpful?

    0 comments
  4. Anonymous
    2014-09-14T17:52:36+00:00

    Thank you.

    Just out of curiosity - if you would plug in a USB device to your computer now - would the error message in Event Viewer appear? I just plugged my USB stick and get this error.

    If this does not happen for you, could you please check if the image you are using is having the latest Windows Updates? Perhaps the issue had started after this week Windows Updates were installed.

    Was this answer helpful?

    0 comments