Device Setup Manager Metadata staging failed Event ID 131

Hi DiverJer:

Just an FYI that Microsoft released a partial fix for these errors with the February 2024 Patch Tuesday updates of 13-Feb-2024.

The 15-Feb-2024 BleepingComputer article Microsoft says it fixed a Windows Metadata server issue that’s still broken states in part:

..."Same here - no 131's anymore but **** of 201's," reads a post on the Microsoft forums. It is unclear why Microsoft disabled the Metadata servers in the first place and why they are not bringing them back online as expected. BleepingComputer contacted Microsoft about this issue yesterday but has not received a response to our email.

The release notes for the Feb 2024 cumulative Quality Update KB5034763 (OS Build 19045.4046) for my Win 10 v22H2 machine state “This update addresses an issue that affects the download of device metadata. Downloads from the Windows Metadata and Internet Services (WMIS) over HTTPS are now more secure.”

Since installing KB5034763 I have not had any DeviceManagerSetup Event ID 131 errors logged in my Event Viewer at Applications and Services Logs | Microsoft | Windows | DeviceSetupManager| Admin ***, but I'm still seeing dozens of warnings logged every day for for DeviceManagerSetup Event ID 201 that say "A connection to the Windows Metadata and Internet Services (WMIS) could not be established".

*** NOTE that I did not apply the workaround suggested <here> on page 1 of this topic (i.e.. my setting at Advanced System Settings | Hardware tab | Device Installation Settings button | "Do you want to automatically download manufacturers' apps and custom icons available for your devices?" is still set to the default YES).

Dell Inspiron 5584 * 64-bit Win 10 Pro v22H2 build 19045.4046 * Firefox v123.0.0 * Microsoft Defender v4.18.23110.3-1.1.24010.10 * Malwarebytes Premium v4.6.9.314-1.0.2276 * Macrium Reflect Free v8.0.7783

I am having same issue. Repeated BSD crashes with stop code of "Inaccessible Boot Device". Examination of Event Viewer logs show simultaneous Code 131 error (sometimes many). This started a few weeks ago, and occurs several times a day.

I am running Win Pro 22H2 build 22621.3085 on a Lenovo Yoga c940 model 14IIL laptop.... I have tried running Windbg but there are no dump files generated by these repeated crashes.

Hi RoboF839:

I would give you the same advice I gave to Alcala Angel - use the workaround posted <here> on 23-Dec-2023 on page 1 of this thread (i.e., change the Device Installation Settings to "No" in your Advanced System Settings). If this stops your DeviceSetupManager Event ID 131 errors but your BSODs continue then the two problems may not be related.

I have a Win 10 OS but some of the following information may still be helpful to you. My 13-Oct-2023 post # 2593948 in bsfinkel's Unknown BSOD in the AskWoody forum has information on using free utilities like BlueScreenView and/or WhoCrashed to analyze any mini-dump files located in the hidden and protected C:\Windows\Minidump folder. These free utilities aren't as accurate as a detailed Windows Debugger (WinDbg) analysis of full dump files, but they can sometimes correctly identify the name of the driver or module in the crash stack that was responsible for your BSODs.

If your BSODs are not generating full dump files at C:\Windows named MEMORY.DMP that are required for a proper WinDgb analysis in BleepingComputer's Windows Crashes and Blue Screen of Death (BSOD) Help and Support forum then post # 2596155 of that same AskWoody thread also has instructions on how to configure your advanced System Failure settings at Start | Settings | System | About | Advanced System Settings to generate full dump files. See the Windows Central article How to Manage Crash Dump Settings on Windows 10 and ElevlenForums tutorial Change BSOD Crash Memory Dump File Type in Windows 11 for detailed instructions and a description of the different types of memory dump files you can select from the Write Debugging Information dropdown.

Dell Inspiron 5584 * 64-bit Win 10 Pro v22H2 build 19045.3930 * Firefox v122.0.0 * Microsoft Defender v4.18.23110.3-1.1.23110.2 * Malwarebytes Premium v4.6.8.311-1.0.2249 * Macrium Reflect Free v8.0.7783

Hello Great White North & Others:

I am having same issue. Repeated BSD crashes with stop code of "Inaccessible Boot Device". Examination of Event Viewer logs show simultaneous Code 131 error (sometimes many). This started a few weeks ago, and occurs several times a day.

I am running Win Pro 22H2 build 22621.3085 on a Lenovo Yoga c940 model 14IIL laptop. I have performed a complete OS reset, run all of the vendor's hardware diagnostics, run sfc /scannow, and made sure I have all of the latest drivers, etc. I have also disconnected from my dock and all peripherals (except a Synology 220+ NAS now connected by WiFi).

I have tried running Windbg but there are no dump files generated by these repeated crashes.

The symptoms are similar to those described by Alcala Angel - shortly before the BSD freeze the NAS begins to spool up and then displays freeze.

My immediate question is whether it is possible the Code 131 error and the BSD are related? It would help in terms of where I focus my time.

Thanks to all,

My Pc restarts after booting up a game now and also sometimes after 20mins of being on in general. I sometimes also get BSOD on those random restarts. this all started after that update. What could I do? I've tried so many things even upgraded parts of my pc and still get these issues... Checked all my wires and everything is perfect. I can't do anything! I am surprised it hasn't shut off yet actually.

The above mentioned fix does stop the errors, but keep in mind its just a bandaid fix and doesnt actually fix fix the problem sadly. Only Microsoft can actually fix it. So bandaids it is.