OneDrive replaces newer versions of files with old versions

Hi Craig

I'm having the same issue here, I have read most of the thread + a few other sources and by now I know every single work around.

But this is the first time I write in these forums and I wanted to see if you had any insight / advice.

It's clear OneDrive has a massive bug, this is not a minor detail, this is at the core of what OneDrive is supposed to do. For me (and plenty of people in this thread) there is no point in using OneDrive at all, if it cannot work with multiple devices. Yet I see this issue has been happening for more than a year and I don't see any suggestion that it will ever be fixed. Any idea on why MS is giving us the cold treatment here? Are we reporting it in the wrong place? Is there any way to get an actual answer from them?

I get you don't work for them, but you do seem to have more experience with these things.

I really want to avoid the pain of migrating to a new cloud and loose all my history, but this is a dealbreaker for me.

The whole point of having OneDrive was to be able to access files as local, with or without connection and have OneDrive figure out the synchronization. Sure there are always hard problems like conflicts when I update both sides while offline, that's fair. But there is nothing complicated here; a very old file stored in a computer should not be overwriting all the changes that have been done to that same file since that computer was offline, specially not without a warning.

not sure what you mean - I don't have an On / Off switch under "Files On Demand".

these are the settings on Device A.

On Device B, since making the post, I have selected "Free up disk space" on all files at the highest folder level, in the hope that that will fix it.

Ultimately, I agree, it should not be based on which device has the downloaded file, but should maintain the most recent file from the Sharepoint server.

Hi Richard,

I was proposing "saving as" a new file, with a new name. Not changing the name of the existing file.

That should work, no?

changing the name does not help... save as a new new name still gets screwed up you have to do a copy then save the new name...

This happened to me today. I used a notebook that hadn't been turned on since last year and it synchronised 160,000 files in the wrong direction. Fortunately, most hadn't been changed, but some critical documents and spreadsheets were overwritten. I can find more recent versions in version history and restore them, but I can't remember every file that has been updated in the last three months, so I'm sure the consequences of this will be apparent for months.

This is staggering incompetence on Microsoft's part.