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

I foolishly renamed a folder and now have this issue.

Looks like its just a sucks to be me scenario.

Just posting here hoping answer might come up because this is going to be a pain in the backside for working on files.

Fix it please. our family will now struggle to sync our damn files

Evan,

I totally agree with you. I am shocked that an "operational" migration could be executed so badly. And the lack of information regarding the migration does not help manage customer expectations. A simple statement from MS saying "Apologies for the slow migration

As an IT professional I can say that it’s not likely that they would add that complexity.

I agree that that is likely what has happened. But is just sad. Grumble-rambling in 3,2,1.

I've been doing this over 30 years. Any company that doesn't have hundreds of thousands of employees would allow their engineering teams to have a ton more say-so in the way their products worked. In any numbers of companies I've worked for, the developers would have quickly determined the implications of a stupid migration process.We would tell our infrastructure AND product design staff that they need to accommodate the scenarios where ANY customer, big or small whose users are sharing content with another within the same product package (eg organizations and family groups).Yes, this adds a hit complexity.  But sometimes a little complexity is worth it. Profits are made on many dimensions, not just catering to whale clients.  You've heard of the long tail, no?

Every MS365 customer that pays to use the system might not be as big a revenue source as your top N-hundred corporate customers.  Tea, you can manage the conversation with your biggest customers.  But when enough of your smaller customers are pissed off, there's no good way to spend enough resources to manage all the support request AND succeed at having happy customers. Therefore, you don't do what MS is doing with this issue.Instead, you listen to social media...and your own damned community forums.  You listen to your software engineering teams.  You tell them, "hey there's this one post that has thousands of posts.  Wow, it looks like we didn't make the right choice doing it the way we are doing it!  Wow, this has been going on for at least months if not longer!  Wow, this sucks to have so many upset users of our product! Can we do something different to improve the experience? Let's have some pride in doing what we wake up every day to earn our paychecks "Management has hired too many people.  They've failed to implement a way for these people to effective listen to their customers.  They have clearly built a culture that doesn't listen to individual employees concerns.Theirs is a very dysfunctional model. They probably could draw the same exact revenue using 20% of the staff AND have happier customers doing so. And they wouldn't have to rely as much on a predatory monopolistic model and dark patterns that ratchet subscription revenues ever upward.The C-suite simply can't see what they're leaving off the table.Back to the original claim about complexity:This is NOT that complex of a problem.  You migrate every user within the same organization or family at the same time, first.  Your prioritize organisations by revenue and also by the revenue of the organizations with whom they've shared content, again prioritizing them based on organizational revenue. You basically have a prioritized graph of dependencies with clusters of users along the way.  It ends with low revenue customers and those sharing with few other users. But it almost eliminates the pain we all came here to complain about. If you have to keep more computer and storage resources alive to do it this way, you work on speeding up the process. You don't force massive ingress/outgress traffic on every single endpoint.  If content is already local, just move it instead of deleting and re-downloading it.

Some more months of development would save many more months of execution time. This is not even close to rocket science.  There are zillions of developers (okay maybe just many hundreds of thousands if not millions) without any formal comp-sci or math training that could figure out how to build these dependency graphs.Large orgs employ too many under-knowledged first line support staff who have no ability or motivation to escalate when they see a trending issue.  If you make it too hard for users to complain, then blockade customers with only first line support not empowered or informed enough to escalate, and then you don't properly analyze your calls and social media...you are doing it all wrong.These huge companies could make soooo much more money by using many fewer staff and managing them differently.

Class Action - this totally broke basic, useful, and critical capabilities - FOR OVER A YEAR!

We all deserve full refunds of our MSFT subscriptions during this period.