Continues Errors at startup "Metadata staging failed"

[mbushnaq00]

Since yesterday I have noticed a delay during the welcome circle loading screen after login. Then I checked the event viewer and found out that I get around 15 errors of the same event ID 131 which contains the following details:

Log Name: Microsoft-Windows-DeviceSetupManager/AdminSource: Microsoft-Windows-DeviceSetupManager
Date: 9/13/2014 1:07:25 AM
Event ID: 131
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: ASUS
Description:
Metadata staging failed, result={1C852A4D-B800-1F08-ABCD-E4115B8201DD} for container '0x80070490'
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-DeviceSetupManager" Guid="{FCBB06BB-6A2A-46E3-ABAA-246CB4E508B2}" />
<EventID>131</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x4000000000000000</Keywords>
<TimeCreated SystemTime="2014-09-12T21:07:25.275201900Z" />
<EventRecordID>4369</EventRecordID>
<Correlation />
<Execution ProcessID="332" ThreadID="4204" />
<Channel>Microsoft-Windows-DeviceSetupManager/Admin</Channel>
<Computer>ASUS</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="Prop_ContainerId">{1C852A4D-B800-1F08-ABCD-E4115B8201DD}</Data>
<Data Name="HRESULT">2147943568</Data>
</EventData>
</Event>

I have not done any hardware changes and have no idea why these error suddenly started to show up.

I have searched everywhere about this error and could not find any matching solution. I appreciate if someone can help me figure out what is the cause of these errors and a solution. Thanks

EDIT: Just to clarify, I have tried the following troubleshooting steps:

Ran the following commands:

sfc /scannow
DISM.exe /Online /Cleanup-image /Restorehealth
net stop wuauserv
ren SoftwareDistribution SoftwareDistribution.old
net start wuauserv

finally, I also tried running the "Windows Update Diagnostics Tool"

SF diagnostic logs attached

 

[HarryMcDoogle]

I have the same exact problem. It started around 5 am on 9/12/2014. Now every time I restart I'm flooded with about 19 of event ID 131 DeviceSetupManager errors.

Like you I made no changes to my system and couldn't find any more info online (besides this post). If you figure out a fix, please let me know.

 

[Faizy450]

I have the same exact problem. It started around 5 am on 9/12/2014. Now every time I restart I'm flooded with about 19 of event ID 131 DeviceSetupManager errors.

Like you I made no changes to my system and couldn't find any more info online (besides this post). If you figure out a fix, please let me know.

Exact same error as OP, I know OP is using an Asus motherboard, are you? I am. Could be something to do with a driver etc

 

[HarryMcDoogle]

Exact same error as OP, I know OP is using an Asus motherboard, are you? I am. Could be something to do with a driver etc

Yes I am, I'm using a asus P8Z68-V PRO.

 

[Faizy450]

Exact same error as OP, I know OP is using an Asus motherboard, are you? I am. Could be something to do with a driver etc

Yes I am, I'm using a asus P8Z68-V PRO.

Most likely a driver or bios glitch across the Asus lines then, I'm using a Asus Maximus VII Z97 Ranger.

 

[CrappyAlloy]

It's not an ASUS issue, as I just built this new X99 rig a week ago and I'm using an MSI X99S board. I get about 10+ of these errors every start up. I have the same 'for container '0x80070490' as the OP. I've also tried the solutions the OP tried with no success. Everything is up to date on my system and it still occurs, any time you reboot or just plug in a device. Interestingly action center and device manager show everything fine, and all connected devices seem to be working as intended.

I'm not sure if there is any delay that the OP is mentioning in my system though because it is so new.

Searching for that hex value above gives lots of results about Windows update but that too seems to be working fine. What most of us have in common seems to be Windows 8.1/Pro. I was starting to think it was just my system before I found this thread, maybe because the chipset drivers for X99 were so new. But after seeing this I'm thinking it has something to do with Windows 8.1/Pro, possibly an update we downloaded recently that is causing it.

EDIT: I forgot to mention I tried removing my AV (Avira) and that didnt stop it from occuring. However booting into safe mode does, it has to be a driver/recent-update issue.

 

[hqsec]

I get similar errors since yesterday also. I don't use ASUS motherboard also.
My problems didn't start right after Windows 8.1 update but only yesterday. I also run disk C cleanup with Windows Update cleanup option enabled. Did any of you do the same? Could this be a source of a problem?

 

[mbushnaq00]

OK, after extensive research and trial and errors, I figured a work around for the issue.

It seems the issue is coming from Windows Update trying to retrieve info about the installed hardware from the internet and failing during startup.

To prevent this from happening do the following:

Go to Control Panel > Type in the search "device installation" > Click on "Change device installation settings"

Click on "No let me choose what to do" > choose the option "Never install driver software from Windows Update" and make sure that "Automatically get the device app and info provided by your device manufacture" is UNCHECKED. < This is the source of the issue

Restarted and shutdown a couple of times and the error is totally gone.

 

[HarryMcDoogle]

Thanks, Nice Job tracking that down. Following your directions I was also able to stop the errors from showing up. I assume that Microsoft must have messed something up in one of those recent updates. Hopefully they will fix soon. Atleast I know what it is and how to stop it for now. Thank you once again.

 

[hqsec]

OK, I will test it out. I also found out what triggered this error first time to happen. It was task called "Metadata Refresh" located in Device Setup folder of Task scheduler. First error appeared at the same time when this task was last run. The task has 0x0 result (operation completed successfully?).

 

[hqsec]

@mbushnaq00 - thanks, your solution works. Disabling only the last option will work also.

 

[streetwolf]

Glad to see I'm not alone. As mentioned the problem came with the Windows Update on 9/9/14. I restored my system to before I applied the updates and had no problems.

It seems the errors are not affecting anything so I just turn logging off for them. It's found in Event Viewer under DeviceSetupManager

 

[Wagnard]

Just a little question to all having this problem, did you guys ever run Display Driver Uninstaller (DDU).
Just want to make sure to see if DDU is responsible or not.
As if it is, I must fix this asap.

 

[mbushnaq00]

Just a little question to all having this problem, did you guys ever run Display Driver Uninstaller (DDU).
Just want to make sure to see if DDU is responsible or not.
As if it is, I must fix this asap.

nope, I dont think DDU relates to the issue

 

[Wagnard]

Just a little question to all having this problem, did you guys ever run Display Driver Uninstaller (DDU).
Just want to make sure to see if DDU is responsible or not.
As if it is, I must fix this asap.

nope, I dont think DDU relates to the issue

Thanks a lot, I was almost sure from what I Knew already but now you confirm it.
Thanks and have a nice day.

Wagnard.

 

[hqsec]

I also never run DDU. It must be something related to last Windows updates.

 

[streetwolf]

I set "Never install driver software from Windows Update" and "Automatically get the device app and info provided by your device manufacture" to UNCHECKED.

Rebooted and got lots of Warnings about Windows Update and I think two other related things.

I replaced a crap load of Errors with a crap load of Warnings. Anyone else see this?

 

[Marcus]

This is more of a temporary workaround than real solution. I would like my system and drivers to update normally. Correct me if I'm wrong, but disabling devices check is not recommended. I am under the impression Windows Update is not operating as it should. Also, being new here I don't get why thread is marked as solved while issue is still there. However, I don't think "metadata staging failed" error is due to any recent updates. I just made a full system restore, and without any updates installed it still occurs at every startup, flooding event viewer same as before. It looks to me this thing is somehow related to Windows and its update system or servers

 

[JohnBurns]

OK, after extensive research and trial and errors, I figured a work around for the issue.

It seems the issue is coming from Windows Update trying to retrieve info about the installed hardware from the internet and failing during startup.

To prevent this from happening do the following:

Go to Control Panel > Type in the search "device installation" > Click on "Change device installation settings"

Click on "No let me choose what to do" > choose the option "Never install driver software from Windows Update" and make sure that "Automatically get the device app and info provided by your device manufacture" is UNCHECKED. < This is the source of the issue

Restarted and shutdown a couple of times and the error is totally gone.

Thank you for posting...it solved my problem on 2 desktops. I really appreciate it.

 

[Marcus]

OK, after extensive research and trial and errors, I figured a work around for the issue.

It seems the issue is coming from Windows Update trying to retrieve info about the installed hardware from the internet and failing during startup.

To prevent this from happening do the following:

Go to Control Panel > Type in the search "device installation" > Click on "Change device installation settings"

Click on "No let me choose what to do" > choose the option "Never install driver software from Windows Update" and make sure that "Automatically get the device app and info provided by your device manufacture" is UNCHECKED. < This is the source of the issue

Restarted and shutdown a couple of times and the error is totally gone.

Thank you for posting...it solved my problem on 2 desktops. I really appreciate it.

Your problem is not really solved, you are just preventing Windows from automatically installing drivers. Windows is not checking for driver software anymore and therefore you won't receive error alerts in the event viewer. But the issue is still there, as "normally" Windows is supposed to do that kind of check and update/install procedure