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

For me, in Belgium, on three of my Win10 systems, this started happening again around the 24th of april.

I’ve learned that the metadata address that the link refers to is actually an alias that can resolve to a whole multitude of servers across the globe - some of them appear to be less responsive than others.

I guess the network of metadata servers has become too large to manage effectively

But is this necessary for the correct functioning of our PCs? It’s relatively new. If Microsoft removed it what would the impact be?

Maybe time to try because I’ve tried other suggestions and they haven’t worked. I’m just a normal home user. These error messages are meaningless to me. I wish they’d write them in Plain English.

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.

Hi Dave,

as a direct reply to your request:

Screenshot:

The DeviceMetadataServiceURL:

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

That address hits a "302 moved temporarily" redirect to

http://dmd.metaservices.microsoft.com/metadata.svc 

And that address just times out with no hit.

So if you could suggest what link should be used instead - or influence Microsoft to fix this in a patch - a lot of people would be really grateful.

Edit: I just realized that maybe the "http://dmd.metaservices.microsoft.com/metadata.svc " address proabably isn't supposed to work in a browser.
I think the problem lies in some (at the moment quite a few, I guess) of the servers that are possible "owners" of that address

Stupid question, but why don't they just fix that link?

I totally agree.

It's now been 6 months since this thread was started and Msft still haven't fixed the link. It's ridiculous.

That is helpful! In my case most of the errors are about my audio devices, as well as my wireless mouse/keyboard. But tthe drivers for these devices are all current. So I don't know what the errors are telling me.