Windows 10: Metadata staging failed, for Event ID:131

Metadata staging failed, result=0x80070490 for container '{5094484E-6925-FDD5-AACE-D9DA6785FB29}' Event ID:131I 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

:)

 

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,

 

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 URL (go.microsoft.com/fwlink/?linkid=252669&clcid=0x409) and got redirected as site not available to dmd.metaservices.microsoft.com where I pressed continue and got a 505 Bad Gateway error.

And then just for the heck of it I did a DISM with /checkhealth and all was good, did DISM with /scanhealth and it said all was fine. Even did sfc /scannow and chkdsk, all was well. NO system files missing or disk problems.

Then I did some thinking (which can be dangerous) Booting or adding external drives got many of the 131 errors. However when I disconnect from the internet and boot system or add external drives- I GOT NO ERRORS Event code131.

Between all this, I believe our friends at Microsoft have a bad pointer. in the registry entry devicemedadataserviceURL.

I did an image of system prior to updating, thought about restore and still considering. All is working fine, I tried all devices and all are working. I shouldn't look at that event log! I just today after the mentioned above updates started getting these errors.

I should add going to control Panel, search for Device Installation, select change device installation setting to NO- does fix the error. Tested, reboot or adding external drive no longer gets the 131 error. Now is this a good idea, I don't know, I am not that up on computers anymore. I retired in 2003 after 38 years as system software tech on mainframes. Was certified also for Microsoft, but a lot changed since then and I really don't attempt to keep up.