Folders Shared with me are syncing as internet shortcut in OneDrive on Windows PC

Some syncing issues also happening on iOS versions of Microsoft applications (OneDrive, M365 Copilot, Word, Excel, PowerPoint, etc.), I've detailed these as best I could.

Issues crippling iOS Microsoft apps

So far only the Documents appearing as LiveFolders has been fixed, would love to see the rest fixed up so I can work completely on iPad again.

Agreed the code to migrate once developed and proven does not change.

However the volume of data which must be copied and verified must be vast, especially as this has taken over a year before this thread has quietened down.

Hi Mike,

The issue here is not how many users run Windows, or even the sub-set of those that use OneDrive or the total volume of data to be migrated. The issue is the length of time between the first member and last member in the same share group.

Example: You and I do not share any folders, so the migration status of you or any the people you share has no impact on me. i.e. if all of my group are running V1.0 and all of your group are running V1.0, V2.0 or mixed, I'm not impacted.

If all of your group moved from V1.0 to V2.0 on the same day, your group would be impacted for 1 day, regardless of what anyone else is doing.

I'm part of a group of 3, member #1 got migrated from v1.0 to V2.0 in earlier March 2025, now we are all impacted. Then member #2 got migrated and member #1 and #2 start getting their shares working again. I as member #3 still was not migrated by the end of April and so unable to share with the rest of my group. I couldn't wait any longer, so I created member #4 and manually copied all the data from member #3 to member #4. It took me about a days work to setup and migrate everything (the same day it would have taken Microsoft). I have been using the profile of member #4 ever since, the active members of the group are all on V2.0 and life is back to normal.

Member #3 on the other hand, has a few small files left, like less than 20mb and it still has not been migrated 4+ months later.

From the comments made my others, it seems to me, there is a "primary" member of the group (with many files/GBs) and 1 or more members that have a local share from the primary. It seems that Microsoft is migrating all the "small" members first and leaving the bigger "primary" members for weeks/months/years and it's this gap that is creating the grief for everyone.

With good planning and good coding, in my view, Microsoft should have identified all the members of the group, then migrated the primary member first (this won't take months, hours to days depending on their size), then all the small users, that primarily have a share. Perhaps all members could be migrated simultaneously, still we are taking hours/days of impact to the group. Perhaps with minimal/calculated impact, they could have multiple groups migrating at one time, BUT they should never start on a new group (beyond their performance capability) until they have completed the groups they have already started.

My member #3 has been left on V1.0 (with almost no files), an unfinished group and they continue to start working on more and more new groups. Their lack of planning and good code has left, likely100's of thousands of groups with just one member not migrated. It seems like pure luck that Microsoft completed the last member of a group, with no indication when the first and last member will be migrated.

I would think it is technically possible for Microsoft to put a pause on starting any new group, giving themselves some time to complete all the groups they have already started on. All the groups left on V1,0 and those already migrated to V2.0 will not be impacted by the pause, but the mixed groups will all have a priority put on them to complete. While they are waiting for the existing groups to complete, they could be building new code to put a priority on completing a group before taking on too many new groups.

It's not a matter of undoing, it's a matter of completing the migration from the old software to the new. Given how long it's gone on, I suspect files might have to physically move or be rehashed or similar.

The real problem is that they chose to migrate accounts from the old to the new, with the full knowledge that this key feature would break for those users sharing between the two versions. OneDrive (both the software and platform) are 100% in their control, they could have built a temporary fix/layer of abstraction that could have kept shared folders working normally between the two versions, and none of us would have known the difference. This thread wouldn't exist.

Worse, it was almost a year in when it was revealed the truth about what was going on, prior to that, I believe most of us thought it was a bug in the system with certain accounts. The OneDrive support page still lists it as a known issue without any specific information.

The problem/migration was fixed for my family a few months ago, but as far I know, no one has even noticed the fix, they went back to sharing photos via e-mail (as opposed to our shared folder before). It was broken for almost a year, no one trusts it anymore.

Agreed the code to migrate once developed and proven does not change.

However the volume of data which must be copied and verified must be vast, especially as this has taken over a year before this thread has quietened down.