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: Newest
  1. Anonymous
    2016-01-15T19:23:20+00:00

    Double click the little red ab string icon    and it should pop a box to change the url provided you are logged into to windows as an administrative user.    If youre not.. ask who owns the computer to do it.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2016-01-15T18:51:51+00:00

    You can also make a backup copy of the registry key you are going to modify.

    You must be logged on as an administrator to perform these steps. If you aren't logged in as an administrator, you can only change settings that apply to your user account.

    Before you make changes to a registry key or subkey, we recommend that you export, or make a backup copy, of the key or subkey. You can save the backup copy to a location you specify, such as a folder on your hard disk or a removable storage device. If you make changes that you want to undo, you can import the backup copy.

    1. Open the Registry Editor by clicking the Start button , typing regedit into the search box, and then pressing Enter.‌  If you're prompted for an administrator password or confirmation, type the password or provide confirmation.
    2. Locate and click the key or subkey that you want to back up.
    3. Click the File menu, and then click Export.
    4. In the Save in box, select the location where you want to save the backup copy to, and then type a name for the backup file in the File name box.
    5. Click Save

    How do I actually change the URL?  Registry won't let me select and paste in a new URL.  If I click on the URL I get 'New' and then I can choose different formats.  When I choose 'string' for instance, it adds a new string to the bottom of the list.  How do I get this done.  If you tell me I need administrator permission, then where do I change my permission status?

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2016-01-06T10:26:27+00:00

    This is a timing issue on the Microsoft Server not forwarding the url fast enough.  The task to refresh the metadata does actually complete if you follow it through in your event log. However it is completing g a few milliseconds too late to atop the OS reporting ' Metadata staging Failed'   This started happening on 6th May 2015 and a lot of us have been using the temporary fix you suggest since then.

    Microsoft are fully aware aware of this issue and did fix it in October but after a week the url stopped forwarding again.

    The history of this issue goes back as far as September 2014 when it first started - Microsoft fixed the issue but it returned in 2015.   

    If you follow all the comments through uou will note I have been working with Microsoft on the issue since May.  However, they appear to have stopped responding.

    What we need is for more users to report the issue to get them moving.  It needs reporting at level 2 to get a response.

    Hope this helps. 

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

    Was this answer helpful?

    0 comments No comments