Continues Errors at startup "Metadata staging failed"

[amtino]

Temporary fix

I personally have not had event id 131 for the past couple of months, it merely went away, but I have to say this happened twice before over the past two years and then it returns.

If you want to stop events flooding your event log change the registry key: 131, 200, 201 etc.

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

if you need further assistance doing so please post back

Merry Xmas

 

[rAn]

New member, and much like everyone else in here, am dealing with this issue. This thread hasn't been updated in over 7 years, so I dont know how relevant my input would be. I installed Win 10 Pro on a brand new WD HDD in a dual boot configuration on 12-25-23 and allowed all updates and patches. I began to notice these issues on 12-27. Sammys fix for this did not help me. The one fix that worked was changing the "c" to an "s" in: "http://go.microsoft.com/fwlink/?LinkID=252669&clsid=0x409"
I should also mention that I tried the other various tips and so called "fixes" to no avail. Im curious to see if there has been any 'updated' news regarding this.

 

[HankChen]

New member, and much like everyone else in here, am dealing with this issue. This thread hasn't been updated in over 7 years, so I dont know how relevant my input would be. I installed Win 10 Pro on a brand new WD HDD in a dual boot configuration on 12-25-23 and allowed all updates and patches. I began to notice these issues on 12-27. Sammys fix for this did not help me. The one fix that worked was changing the "c" to an "s" in: "http://go.microsoft.com/fwlink/?LinkID=252669&clsid=0x409"
I should also mention that I tried the other various tips and so called "fixes" to no avail. Im curious to see if there has been any 'updated' news regarding this.

I also had this problem since 12-27. I tried your fix and successfully solved the problem. Thank you very much.

 

[SillyKeith]

For those hitting this issue in the new year (2024), the Device Metadata Service site is down and has been since ~12/27/2023 . Once they get the service back up, these 131 and 201 errors will go away. I've no idea when this might be, but it shouldn't take them long to get it back up.

 

[itorres008]

New member, and much like everyone else in here, am dealing with this issue. This thread hasn't been updated in over 7 years, so I dont know how relevant my input would be. I installed Win 10 Pro on a brand new WD HDD in a dual boot configuration on 12-25-23 and allowed all updates and patches. I began to notice these issues on 12-27. Sammys fix for this did not help me. The one fix that worked was changing the "c" to an "s" in: "http://go.microsoft.com/fwlink/?LinkID=252669&clsid=0x409"
I should also mention that I tried the other various tips and so called "fixes" to no avail. Im curious to see if there has been any 'updated' news regarding this.

This sounds logical in that perhaps clsid looks like a class id, a serial number that represents a unique ID for any application component in Windows. However, it appears the clcid=0x409 parameter represents the English (United States) locale. In Microsoft's Locale Identifier (LCID) system, 0x409 specifically identifies the English (United States) locale. The LCID (Locale Identifier) is commonly used in software to specify language and cultural settings, particularly in Windows operating systems and Microsoft applications.

Performing the change to "clsid" is not solving the URL problem, but just substituting the Event 131 error for a Warning 201: A connection to the Windows Metadata and Internet Services (WMIS) could not be established.

What I've seen many people saying is a solution is using the URL http://dmd.metaservices.microsoft.com/metadata.svc . Also, sounds logical since the original Microsoft redirect URL does go to http://dmd.metaservices.microsoft.com/metadata.svc if you use it in a browser. However, that doesn't work for me. Perhaps there is some parameter missing. Will keep searching.

 

[SillyKeith]

This sounds logical in that perhaps clsid looks like a class id, a serial number that represents a unique ID for any application component in Windows. However, it appears the clcid=0x409 parameter represents the English (United States) locale. In Microsoft's Locale Identifier (LCID) system, 0x409 specifically identifies the English (United States) locale. The LCID (Locale Identifier) is commonly used in software to specify language and cultural settings, particularly in Windows operating systems and Microsoft applications.

Performing the change to "clsid" is not solving the URL problem, but just substituting the Event 131 error for a Warning 201: A connection to the Windows Metadata and Internet Services (WMIS) could not be established.

What I've seen many people saying is a solution is using the URL http://dmd.metaservices.microsoft.com/metadata.svc . Also, sounds logical since the original Microsoft redirect URL does go to http://dmd.metaservices.microsoft.com/metadata.svc if you use it in a browser. However, that doesn't work for me. Perhaps there is some parameter missing. Will keep searching.

I've been in contact with Microsoft about this service and here is what they said:

"We are aware that this service is down but we do not have an ETA on when it might be restored. "
That was on 1/29/2024.

The only other way to make this go faster would be to UPVOTE this feedback item: DeviceSetupManager errors