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 No comments

115 answers

Sort by: Most helpful
  1. Anonymous
    2025-02-10T19:10:10+00:00

    I turned off automatic updates and reported it to Microsoft. Still not fixed so I won't update.

    You think it'll be fixed with automatic updates turned off? You would need it on for your pc to be able to update automatically to get fixed, wouldn't you?

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2024-12-27T20:46:21+00:00

    I am also having this issue and while some of the errors I was able to narrow down to old printer drivers deciding to reinstall themselves repeatedly (I fixed that) most of the Container IDs throwing errors are pointing to generic/system devices, like the Generic PnP Monitor service (NOT the driver for my specific monitor).

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2024-09-29T10:36:41+00:00

    I have just been manually disabling the Device Setup Manager service, which is tricky to do, but works!

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2024-09-07T21:59:36+00:00

    What i don't understand is why now amd why not everyone?

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2024-09-06T06:30:02+00:00

    I am getting the same error, but it is causing my computer to restart by itself and it's always random. Any help would be greatly appreciated.

    Was this answer helpful?

    0 comments No comments