Windows 10: Clean install 1909 event ID 131 help me to fix it

After making clean install of 1909 I get bunch of these event ID 131 errors.

Description says "Metadata staging failed, result=0x80004005"

I googled a bit and its quite often error and it has something to do with Devices and Printers being timing out to update with internet server. Some people advice to change the server url but not sure if I should touch it or worry about it since some folks say that issues resolves itself after some times.

Any info on this?



https://preview.redd.it/qsp82wx3cdy...bp&s=45373236c196a2af1453bdb5112cb8190677724a

submitted by /u/mRnjauu
[link] [comments]

:)

 

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

 

Event ID 131 Metadata errors happening lately.

I got a few yesterday but none today.

 

Metadata staging failed - Event ID 131


Good morning,

Ever since I upgraded my computer to Windows 10 (Home) 64-bit a few months ago from Win 8.1 I have discovered the following Event ID 131 error in Event Viewer, sometimes as many as five times in a row, after restarting or upon booting up:

Metadata staging failed, result=0x80070490 for container '{1959BB49-AC94-11E5-AE34-3010B356F6E6}'

After googling for a few hours I did find a forum (TechNet) where this error was attributed to 'timing' and that Microsoft was aware of it.

A couple workarounds were given until Microsoft comes up with the fix. One workaround given was changing the time from 'Windows-time' to 'time-nist.gov'. However, even though it worked for some folks, it didn't stop the error in my Event Viewer.

I am just wondering if anyone on this forum has experienced the same Event Viewer error and maybe found a way to stop it from occurring.

Thanks and regards,