Windows 10: Metadata staging failed - Event ID 131

Discus and support Metadata staging failed - Event ID 131 in Windows 10 Support to solve the problem; 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... Discussion in 'Windows 10 Support' started by 2harts4ever, Jan 5, 2016.

  1. 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,


    :)
     
    2harts4ever, Jan 5, 2016
    #1

  2. Windows 10 error id 131 metadata staging failed after upgrade to Windows 10 from Windows 7

    Very helpful. Thanks for sharing this information.

    Rudolf Aigner
     
    RudolfAigner, Jan 5, 2016
    #2
  3. Windows 10 error id 131 metadata staging failed after upgrade to Windows 10 from Windows 7

    Hi Scott,

    Thank you for posting the query on Microsoft Community.

    Try to run the following commands and check if it helps.

    • Open command prompt. (Type it in Search or Press Windows Logo Key+X. Click on Command Prompt admin).
    • Type the following 4 commands at the CMD prompt:
    dism /online /cleanup-image /restorehealth

    sfc /scannow

    powershell

    Get-AppXPackage -AllUsers |Where-Object {$_.InstallLocation -like "*SystemApps*"} | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}

    • Close the CMD window.
    • Check to see if the issue is resolved. If not, restart the PC.
    Hope this helps in resolving the issue. If the issue persists, do get back to us. We will be happy to assist you.
     
    Kalpana Shankarappa, Jan 5, 2016
    #3
Thema:

Metadata staging failed - Event ID 131

Loading...
  1. Metadata staging failed - Event ID 131 - Similar Threads - Metadata staging failed

  2. 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....
  3. 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...
  4. Clean install 1909 event ID 131 help me to fix it

    in Windows 10 Ask Insider
    Clean install 1909 event ID 131 help me to fix it: [ATTACH] After making clean install of 1909 I get bunch of these event ID 131 errors. Description says "Metadata staging failed, result=0x80004005" I googled a bit and its quite often error and it has something to do with Devices and Printers being timing out to update...
  5. 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,...
  6. 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...
  7. Event Error 131-DeviceSetupManager-Metadata staging failed

    in Windows 10 BSOD Crashes and Debugging
    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 (...
  8. 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...
  9. Event ID 10031

    in Windows 10 Support
    Event ID 10031: Good point @swarfega. I find Reliability Monitor to be a much quicker way to zero in on stuff I might actually be concerned about. And even then, much of what surfaces -- IE errors of late which is moving me away from IE and more onto Chrome, Firefox and, to some extent, Edge...
  10. 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...

Users found this page by searching for:

  1. Metadata staging failed result=0x80070057

    ,
  2. event 131 metadata staging failed

    ,
  3. metadata error 131

    ,
  4. Metadata staging failed result=0x80070057 for container,
  5. metadata staging failed,
  6. event id 131,
  7. event id 131 metadata staging failed,
  8. Metadata staging failed result=0x80004005 for container {62BBF3D4-56D1-5121-8B49-5EEF914BC2EE},
  9. Metadata staging failed result=0x80004005,
  10. metadata staging failed result=0x8007000d for container {00000000-0000-0000-ffff-ffffffffffff},
  11. win 10 event 131 metadata staging failed,
  12. metadata staging failed result=0x80070057 for container {1226dcc6-7456-51c2-853f-b2ff1800b181},
  13. metadata staging failed win 10