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: Most helpful
  1. Anonymous
    2015-08-26T09:30:56+00:00

    FYI I also have another problems in Win 10 Pro. No App Store, no OneDrive, cannot do a "repair install" with ISO, cannot go back to Win 8.1........

    Tommy

    had same issue after update (diccided to remove/move windows.old folder there where sysmklink or ntfs link to user folder and what do you think explorer start to move app data and explorer data that in use :( it was big fake.... and move folders back under other user didn't help only reregister metro apps script help); found solution in other topic:

    Do backup any data you’ve saved in the Modern Apps  as all of them will be re-installed. Desktop software and apps won’t be affected though.

    1. Open Windows PowerShell as Administrator
      1. Right click Start button
      2. Choose Command prompt (Admin)
      3. Key in Powershell in the black window and hit Enter
    2. Paste the following command in the Administrator: Windows PowerShell window and press Enter key:
       Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}
      
    3. Wait for PowerShell to execute and complete the command. Ignore the few errors (in red color) that may pop up.

    (for recover settings and fileexplorer at start menu copied ane folder from other user)

    or you can create another user, but it hard reconfig all settings and passes;

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2015-08-26T07:35:26+00:00

    I have same type of errors in Activity log logged during startup of Win 10 Pro.

    3-4 of them, seems always to be in container 0x80070490.

    Is it a problem, or can I just leave it?

    FYI I also have another problems in Win 10 Pro. No App Store, no OneDrive, cannot do a "repair install" with ISO, cannot go back to Win 8.1........

    Tommy

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2015-08-23T00:44:41+00:00

    2 posts ago Wolfpup3 asked...     ...but is it at least harmless?

    That was my question, as well as Crysta's.

    Then the same poster stated...      ...harmless in most cases...

    I'm confused, did they/you answer their/your own question after some research/revelation? My machine seems to suffer nothing from this one, but I like to have a clean eLog,

    as if that was possible in M$ land.

    Seems we should ignore this one like I do the other many uncorrectable entries.

    Just like this forums spelling check flags 'uncorrectable' which for Oxford is a real word.

    Just like the 6 eMailed win10 upgrade assistant notices have taken us to a dead link since inception, they couldn't fix that 5 times, or never checked it to see it was broken @ start.

    You mean you expect things to work, without being patched a bunch of times?

    You must also use Linux, or have an Apple, or grew up with **** Amigas!

    Get used to it - nothing Bill makes will ever be finished till long after you drop the cash 

    • if at all. We'd never be able his o/s's at all without Google. Remember that old commercial,   "How do you think I got so bloody rich?"

    Another good example:  after this post, the site's security update page came

    up & I pressed "Everything looks good" then immediately received this eMail...

    Hello J.Post,

    We're glad that you joined us. The Microsoft Community welcomes novice users who are looking for help, technology experts who are looking to share their expertise, and everyone in between.

    Now that you've registered, you can ask questions, reply to posts, start or join discussions, or comment on the latest wiki articles. Pretty soon you might start earning badges and awards too!

    See, Been There - Done that - will it ever end?

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2015-08-22T21:55:25+00:00

    This isn't actually a 'problem'.  It's detecting a mismatch, however it's intentional and harmless in most cases (unless there's actually something wrong and it's running massively slower than the manufacturer intended).

    I didn't say anything about "only one", and in fact this isn't "one", but I don't know what else you're referring to.

    Was this answer helpful?

    0 comments No comments