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-16T14:26:03+00:00

    similar here

    Was this answer helpful?

    0 comments
  2. Anonymous
    2014-09-16T07:48:52+00:00

    Hi

    I spoke to Microsoft last Friday and they denied there was an issue wiht their servers or the url:

    However, wanting to restore this laptop like yourself I decided to try again yesterday:  UK - 0344 800 2400.  The first technical support person just did not have a clue what I was talking about.  I am fairly aufait with computers and think I can explain things well but no he could not get to grips with it and he ignorantly put the phone the phone down in the end.

    Being persistent, I tried again and this time I got through to a human being who was as helpful as he could be:

    Suggestions I had already tried anyway:

    sf/scannow

    DISM Health Check

    remove everything in theTemp Folder

    reset internet explorer and wait for new data to be downloaded from Microsoft.

    None worked as I had already tried this, so people don't waste your time with all this, it will not resolve your issue.

    In the end he agreed the issue was the url:  He also stated that if people don't make them aware of issues, they cannot fix them.  He stated he would issue a ticket to inform the developers of the issue.

    The more people that report this issue perhaps the faster the fix/patch will arrive.

    Sorry I hate errors in my log and I am persistent when something goes wrong that I know I have not caused.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2014-09-16T01:03:30+00:00

    I wish Microsoft would fix the Error.  I don't like changing anything in the registry.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2014-09-15T23:12:38+00:00

    You see, I too am working on restoring a laptot. That is precisely why I would expect all devices to update and install as they are supposed to, and Windows Update to work properly. I need to have an up-to-date perfectly working system. Otherwise I would have just ignored event viewer messages and waited for them to fix the issue. But this is really taking too long, simply to update or change a little URL. I'm wondering if people at Microsoft have even realized there is a problem that most probably is not related to any recent updates, but to a change they made on their end. It's been quite a mess lately.

    And thank you to you too for your contribution to the post

    Was this answer helpful?

    0 comments