I just checked ... seems the original url works fine now. Thanks Emkay1001 !
Multiple errors in Event Viewer: EventID 131 from DeviceSetupManager since September 12, 2014
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.
139 additional answers
Sort by: Oldest
-
Anonymous
2015-09-13T23:51:20+00:00 You may wish to read amtinos comments here: If you check your event log your devices are updating 'albeit a few seconds later than they should be' this sure is a timing issue on the server:
amtinos comments: can be found on this link: https://social.technet.microsoft.com/Forums/en-US/04e31d9e-90ec-4d05-94ab-d2b53b026453/metadata-staging-failed-device-setup-manager-eventid-131-0x80070490
and state the following:
I am currently working with a Level 3 engineer at Microsoft on this issue: They have acknowledged this is a timing issue on their server, they have passed this to the back end team for a resolution.
This has been ongoing since 6th May 2015 - temporary fixes turning off driver updates and changing urls in the registry are not the answer. The answer is to ask Microsoft to work a little faster on resolving the timing issue they have on their server. I have been working with them since May, this is not system related. Please do not make un-necessary changes to your system.
You may receive event id 131 stating that metadata staging failed and devices did not update but if you read your event log in full, a few seconds later the devices do actually update. This really is a timing issue.
Event Log:
Select Applications and Services
Select Microsoft
Select Windows
Select Device Set up Manager
Now you should see the red errors with event id 131 and underneath that you will the successful update of devices a few seconds later.
This is 'a timing issue on the server' not hardware or software related.
Hope this helps
-
Anonymous
2015-09-14T17:23:41+00:00 Hi amtino,
As you may have see on the TechNet Post, Microsoft has declared that it is "Answered" and I am not disagreeing with them. I said so in a post FOR Windows 10.0 Pro Build 10532 here:
Thank You again for your efforts,
Best Regards,
Crysta
-
Anonymous
2015-09-14T17:31:16+00:00 It would be helpful to note that along with;
Event Log:
Select Applications and Services
Select Microsoft
Select Windows
Select Device Set up Manager
To add both "Admin" and "Operations"
Crysta
-
Anonymous
2015-09-14T19:07:43+00:00 fwiw..
I started having a 131 error and had a good idea what it was.. I just fresh installed again the 10532 build a few days ago.
Realtek card reader here. Microsoft gives a driver with the install that's not quite right - I had changed it to an older driver then remembered that realtek has a newer driver so installed it. I imagine that's when 131 error started.
I uninstalled its driver .. refreshed device manager a couple times ,, so I could uninstall the other two versions completely & following a restart to make sure it had no drivers... installed the newest and haven't had a 131 since. So just uninstalling all the 'other' drivers that were not being used anyhow - seems to have gotten rid of that error here.