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
    2024-08-23T08:11:16+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

    anyone else have same problem ?

    Was this answer helpful?

    0 comments
  2. lmacri 2,505 Reputation points
    2024-08-22T11:49:18+00:00

    yes it does indeed take away the errors popping un in event viewer, but it does not stop the games crashing....

    Hi michael schubert1:

    If you used the workaround posted <here> on 23-Dec-2023 on page 1 of this thread (i.e., you changed the Device Installation Settings to "No" in your Advanced System Settings) to stop your DeviceSetupManager Event ID 131 errors and your games are still crashing then that implies that your crashes are not caused by the logging of these errors.

    However, changing your Device Installation Settings to "No" will prevent Windows from searching for updates for your hardware drivers, and it's always possible that you have an outdated or buggy graphics driver (a common cause of crashes for graphics-intensive applications) or some other hardware driver.

    You did not mention your computer model, operating system or what game(s) are crashing, but if your APPCRASH events are generating .WER (Windows Error Reporting) files you should be able to display details about your crashes, including the faulting module name, using NirSoft's AppCrashView utility. It's a portable app, which means that all you have to do is unzip the appcrashview.zip file in any location (including a removable USB stick) and run the AppCrashView.exe executable. The program isn't installed on your hard drive so you can simply delete the unzipped AppCrashView files if you don't want to use it again.

    If the developer of your game has their own forum you might want to post there and request assistance so this thread doesn't go off-topic.

    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?

    0 comments
  3. Anonymous
    2024-08-17T23:22:57+00:00

    Si ma per adesso il mio pc va di merda grazie ai geni che hanno fermato tutto il regno unito con aggiornamenti sbagliati.... TUTTO STA ANDANDO IN ROVINA NON SONO IN GRADO DI FARE DEI AGGIORNAMENTI SERI SENZA DANNI TUTTO VA A ROTOLI.......

    Was this answer helpful?

    0 comments
  4. Anonymous
    2024-08-10T09:44:32+00:00

    The usual sloppiness shown by Microsoft. Annoying bugs and problems not solved for many months or years...

    Was this answer helpful?

    0 comments
  5. Anonymous
    2024-07-09T09:01:29+00:00

    Same here.

    Was this answer helpful?

    0 comments