I've been having the same problem in my event viewer then having attempt to write readonly memory now I have a clean install of windows could it be my gpu or memory?
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
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Anonymous
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-08-03T09:35:16+00:00 -
Anonymous
2024-08-02T15:06:00+00:00 Whoops Sorry my mistake. Thought you were referring to the Outlook bug. As far as I can see the metadata bug is down to MS and the URL the API is connected to. Attempts to access either the URL in original registry as in installed out of the box or the suggested update URL all fail. Same in server version of the OS too.
-
Anonymous
2024-08-02T13:36:36+00:00 Nick, I was referring to the bug in this topic title.
-
Anonymous
2024-08-02T12:51:35+00:00 Hi Ray,
The bug affected anyone running Office 365 in a network with UNC shares had nothing to do with USB. It is now fixed after nearly two years.
-
Anonymous
2024-08-02T12:12:40+00:00 Hi Nick, I’m still using Office Pro 2010 which holds emails back to the late 1990s. No such problems with that version.
Fortunately this current bug doesn’t impact on me using my computer and I suspect it’s linked to the many USB2 devices connected via a powered hub. On an older PC running W10 updated free to 11 the problem doesn’t exist.