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
    2024-12-10T06:45:29+00:00

    I have the same issue, only I was able to narrow the UUID's down to specific UPNP devices that are trying to get added as "software devices" in Device Manager and typically show up as "Multimedia Devices" in the Devices and Printers dialog. Turns out, they are ALL SONY devices - two TV's, a receiver and a Blu-Ray player that are all connected to the same network.

    I caught it by noticing that Device Manager continually refreshed and simply ended up watching for changes and thinking it had to be a USB device erroring. I brought up event viewer anyway and noticed that the DeviceSetupManager had been spamming these errors on the same handful of UUID/Containers all day AFTER a fresh install.

    I tried turning off UPNP in services with no success. I disabled the devices in device manager with no success. I tried uninstalling them with no success and turned off network discovery with no success. They all kept reappearing, sometimes with multiple instances.

    This "fix" technically worked, it stopped the error messages in event viewer, but device manager is still refreshing at ~10ish second intervals meaning there is still something happening in the background that isnt being caught in the logging.

    Im not sure how totally disabling UPNP and network discovery even still allowed the devices to reappear. Thats incredibly concerning in its own right, not to mention this error having been present for going on 2 years.

    I've seen some people think that the Containers are random, but they arent. Check the UPNP devices and see if the UUID or "Unique Identifier" of the device (Go to Devices and Printers, right click on one of the Multimedia devices like a TV and click properties, then the UPnP tab. The UUID is on that tab) matches up with one of the containers in the "Metadata staging failed"/DeviceSetupManager errors in the event viewer. I'll put money on the fact that it probably does.

    If anyone else see's this, please let me know. I truly think that this is not only a Microsoft issue, but also an issue with how Sony aggressively makes their devices spam UPnP traffic across the network.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  2. lmacri 2,505 Reputation points
    2024-10-06T14:32:54+00:00

    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...

    Hi Chasse Court:

    If you read my 23-Dec-202 post <here> on page 1 of this topic I said "These DeviceSetupManager Event ID 131 errors in my Event Viewer are annoying but they don't seem to be causing any obvious problems on my Win 10 laptop". I didn't claim that was the case for everyone.

    Try the workaround suggested in that post (i.e., change the Device Installation Settings in your Advanced System Settings to "No" and re-boot ***) . If this stops your Event ID 131 errors and you continue to have issues with your LG Webos TV then the Event ID 131 errors are not the root cause of your problem.

    Dell Inspiron 15 5584 * 64-bit Win 10 Pro v22H2 build 19045.4894 * Firefox v131.0.0 * Microsoft Defender v4.18.24080.9-1.1.24080.9 * Malwarebytes Premium v5.1.11.133-1.0.5048 * Macrium Reflect Free v8.0.7783

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2024-01-15T22:57:14+00:00

    I am late to the party, but this is happened to me too. I have an external drive with most of my games on it and after an update on 1/10/24 I started losing signal a lot. It had happened once on the 12th of December, but I chalked it up to just one of those things since it didn't happen again until the 10th. It has been happening every day since then no matter what I do. Like you, I followed some advice about looking at the event viewer and I am getting the DeviceSetup Manager Error Event ID 131. I am going to try what you did and see if it works. I used to dabble in tech support, but that was over 20 years ago and the systems are a lot different now. I no longer have the tech head for this stuff and just want my games back. I have the following:

    OMEN by HP Desktop PC

    20C1 Cycle AV

    NVIDIA GeForce RTX 2060 Super (8 GB GDDR6 dedicated)

    WD Black 256 GB PCIe® NVMe™ TLC M.2 SSD

    HP OMN Moria3 B450 30L PREM US PC

    HyperX® 16 GB DDR4-3200 XMP RGB SDRAM (2 x 8 GB)

    Realtek Wi-Fi 5 (2x2) and Bluetooth 5 combo, MU-MIMO supported

    Office Trial

    Windows 10 Home PLUS

    Cooler Master 500 W Smart AC power adapter

    OSLOC US

    AMD Ryzen™ 5 3600 W/RGB Air Cooling (3.6 GHz up to 4.2 GHz, 32 MB L3 cache, 6 cores)

    MISC HEVC MEDIA EXTENSION HP

    WARR 1/1/0 US

    CKIT HP CTO OMEN 1C20 US

    I opened up a ticket with NVidia but so far none of what they have suggested is working. I've only had this system since Feb 2021 so I am thinking it has to be an error in Windows somewhere screwing with the driver. Not sure.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  4. Anonymous
    2024-01-08T22:48:05+00:00

    Same here, I reported it today.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  5. Anonymous
    2023-12-29T12:18:03+00:00

    Good advice. That’s what I plan to do😊

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments