Event Viewer Metadata Entries – 131 & 201 due to Microsoft Registry Error

Topic

New Reply

[Tex265]

Upon checking my Event Viewer for another item, I noted that I am being flooded with Administrative Events 131 and 201.

Event 131, DeviceSetupManager    Metadata staging failed, result=0x80070490 (vars container numbers).

Event 201, DeviceSetupManager   A connection to the Windows Metadata and Internet Services (WMIS) could not be established.

https://answers.microsoft.com/en-us/windows/forum/all/device-setup-manager-metadata-staging-failed-event/67212749-06b1-48c6-9033-f560badb8751

It appears there may be an incorrect URL in the Registry that MS needs to fix (or can be fixed by Susan?) Anyone else with information?

There is also some mention in another posting that perhaps the December CU KB5033372 may fix the issue, but another said it caused the issue for them.

Windows 10 Pro x64 v22H2 and Windows 7 Pro SP1 x64 (RIP)

• This topic was modified 1 year, 3 months ago by Tex265.
• This topic was modified 1 year, 3 months ago by Tex265.

Reply | Quote

Replies

https://www.tenforums.com/windows-10-news/209722-kb5033372-windows-10-cumulative-update-build-19044-3803-19045-3803-a-3.html

I do not have those event id 131 & 201 entries in my event viewer, even with KB5033372 update installed.

Reply | Quote

Did you have them BEFORE installing the December update?

Since the culprit points to a registry URL entry error by MS, could you check that registry entry on your system and see/report what it shows?

Windows 10 Pro x64 v22H2 and Windows 7 Pro SP1 x64 (RIP)

Reply | Quote

I also have scores of these errors and warnings regarding those same metadata problems with the same event id’s mentioned above on both my Windows 11 23H2 machines, one a desktop pc and the other a laptop. They are continuing to show up after the December updates, though I’m not certain if they were there before (but I think they were). They are not just generated at bootup, either, but continue long after. It’s possible they began showing up after I installed the preview update KB5032288 on December 7th. Yes, I know, we’re not supposed to install those. I choose to install everything Windows Update sends down the pipe so as to keep my systems up to date. These errors and warnings do not seem to affect either system’s performance or operation.

 

Reply | Quote

I see this as a cosmetic error that I would wait for Microsoft to fix.

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote

I did not see this and posted a topic on the same. I have a LOT of these errors starting with install of the Win 10 22h2 Nov update.

https://www.askwoody.com/forums/topic/ready-for-thanksgiving-updates/#post-2614057

The solution to turn off : “Windows Settings, then select System, then select About (lower left-Windows 10), then Advanced System Settings (on the right-side), then select the Hardware tab, then click the Device Installation Settings button. In the popup box that appears, you can change it from YES (recommended) to NO (your device might not work as expected” makes me wonder why I would want that enabled at all!

Can you comment on that Susan?

1 user thanked author for this post.

NaNoNyMouse

Reply | Quote

Yup, that (switching to “NO”) worked to stop the 131/201 errors for me. Do I need to remember to revert after MS fixes the issue?

Reply | Quote

Tex265 wrote:

Upon checking my Event Viewer for another item, I noted that I am being flooded with Administrative Events 131 and 201…

Hi Tex265:

Also see the 21-Dec-2023 replies in post # 2614027 and post # 2614039 of Susan Bradley’s Ready for Thanksgiving updates? for comments about these DeviceSetupManager Event ID 131 errors.
————-
Dell Inspiron 5584 * 64-bit Win 10 Pro v22H2 build 19045.3803 * Firefox v121.0.0 * Microsoft Defender v4.18.23110.3-1.1.23110.2 * Malwarebytes Premium v4.6.6.294-1.0.2201 * Macrium Reflect Free v8.0.7783

Reply | Quote

Please note that DonT5 has filed a bug report at https://aka.ms/AAo1su9 about these DeviceSetupManager Event ID 131 errors via the Microsoft’s Feedback Hub app – see DonT5’s  04-Dec-2023 topic Getting multiple Event ID error 131 Device Set-up Manager in the MS Answers Windows 10 board.

If you have the Feedback Hub app on your system (my Win 10 laptop shipped from the factory with this app preinstalled) then be sure to go to that bug report and give it an Upvote.
————-
Dell Inspiron 5584 * 64-bit Win 10 Pro v22H2 build 19045.3803 * Firefox v121.0.0 * Microsoft Defender v4.18.23110.3-1.1.23110.2 * Malwarebytes Premium v4.6.6.294-1.0.2201 * Macrium Reflect Free v8.0.7783

1 user thanked author for this post.

Tex265

Reply | Quote

Tex265 wrote:

Upon checking my Event Viewer for another item, I noted that I am being flooded with Administrative Events 131 and 201.

All helpful news!

In the meantime, I was able to eliminate the 131 & 201 Events by following some Windows 10 posting advice and go to Control Panel> System> Advanced System Settings> Select the Hardware Tab> then the Device Installation Settings button and click “NO” and Save Changes.

Some are saying that the Windows 10 December update KB5033372 fixed the problem, but others said it caused the problem.  Since Susan has not given the go-ahead for December, I have not installed the update to see.

Windows 10 Pro x64 v22H2 and Windows 7 Pro SP1 x64 (RIP)

Reply | Quote

Hi Tex265:

I installed KB5033372 (OS Build19045.3803) on 17-Dec-2023 and it looks like my DeviceSetupManager Event ID 131 errors documented in my 21-Dec-2023 post # 2614039 in Susan Bradley’s Ready for Thanksgiving updates? have not stopped, but their frequency seems to have decreased slightly.

I’m also still getting Event ID 201 (A connection to the Windows Metadata and Internet Services (WMIS) could not be established) warnings logged multiple times a day for DeviceSetupManager.

————–
Dell Inspiron 5584 * 64-bit Win 10 Pro v22H2 build 19045.3803 * Firefox v121.0.0 * Microsoft Defender v4.18.23110.3-1.1.23110.2 * Malwarebytes Premium v4.6.6.294-1.0.2201 * Macrium Reflect Free v8.0.7783

1 user thanked author for this post.

CAS

Reply | Quote

My Win10 22H2 test VM did experience some intermittent event 201 warnings  and 2 event 131 errors but beginning on 12/12/2023 (3 days before installing the December CU) the flood gates opened and there has been a daily blizzard of those two events.

Reply | Quote

Windows 10 22H2 December CU. I am flooded with 131, 201 event errors and warnings

Reply | Quote

Tex265 wrote:

…I was able to eliminate the 131 & 201 Events by following some Windows 10 posting advice and go to Control Panel> System> Advanced System Settings> Select the Hardware Tab> then the Device Installation Settings button and click “NO” and Save Changes

Hi Tex265:

Microsoft released a partial fix for these events with the Feb 2024 Patch Tuesday updates. From the 15-Feb-2024 BleepingComputer article Microsoft says it fixed a Windows Metadata server issue that’s still broken, which 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 Improvements section of the release notes for the Feb 2024 cumulative Quality Update KB5034763 (OS Build 19045.4046) for my Win 10 v22H2 machine states “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.”

After applying KB5034763 I checked my Event Viewer at Applications and Services Logs | Microsoft | Windows | DeviceSetupManager| Admin and confirmed my DeviceManagerSetup Event ID 131 errors have stopped***, but I’m still seeing dozens of warnings logged every day for the DeviceManagerSetup Event ID 201 connection errors that say “A connection to the Windows Metadata and Internet Services (WMIS) could not be established“.

*** NOTE that I have not applied the workaround suggested in 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

Reply | Quote

Hi Imacri,

I’m afraid

KB5034763 of 15 Feb 2024 did not help me with this problem.
I started getting the ID 131 error messages on 4 March 2024 – in the last 7 days I have had 448 error messages. ID 201 again in the last 7 days 100 warnings.

The only windows update on the 4 February 2024 was KB 5034582 (Cumulative Preview for .NET Framework 3.5 etc.)

I did some searches to see how far back these errors have been occurring and the earliest was about 2014, only 10 years. Is there any point in even approaching Microsoft? It seems to me to be a lost cause, as they have never really paid serious attention to these warnings.

<hr />

Lenovo Z51 64-bit Win 10 Home, build 19045.4046 22H2. Malwarebytes Premium 4.6.9.314   1.0. 81848 1.1.2276,  Windows Defender Security,   Firefox 123.0.1 64 bit

Reply | Quote

I too had the Event Logs begin flooding with the annoying 131 errors on 12-8.  I hadn’t just installed any updates, & the related URL in the registry had not changed from earlier registry values.  I suspect there was a problem with Microsoft’s servers.

Rather than modify my Device Installation Settings (potentially missing an important device update), for the time being I merely turned off logging for Microsoft-Windows-DeviceSetupManager/Admin (Under Applications and Services Logs.)  The logging toggle is in the right side Actions panel of the Event Viewer.  I’ll re-enable its logging after Microsoft has a chance to fix the issue.

Reply | Quote

Oh, I also reported the issue on the Feedback Hub.  Nudge, nudge…

Reply | Quote

rChaz wrote:

(potentially missing an important device update)

Never trust Windows update drivers, firmware.
Always download from OEM or your PC manufacturer support site.

Reply | Quote

Alex5723 wrote:

rChaz wrote:

(potentially missing an important device update)

Never trust Windows update drivers, firmware.
Always download from OEM or your PC manufacturer support site.

Totally agree which is why I asked early on what possible reason would I want this turned on in the first place? Can’t imagine what I could miss of importance and the risk outweighed any reward.

Reply | Quote

rebop2020 wrote:

and the risk outweighed any reward

There is minimal risk if you check periodically for BIOS/Firmware, drivers.. updates.

For GPU updates (AMD, Intel, NVIDIA) follow my posts at : https://forums.lenovo.com/t5/Gaming-Laptops/GPU-Updates-Intel-AMD-Nvidia-Driver-updates-Fixes-Follow-this-thread-by-alex5723/m-p/5071433

Reply | Quote

Alex5723 wrote:

Windows 10 22H2 December CU. I am flooded with 131, 201 event errors and warnings

no 131 event id errors found on my DeviceSetupManager event log.
some 201 errors do show up on mine but not 131

Reply | Quote

rebop2020 wrote:

Device Installation Settings

Device Installation Settings = NO blocks Windows update drivers installation which is a good thing (the only option for Windows home users).

Reply | Quote

Hi Tex265:

Just an FYI that Susan Bradly started a new topic about these DeviceSetupManager Event ID 131 errors in the Windows 11 Version 23H2 board at New Windows 11, lots of Events 131 on 06-Sep-2024.  I’m beginning to doubt that Microsoft will ever fix this issue.
———–
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.10.127-1.0.5021 * Macrium Reflect Free v8.0.7783

1 user thanked author for this post.

satrow

Reply | Quote