How does something like that ship? That’s going to affect virtually every Office user. Why not just filter out files that won’t sync and warn the user?
How does something like that ship? That’s going to affect virtually every Office user. Why not just filter out files that won’t sync and warn the user?
The thing constantly overrides user-set preferences: fonts, colors, and worst of all - default apps. Reports usage data to Microsoft with no way to turn it off. An update mechanism that lives its own dominating life, interrupting user workflow whenever it wants.
Once something like Classic Shell was installed, it was pretty slick and reliable.
My last Windows machine now runs 10 begrudgingly, and compared to my daily drivers MacOS and Ubuntu, it's a shockingly inconsistent operating system. I don't rely on it for "real work" thankfully.
This might be the Second Law of Thermodynamics at work, but seriously, I don't understand how these things got shipped.
C:\Users\Rumpelstiltskin\OneDrive - Rumpelstiltskin's Gold Spinning Services Inc.\
Then you realize that Excel has a 218 character path limit on file names and things get ridiculous really fast. subst X: C:\Users\Rumpelstiltskin\OneDrive - Rumpelstiltskin's Gold Spinning Services Inc.\
Annoying, but it does work.Eventually I settled on abbreviating company names and putting OneDrive in C:\OD, so:
C:\OD\OneDrive - RGSS\Shared Folder\
Not great, but better. Then when you share files and someone else syncs, they get: C:\OD\RGSS\Rumpelstiltskin - Shared Folder\
And it all goes to hell again. Lol. The base path length's are reasonably close though and seems to work ok.The blacklisted file types are frequently changing, tanking your sync performance, and the client applications that use them communicate directly with their backend services.
I'm not saying it's a good reason, but it's not completely arbitrary.