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

Hi, LouiscarrElcarumba

I suspected the disconnect was not related in the same way I suspect the references to BSOD and other issues are not directly related. The URL being in your friends registry doesn't mean it is being used. As you know you can turn off calls to it in both GUI and Registry.

As for a "Dead URL" not so sure it is dead. The only way anyone has tested it is with a port 443 HTTPS or port 80 HTTP visit with a browser and I am sure that is not how the URL is meant to be used. It may very well still respond to different HTTP(S) calls other than that and it may then establish a session or web socket on other ports when it works correctly.

This could also explain why your friends seems to be working. The data in the call their pc is supplying to the URL may be getting a correct response where others using different data (based on connected devices) don't. The problem as usual is MS does not fix things when the break unless they have too. Fairly certain that AI filters the CompatTelRunner.exe data and simply removes low level stuff as it considers it noise.

My gut reaction is that like so many MS articles on event log errors their usual advice, as it is here, is to turn it off or suppress the event log messages. Root Cause Analysis not being a Microsoft priority here.

Yeah it appears it is a dead URL... Like Microsoft won't fix the server of that URL.

I see mainly here and in other places that the reason is that the url is dead, ie. the server is not "serving".

It obviously IS more complex than that because that is a simple explanation that I've just pointed out cannot be the case.

If a data call is sent to a dead url, then it really doesn't matter what the differences between our PCs are. There will be no response. Unless you are suggesting that the URL only seems to be dead when pinged but will respond to it being used by MS which I doubt.

I mentioned this comparison because I have not heard it anywhere else yet and thought it would be useful information to anyone struggling to understand the issue. There has to therefore be some other factor that causes this behaviour on one pc and not on others when the registry data is exactly the same.

As for the connect / disconnect sound periodically ( which only caused one game to freeze for 5 seconds and not others), I spoke too soon on that.

It came back and due to the cleaner event viewer logs I was able to determine this was a usb disconnect (probably a powered hub I used in the pc to split up to send to two Corsair peripherals), getting disconnected. This happened to be some conflict between Dell Display manager and I presume ICUE (not sure) but disabling DDM has solved that issue after hours of testing now.

In case that was the cause of the 131 errors remains to be seen as I will re-enable devices service and the registry entry to see if they were connected.
DDM was installed a day before all the errors started and the connect/ disconnect sounds presumably too.

I'll find out soon enough but I've spent hours on this and need sleep.

Whilst I appreciate your inference that someone else is not seeing those log entries you miss the complexity of the situation. The only thing your PC and that if your friend may have in common is the operating system. The data call sent to the URL is device dependant. Unless your friends PC is in every way identical we are comparing apples with oranges. What is more significant is your statement that disabling this stopped the problem in your game.

I had this problem which started on 11th Sept. I was constantly getting the Connect/ disconnect sound which made me investigate.

I've seen all the possible solutions and for what it's worth, the problem is NOT the url if someone else does not have the problem and the URL is exactly the same as mine.

This is true in my case when I asked a friend who has no 131 or 201 200 errors whatsoever, to check his entries in the registry and they are exactly the same as mine.

So it seems there's a lot of "barking up the wrong tree" going on with this URL stuff. The URL is indeed not working but seemingly in some cases the intended behaviour is not to cause logs or constant connect disonnects.

This actually cased a constant freeze in one of my games.

I disable the service and the registry entry and I no longer get the connect / disconnect sound or the freeze.

There's more to this than meets the eye if someone else has this same URL and it doesn't cause problems.