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-13T21:52:55+00:00

    Based on your comment, I checked and found that there's new windows cumulative update available. I installed it and will check. In the meantime, I still see the same link in the DeviceMetadataServiceURL (and it's also not working):

    https://go.microsoft.com/fwlink/?LinkID=2257403&clcid=0x409

    (It points to https://devicemetadataservice.trafficmanager.net/dms/metadata.svc)

    Was this answer helpful?

    0 comments
  2. Anonymous
    2024-02-13T21:43:08+00:00

    Just found this, but trying a few of them was just shooting in the dark.. https://urlscan.io/search/#devicemetadataservice.trafficmanager.net

    Was this answer helpful?

    0 comments
  3. Anonymous
    2024-02-13T21:00:17+00:00

    Unfortunately, that patch doesn't fix the issue. Darn it!!!

    Was this answer helpful?

    0 comments
  4. Anonymous
    2024-02-13T20:20:00+00:00

    A Bleeping Computer.com staff member told me today that Microsoft told them that this Feb 13th patch will solve the Metadata Staging issue.

    https://support.microsoft.com/en-gb/topic/february-13-2024-kb5034763-os-builds-19044-4046-and-19045-4046-f1c993e4-32b3-4cc8-947a-69e70ae124d5
    https://support.microsoft.com/en-us/topic/february-13-2024-kb5034765-os-builds-22621-3155-and-22631-3155-023d9141-a5b0-470a-b0f5-2ee3b48f48ce
    NOTE:      This update will cause problems for anyone who happens to be using "Co-Pilot for Windows 10", like Joaquin Phoenix.
    ;-)

    Was this answer helpful?

    0 comments
  5. Anonymous
    2024-02-13T19:28:55+00:00

    After applying the February Windows Update there is a change in the URL in the registry from HTTP to HTTPS and the other parts of URL change as well:

    Image

    Was this answer helpful?

    0 comments