Device Setup Manager Metadata staging failed Event ID 131

Anonymous
2023-12-08T03:12:46+00:00

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.

Windows for home | Windows 10 | Devices and drivers

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

115 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2024-03-24T10:09:42+00:00

    “The device installation thing in advance system settings was one of the first things I tried on reading up on this. I didn't do anything to help them.”

    That “fix” should have stopped the warnings and errors by preventing the driver updates. Double check that setting. Make sure when you open “Devices and Printers” there is a yellow band at the top that says something about being able to provide better performance and fancy icons.

    The gpedit seemed promising provided the MS site is *ACTUALLY* available and providing the updates. I’m not convinced they are.

    I suspect we’re just going to have to update drivers via the OEM websites for the next two years at which time support for Windows 10 ends, and I switch to my iPad and toss my Windows machines altogether.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2024-03-24T01:40:27+00:00

    I've actually tried both those things. The registry/gpedit fix resulted in a proliferation of Event IDs 200, 201, and 302 -- many more than there had been. And it didn't even stop Event ID 131.

    And I double-checked: the relevant container number was one I had already specified in gpedit to allow.

    The device installation thing in advance system settings was one of the first things I tried on reading up on this. I didn't do anything to help them.

    I just tried it again. So far it seems event ID 131 is gone this time, but there are as many event IDs 200, 201, and 202 as ever.

    These are warnings, though,so I guess that's better?

    So I put things back the way they were, the registry and gpedit, that is, because it seems like only Microsoft can fix this. If they bother.

    Very discouraged.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2024-03-19T20:04:07+00:00

    I have also had this happening since last fall. My PC has been super unstable. Keeps hard freezing and everyday I'll get dozens of these 131 event codes in my event viewer.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2024-03-18T17:39:12+00:00

    Thanks - trying it now. Will let you know how I get on. You would hope Microsoft would actually issue a fix for it in an update.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2024-03-14T05:43:15+00:00

    I tried making that http into https, and that gets rid of the event ID 131 errors, but not the event IDs 200,201, or 202, although those are warnings rather than errors; in fact I think there are even more of those, lol.

    Changing the device installation settings doesn't get rid of those, and that by itself doesn't get rid of the event ID 131 errors either. Not from Control Panel, anyway. I have not yet tried doing it via Group Policy (in on Windows 10 Pro) or via the registry. Is it worth trying those?

    Was this answer helpful?

    0 comments