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

296 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2024-02-29T14:54:29+00:00

    Did you install the Feb 13th patch that mitigates the issue?

    The registry hack works for sure. But then you won't have Metadata Staging when they finally get their servers back online for the planet.

    Look back through this thread for the patch info and the registry hack.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2024-02-29T13:01:23+00:00

    Error Event 131 seems to have re-appeared - not sure what's changed

    The warning 201 never stopped

    Was this answer helpful?

    0 comments
  3. Anonymous
    2024-02-19T03:14:51+00:00

    Yea, I tried that early on, fomr the Windows Catalogue site with the manual updates.

    I've given up on trying to get this update. Just gonna delay updates for a couple weeks to see if a newer one solves it.

    I also ordered a cheap stick of compatible RAM just to see if there's a hardware issue on my end as well.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2024-02-18T21:47:18+00:00

    Arron123abcxyz have you tried to download the update dircretly from Microsoft website that should then sort your issue out

    Was this answer helpful?

    0 comments
  5. Anonymous
    2024-02-18T21:43:22+00:00

    Still doesn't work. Says access denied, even as administrator. I also tried renaming through windows explorer, btu says files ar currently in use.

    However, I was able to get that latest update to fully install by deleting the hidden "$WinREAgent" folder in C: drive.

    Unfortunately, after rebooting the PC after the update was completed and using windows for a while, I got the "Driver Power State Failure" again, and after a couple failed reboots it restored me back to the PC state before the new Window Update installed.

    So, I don't know what the heck is up. Not sure if my issues are related to this metadata staging failed error, or something else altogether. Might be hardware issue?

    My system is running fine on Windows OS build 22631.3007.

    Looks like I'm staying on that until further notice.

    Hi Anon,

    I googled it and found this link that explains that some services need to be stopped first. Weird, I can rename it on my Windows 10 machine without needing to stop any services...

    Try the procedure here and include the "catroot2" folder that's mentioned:
    https://answers.microsoft.com/en-us/windows/forum/all/cant-rename-catroot2-and-softwaredistribution/ac10e0ba-9ead-4284-91e5-31acc430bd08

    Was this answer helpful?

    0 comments