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
Log name: Microsoft-Windows-DeviceSetupManager/Admin
Source: DeviceSetupManager
Event ID: 131
Level: Error
User: SYSTEMMetadata staging failed, result=0x80070490 for container ‘{00000000-0000-0000-FFFF-FFFFFFFFFFFF}’
Открыл редактор реестра под админом:
HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionDevice MetadataDeviceMetadataServiceURL
Было значение
http://go.microsoft.com/fwlink/?LinkID=252669&clcid=0x409
Поменял на
http://dmd.metaservices.microsoft.com/dms/metadata.svc
Детали здесь.
- Об авторе
- Недавние публикации
-
misvin
- Posts: 13
- Joined: 4. Oct 2017, 17:46
- Primary OS: MS Windows 10
- VBox Version: OSE other
- Guest OSses: Windows 10
Windows 10 Guest (64-bit) Metadata staging failed, Device Setup Manager EventID 131
After the latest Windows 10 Update (2019-09 Cumulative Update for Windows 10 for x64-based Systems, Version 1903 (KB4515384) ■ Build 18362.356), Event ID 131 occurs in the Event Viewer.
Metadata staging failed, result=0x80070057 for container '{D397268A-724C-B4EF-D641-C9234BA2948B}' Metadata staging failed, result=0x8007000D for container '{00000000-0000-0000-FFFF-FFFFFFFFFFFF}' Metadata staging failed, result=0x80070057 for container '{ED17222B-F1C7-537F-9546-745658ADE2E3}'
The problem occurs on Windows 10 (64-bit) Guest only. To isolate the issue, I have created a new VM on Windows 10 (64-bit) Host and launched Windows Update in the Windows 10 (64-bit) Guest.
There are no such events on Windows 10 (64-bit) Host and Windows 10 (32-bit) Guest.
VirtualBox version: 6.0.12.
The problem exists both with installed Guest Additions and without Guest Additions.
Last edited by socratis on 16. Sep 2019, 11:55, edited 1 time in total.
Reason: Enclosed the information in [quote][pre] tags for better readability
-
socratis
- Site Moderator
- Posts: 27689
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: Windows 10 Guest (64-bit) Metadata staging failed, Device Setup Manager EventID 131
Post
by socratis » 16. Sep 2019, 11:55
And why would that be a VirtualBox issue?
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the «QUOTE» button, please use the «POST REPLY«, at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
-
multiOS
- Volunteer
- Posts: 770
- Joined: 14. Sep 2019, 16:51
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: WIN11,10, 7, Linux (various)
- Location: United Kingdom
Re: Windows 10 Guest (64-bit) Metadata staging failed, Device Setup Manager EventID 131
Post
by multiOS » 16. Sep 2019, 14:26
New to this forum, but if you do a ‘Google’ search for «meta data staging failed» you’ll find that it has been a relatively common Windows error on real hardware for several years. You should probably pursue the approach that you would do if it happened on a Windows Host installation and forget the fact that you are using a Virtual Machine.
-
misvin
- Posts: 13
- Joined: 4. Oct 2017, 17:46
- Primary OS: MS Windows 10
- VBox Version: OSE other
- Guest OSses: Windows 10
Re: Windows 10 Guest (64-bit) Metadata staging failed, Device Setup Manager EventID 131
Post
by misvin » 16. Sep 2019, 15:00
2multiOS
- The problem started only after the last Windows 10 Update (Build 18362.356) and only in the Windows 10 (64-bit) guest.
- Windows 10 (64-bit) Host (on this PC) does not have this problem.
- All of Google’s suggestions regarding «Metadata staging failed» didn’t help me solve this issue. I tried:
- I changed device installation settings (Turning off the updates)
- I changed the address devices metadata in the Registry from go.microsoft.com/fwlink/?LinkID=252669&clcid=0x409 to http://dmd.metaservices.microsoft.com/dms/metadata.svc.
I just want to know if anyone else has this problem.
-
socratis
- Site Moderator
- Posts: 27689
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: Windows 10 Guest (64-bit) Metadata staging failed, Device Setup Manager EventID 131
Post
by socratis » 18. Sep 2019, 17:44
Just because an OS/program that runs in the context of VirtualBox has a problem, it doesn’t make it a VirtualBox problem necessarily. You’re having an issue that has most probably nothing to do with VirtualBox, so my suggestion would be to treat it as such, as a native problem with the guest OS, and start searching in the appropriate forums.
I don’t have it on two Win10 VMs that I have, one 32- and one 64-bit…
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the «QUOTE» button, please use the «POST REPLY«, at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
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.
Event 202, DeviceSetupManager
"The Network List Manager reports no connectivity to the internet."
Event 200, DeviceSetupManager
"A connection to the Windows Update service could not be established."
Event 202, DeviceSetupManager
"The Network List Manager reports no connectivity to the internet."
Event 201, DeviceSetupManager
"A connection to the Windows Metadata and Internet Services (WMIS) could not be established."
Event 202, DeviceSetupManager
"The Network List Manager reports no connectivity to the internet."
Event 200, DeviceSetupManager
"A connection to the Windows Update service could not be established."
Event 131, DeviceSetupManager
"Metadata staging failed, result={00000000-0000-0000-FFFF-FFFFFFFFFFFF} for container '0x80070490'"
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?
я «очищаю» Windows 10, и я замечаю серию предупреждений в средстве просмотра событий каждый раз, когда я запускаю Windows. И они находятся в следующем порядке.
Event 202, DeviceSetupManager
"The Network List Manager reports no connectivity to the internet."
Event 200, DeviceSetupManager
"A connection to the Windows Update service could not be established."
Event 202, DeviceSetupManager
"The Network List Manager reports no connectivity to the internet."
Event 201, DeviceSetupManager
"A connection to the Windows Metadata and Internet Services (WMIS) could not be established."
Event 202, DeviceSetupManager
"The Network List Manager reports no connectivity to the internet."
Event 200, DeviceSetupManager
"A connection to the Windows Update service could not be established."
Event 131, DeviceSetupManager
"Metadata staging failed, result={00000000-0000-0000-FFFF-FFFFFFFFFFFF} for container '0x80070490'"
Кажется, что событие 202 повторяет каждый другой экземпляр, пока я наконец не получу ошибку: событие 131. Что мне нужно сделать, чтобы исправить эти проблемы, чтобы они перестали появляться каждый раз в средстве просмотра событий?