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-08-23T17:25:22+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.

    Here's my registry page.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2024-08-23T07:19:01+00:00

    i experience a problem in windows startup in which mouse and keyboard don't start immediately they delay to start an then hear device connection sound and they start working

    but i was not able to find a cause of the problem could it be this metadata staging failed error which causing it

    anyone else have same problem ?

    Was this answer helpful?

    0 comments
  3. Anonymous
    2024-08-20T18:22:37+00:00

    This is crazy, why will they not address this MAJOR PROBLEM!?!?

    Was this answer helpful?

    0 comments
  4. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more

  5. Anonymous
    2024-08-18T14:06:38+00:00

    Log Name: Application Source: Application Error Date: 18/08/2024 5:13:41 PM Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: Josh-PC Description: Faulting application name: RzChromaConnectServer, version: 1.0.0.45, time stamp: 0x66a30916 Faulting module name: ucrtbase.dll, version: 10.0.19041.3636, time stamp: 0x6763d3a2 Exception code: 0xc0000409 Fault offset: 0x0009eddb Faulting process id: 0x21b8 Faulting application start time: 0x01daf13e26bf2a86 Faulting application path: C:\Program Files (x86)\Razer Chroma SDK\bin\RzChromaConnectServer Faulting module path: C:\Windows\System32\ucrtbase.dll Report Id: 5b66c5a5-6eff-4b97-bd05-3060a28d5ed2 Faulting package full name: Faulting package-relative application ID: Event Xml: http://schemas.microsoft.com/win/2004/08/events/event"> 1000 0 2 100 0 0x80000000000000 52664 Application Josh-PC RzChromaConnectServer 1.0.0.45 66a30916 ucrtbase.dll 10.0.19041.3636 6763d3a2 c0000409 0009eddb 21b8 01daf13e26bf2a86 C:\Program Files (x86)\Razer Chroma SDK\bin\RzChromaConnectServer C:\Windows\System32\ucrtbase.dll 5b66c5a5-6eff-4b97-bd05-3060a28d5ed2

    Was this answer helpful?

    0 comments