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-08-02T10:06:34+00:00

    Hi Ray,

    lost track of how many years since I started using it but have to disagree, plenty of bugs that took longer or have never been resolved. Check this one in Outlook for a recent example of how long it can take.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2024-08-02T09:55:49+00:00

    I have used Windows OS for over 33 years and in all that time have never known a bug like this to remain unresolved for so long. What is equally frustrating is Microsoft don’t appear to know how to resolve it. Bill Gates would be ashamed.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2024-08-02T00:50:49+00:00

    Still not fixed after 6 months! What the hell is wrong with Microsoft?

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2024-07-27T12:06:01+00:00

    Same issue persists and I have a screenshot of the registry please have a look.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2024-07-23T14:45:48+00:00

    .. For now I simply turned off the setting for Device Installation Settings to off. This is the only solution for now or else you'll be pulling your hair for hours and you'll be to no avail!

    Wait for MS to fix it, this is not Windows issue.

    Wow! Thank you for this. Not only eliminated the Event id 131 errors but al a significant number of other errors with event id 2,161,1000,2008,7031,8193 and 10005.

    Meh, I'm not sure why you are thanking me for this. You should've known this solution already!

    I'm not happy that the problem still persists last 1 month! It is a scandal! This isn't really a solution. If at any time we buy a new device we won't be able to install device drivers and the devices might not work properly unless we are lucky to find the drivers through official website.

    But some devices like gamepad controllers only install via windows update driver and that's not going to work now until Microsoft don't fix it!

    Hey, Thanks for this tip. I did the same thing and all my software and files are loading in comparison to before they were all crashing my PC. I am so disappointed that this issue still persists after so many year!!

    Was this answer helpful?

    0 comments No comments