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. lmacri 2,505 Reputation points
    2024-04-07T14:48:22+00:00

    Event ID 131 Source: DeviceSetupManager

    this one has 250 errors in the last 7 days Microsoft-Windows-DeviceSetupManager/Admin

    what do I do? I got 5 BSOD this week

    Hi Cleaven D'H :

    Please try the workaround suggested in my 23-Dec-2023 post <here> on page 1 of this thread [i.e., open a Run dialog box (Windows key + R), enter sysdm.cpl to open your Advanced System settings and change the Device Installation Settings to "No".***

    Image

    If this stops your Event ID 131 errors after you re-boot your computer and your BSODs stop then you can be relatively certain the Event ID 131 errors are the cause of your problem. If your system continues to BSOD after the Event ID 131 errors have stopped then you will have to continue troubleshooting to find the root cause of your BSODs. Note that I have chosen to leave my Device Installation Settings to the default "Yes" (for testing purposes only) and dozens of these DeviceSetupManager Event ID 131 errors are logged in my Event Viewer every day, but these errors do not have a noticeable impact on my system performance.

    _______________________________________

    *** NOTE: Changing your Device Installation Settings to "No" should prevent Windows from checking for available updates for your hardware drivers, but this should not be a issue since there are other ways you can check for available hardware driver updates (e.g., on your computer manufacturer's support site, using the Intel Driver & Support Assistant utility, etc.) while you are waiting for Microsoft to fix this bug.

    Dell Inspiron 15 5584 * 64-bit Win 10 Pro v22H2 build 19045.4170 * Firefox v124.0.2 * Microsoft Defender v4.18.24020.7-1.1.24030.4 * Malwarebytes Premium v4.6.12.323-1.0.2309 * Macrium Reflect Free v8.0.7783

    Was this answer helpful?

    0 comments
  2. Anonymous
    2024-04-07T13:57:49+00:00

    Event ID 131
    Source: DeviceSetupManager

    this one has 250 errors in the last 7 days

    Microsoft-Windows-DeviceSetupManager/Admin

    what do I do? I got 5 BSOD this week

    Was this answer helpful?

    0 comments
  3. Anonymous
    2024-04-05T04:08:14+00:00

    THis is crazy, why is Microsoft not fixing this? I have 6 computers at my office all with the same exact issue, ****?!?!?

    Was this answer helpful?

    0 comments
  5. Anonymous
    2024-03-24T10:59:22+00:00

    Updating drivers via the OEM websites is what I've been doing anyway. Just without waiting for Windows to do so, if it seemed to need it.

    This is not just a Windows 10 issue, though. The more errors, the more I've been looking, and it's on the Windows 11 forums too. So they're going to have to fix it eventually or...?

    Meanwhile, I guess warnings are an improvement over errors.

    I hope.

    Was this answer helpful?

    0 comments