Device Setup Manager Metadata staging failed Event ID 131

Don't seem to be causing any obvious problems? Like hell they're not!

I keep getting these problems related to my LG Webos TV and the error is causing sounds like USB disconnect/RE Connect on a regular basis, in addition after doing this a number of times it is causing my Laptop to reboot.

The annoying thing is this Laptop is brand spanking new - less than a week old and I can't tell if this is a problem with the laptops hardware or something Microsofts STUPID operating system is doing, even more annoying is that it chooses to reboot right in the middle of some complicated task as opposed to when it's not being used and it's driving me up the damned wall.

Every time I lose work, it's beyond a joke.

Microsoft needs to damn well fix this!

Fix: Error: Device setup manager metadata staging failed event ID 131

Here's what I did that worked for me:

Step 1: (corrects future devices)

a) open regedit

b) goto key HKEY_LOCAL_MACHINE > SOFTWARE > Microsoft > Windows > CurrentVersion > Device Metadata

c) goto key DeviceMetadataServiceURL key and enter: https://dmd.metaservices.microsoft.com/dms/metadata.svc . If you go there directly you'll get site cant be reached, but it seems to work in practice

d) restart

then

Step 2: (This will fix existing installed devices)

a) open event viewer and search for 131 errors metadata staging failed and copy the containers including brackets (Copy each to to notepad if there are many to make it easier)

b) open gpedit

c) goto computer/configuration/administrative templates/system/device installation/device installation restrictions

d) click on allow administrators to override device installation restriction policies

e) then click enabled

f) (now clean up existing installed devices): - go to the same key as before (computer/configuration/administrative templates/system/device installation/device installation restrictions) and find allow installation of devices that match any of these device ID. - go to event viewer and copy IDS into noptepad Include brackets in copies "{}" - then enter them by enabling key and pressing the show button - enter the IDs one each line

g) restart

Here’s my take. They fixed the attempted overwrite of drivers downloaded when they are not there, i.e., the 131s but the link is still screwed up. Yea Microsoft. It’s a nonfix fix. Your drivers and devices are not updating. It doesn’t get an answer when knocking on the door and moves along.

Just leave the “No, I take care of my stuff” boxed checked and move on.

The problem has to do with Metadata Staging servers that Microsoft operates and which are down since November and which a recent Windows Update now has every updated Windows 10 and Windows 11 machine pointing to. They contact those servers to get device drivers and high-res device icons. I noticed this because I handle printing in my organization and this is affecting the adding of printers to a user's local profile. You can print to a newly added queue immediately but, you must wait 4-6 min before you can manage it.

I have an enterprise support case open with them and it has been escalated to the Drivers & Updates team.

I just bought and built a new PC ... This problem has me getting 4 or 5 BSOD a day. ...

Hi RayanneZ:

Does the workaround posted <here> on 23-Dec-2023 on page 1 of this thread (i.e., changing the Device Installation Settings to "No" in your Advanced System Settings) stop your DeviceSetupManager Event ID 131 errors?

As far as I know, when this setting is set to "No" the only side effect is that Windows Update will stop offering firmware and hardware driver updates, and that's a good thing in my opinion. Shortly after I purchased my Dell Inspiron 5584 laptop it would not boot up because Windows Update unexpectedly delivered a BIOS firmware update, and since then I've used my Local Group Policy Editor (available with Win 10/11 Pro editions, not Home editions) to configure Windows Update to stop offering firmware and driver updates. I currently use Dell Update, Dell's proprietary software updater utility, to check for Dell software and driver updates that match the Service Tag for my Inspiron 5584 and can also be found on Dell's support page for the Inspiron 5584. I'm not sure what you mean by "bought and built" and what customizations you've made to your new computer, but it's always possible that a performance tweak or an outdated or incompatible hardware driver is responsible for your BSODs.

If changing your Device Installation Settings to "No" in your Advanced System Settings doesn't stop your BSODs then I'd suggest you post in BleepingComputer's Windows Crashes and Blue Screen of Death (BSOD) Help and Support board - see the posting instructions <here>. One of their trained volunteers will analyze your crash dumps with the WinDbg debugger and should (hopefully) be able to isolate the cause of your BSODs.

Dell Inspiron 5584 * 64-bit Win 10 Pro v22H2 build 19045.3803 * Firefox v121.0.1 * Microsoft Defender v4.18.23110.3-1.1.23110.2 * Malwarebytes Premium v4.6.8.311-1.0.2242 * Macrium Reflect Free v8.0.7783 * Dell Update for Windows Universal v5.1.0