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
    2023-12-29T19:37:13+00:00

    I also supplied feedback via the Feedback Hub:

    1.) Click Start -> Search for Feedback Hub --> Open Feedback Hub

    2.) On the Home tab search for "DeviceSetupManager Event ID 131 error"

    3.) Click Upvote

    4.) Search for other keywords such as metadata or 131 error and upvote those as well

    Was this answer helpful?

    30+ people found this answer helpful.
    0 comments
  2. Anonymous
    2023-12-11T02:24:55+00:00

    Started having same problem on December 6. The device manager is unable to reach the microsoft OEM repository. Check your Warnings for 200, 201 errors.

    What I have done is settings>system>advanced settings, on hardware tab, install button, “manage my own devices”. I’m on my ipad and that’s from memory.

    If your system is stable, and you are NOT going to attach new devices, this turns off the auto-update of device drivers. If you add a new device you may have to update from the manufacturer site.

    This does two things, keeps your machine from flooding the events log and keeps it from constantly wasting resources to do that.

    Now, that done. Check it once a week by reselecting the automatic update and see if it’s been fixed.

    Was this answer helpful?

    30+ people found this answer helpful.
    0 comments
  3. Anonymous
    2023-12-20T21:41:04+00:00

    I'm getting the same problem. Extremely annoying, computer dings very very regularly due to this failure.

    Yes, confirmed that the registry key above referencing http://go.microsoft.com/fwlink/?LinkID=252669&clcid=0x409 points to a remote microsoft service that is not working.

    Was this answer helpful?

    20+ people found this answer helpful.
    0 comments
  4. Anonymous
    2024-05-08T14:18:08+00:00

    More than 6 months later and Msft still haven't fixed this.

    COME ON MICROSOFT !!!!!

    I pride myself in having my servers setup so there are normally no errors in the Event Log.

    That way if something happens, a qiuck glance in the Event Viewer can give a hint to where you're problem lies.

    Now when I open Event Viewer on a perfectly fine server, it's all riddled with DeviceSetupManager errors.

    COME ON MICROSOFT !!!!!

    Was this answer helpful?

    10+ people found this answer helpful.
    0 comments
  5. Anonymous
    2023-12-21T05:02:20+00:00

    Thank you very much for the perfect explanation, Jphn.

    Same here, the redirect is broken. In my case, the redirect URL points to:

    http://dmd.metaservices.microsoft.com/metadata.svc

    which gives me a 502 Bad Gateway response.

    502 Bad Gateway

    Microsoft-Azure-Application-Gateway/v2

    Was this answer helpful?

    10+ people found this answer helpful.
    0 comments