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

Here is the statement from the Microsoft OneDrive product group (Redmond USA) about the OneDrive Personal problem:

***This is related to a backend migration we are doing and unfortunately, we don’t fully support syncing shared folders in the case where one user has migrated and the other has not. We’re doing everything possible to accelerate things so that it can be resolved as soon as possible for users of the feature. When the accounts are migrated, there is automated logic that makes them go back to a syncing folder within several days.***I have heard, that shared Folder issue is gone.
The best thing is: WAIT and do nothing

Mr. Hans, thank you for replying in this topic...as we know that you are important person in the MS OneDrive Division (or related with them somehow) :)

Can we ask you for a favor?. Please tell the OneDrive backend team, that this is not a way how it should be done in matter of communication or migration.

If they know that it will break something, why dev team did not make any statement about it? Like answer to this topic with explanation or the ETA of the migration. They broke things and they knew that it will take some time to migrate and they don't say anything. People are struggling on their own, wasting time, Support do not know nothing about it to share the explanation about it. They say: "did you try to turn it off and on again?".

When the shitstorm happen, people were so desperate that they try to contact someone in social media or other platforms to bump the problem higher. Shitstorm happen and then MS put some sentence on support page: "that they are aware of that". After months!!

Backend team should inform support that it could be reports about this, so please inform users that they have to wait.

Backend team knew that it will take time, at least 3 months, because I was hit by this 3 months ago. So what backend team was expecting? That people will not notice? Let's be strait: backend team f*cked up this. Please be aware of time spent by people, frustration, research because nobody from dev team was not willing to inform users about it, or make migration in better way.

I am very grateful for your engagement in this, but i have a personal "request" for you... when you will someday in a meeting with them, please tell them that they totally screw things up. Next time, they should track migration process to users who share something and to users that do not share. Migrate accounts connected with each other by sharing in the first place. Inform support about it, inform about ETA.

Again, thank you Hans.

Totally in agreement with this post by BENEQ -- and, Hans, thanks for explaining the situation.

@Dear Migration Team:

The handling and management of that migration project with regard to the known and expected fallout among users is just terrible and maybe reckless if you consider that nobody cared about the users, their broken and disrupted workflows, and their time!

And with regard to Office365 subscribers,... these users are paying customers, not free-riders who use an unsupported tool.

So, knowing that this situation and project was handled not properly, MAY WE EXPECT AT LEAST AT THIS POINT AN ETA regarding the migration completion?

Project management cannot deny to have something like that. I understand the project team disguised the migration as a bug to be able NOT making a statement about the project completion, but now, that the 'cat is out of the bag', dear project management, show us that you have the project under control and that the migration is going according to plan... I mean it seems it started last year, and this month you guys pushed a larger portion through the migration, but we need to know when and if that ends.

By not making an announcement, we all must assume that all products are managed that way and we, the customers, cannot rely on the stability of a product. Stability and product quality is the only reason in a professional environment to pay for something.

Please show us some leadership, and do not give us the feel our only remedy is to speak to uninformed support teams who start with the advice like 'have you uninstalled, reinstalled it already' like they would start when my 99-year-old grandma would call in.

TIA !

Here is the statement from the Microsoft OneDrive product group (Redmond USA) about the OneDrive Personal problem:

***This is related to a backend migration we are doing and unfortunately, we don’t fully support syncing shared folders in the case where one user has migrated and the other has not. We’re doing everything possible to accelerate things so that it can be resolved as soon as possible for users of the feature. When the accounts are migrated, there is automated logic that makes them go back to a syncing folder within several days.***I have heard, that shared Folder issue is gone.
The best thing is: WAIT and do nothing

Mr. Hans, thank you for replying in this topic...as we know that you are important person in the MS OneDrive Division (or related with them somehow) :)

Can we ask you for a favor?. Please tell the OneDrive backend team, that this is not a way how it should be done in matter of communication or migration.

If they know that it will break something, why dev team did not make any statement about it? Like answer to this topic with explanation or the ETA of the migration. They broke things and they knew that it will take some time to migrate and they don't say anything. People are struggling on their own, wasting time, Support do not know nothing about it to share the explanation about it. They say: "did you try to turn it off and on again?".

When the shitstorm happen, people were so desperate that they try to contact someone in social media or other platforms to bump the problem higher. Shitstorm happen and then MS put some sentence on support page: "that they are aware of that". After months!!

Backend team should inform support that it could be reports about this, so please inform users that they have to wait.

Backend team knew that it will take time, at least 3 months, because I was hit by this 3 months ago. So what backend team was expecting? That people will not notice? Let's be strait: backend team f*cked up this. Please be aware of time spent by people, frustration, research because nobody from dev team was not willing to inform users about it, or make migration in better way.

I am very grateful for your engagement in this, but i have a personal "request" for you... when you will someday in a meeting with them, please tell them that they totally screw things up. Next time, they should track migration process to users who share something and to users that do not share. Migrate accounts connected with each other by sharing in the first place. Inform support about it, inform about ETA.

Again, thank you Hans.

This is what a guy working for Microsoft wrote on his personal blog:

This is related to a backend migration we are currently doing. Unfortunately, we do not fully support syncing shared folders if one user has migrated and the other has not. We are doing our best to speed things up so that the issue can be fixed as quickly as possible for users of the feature. When accounts are migrated, there is an automatic logic that ensures that within a few days the synced folders are back.

This is doing my head in. I first got hit by it a couple of weeks ago. I noticed it on my wife's OneDrive where we share a common folder structure. It has really caused a lot of issues as we have many files and folders that are linked in applications and shortcuts.

It appeared as a sync issue with the "Shared" folder locally on her PC being renamed as "Shared-1" and Shared being added as a URL file.

Of course, initially I went down the rabbit hole of trying to fix it, and then came across these reports.

I have had to move most of these files and folders to a private Synology NAS and use Synology Drive to accommodate the use-cases we have.

I can't belie that Microsoft have let this go on so long without resolution.