Metadata staging failed, for Event ID:131

Question

Metadata staging failed, result=0x80070490 for container '{5094484E-6925-FDD5-AACE-D9DA6785FB29}' Event ID:131

I check registrty DeviceMetadataServiceURL and found this URL: http://go.microsoft.com/fwlink/?LinkID=252669&clcid=0x409 , but URL redirect me to http://dmd.metaservices.microsoft.com/metadata.svc with status Error 502 Bad Gateway

Answer 1

Hello，IvailoMarkov

Thank you for posting in the Microsoft community.

Regarding the 131Metadata staging failed message you mentioned, it is due to the number of tasks in the task queue being full or exceeding the quota, you can try to solve this problem by modifying the value of the quota key to increase it to the maximum value:

1. Click Start, type regedit, and then press ENTER.
2. Locate and then click the following registry key:  HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Schedule\Configuration
3. Right-click TasksInMemoryQueue, click Edit, and then click Modify.
4. In the Value data box, type 1000 (Decimal).
5. Right-click TasksPerHighestPrivEngine, click Edit, and then click Modify.
6. In the Value data box, type 1000 (Decimal).
7. Right-click TasksPerLeastPrivEngine, click Edit, and then click Modify.
8. In the Value data box, type 1000 (Decimal).
9. Exit Registry Editor and reboot the machine.

Disclaimer: Generally, modifying registry subkeys or work group is intended for advanced users, administrators, and IT Professionals. It can help fix some problems, however, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For further protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click How to back up and restore the registry in Windows - Microsoft Supportto view the article.

If your problem is not solved yet, you can tell me the specific scenarios and errors, and I will research further and provide you with a solution.

I wish you all the best and please feel free to contact me if you have any questions, I look forward to hearing from you which will determine where we go next!

Best Regards，

Rota Ye |Microsoft Community Support Specialist

Answer 2

Hi Rota Ye,

I followed your steps exactly to change the registry values, but the Event Viewer keeps getting the same errors despite this.

I don't do anything unusual on the computer, even in idle it keeps logging these errors.

I have VMware Workstation running with two virtual machines with Linux servers and one Plex server, but the system load is minimal.

Answer 3

Hello，IvailoMarkov

We are glad to receive your reply! We are sorry that our above action plan may only work for Windows Home and Professional editions. The issue you are inquiring about is beyond the scope of our forums as it relates to VMware Workstation. Our community provides technical support for the daily use and upgrade of Windows Home and Professional, which is better suited for posting on Microsoft Learn (English only, you can use the translation tool to assist in your communication), which is designed for advanced users such as yourself. It is more appropriately posted inMicrosoft Learn **** (English only, you can use a translation tool to assist with communication), which is intended for advanced users like you.

You can ask a question by clicking on "Ask a question", there are experts in this field who can provide more specialized solutions.

I won't be able to help you, but I'll keep the question on file in case one of our wonderful volunteers comes up with something for you.

Best Regards，

Rota Ye |Microsoft Community Support Specialist

Answer 4

You didn't understand me, I'm using Windows 10 Professional 64bit, on which I have VMware Workstation installed :) (Forget I mentioned VMware, my OS is Windows 10 Pro 64bit)

Anyway, your way didn't work and the errors keep getting logged in the Event Viewer

Do you have any other suggestions on how to fix this error (Metadata staging failed, for Event ID:131) ?

Answer 5

This is the problem:

This reg key: HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Device Metadata\DeviceMetaDataServiceURL

Points to this URL: http://go.microsoft.com/fwlink/?LinkID=252669&clcid=0x409Which then redirects to this URL: https://devicemetadataservice.trafficmanager.net/dms/metadata.svc

The 2nd URL is broken and this has happened many times before, going all the way back to Windows 7 in 2015.

Microsoft needs to fix this.  It has been noticed in Germany that it started happening after installation of the 2023-11 Cumulative Update for Windows 11 Version 22H2 for x64-based Systems (KB5032288) and the 2023-11 Cumulative Update for Windows 10 Version 22H2 for x64-based Systems (KB5032189).  Don't know about Windows 8.1. Windows 7 systems are EOL and get no patches without an extended license.

In addition to the following regedit changes, the Metadata Staging (used for many things, not just print queues) can also be disabled by going into Windows Settings, then select System, then select About (lower left), then Advanced System Settings (on the right-side), then select the Hardware tab, then click the Device Installation Settings button.  In the popup box that appears, you can change it from YES (recommended) to NO (your device might not work as expected).

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Device Metadata]

"PreventDeviceMetadataFromNetwork"=dword:00000001

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Device Metadata]

"PreventDeviceMetadataFromNetwork"=dword:00000001

Now I don't know about you but, for me, I would prefer that Microsoft gets off its behind and fixes the URL, once again... Then I can expect my device to work "as expected"). Capiche?!?

Changing the regkey or changing the system setting are both quick fixes and they are NOT acceptable options to me...