Device setup manager ошибка 131

Hi Folks,

Amtino on the «Microsoft Community» wrote on this Subject:

A new resolution to the issue without changing the url in the registry or touching anything we shouldn’t really:

Click on time and date at bottom right of screen.

select Internet time

change the server in the drop down list from windows time to nist.gov.   Update the time.

Your system should now be error free:  I have tested this by refreshing all hardware devices etc.  all OK.

The nist.gov time server is obviously correct to the millisecond and the window time server is not! 

http://answers.microsoft.com/en-us/windows/forum/windows8_1-performance/multiple-errors-in-event-viewer-eventid-131-from/e5054c3b-bc91-4beb-894f-4d0d9f0dd8ca?page=10&msgId=c7ebffc8-93c7-4c7c-a009-4e972596adf3

I can attest that this does work the why the Meta System was suppose to work in the first place! Set everything back to the why Microsoft Recommends and change the Time Updating Source. Since I am in the North West I chose accordingly as follows:

Verification:

Control Panel

Printers and Devices

Right Click with mouse on any blank space

Click refresh

Finally a real answer to this long term problem. Even though I did not have an issue in Windows 8.1 Pro, I changed them too, as a preventative precaution.

I am going to «Unanswer» the Former Answers. There time has passed. I hope the moderators support this….

Best Regards,

Crysta

---

PhotM Phantom of the Mobile

• Marked as answer by
  Phantom of the Mobile
  Sunday, October 11, 2015 2:20 PM

---

С моей платы ASUS P8Z77-V Deluxe есть только бета-драйверы WIN 10

указанное сообщение на дисплее события. Чтобы войти в опции питания и отсутствующий драйвер чипсета / материнской платы ??? Случайный взгляд в

Если это сообщение зарегистрировано в принципе, компьютер выходит из строя во время выключения.

Перед тем как это сделать, нажмите ссылку выше «Некоторые настройки в настоящее время недоступны.

Алло,
Итак, сначала все работает на моем ПК. Эта ошибка может возникнуть, если система перестает отвечать на запросы, как правило, отключая быстрый запуск. Возможно, это связано с ошибкой, которая произошла или произошла сбой, или неожиданно было прервано питание. Сбой, и он также едет нормально и быстро.

Назад
включение означает, что он был снова выключен … если я снова выключу компьютер и в 18:10, например, WIN 41 НЕ был загружен через ОБНОВЛЕНИЕ, а был совершенно новым на отформатированном SSD! Идентификатор события XNUMX НО: НИЧЕГО не произошло сбоев, ПК в норме и доступен, нажмите «, чтобы позволить Windows освободить настройки.

ПК загружается очень быстро, Windows работает стабильно БЕЗ Event Viewer говорит мне, например

Если подходящие драйверы для Windows 10 недоступны, отключите быстрый запуск в разделе «Пароль при повторной активации».

• General discussion

• 

  На сервере Windows Server 2012 в журнале событий ошибка:

  Источник: DeviceSetupManager

  ID: 131

  Metadata staging failed, result={7B335BB8-5F61-8283-C19B-3256F828BECF} for container ‘0x80070490’

  Не могу понять, что это за ошибка.

  • Changed type
    Petko KrushevMicrosoft contingent staff, Moderator
    Tuesday, July 7, 2015 12:35 PM

  Thursday, June 25, 2015 9:35 AM

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

,Japan

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.

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.

Well, the main subject.

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

1. ignore
2. Stop recording in the event log
3. 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.

HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionDevice MetadataDeviceMetadataServiceURL

Event Log

The event log is reprinted.

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

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.

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]

1. Default value is redirected
2. Redirect URL returns [400 ERROR]
3. Modified URL returns [400 ERROR]
4. …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

Validation: Windows 10 Pro November 2019 Update, v1909.18363.476

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