Windows 10: ERROR Source: DeviceSetup/Manager Event ID: 131 "Metadata staging failed, result=0x80070490"

I have a New System i7, 32gb ram, Nvidia rtx 4080 with a fresh install of Windows 11 Pro. Each time I shut down or restart I get:Administrative Events..... ERROR.... Source: DeviceSetup/Manager..... Event ID: 131General Description ........Metadata staging failed, result=0x80070490 for container '{5C6A2833-D869-55F7-BBBB-CA42364EFC22}' My Event Viewer has several of these ERRORS around every shutdown/restartThe system is only a few days old. I have not had it long enough to mess it up. Less than a few few hours. All drivers are up to date, windows is up to date. Tried sfc scannow....Check

:)

 

Metadata staging failed, for Event ID:131

You didn't understand me, I'm using Windows 10 Professional 64bit, on which I have VMware Workstation installed (Forget I mentioned VMware, my OS is Windows 10 Pro 64bit)

Anyway, your way didn't work and the errors keep getting logged in the Event Viewer

Do you have any other suggestions on how to fix this error (Metadata staging failed, for Event ID:131) ?

 

Multiple event 131/DeviceSetup/Manager in Windows 10 Pro

I'm seeing multiple event 131's on my PC. The errors read:

Metadata staging failed, result={00000000-0000-0000-FFFF-FFFFFFFFFFFF} for container 0x80070490.

Metadata stating failed, result= {23524F5A-1BD3-5AAA-B457-32B6D788506D) for container 0x80030490.

Any idea as to what this error is all about and how to fix it?

 

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,