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

Same and worse. My PC will start and work for a little bit, then restarts liker every 10 min. Not very happy

Hey man, same things been happening to me. How'd you fix it?

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.

ChatGPT said:

ChatGPT The errors you're seeing in the Event Viewer could potentially be related to the "Management Engine Interface" or the "Intel Chipset Driver," especially if they involve hardware or device communication issues. Here are a few possibilities to consider:

1. Driver Issues: Outdated or incompatible drivers for your Intel chipset or Management Engine can cause errors. It's worth checking for updates for these drivers from the Intel website or through your motherboard manufacturer.
2. Device Metadata: The "Device Metadata" registry key is used by Windows to manage device-related metadata. If there are issues with how devices report their metadata (like drivers not properly registering), it can lead to errors in the Event Viewer. An empty "ActiveDownloads" folder indicates no active metadata downloads, which is typically not a concern but may point to issues if devices are not recognized correctly.
3. Hardware Compatibility: Sometimes, hardware changes or updates can lead to compatibility issues. If you've recently changed hardware or updated drivers, consider rolling back to previous versions to see if that resolves the errors.
4. Software Conflicts: Conflicting software, especially if it relates to device management, could also result in errors. Make sure any related software is up-to-date.
5. Windows Updates: Occasionally, Windows updates can introduce new issues or conflicts with existing drivers. If you've noticed problems after a recent update, check if there are any patches or fixes available.

To troubleshoot further, consider:

• Updating or reinstalling the Intel Chipset and Management Engine drivers.
• Checking for Windows updates and installing any pending ones.
• Looking at the specific error messages in the Event Viewer for more context.

I posted earlier, i'm going to try to remove it,, I just noticed the exact name and model of lapdoggie you're using, and here is the answer i got back. Hope it's more definitive.

asus rog strix g16 giving following err :: Metadata staging failed, result=0x80070490 for container '{564E4238-4832-4447-5633-5CB9010C3444}', DeviceSetupManager id 131

ChatGPT said:

ChatGPT The error message you're encountering on your Asus ROG Strix G16—specifically "Metadata staging failed" with the result code 0x80070490—is often associated with issues in Windows, particularly with the Device Setup Manager. Here are some steps you can take to resolve this issue:

1. Run Windows Update Troubleshooter

• Go to Settings > Update & Security > Troubleshoot.
• Click on Additional troubleshooters and select Windows Update.
• Follow the prompts to run the troubleshooter.

2. Check for Windows Updates

• Make sure your system is up to date. Go to Settings > Update & Security > Windows Update, and check for updates. Install any available updates and restart your PC.

3. Repair System Files

• Open Command Prompt as an administrator (search for cmd, right-click, and choose Run as administrator).
• Run the following commands one at a time:

    bashCopy codesfc /scannow
    DISM /Online /Cleanup-Image /RestoreHealth
  

• Restart your computer after the scans complete.

4. Reset Windows Update Components

If the issue persists, you can try resetting the Windows Update components:

1. Open Command Prompt as an administrator.
2. Type the following commands one by one, pressing Enter after each:

    bashCopy codenet stop wuauserv
    net stop cryptSvc
    net stop bits
    net stop msiserver
    net stop dosvc
   
    net start wuauserv
    net start cryptSvc
    net start bits
    net start msiserver
    net start dosvc
   

3. Check Device Manager for Issues

• Press Win + X and select Device Manager.
• Look for any devices with a yellow triangle indicating issues. If you find any, right-click on them and select Update driver or Uninstall device (it will reinstall automatically on reboot).

6. Create a New User Account

Sometimes, user profile corruption can lead to issues:

• Go to Settings > Accounts > Family & other users.
• Click Add someone else to this PC and follow the prompts to create a new user account.
• Log in to the new account and check if the issue persists.

7. Reinstall or Repair the Application Causing the Issue

If this error is linked to a specific application, try repairing or reinstalling that application.

8. Check for Malware

Run a full system scan using Windows Defender or any trusted antivirus software to ensure that malware isn't causing the problem.

9. Consider a System Restore

If this issue started recently, you might want to perform a system restore to a point before the issue began:

• Search for "Create a restore point" in the Start menu.
• Click on System Restore and follow the prompts.

10. Reset or Repair Windows

As a last resort, you might consider resetting Windows or performing a repair install, which keeps your files but reinstalls the OS.

If none of these steps resolve the issue, there may be a deeper underlying problem, and you might want to consider reaching out to Asus support or a professional technician.

The joys of Windows OS :(

I once proved a point about the problem being the OS by booting the laptop from a Linux distro. After installing the drivers in Linux the external devices worked perfectly.