Maybe a bit off-topic, but I sure wish they'd do this for OneDrive! I installed Windows for personal use for the first time recently (although I use it exclusively at work) and it drove me ABSOLUTELY BONKERS that my home drive was mapping to C:\Users\atribecalledqst\OneDrive. What I hated the most was that the File Explorer just calls the folders in there e.g. "Documents" and "Pictures" without showing the full path.…
The proper way of doing it is to use the API calls that have existed for decades to get the paths of well-known folders. It is because they are known to move and in fact having a roaming profile on a server location dates to the mid 90s with WinNT. If you're hard coding paths you're doing it wrong.
A user doesn't want to do this though.
I tried casually using a windows 11 machine for something the other day (I think I was fixing game folders for my girlfriend), using just explorer, and it was pretty obscenely bad how overly confusing it had gotten. I say this, and I fairly routinely debug old build systems with complex nesting file structures, I know my way around a file system.
This wasn't a case of "oh you're just a power user", this was a case of the system had broken, and the simple advice of "backing up your files" and "copy your files over here" wasn't working.
Telling everyone they need to use API calls is just ridiculous, the filesystem is just broken for the average user.