Windows 10: KB5032278 Update - ID error 131

Since installing the KB5032278 update, I am receiving DeviceSetupManager error 131 in Event Viewer. The only solution to prevent the error from occurring is to disable the automatic download of manufacturer's applications and icons for devices in the device installation settings.Anyone else experience this since that update?

:)

 

Event ID 131 Metadata errors happening lately.

Just to update anyone else who is having this issue. For nearly a week since I did a clean installation Ive been seeing 16 DeviceManagerSetup Event ID 131 errors every time I boot up my PC. Yesterday that number reduced to 11. Ive just booted up my PC and I have only one error now. I haven't done anything at all to try and fix this because last time it resolved itself after a few days without me doing anything. My gut feeling tells me it has to be something to do with Microsoft's servers but I don't know for sure

Update:
On patch Tuesday CU KB4524570 was automatically installed on version 1903. I now have Build 18362.476. I have the option also to download and Install 1909 feature update but I haven't done so yet. Im holding off for a couple of weeks to verify that feedback on here shows that it is stable before I upgrade to 1909.
After the CU KB4524570 installation Im now seeing no DeviceManagerSetup 131 errors at all again

 

Event ID 131 Metadata errors happening lately.

Update:
On patch Tuesday CU KB4524570 was automatically installed on version 1903. I now have Build 18362.476. I have the option also to download and Install 1909 feature update but I haven't done so yet. Im holding off for a couple of weeks to verify that feedback on here shows that it is stable before I upgrade to 1909.
After the CU KB4524570 installation Im now seeing no DeviceManagerSetup 131 errors at all

 

Event ID 131 Metadata errors happening lately.

2 days later and several shutdown and bootups...Im still seeing just one Event ID 131 DeviceSetupManager error. I expect that this error will also disappear on its own soon but I haven't got a clue why this happens. I went from 16 of these errors a week ago. Then it went down to 11 errors...and now just one. All this without any input whatsoever from me. Event viewer application logs show that when these errors are triggered it seems to be just a timing issue, probably caused by Microsoft Servers because straight afterwards the event is actioned. Very strange!