Windows 10: Problem related to DeviceSetupManager. Lots of errors and warnings.

I have tried several ways to get rid of all warnings and errors in Event viewer. A registry hack seemed to help a little, but only for error 131. Now I have reinstalled again, hoping that a clean install could help, but no.I understand this happens when Windows try to receive metadata for devices, and has a wrong address on server.I don't want to choose never update drivers. Is there another solution?I made my own event report, and this is only for this evening. Two screens with errors and warnings from DeviceSetupManager.

:)

 

Constants DeviceSetupManager 201, 202, & 203 Warnings in Windows 10 Version 1803

In Windows 10 Version 1803, I am consistently getting Device Setup Manager 201, 202, and 203 warnings. A group of 4 warnings (202, 200, 202, 201) will immediately follow the last 4. I'm not sure when these warnings started, but they been going on for
a couple of weeks at least. There are so many of them that it completely fills the devicesetupmanager\admin file within a day or two and my Administrative Events log file is virtually useless because of the large number of superfluous devicesetupmanager warnings.
I've searched for these warnings on Google, but there is nothing recent and no resolution for the problem, however, many people have experienced the same warnings. Any suggestions?

 

A series of DeviceSetupManager warnings in Windows 10 event logs

I have been "cleaning up" Windows 10, and I'm noticing a series of warnings in the Event Viewer every time I start Windows. And they are in the following order.

It seems that Event 202 repeats every other instance until I finally get the error: Event 131. What would I have to do to fix these problems, so they stop showing up every time in Event Viewer?

 

Lots of DeviceSetupManager error in event viewer (windows 11, new self built computer and LOTS of DeviceSetupManager warnings and errors)

Hi, Celestin Rico

Welcome to the Microsoft Community.



Please don't worry, this is not caused by your GPU issues. For this issue you can try the following suggestions, there are many community members who have reported that these suggestions work and hopefully this applies to you as well.

The reason for this error is the registry key:

Point to this URL: http://go.microsoft.com/fwlink/?LinkID=252669&clcid=0x409

Then redirects to the following URL: https://devicemetadataservice.trafficmanager.net/dms/metadata.svc

The 2nd URL is broken.

Here are two things you can try:

1. Disable metadata staging:

• Windows Settings > System > About > Advanced System Settings > Select the Hardware tab > Click the Device Installation Settings button.
  
• In the pop-up box that appears, you can change it from Yes (recommended) to No (device may not function as expected).
  

2. Edit the registry:

"Enabled"=dword:00000000

"PreventDeviceMetadataFromNetwork"=dword:00000001

This issue should be solved temporarily by the above method, if you want to completely solve this issue, it may require the development team to fix it. You can submit your ideas and suggestions through the Feedback Hub, and the development team will regularly review submissions for ideas or fixes. Please share the feedback link here after submitting, as it will allow others on the forum to vote for your submission, including me. More votes will lead to more visibility and higher priority to the development team.



If there is anything not clear, please do not hesitate to let me know.



Best Regards

Martin | Microsoft Community Support Specialist