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

My registry key is already set to this URL and I am still receiving the error.

Hi Surya,

I appreciate your suggested work around. It is however not "caused by a faulty policy in the GPE."

Why am I seeing lots of Event ID 131 - DeviceSetupManager - Metadata - Microsoft Community shows three methods of doing the same thing you suggest. One in the GUI and two registry keys (one of which I suspect is what is set by your GPE workaround.

All your post and the one I referenced above is doing is preventing the API call to the URL so the error is not logged.

The root cause is the failure of Microsoft to provide the correct metadata in response to this call.

That is cause of the error and the subsequent Event ID logged and is reported in the post above in the answer by Martin -MSFT

"I have seen this problem reported by other members of the community and the reason for this error is the registry key:

   HKLM/SOFTWARE\Microsoft\Windows\CurrentVersion\Device Metadata\DeviceMetaDataServiceURL 

Point to this URL: http://go.microsoft.com/fwlink/?LinkID=252669&clcid=0x409

Then redirects to the following URL: https://devicemetadataservice.trafficmanager.net/dms/metadata.svc

The 2nd URL is broken. (as you guessed at the end of your post)"

This is caused by a faulty policy in the GPE.
Here’s how you can access the Group Policy Editor:

1. Open the Group Policy Editor:
   Press Win + R to open the Run dialog box.
   Type gpedit.msc and press Enter.
2. Navigate to:
   Computer Configuration > Administrative Templates > System > Device Installation > [ Setting] Prevent device metadata retrieval from the internet set it as Enabled
   

In this section, you can find and configure policies related to device metadata retrieval and other device installation settings.

Hi Jordan,

Subnautica? no ideas sorry, doubt its related but looks like not only the GPU/CPU got hot so did your sub ;)

yep that is the expected response from the web URL and why I suspect everyone is getting the 131 Error message. Nothing you can do my friend suspect only Microsoft knows what they broke and if and when they are going to fix it. More often than not they simply ask you to ignore what's broken saying it is not vital etc.

this is what i got

The two other photos are of when i was playing subnautica on max settings the gpu got up to 100% and then the cpu and gpu dropped to low percentages