en[EVENT131] Metadata staging failed

SC2 2019-11-15

2024-06-18

Atom | RSS

このサイトを検索 | Search this site

,Japan

to japanese

EVENT ID 131 /DeviceSetupManager

This article is about [Event ID 131 | DeviceSetupManager] that was recorded after Windows 10 November 2019 Update, v1909 update.

If I was looking up,

I found a procedure to modify the value of DeviceMetadataServiceURL in Registry Editor, which is the same procedure as [Event ID 200 | DeviceSetupManager] that I wrote down in this blog.

On my PC, Event ID 200 was logged after updating to Windows 10 v1903 and was related to DeviceMetadataServiceURL.

The DeviceMetadataServiceURL was fixed at v1903, but the value of DeviceMetadataServiceURL after v1909 update was initialized to the URL before correction.

Before correction

http://go.microsoft.com/fwlink/?LinkID=252669&clcid=0x409

That means

It seems that the Windows Update function update program that changes the OS build is designed to initialize [DeviceMetadataServiceURL] to an invalid URL.

Stop recording in the event log

There are three types of Event-ID131 countermeasures that I consider.

ignore
Stop recording in the event log
Modify DeviceMetadataService URL

Since Steps B and C use Registry Editor, there is a risk that the PC cannot be restarted if the operation is mistaken, so we recommend Option A for those unfamiliar with the PC.

Event Log

Event Log
message	Metadata staging failed. Result of container'{00000000-0000-0000-FFFF-FFFFFFFFFFFF}'=0x8007000D
log name	Microsoft-Windows-DeviceSetupManager/Admin
Source	DeviceSetupManager
Event id	131
level	error
user	SYSTEM
Guid	{fcbb06bb-6a2a-46e3-abaa-246cb4e508b2}

Repair procedure

Registry operations are at your own risk

Before working with Registry Editor
Make a backup copy of your registry in case something goes wrong.

To start Registry Editor:

Start the execution by specifying the file name ( Win + R ).
Type regedit in the box next to your name
OK Click on the

Describe the procedure for options B and C.

Option B

This is the procedure to stop recording in the event log.

Start Registry Editor
Move to the next level
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\Autologger\EventLog-System\{fcbb06bb-6a2a-46e3-abaa-246cb4e508b2}
Change to Enabled=0 (default value: 1)
Restart Windows
End of procedure

Option C

The procedure to correct the value of DeviceMetadataServiceURL.

Start Registry Editor
Move to the next level
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Device Metadata
Modify DeviceMetadataServiceURL data to http://dmd.metaservices.microsoft.com/dms/metadata.svc
Restart Windows
End of procedure

Before: http://go.microsoft.com/fwlink/?LinkID=252669&clcid=0x409

Afterword

According to me,

It has been pointed out since around 2016 that an invalid URL is registered in "DeviceMetadataServiceURL".

According to a Windows 10 Forums post, modifying DeviceMetadataServiceURL may cause EVENT-ID 200, 201, 202 to not be logged.

Now,

The message "Metadata staging failed" in the event log may be related to the Task Scheduler Microsoft Compatibility Appraiser.

Microsoft Compatibility Appraiser is one of the telemetry functions that Microsoft has built into Windows 10 and is a program that constitutes the "Microsoft Customer Experience Improvement Program".

Telemetry is a function to process user information anonymously and send it as statistical information to the Microsoft server.

Event ID131 may be repaired by stopping the Microsoft Customer Experience Improvement Program, which is outside the subject of this article and will be detailed in a separate article.

Tracking information

2020/01/17

Revalidated the URL related to DeviceMetadataServiceURL.

When you access the modification URL (option B) described in this article, 400 ERROR is returned, but if the event log recording stops after the modification, it means that it is functioning effectively.

If it doesn't improve, return it to the default value.

[result]

Default value is redirected
Redirect URL returns [400 ERROR]
Modified URL returns [400 ERROR]
...Would you fix it?


Division	URL	result
Default value	http://go.microsoft.com/fwlink/?LinkID=252669&clcid=0x409	redirect
redirect	http://dmd.metaservices.microsoft.com/metadata.svc	400 ERROR
Modification URL	http://dmd.metaservices.microsoft.com/dms/metadata.svc	400 ERROR

HTTP ERROR 400

http://go.microsoft.com/fwlink/?LinkID=252669&clcid=0x409
(→ http://dmd.metaservices.microsoft.com/metadata.svc)

Transcription

This page is not working
If you continue to encounter this issue, contact the site owner.
HTTP ERROR 400