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. DaveM121 929.6K Reputation points Independent Advisor
    2023-12-08T11:29:15+00:00

    Hi, I am Dave, I will help you with this.

    Usually this is caused by an incorrect entry in the registry.

    Click your Start Button, type regedit and hit Enter to open the Registry Editor.

    Click View and make sure 'Address Bar' is turned on.

    Paste this into the Address Bar at the top and hit Enter.

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Device Metadata

    Please provide a screenshot of that Registry Editor page.

    Was this answer helpful?

    20+ people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2023-12-10T16:30:24+00:00

    Hello!

    I also have such lines in the Event View. What could be the reason for the errors?

    Question: can the error be due to the "Management Engine Interface" or "Intel Chipset Driver", and the updates that are associated with them. Or is it not related to this at all?

    By the way, I have two folders along this path - "Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Device Metadata", there are two folders "Device Metadata" and "ActiveDownloads". "The ActiveDownloads folder is empty. And in "Device Metadata" there are lines that are in the screenshot.

    Was this answer helpful?

    20+ people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2024-01-04T13:08:57+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.

    Was this answer helpful?

    10+ people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2023-12-29T19:42:36+00:00

    I also supplied feedback via the Feedback Hub:

    1.) Click Start -> Search for Feedback Hub --> Open Feedback Hub

    2.) On the Home tab search for "DeviceSetupManager Event ID 131 error"

    3.) Click "Upvote"

    4.) Search for other keywords such as metadata or 131 error and upvote those as well.

    Image

    Was this answer helpful?

    10+ people found this answer helpful.
    0 comments No comments
  5. Anonymous
    2023-12-10T10:47:10+00:00

    Welcome to the club m8, something really went sideways with one of the latest windows updates.

    The last update I installed is KB5032189, on the 15th of November.

    The issue first started appearing on the 5th of December with just 3 instances in the Event Log. On the 6th it started flooding it, I disabled the device installation settings that day after 50+ errors appeared in the log. I tried multiple fixes, only disabling the device installation settings work and the problem reappears when I try to enable it again (to test if it's still broken).

    Was this answer helpful?

    10+ people found this answer helpful.
    0 comments No comments