OK, here's a few things to consider.
Apps failing to write userdata: this sounds serious, and weird - haven't run into it myself, so I'm a bit stumped as to why it might be happening. Read something somewhere sometime (
) that you can end up in weird situations if you install your apps with UAC disabled and then re-enable UAC, but... *shrug*
Hotkeys: there's several ways to define these, one of them has the possibility to override existing hotkeys (ie., built-in Win+
X). This method requires setting up a system hook, injecting DLL into all processes, (try to) un-register hotkey in all processes (because you don't know which one has registered the hotkey), and then re-register the hotkey. It should be obvious why this won't work for elevated apps if the I-want-hotkey app is running from a LUA. Doesn't explain some of the Win7 hotkey weirdness fully, though!
1Permissions on secondary drive: this has already been mentioned by Carol and Eóin, but needs a slight clarification: it's not because of acccount/computer name, but the
SID (not GUID, they look slighty similar but aren't) assigned to your user account; if you upgrade Windows, the SID should carry over, when you do a fresh install you get a new (random) one. This is not a Windows 7 thing, but rather it's generic NT. You'll see the same if you carry an NTFS-formatted USB drive to another computer. Too bad there's no built-in "
really take ownership and fix permissions of all these files, and get rid of the orphan SID".
Monitor woes: sounds weird too, defining primary monitor works fine on
my win7 installation.
Win+{up,down} is a YMMV thing - I really like the behavior, as I often go between maximized and "restored" state. Maximized firefox is awful on a 1680-wide screen
1: I override Win+F to locate32 and Win+E to xplorer
2, but in
some applications those hotkeys are overridden - even though those apps aren't elevated! I'm pretty stumped as to why this happens, but I think it might happen in apps programmed in MFC.