Windows 10: Device Setup Manager Metadata staging failed Event ID 131

I did KB 890830, KB5032339, KB5032189 and KB4023057 today and on reboot after updating I started getting many of the event id 131 Device Setup Manager Metadata staging failed. I would get the code 131 when plugging in my backup USB external. Even when using USB thumb drive- this never happen prior to today's update. Also, lots of the Event ID on boot. Never had these prior to the update. I am on WIndows 10 PRo, 22H2, OS Build 19045.3693, Dell OPtiplex 64 bit, 12GB memory and 500GB disk. I got to looking at the registry for devicemedadataserviceURL. I went to that UR

:)

 

Device Setup Manager event

Hi,

Thank you for posting your query in Microsoft Community.

I understand your concern and will assist you to resolve this issue.

I suggest you to refer the link below and check if it helps.

Windows Update error 0x80070490

https://support.microsoft.com/en-us/kb/958044

Device Setup Manager Event ID 131 0x80070490

Metadata staging failed, Device Setup Manager EventID 131 0x80070490

Hope this helps. If the issue remains unresolved, please get back to us and we would be happy to help.

 

Windows 10 error id 131 metadata staging failed after upgrade to Windows 10 from Windows 7

this error started after upgrade to windows 10 from windows 7 it is id 131 device setup manager metadata staging failed I am attaching a picture of event viewer showing errors these errors happen almost every day.

 

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,