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
    2023-12-26T09:54:10+00:00

    Unfortunately, it has nothing to do with latest Windows 10 update patch.

    I'm on the older Windows 10 1903 Final Build version. I get Metadata staging failed errors and they got triggered when I first entered Devices and Printers in control panel. As soon as I did this, those errors started triggering at startup! Prior that there were no problems.

    I did a Windows System Restore to last months date but it did not solve the problem at all. It simply carried over the new problem with the old restore point.

    I tried with both Metadata staging URL links. Clearly this is a Microsoft server side problem... 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.

    Was this answer helpful?

    10+ people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2024-01-18T17:37:22+00:00

    I cannot believe your misinformation! This has got nothing to do with Google Chrome or any chromium browser. As a matter of fact I don't have google chrome installed on my system.

    These meta errors are related to Devices and Printers meta servers. What it is trying is to search for drivers and be satisfied that your drivers are up to date. But the errors are triggered because the server is down.

    The only way to solve the problem is to manually turn off PreventDeviceMetadataFromNetwork 1 either via regedit or via the control panel. Errors stop and never get triggered.

    No amount of fresh Windows 10/11 re-installations will help solve the problem until MS fixes this server. Because even if you were to reinstall Windows with all legacy drivers. The problem is that the moment you open Devices and Printers you will get these errors to trigger infinitely after that. If the server was fixed even temporarily for a few minutes and you managed to be lucky to update metadata staging within that small time frame the errors will vanish!

    But the problem is the servers are never on, not even briefly for a few minutes per day.

    Was this answer helpful?

    10+ people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2024-01-04T08:46:04+00:00

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

    Events

    Version

    Was this answer helpful?

    10+ people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2023-12-11T00:10:20+00:00

    I have the same error message too. Here is my screen shot

    Was this answer helpful?

    10+ people found this answer helpful.
    0 comments No comments
  5. Anonymous
    2024-12-24T19:57:12+00:00

    This is a MS ISSUE. There is nothing anyone can do to resolve the problem. I've been reading numerous pages and forums since I've had this issue for a while. You can patch it up like a band aid, but its still gonna be an issue i.e like your check engine light and disconnecting the battery for the light to go away but it will reappear eventually. I totally agree with all the frustration. Its an issue that will not hinder or effect your system from running just fine. MS will have to address it with future updates.

    Was this answer helpful?

    9 people found this answer helpful.
    0 comments No comments