[Windows] Does not deal with "shell folders" not being on C:\

[Jo Shields]

It is reasonably common for Windows users with an SSD to install the OS and apps to the SSD on C:\, and set user directories (i.e. C:\Users and components thereof) onto another drive. In my case, I used the letter K:\, and followed the instructions at http://answers.microsoft.com/en-us/windows/forum/windows_7-files/win7-how-do-i-move-user-folder-to-a-different/565f16a5-e5ed-43c9-8422-4f56aebb296e

Most apps are happy with this arrangement, and "set USERPROFILE" in a cmd.exe window correctly returns a folder on K:\

However, the U1 client does not deal with this arrangement at all.

It fails if C:\ProgramData isn't as expected, because it tries to read the U1 server's SSL certificate from C:\ProgramData and fails to find it.

It fails if C:\Users isn't as expected, because even if you make the certificates work (by turning C:\ProgramData into a junction point to K:\ProgramData) then syncing purchased music tracks from U1MS fails when the syncdaemon attempts to move partial downloads from the xdg cache folder to C:\Users\foo\.ubuntuone

Apparently when following the guide linked above, all profiles have correct folders set in HKCU in the registry, and the folders are applied to all new users as per HKLM\Software\Microsoft\Windows NT\CurrentVersion\ProfileList. However, the values in HKLM are set to C:\ values, which are wrong.

It's been theorized on IRC that switching the API used by U1 from a deprecated API to a new Vista API for determining folders would fix the issue

At any rate, it would be nice if U1 could deal more gracefully with C:\Users not being on C:\