Device Setup Manager Metadata staging failed Event ID 131

Anonymous

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.

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

Anonymous

2024-11-25T20:41:16+00:00

i dont understand
Was this answer helpful?

1 person found this answer helpful.

0 comments No comments
lmacri 2,500 Reputation points

2024-09-06T13:08:06+00:00

Hi YippeKiYayMothr :

If you temporarily change the Device Installation Settings to "No" in your Advanced System Settings as instructed <here> in the 23-Dec-2023 post on page 1 of this thread *** and re-boot your computer this should stop the DeviceSetupManager Event ID 131 errors.

After you have done this please monitor your Event Viewer for a few days to confirm your DeviceSetupManager Event ID 131 errors have stopped, and then post back to let us know your computer model, Windows OS, and whether your random system restarts have also stopped.

*** NOTE: Temporarily changing this advanced system setting to "No" will not harm you system, but it will prevent Windows from searching for new drivers for your hardware components. However, this should not be a problem for most users, even if this setting is left at "No" in the long term while they wait for Microsoft to fix this bug, since most computer models have a support page on the manufacturer's site that has download links for the latest recommended drivers for their hardware components.

Dell Inspiron 15 5584 * 64-bit Win 10 Pro v22H2 build 19045.4780 * Firefox v130.0.0 * Microsoft Defender v4.18.24070.5-1.1.24070.3 * Malwarebytes Premium v5.1.9.124-1.0.5014 * Macrium Reflect Free v8.0.7783
Was this answer helpful?

1 person found this answer helpful.

0 comments No comments
lmacri 2,500 Reputation points

2024-08-23T12:16:14+00:00

i experience a problem in windows startup in which mouse and keyboard don't start immediately they delay to start an then i hear device connection sound and they start working but i was not able to find a cause of the problem

could it be this metadata staging failed error which causing it? ...

Hi taha khalid:

The impact of these DeviceSetupManager Event ID 131 errors varies from machine to machine. For example, I typically see about 30 to 40 of these errors per day (in short bursts of 5 or 6 errors) on my own Win 10 v22H2 machine and they don't appear to be causing a problem so I'm just ignoring them for now.

If you want to know if your DeviceSetupManager Event ID 131 errors are interfering with the loading of your keyboard and mouse drivers at bootup the best way to test this is to change the Device Installation Settings to "No" in your Advanced System Settings as instructed <here> in the 23-Dec-2023 post on page 1 of this thread and re-boot to stop the errors. Monitor your Event Viewer for a few days just to confirm this has stopped the Event ID 131 errors and see if this fixes the problem with your keyboard and mouse. If the problem persists then the Event ID 131 errors are not the cause.

Dell Inspiron 15 5584 * 64-bit Win 10 Pro v22H2 build 19045.4780 * Firefox v129.0.2 * Microsoft Defender v4.18.24070.5-1.1.24070.3 * Malwarebytes Premium v5.1.8.123-1.0.5007 * Macrium Reflect Free v8.0.7783
Was this answer helpful?

1 person found this answer helpful.

0 comments No comments
Anonymous

2024-08-22T01:43:06+00:00

yes it does indeed take away the errors popping un in event viewer, but it does not stop the games crashing....witch is what brought me to the event viewer in the first place.so as of a year later we are all still having the crashes. And in my case i cant paly any games.
Was this answer helpful?

1 person found this answer helpful.

0 comments No comments
Anonymous

2024-01-09T17:54:42+00:00

Thanks. You've done a service to humanity.
Was this answer helpful?

0 comments No comments

Share via

Device Setup Manager Metadata staging failed Event ID 131

115 answers