Metadata staging failed - Event ID 131 errors in EventLog

Heya,
just found, this Metadata staging failed - Event ID 131 errors in event log, when start up my pc. From Google search found, that there is http link, where PC get this data in registry:
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Device Metadata
-DeviceMetadataServiceURL
I check on Win11 beta and Canary build: http://go.microsoft.com/fwlink/?LinkID=252669&clcid=0x409, which redirect to http://dmd.metaservices.microsoft.com/metadata.svc. This web address give me 502 Bad Gateway error on three different ISPs, so may be problem is at all on Microsoft side.
Here is link for problem in MS Feedback Hub: The Windows Insider Program

Please share more info, that problem exist for you too, here. Thanks.

Having the exact same issue here.

Thanks I have same log, so will wait MS to fix.

Same issue here. Continous DeviceSetupManager event IDs 131, 200, 201 & 202. It started a week, ten days ago.

Hi, the same on my Windows 10 machine, haven't updated my Windows 11 machine yet. As already mention, I have that same link in registry and get same error. I would get this error many times on a boot or when plugging in external USB drive. I could stop getting the error by disconnecting from internet, then no errors when booting or plugging in external drives. Finely, I should add going to control Panel, search for Device Installation, select change device installation setting to NO- does fix the error. Then I can be connected to internet and reboot or add my USB external drive and no errors. Not sure this is a wise fix, but does work. I think this pretty much proves that Microsoft has a problem with this link in the registry DeviceMetadataServiceURL Haven't had any 200 errors, but haven't done the Windows 11 machine yet. I posted this on the 11 forum just to show this seems to be more than just Windows 11 issue and how I fixed it.

Correction, did get the 200 errors in warning section. But they also stopped after my little fix.

Same here on latest Windows 11 release preview. Lots of 131 and 201 errors starting within a week of today. Waiting for fix

Setting Device Installation Settings to No, Did stop the errors. Now to remember to come back in the future and turn it back on.

Did this on my Laptop which I update today, did same fix. You would think Microsoft would fix that URL so it didn't error put out an update. Fixing the URL to actually point to something seems the easiest?

I'm getting the same error, hopefully MS will fix this soon.

You are not alone. Started seeing the same issue on Windows 10 22H2 a few days ago. Still going on.

AK6DN said:

You are not alone. Started seeing the same issue on Windows 10 22H2 a few days ago. Still going on.

Click to expand...

it was sort of an issue on Win10 22H2 but one user claimed the recent KB5033372 update for Win10 might have fixed it (for some people but not for everyone else though)

for Win11 22H2/23H2 users, try installing the newly released KB5033375 update released Tue. 12/12
post there the KB5033375 update thread whether the event id 131 errors still occur or not with that update

My errors were occurring due to my HP printer driver. I uninstalled and re-installed it and the error appears to have gone away.

I searched the GUID in Regedit and determined the errors were printer related. Not sure why they showed up suddenly.

Im having similar issues. If I do the "change device installation setting to NO" trick, how can we know if Microsoft sorted this issue out? Is there a place where we can see updates or receive notifications about this?

This is still an issue as of 2/2/2024 and I noticed the problem in mid December...

I was thinking of going back and changing that to see if it was fixed, but will leave device installation setting to NO for now.

Woah! Still not fixed in August 2024. URL still broken.

hexaae said:

Woah! Still not fixed in August 2024. URL still broken.

Click to expand...

I "liked" this post to agree with it, that yet in September, running with a fresh install of Windows 11 23H2, current channel, non-Insider build, this issue contains to plague my event logs.

I'm not sure what the deal is, but I do notice inconsistency of how often it happens and what does and doesn't trigger it. It very much looks like spotty server/URL availability. I'm honestly not sure that I ever came across this component or event in Windows 10 and back, so I'm not sure if this is some new Windows 11 feature added at some point for device metadata recognition to better integrate into the OS for their native features like onboard monitor color profiles/HDR support, dynamic lighting to control RGB-capable devices, etc., but nothing I do seems to make a difference as to whether this comes or goes.

I can say as a system administrator in an enterprise environment, we occasionally run into issues similar to this with the WSUS service as used by System Center ConfigMgr for internally managing updates, as the WSUS servers that talk to Microsoft occasionally fail to reach their Windows update catalog URL's, but it isn't nearly as frequent as this, and it's usually obvious when it happens, as myself or other admins on Reddit will have already posted something similar at the same time, showing we can't access the download links to update content in the metadata for catalog entries. To be clear though, this is an entirely different system component in an entirely different log that you won't find on a Windows 11 system - I'm just comparing it to say that MS web-services for their OS features these days have been known to go up and down.

Hello,
same issue here, since May 17th, 2024 (I bought it in April 2024!). There seem to be various workarounds (regarding the flow of error messages) at various forums for various end-user types and various windows versions, but the root cause remains maturing like a Gouda. At µSoft they might be thinking what Sia already advised our beloved planet: "Some people have real problems". Yet at µSoft they'll probably - and should - call it "prioritising". Afaic, I kept this one in the "If it ain't broke, don't fix it"-league thus far, because my laptoppy works seamlessly on the whole (knock on weed. Ehm..., no, wood! Of course) and this does not seem to reduce performance. I dope, eehmm.., hope, µSoft is going to have an actual solution though, before the link rot's induced log-bloating here takes on excessive forms......







Quote: "After installing the updates, XXXXX can confirm that the new Metadata server URL, https://go.microsoft.com/fwlink/?LinkID=2257403&clcid=0x409, is using HTTPs and redirects to the new URL https://devicemetadataservice.trafficmanager.net/dms/metadata.svc?LinkID=2257403&clcid=0x409, which also uses HTTPs.
However, Microsoft has failed to associate an IP address to devicemetadataservice.trafficmanager.net in DNS, causing connection attempts to fail.".

The images above are from my laptop (W11, 23H2), the URL has already been updated apparently by some KB or maybe already when I bought it (new). There isn't much end-users like me can do anyways, the effective repair(s) will have to come from µSoft.