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-10-30T18:25:07+00:00

    oh man... you are -unfortunately- right!

    I was ok after changed server at beginning of october, now one-three-one is back again :(

    Was this answer helpful?

    0 comments
  2. Anonymous
    2015-10-30T18:02:27+00:00

    yes Event ID 131 has returned on my system today also after  almost 3 weeks of clean working.

    Microsoft this is poor.....

    Was this answer helpful?

    0 comments
  3. Anonymous
    2015-10-30T17:53:54+00:00

    I have been running windows successfully on the correct time server and the correct url in the registry since 2nd October when Microsoft assured me the timing error had been fixed.

    I agree it appeared it had and my systems were working flawlessly and I finally accepted after six months of begging, they had finally answered my requests.

    However!    at 1am on 29th October during maintenance I note that on all 3 operating systems I have, the 131 event ID returned.

    I have tried changing the time server to nist.gov - doesn't work for me.

    I find it hard to believe that Microsoft fixed this on 2nd October and then a few days after 'daylight saving'   it suddenly re-appears.

    I have reverted back to the alternate url in the registry and all is well.

    I for one will never change my systems back to the correct url, I cannot trust Microsoft anymore with their open ended promises and this merely racks havoc with my systems.

    I am sure all of you will note the Event ID 131 has returned.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2015-10-11T13:50:08+00:00

    Click on time and date at bottom right of screen.

    select Internet time

    change the server in the drop down list from windows time to nist.gov.   Update the time.

    thanks, It worked for me.

    I made the suggested server change, and after that change (1 week ago) no more event id 131  raised.

    Was this answer helpful?

    0 comments