i think i have the exact same problem. do you see the same errors and warning in the event vieuwer every time it happens aswell? (for me its often about 25+ events)
Metadata staging failed, result=0x80070490 for container '{564E4238-4832-4447-5633-5CB9010C3444}', DeviceSetupManager id 131.' If you happen to know what this means, please help me with this error
Hi
I am getting this error when I start the computer I am getting error
Metadata staging failed, result=0x80070490 for container '{564E4238-4832-4447-5633-5CB9010C3444}', DeviceSetupManager id 131.'
, please help
me with this error
Windows for home | Windows 11 | Performance and system failures
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
296 answers
Sort by: Most helpful
-
Anonymous
2024-03-28T20:55:18+00:00 -
Anonymous
2024-03-28T13:30:29+00:00 when i go under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Device Metadata i only have the (default) folder with no set value. is this something i should be worried about?
-
Anonymous
2024-03-28T13:09:10+00:00 TY1 Disabling the device installation settings immediately improved my laptop's performance. It has been running very slow lately.
Windows Server 2022 that I administer has been struggling with this problem from time to time. The problem disappeared after uploading a large patch, then again for a month without any problems. After a month it came back again, now I applied your solution and restarted the server. Bingo! No error occurred.
-
Anonymous
2024-03-27T13:20:47+00:00 Same problem here!
-
Anonymous
2024-03-26T00:46:50+00:00 I tried a lot of things posted here and nothing. Then my chrome started being unstable. Uninstalled and reinstalled chrome. A few hours later, I realized the error audio notification had stopped. I opened event viewer, custom views then administrative events. Scrolled back and verified--- the errors stopped after chrome was reinstalled.
I don't know what prompted the error but reinstalling chrome solved the problem in less than 5 minutes. Hope this helps someone.