Windows 10: Event ID 508 and 510

I get error lilke this, first thing I would lilke to say is that it is almost certainly NOT a hardware problem, when I google these errors, like mine they reference file C:\Users\XXXXXXX\AppData\Local\Microsoft\Windows\SettingSync\remotemetastore\v1\edb.log

The idea an error on one specific file, one different machine is down to hardward is insane, why that file not the billions of other files on the machine????

And of couse all the "help" advises running check disk or similar hardware checks and of course they all come back fine ie no problem which of course is what you would expect.

Then of course you get the usual stock useless answers such as up date your drivers.

I suspect there errors are down to your drive being busy.

As to why I am not sure.

Anyhow nobody seems to report solving the problem the threads tend to just lead to nowhere.


I did use to get further errors ie event id 533 but I did something which seemed to get rid of it.

Note the v1 bit ie slightly different location.

These files refered to are all hidden files, you can't see them even if you show hidden files, to see them you have to do a further step. You need to go into folder options and uncheck hide protected operating system files.

I can't remember exactly what I did but I think recreated some files or folder when I did that even 533 which used to follow 508 and 510 seemed to disappear. I did that because I followed solution elesewhere, can't remember where you might find it if you google it.

So all in all I don't know, one thing worth mentioning is this "remote" and the Sync bit, is this to do with synchronisng files over the network, ie I am thinking of onedrive, I did see a reference to onedrive inthe file refered to ie meta.edb.

Anyhow I just though I'd relate that as there seems to a lot of backing up the wrong three here perhaps.

This does not seem to be a real world problem for me ie I can boot most of the time but occasionally I do have a boot problem,
I dunno if it is related to this though.

Anyhow it seem most ignore this problem.

 

As an analogy lets say you had to queue up for half and hour to get into a car park, do you think you need to take your car in for a service, get a new car? New plugs? Wrong fuel?

No there was probably jsut a big queue for the car park.

So you take your car to the garage... "Ohh you need a new engine mate".

FFS!!

 

One thing worth looking into is sheduled tasks.

I note most of my errors occur 30 mins after boot, that is when a bit defender task is sheduled, unfortunetly a few occur about 25 mins after boot so they don't quite fit in with that idea.
So a few ideas there.