After installing cumulative updates or specific KB updates like KB890830, KB5032339, KB5032288, KB5032189, and KB4023057, you might encounter the following error messages on your Windows 10/11 screen after restarting:
Event 131, Device Setup Manager
- Metadata staging failed result=0x80070057
- Metadata staging failed result=0x8007000D
- Metadata staging failed result=0x80070490
What is Event ID 131?
Event ID 131 is a note in your system event log, and it basically says that something went wrong during a task called “metadata staging.” This task is managed by the Device Setup Manager and is all about getting your computer ready by storing important information about drivers. This driver info is crucial for setting up and configuring your hardware devices on Windows. When the metadata staging process fails, it can cause problems like drivers not being set up correctly, devices not working as they should, or even making your system a bit unstable.
What does ‘Metadata stagging failed’ mean?
Metadata Staging refers to the process of preparing and storing driver information within the Windows system. When you install updates, drivers, software, or hardware, this entails configuring and storing driver information in the Windows system, crucial for the successful installation of the respective hardware, driver, software, or updates.
Encountering a Metadata Staging failed error indicates that the storage of device information to the Windows system has failed for unknown reasons during the device setup process.
Following the installation of updates, the Windows system initializes the installed hardware and stores its metadata. However, if, for unknown reasons, it fails to store the configuration and metadata information to the PC, it triggers Event ID 131, signaling a Metadata Staging Failed error with error codes such as 0x80070490, 0x8007000D, or 0x80070057.
Cause:
The ‘Device manager event ID – 131 Metadata staging failed‘ may occur due to various reasons such as:
- Outdated or Incompatible Drivers.
- Corrupted or Missing system files.
- Hardware Issues/failure
- Malware/Viruses Infection, etc.
How do I fix ‘Device manager event ID – 131 Metadata staging failed’ error?
To resolve the Metadata Staging Failed error on your computer, follow these troubleshooting steps:
Solution 1: Fix using the Outbyte PC Repair Tool
As mentioned earlier, the Device Manager error 131 – Metadata Staging Failed can be triggered by various factors, including corrupted system files, outdated or incompatible drivers, misconfigurations in the Windows registry, and virus/malware infections.
It’s crucial to address these issues to resolve the error. One effective solution is to use the Outbyte PC Repair Tool, which can help fix Windows issues and optimize your system for better performance.
Step 2. SCAN your Windows PC
Step 3. Click Fix button to Repair Error
Solution 2: Update the Device Drivers
Updating all your drivers is essential to resolve compatibility issues. However, manually going through each driver and updating them can be time-consuming and doesn’t guarantee a smooth process. It’s advisable to use the best driver updater software, which automates the driver-related tasks and ensures a more efficient and reliable update process.
The majority of Windows issues arise from corrupted, outdated, missing, or incompatible drivers. However, with DriverEasy, these problems can be effortlessly resolved. DriverEasy automatically scans, installs, or updates drivers, ensuring that your system remains up-to-date and optimized.
| Detects all missing, outdated & mismatched drivers. All drivers certified, and direct from manufacturer. | |
| Creates auto restore point and auto system backup. 1 click to download & install all drivers | |
| Updates driver on Windows 10/8.1/8/7/Vista/XP and Windows Server 2019 – 2003. | |
  | |
Additionally, you can also generate a list of all the currently installed drivers on your system.
Step 1: Open the command prompt as administrator.
Step 2: Copy and paste the following command into your command prompt or PowerShell window, and execute it. This command will locate all the installed drivers on your system and save them in a file named AllDrivers.txt on your desktop.
Dism /online /Get-Drivers /all > %UserProfile%\Desktop\AllDrivers.txtStep 3: Navigate to your desktop and double-click on the AllDrivers.txt file to view the list of installed drivers.
Solution 3: Fix corrupt files and Windows using the SFC, CHKDSK, and DISM commands.
The SFC (System File Checker) tool is a valuable command for repairing corrupted or missing system files. It’s a command-line utility that you can run in an elevated command prompt.
The CHKDSK command is utilized to check disk integrity.
The DISM command is primarily employed to repair Windows images.
SFC/Chkdsk/Dism - Step by Step
sfc /scannow
Dism /Online /Cleanup-Image /CheckHealth
Dism /Online /Cleanup-Image /ScanHealth
Dism /Online /Cleanup-Image /RestoreHealth
chkdsk /f c:
It will show you message:
Chkdsk cannot run because the volume is in use by another process. Would you like to schedule this volume to be checked the next time the system restarts? (Y/N)
Press Y and Press Enter. The disk checking will start on next pc start.
Solution 4: Clear the DriverStore folder.
The DriverStore folder stores all the driver files, and removing a faulty driver might resolve the Metadata Staging Failed issue on your device. To remove the problematic driver, run the following commands in an elevated command prompt.
Step 1: Open the elevated command prompt.
Step 2: To see the files on the DriverStore folder, execute the following commands.
pnputil /enum-driversStep 3: To remove the faulty driver, copy and paste the following commands into the command prompt, and execute them. Make sure to replace “<PublisherName>” with the actual publisher name of the problematic driver as found in the list above.
pnputil /delete-driver <PublishedName> /uninstallStep 4: Check the Event Viewer for additional details about the problematic driver causing the issue, and then proceed to remove it.
Solution 5: Perform System Restore
Initiating a System Restore can be a viable solution for addressing the ‘Device Manager Event ID 131 – Metadata Staging Failed’ issue. Follow these steps to perform a System Restore:
System Restore - Steps by Steps
Solution 6: Uninstall problematic updates.
If you observe that this issue arises after installing a specific update package, consider removing those packages to eliminate the error. Wait for subsequent cumulative updates, as they may include fixes or improvements to address the problem.
Summary:
The ‘Device Manager Event ID 131 – Metadata Staging Failed‘ issue can be resolved by employing various methods, including updating drivers, addressing corrupted file issues, removing faulty drivers from the DriverStore folder, uninstalling problematic update packages, and performing a System Restore.