Metadata staging failed, result=0x80070490 for container '{564E4238-4832-4447-5633-5CB9010C3444}', DeviceSetupManager id 131.' If you happen to know what this means, please help me with this error

Anonymous
2023-12-08T09:54:35+00:00

Hi

I am getting this error when I start the computer I am getting error

Metadata staging failed, result=0x80070490 for container '{564E4238-4832-4447-5633-5CB9010C3444}', DeviceSetupManager id 131.'

, please help

me with this error

Windows for home | Windows 11 | 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

296 answers

Sort by: Most helpful
  1. Anonymous
    2024-03-03T16:50:49+00:00

    Same here - it was fixed for a while, now errors are back.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2024-03-03T03:11:03+00:00

    And now i think I celebrated little early. Now again my system hung with so many "Metadata staging failed" errors. Very strange.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2024-03-02T00:44:39+00:00

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2024-03-01T20:26:07+00:00

    Good news and bad news folks.

    Good news: I am no more seeing that error related to Device Metadata. I have been continuously checking the windows patch and updating so maybe some of the patch fixed that.

    Bad news: My system still keeps hanging and i have to do hard reboot. The "system" event viewer shows me error like the following:

    "The igccservice service failed to start due to the following error: 

    The service did not respond to the start or control request in a timely fashion."

    and

    "A timeout was reached (45000 milliseconds) while waiting for the igccservice service to connect."

    Any idea how to proceed and debug ?

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2024-02-29T22:40:34+00:00

    Scroll back a couple of pages and you'll see where we were discussing that Event 131 did stop after the Feb 13th Windows Update - it's the fact I've noticed it returning without any specific change I thought worth mentioning. The Warning 201 continued even after that Windows Update.

    Was this answer helpful?

    0 comments No comments