Several users come across an error on Event Viewer showing frequently in “DeviceSetupManager” source in “Administrative Events” under the “Custom View” branch. This is Metadata Staging failed error 0x80070490 as revealed in the Short information. However, no user has complained about unusual behavior of computer such as crashes, slow performance, etc but the repeated error entries in the Event Viewer are a matter of concern.
Metadata Staging error 0x80070490 has been appearing since the last week of November and it indicates that Microsoft MetaData server has no longer been accessible since then. A user reports that the issue occurs in Windows 10 22H2, build 19045.3758. Fortunately, there is a workaround for the issue using registry modification.
Table of Contents
Metadata staging failed Error 0x80070490
Here is how to fix Metadata staging failed Error 0x80070490 in Windows 10/11:
One user says” I’ve been finding hundreds of these error messages (0x80070490) in the event viewer since 12/7/23 3:26 PM”. When going to the “General” tab you can read “Metadata staging failed, result=0x80070490 for container ‘{B5B8EDE5-AB99-11ED-9EFC-202B20D46152}”
Note: When Investigating on my computer Windows 11 23H2 (22631.2792), I also found multiple events related to DeviceSetupManager showing 0x80070490 with Metadata staging failed.
These entries appear in the Custom Views/Administrative Events branch. Another user reported that he neither installed anything nor made any changes in settings or configurations before or when the error started showing.
The problem also occurred in 12/2016 when the Metadata Staging Failed error, caused at the time by a Windows update, was handled in the DeviceSetupManager.
Since the end of 11/2023, the DeviceSetupManager errors and warnings related to MetaData staging in Event log have been showing again. The user says that among other things, the printer icons under Devices and Printers would suddenly no longer be available. This occurs on newly installed Windows and therefore has no relation with Windows updates.
The error is just associated with MetaData server or servers that are no longer accessible from Microsoft or no longer work.
See: Fix Event Id 1001 Windows Error Reporting (Solved!)
Modify Registry Entries
The user himself suggests to disable logging of the constant warnings and errors in the event log and this is working. There are two ways to do this:
- Fully deactivate MetaData staging
- or disable DeviceSetupManager logging
The first method would also have the benefit that the system performance would not be affected by failed attempts to reach the MetaData server. Currently, no one from Microsoft is showing interest in the unreachable MetaData server problem hence this is a more relevant solution.
Using the following .reg statement, DeviceSetupManger logging can be disabled:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Channels\Microsoft-Windows-DeviceSetupManager/Admin]
"Enabled"=dword:00000000Below .reg directive will disable MetaData staging:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Device Metadata]
"PreventDeviceMetadataFromNetwork"=dword:00000001To fully deactivate MetaData staging using policies use the following reg directive:
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Device Metadata]
"PreventDeviceMetadataFromNetwork"=dword:00000001Upon changes in these registry entries using the directives the Metadata staging failed Error 0x80070490 will no longer appear in the Event Viewer entries in DeviceSetupManger source. There should be no possibility of anything abnormal due to inaccessibility of metadata server.
Read: Fix LSA package is not signed as expected Event ID 6155 in Windows 11
Source: Borncity.
Methods:
That’s all!!