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

I suspect this issue is what's causing me some issues with my metadata.

On my PC, about a week ago, I suddenly stopped being able to see tags or authors in file metadata get suggested when I typed part of the word. For example, in the past I'd type "Com" into the tags field and after a few seconds it'd suggest "Complete". Same with Authors.

Since a week ago, the dropdown of suggestions has never once appeared, and it takes me two hits of enter to confirm an Author addition, where it used to take one.

My Laptop didn't have this issue until halfway through today. Everything was working as it should, until my laptop started getting a little sluggish so I rebooted. Since that reboot, the metadata editing has been broken in exactly the same manner as on my PC.

I went to event view to see if I could find anything that might suggest what happened, and today, 18 September, I have... 48 of these errors. 349 since the start of September, including before I ran my update. Nothing before September.

that sounds more like a bug in office than this problem. I believe the issue we are discussing here is device metadata not document meta data. I recall seeing this as an issue in a discussion not so long ago, I suggest you try and see if there are any updates pending for office (File > Office Account > Updates) failing which do a full repair of Office and see if that fixes it.

I suspect this issue is what's causing me some issues with my metadata.

On my PC, about a week ago, I suddenly stopped being able to see tags or authors in file metadata get suggested when I typed part of the word. For example, in the past I'd type "Com" into the tags field and after a few seconds it'd suggest "Complete". Same with Authors.

Since a week ago, the dropdown of suggestions has never once appeared, and it takes me two hits of enter to confirm an Author addition, where it used to take one.

My Laptop didn't have this issue until halfway through today. Everything was working as it should, until my laptop started getting a little sluggish so I rebooted. Since that reboot, the metadata editing has been broken in exactly the same manner as on my PC.

I went to event view to see if I could find anything that might suggest what happened, and today, 18 September, I have... 48 of these errors. 349 since the start of September, including before I ran my update. Nothing before September.

Several months ago I was getting 25+ of these error messages after bootup.Checking this morning they’re now down to 14. Something is changing but not at my end.

Maybe Microsoft is getting to grips with it.

Hi LouiscarrElcarumba

"I made that decision after examining the possible consequences vs the pain of having my event log become utterly useless for tracking down the current problem I was experiencing, or any other future problems for that matter."

I totally agree with that. I have found exactly the same problem on PCs and Servers alike, the logs are filled with so much "noise" trying to isolate the signal becomes impossible.

I know pinging isn't a guarantee of a dead url, sure and I can accept yhe logic of analysis of data with responses possibly causing a problem.

My issue started on the 11th, yet many claim for them the issue raised it's ugly head in December 2023.

Something caused this to happen suddenly on my machine specifically on or around that date.

Personally, no MS agent or anyone else forced or convinced me to turn this off. I made that decision after examining the possible consequences vs the pain of having my event log become utterly useless for tracking down the current problem I was experiencing, or any other future problems for that matter.

There is a coincidence here in that I installed Dell Display Manager on the 10th. The sounds started then pretty much and only after looking at the event viewer days later did I see the masses of 131's 200, 201 et al swamping my log.

I did not suspect Dell for ages as what logic would tell me that it was causing a usb disconnect followed closely by an immediate reconnect.

It's a display manager but of course their monitors DO have usb, so ....

I stopped the disconnect initially by killing processes and then when a bunch had been stopped and the disconnects no longer happened, my first goto was Dell and I was going to go down that list. Lucky choice ...

Currently the ICUE conflict is just a guess at this stage.

So what logic is there that this is just coincidence? It's either connected in some way or a hell of a coincidence, both of which I will accept given my experience of computers for 3 decades.

Therefore I will enable the service to find out later as I'm convinced that "something " on "my" machine changed to cause this to happen and if it isn't connected then I WILL keep it disabled as I don't care about icons and drivers. I'm quite used to updating my own drivers for devices I install.

I will turn it on periodically thereafter to check if it's working or if I find disabling the service causes other problems.

I just don't need to waste any more time on this. Enough is enough.