Microsoft windows devicesetupmanager admin код 131 - Доктор Windows

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

Источник

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!

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

Источник

Remove From My Forums

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

Источник: DeviceSetupManager

ID: 131

Сбой промежуточного сохранения метаданных, результат=0x80070057 для контейнера «{83FDFEE6-0CC5-663E-4FB0-48707EF272CF}»

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

Ответы

Привет,

Посмотрите тему с решениями внизу:

Metadata staging failed, result=0x80070057 for container

Мнения, высказанные здесь, являются отражением моих личных взглядов, а не позиции корпорации Microsoft. Вся информация предоставляется «как есть» без каких-либо гарантий. Не забывайте помечать сообщения как ответы и полезные,
если они Вам помогли.
- Помечено в качестве ответа
  
  29 ноября 2019 г. 8:37

Источник

Discus and support Event Error 131-DeviceSetupManager-Metadata staging failed in Windows 10 BSOD Crashes and Debugging to solve the problem; I have recently been besieged with numerous ‘Event Viewer Errors 131- Metadata staging failed.’ These errors just appeared for the first time three…
Discussion in ‘Windows 10 BSOD Crashes and Debugging’ started by Andy Asmussen, Sep 16, 2019.

Event Error 131-DeviceSetupManager-Metadata staging failed

I have recently been besieged with numerous ‘Event Viewer Errors 131- Metadata staging failed.’ These errors just appeared for the first time three days ago, and have logged over 100 same events since.

Following an earlier thread, for this same complaint ( https://answers.microsoft.com/en-us/windows/forum/windows_10-performance/devicemetadataserviceurl-event-131/411a471f-8963-4015-ad7a-2cce49fdb2b6) the ‘DeviceMetaDataServiceURL’ , http://go.microsoft.com/fwlink/?LinkID=252669&clcid=0x409, was found to be incorrect. Web search of this link proved to show an invalid and security threat location. Changing the URL location to http://dmd.metaservices. microsoft.com/dms/metadata.svc, was given as the solution, and evidently had given some users good results. It has not worked for me, and a Web search of the new URL, http://dmd.metaservices.microsoft.com/dms/metadata.svc leads to a ‘404 Not Found’ response, and suggestion to clear the DNS cache. Cache was cleared, but URL still led to «404 Not Found’ result. What is the correct ‘DeviceMetdataServiceURL’?

While it has been proposed that this is more of a nuisance error, than a major problem, and all other programs and computer functions are working well, the amount of Event Errors 131, is frustrating and bothersome. I have run the SFC checker, DISM /Online /Cleanup-Image /RestoreHealth through the Administration PowerShell, all to no avail. Also a ‘Clean Boot’ was systematically followed, with no problems noted.

My current version of Windows 10, is Version 1903, (OS Build 18362.356), with the latest Cumulative Update (KB 4515384), and .NET Framework Update (KB 4514359), being recently installed, along with Store Updates for numerous Apps. I mention these updates as that is the only recent change made to the OS, prior to the appearance of a multitude of DeviceSetupManager — Metadata Setup failures.

Any help or suggestions regarding this issue, would be appreciated … sans doing a ‘Clean Install’ or a ‘Repair Upgrade from Windows 10 ISO file’, as my ISP connection is very..very slow .. and this issue is not terminal .. at least not yet.. A copy of one event error below, with all other 131 Errors similar less specified container:

Log Name: Microsoft-Windows-DeviceSetupManager/Admin
Source: Microsoft-Windows-DeviceSetupManager
Date: 9/15/2019 9:52:37 AM
Event ID: 131
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: DESKTOP-RDH6O3N
Description:
Metadata staging failed, result=0x800704C7 for container ‘{00000000-0000-0000-FFFF-FFFFFFFFFFFF}’
Event Xml:
<Event xmlns=»http://schemas.microsoft.com/win/2004/08/events/event»>
<System>
<Provider Name=»Microsoft-Windows-DeviceSetupManager» Guid=»{fcbb06bb-6a2a-46e3-abaa-246cb4e508b2}» />
<EventID>131</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x4000000000000000</Keywords>
<TimeCreated SystemTime=»2019-09-15T16:52:37.635620300Z» />
<EventRecordID>372</EventRecordID>
<Correlation />
<Execution ProcessID=»11760″ ThreadID=»13348″ />
<Channel>Microsoft-Windows-DeviceSetupManager/Admin</Channel>
<Computer>DESKTOP-RDH6O3N</Computer>
<Security UserID=»S-1-5-18″ />
</System>
<EventData>
<Data Name=»Prop_ContainerId»>{00000000-0000-0000-FFFF-FFFFFFFFFFFF}</Data>
<Data Name=»HRESULT»>2147943623</Data>
</EventData>
</Event>

Thanks,

Andy Asmussen
A series of DeviceSetupManager warnings in Windows 10 event logs

I have been «cleaning up» Windows 10, and I’m noticing a series of warnings in the Event Viewer every time I start Windows. And they are in the following order.

It seems that Event 202 repeats every other instance until I finally get the error: Event 131. What would I have to do to fix these problems, so they stop showing up every time in Event Viewer?
Metadata staging failed — Event ID 131

Good morning,

Ever since I upgraded my computer to Windows 10 (Home) 64-bit a few months ago from Win 8.1 I have discovered the following Event ID 131 error in Event Viewer, sometimes as many as five times in a row, after restarting or upon booting up:

Metadata staging failed, result=0x80070490 for container ‘{1959BB49-AC94-11E5-AE34-3010B356F6E6}’

After googling for a few hours I did find a forum (TechNet) where this error was attributed to ‘timing’ and that Microsoft was aware of it.

A couple workarounds were given until Microsoft comes up with the fix. One workaround given was changing the time from ‘Windows-time’ to ‘time-nist.gov’. However, even though it worked for some folks, it didn’t stop the error in my Event Viewer.

I am just wondering if anyone on this forum has experienced the same Event Viewer error and maybe found a way to stop it from occurring.

Thanks and regards,
Event Error 131-DeviceSetupManager-Metadata staging failed

Event Viewer Errors 131+122 DeviceSetupManager

HI.

I’m getting swamped with event id 122 and 131.

My gpedit.msc policy of «Prevent installation of devices not described by other policy settings» is set to «not configured»
and «Turn off Windows Updated device driver searching» is set to Disabled.

Under [HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionDevice Metadata]
I have «DeviceMetadataServiceURL»=»http://dmd.metaservices.microsoft.com/dms/metadata.svc»

So all should be correct, right?

I have no idea why I’m getting this.

attached Event Viewer message log in zip file.

administrative_events.zip

Thema:

Event Error 131-DeviceSetupManager-Metadata staging failed

Event Error 131-DeviceSetupManager-Metadata staging failed — Similar Threads — Event Error 131
Event Error 131 causing crashing. and freezing on my pc.

in Windows 10 Software and Apps

Event Error 131 causing crashing. and freezing on my pc.: this error is the only one inside my event log before and after crashing. I have tried changing the url to no avail. please help meMetadata staging failed, result=0x80004005 for container ‘{F74A0DD6-F469-50F2-B874-C3E8F3856C72}’- <Event…
DeviceSetupManager Errors (Event IDs 131, 200, 201 & 202)

in Windows 10 Support

DeviceSetupManager Errors (Event IDs 131, 200, 201 & 202): Hello, Googling this issue seemed a lot more common a few years back, including on this forum. I am getting the same errors and warnings every time I boot my PC, and whenever I click on ‘ Control Panel > Hardware and Sound > Devices and Printers’. Error 131 says: «Metadata…
DeviceSetupManager Error ID 131. Constant freezing and restart of PC.

in Windows 10 BSOD Crashes and Debugging

DeviceSetupManager Error ID 131. Constant freezing and restart of PC.: Hi, i’m having problems with windows 10 lately.

I’m experiencing constant freezing and the only way to get back to «normal» for few time due the constantly problem is restarting the PC directly from the case.

Event viewer show me this error ID 131: DeviceSetupManager….
Who do we contact to fix these «Metadata Staging Failed» errors?

in Windows 10 BSOD Crashes and Debugging

Who do we contact to fix these «Metadata Staging Failed» errors?: I’ve been getting these Event ID 131 errors in the Event Viewer for ages, now:

Metadata staging failed, result=0x8007000D for container ‘{00000000-0000-0000-FFFF-FFFFFFFFFFFF}’

They’ve survived at least two Fresh Start re-installs of Windows 10 across both Intel and AMD…
Metadata staging failed, result=0x8007000D

in Windows 10 Drivers and Hardware

Metadata staging failed, result=0x8007000D: Hi,

I have having issue with my Bluetooth headphone. My headphone is shown as paired but sound doesn.t play.

Reconnecting fixes it for a few minutes.

I digged into Event Viewer tool and found the following every-time this happened.

Metadata staging failed,…
Event ID 131 Metadata errors happening lately.

in Windows 10 Support

Event ID 131 Metadata errors happening lately.: So I’m getting these the past couple of days recently.

Metadata staging failed, result={00000000-0000-0000-FFFF-FFFFFFFFFFFF} for container ‘0x8007000D’

Metadata staging failed, result={9C52FEAA-DABE-5636-BEC0-AFDCA171FDBD} for container ‘0x80070057’

Thing is that I don’t…
Metadata staging failed

in Windows 10 Drivers and Hardware

Metadata staging failed: These errors have started building up with every reboot.. What’s going on? Never seen them in W764? But now after upgrading to W10 64..

Metadata staging failed, result={CA0E9E80-3E97-FCAC-730A-8CB080FA2581} for container ‘0x80070490’

A connection to the Windows Metadata…
Event Viewer Errors 131+122 DeviceSetupManager

in Windows 10 Performance & Maintenance

Event Viewer Errors 131+122 DeviceSetupManager: HI.

I’m getting swamped with event id 122 and 131.

My gpedit.msc policy of «Prevent installation of devices not described by other policy settings» is set to «not configured»
and «Turn off Windows Updated device driver searching» is set to Disabled.

Under…
Metadata staging failed — Event ID 131

in Windows 10 Support

Metadata staging failed — Event ID 131: Good morning,

Ever since I upgraded my computer to Windows 10 (Home) 64-bit a few months ago from Win 8.1 I have discovered the following Event ID 131 error in Event Viewer, sometimes as many as five times in a row, after restarting or upon booting up:

Metadata staging…

Users found this page by searching for:

metadata staging failed result=0x8007000d for container {00000000-0000-0000-ffff-ffffffffffff}

,
devicesetupmanager 131

,
Metadata staging failed result=0x8007000D

,
event id 131 devicesetupmanager,
metadata staging failed,
metadata staging failed windows 10,
metadata staging failed result=0x800704c7 for container {00000000-0000-0000-ffff-ffffffffffff},
device setup manager error 131,
device setup manager 131,
error 10/29/2019 9:35:21 pm devicesetupmanager 131 none,
windows 10 event 131 devicesetupmanager failed,
devicesetupmanager event id 131 RDS 2016,
Description:Metadata staging failed result=0x80070490 for container {7ECAC27A-A91D-DC6E-A22B-B104BA0CCB8F},
{fcbb06bb-6a2a-46e3-abaa-246cb4e508b2} 131,
Metadata staging failed result=0x8007EE4F for container {

Источник

Hey, guys!

I’ve been getting these weird event id 131 errors since the 14th out of the blue and I can’t seem to figure out what’s wrong:

Metadata staging failed, result=0x80070057 for container ‘{90DAD2D0-811B-11E9-AFA9-7085C2750CB6}’

Full details look like this:

Log Name: Microsoft-Windows-DeviceSetupManager/Admin

Source: Microsoft-Windows-DeviceSetupManager

Date: 16.09.2019 19:53:24

Event ID: 131

Task Category: None

Level: Error

Keywords:

User: SYSTEM

Computer: SANJURO-PC

Description:

Metadata staging failed, result=0x80070057 for container ‘{90DAD2D0-811B-11E9-AFA9-7085C2750CB6}’

Event Xml:

<Channel>Microsoft-Windows-DeviceSetupManager/Admin</Channel>

<Computer>SANJURO-PC</Computer>

</System>

</EventData>

</Event>

I’ve googled around and so far I’ve changed the URL in registry for Windows metadata and also changed the internet time source to time.nist.gov.

They keep popping up.

I’m running Windows 10 1903 (latest updates).

Any help is appreciated. Thanks in advance!

Источник

@kaktys_3431

Да красиво:smileysad:.. А у меня вот баранки есть к чаю, а более — ничего:smileycry:

А тему то уважаемая @Olga-5000 открыла вполне хорошую и совсем не мутную. И очень хорошо, что она интересуется тем, что происходит внутри её девайса.:smileyrose:

Мне тоже захотелось, немного порывшись, попытаться найти объяснение данной периодической ошибки.

Оказывется о данной ошибке, возникающей при загрузке ОС, MS знает с Мая-2015 и работает над её решением. Там у них (у MS) возникает короткая временная задержка при выполнении клиентского запроса к серверу метаданных. Но затем данные успешно передаются.

Чтобы в этом убедиться — делаем следующие «телодвижения»:

Запускаем Просмотр событий

Открываем закладки:

Журналы приложений и служб—>Microsoft—>Windows—>DeviceSetupManager

Clickаем по Admin

Найдите ближайшее событие ошибки с кодом 131, а затем поднимитесь на следующую строчку, и вы убедитесь, что метаданные были успешно переданы на сервер метаданных MS.

Примерно так:

«Герой» на форуме — это Эксперт, окончально повредивший свой рассудок (updated)

Источник

Вопрос

Ответы

Event Error 131-DeviceSetupManager-Metadata staging failed

Event Error 131-DeviceSetupManager-Metadata staging failed

Event Error 131-DeviceSetupManager-Metadata staging failed

Event Error 131-DeviceSetupManager-Metadata staging failed — Similar Threads — Event Error 131

Event Error 131 causing crashing. and freezing on my pc.

DeviceSetupManager Errors (Event IDs 131, 200, 201 & 202)

DeviceSetupManager Error ID 131. Constant freezing and restart of PC.

Who do we contact to fix these «Metadata Staging Failed» errors?

Metadata staging failed, result=0x8007000D

Event ID 131 Metadata errors happening lately.

Metadata staging failed

Event Viewer Errors 131+122 DeviceSetupManager

Metadata staging failed — Event ID 131

Users found this page by searching for:

metadata staging failed result=0x8007000d for container {00000000-0000-0000-ffff-ffffffffffff}

devicesetupmanager 131

Metadata staging failed result=0x8007000D