CS6 temp file blunder - can you repeat this problem?

Question

There is a serious root problem with Adobe's implemented permissionless-temp-file creation methods (pun intended.) The problem is that during startup, both Bridge and Photoshop CS6 try to make temp files on the root folder of the OS drive. Its affecting many peoples' installations by crashing them on application launch if not run by the super-administrator account on the computer. Adobe says to just run as admin to fix it, which does fix the start up crash. However, for me, it creates a gigantic problem: it breaks OS-to-PS and OS-to-Bridge drag and drop functionality completely!!! I literally was slowed to a crawl in my workflow having to import photos 1 at a time through the file-> open menu because I couldn't drag and drop various files from various locations on my computer. Not everything is clumped in 1 area neatly for Bridge to open everything, and I never realized just how much I used this function until this run as admin band-aid broke it. Eventually I fixed the CS temp location after 10-12 hours of hair pulling research and trial and error, and I finally have Photoshop CS6 working without admin permissions and everything is dandy with drag and drop, but only in PS. Bridge still cannot be run without administrator privileges and cannot have files dropped in or out of it to or from Explorer, and I am getting really frustrated here.
Its kind of disheartening that I have to work for 10 hours in order for me to be able to pay and fully utilize Adobe's software. Even 3 months after being made aware of this issue in other forums, and for how many people it is affecting, they still don't fix it when all they need to do is move the default location of the temp file to somewhere without a need for admin permissions! (I.E. documents folder?)
So does anyone else find their drag and drop ability gone once running Bridge/PS CS6 in admin mode? Am I the only one? Is there a way to move the default temp creation location of Bridge as well? I'm frustrated and I think Adobe seems to be taking this permissions issue way too lightly!

Answer 1

I'm running Windows 7x64 Professional. Temp is actually on my RAMdisk but using a folder junction to trick the programs into thinking its on the default temp folders of the C drive. Disabling UAC will fix it yes, but I don't want to disable UAC as I travel with this computer and security is something I prefer to have with me. Its only set to minimal UAC as well, but still its nice for spotting some things. And now, I really am going to look stupid here, but some reason now I can run Bridge without admin permissions without crashing, but now I can't preview or play .mp4 files which was a problem I had before!!! So, now I have a big WTF? expression on my face right now since I've been meticulously trying to get Bridge to work with drag and drop for over a week (and I guess now it magically does once someone actually pays attention to my posts lol) but now .mp4 functionality is poof without admin rights, no matter where the files reside. I think I give up on Bridge I'll just run it as admin but sheesh...
[[ giant pointless image removed by admin ]]
But, I still can post references... these all have a problem with 'MMXCore.8BX_unloaded' on startup (there are more elsewhere but it takes time to find them all):
http://feedback.photoshop.com/photoshop_family/topics/bridge_cs6_release_crashes_on_startu p
http://forums.adobe.com/thread/1001298
http://www.sjogrens.nu/?p=106
Junction points are mentioned in the second post, and that's what I have done on my system (I did it with a program not command prompt, though)
Really though, after all I've read through and tried, changing the default location of where Photoshop and Bridge intitially put their TMP files to a permission-lax folder would really fix all the problems with this, even if it is caused by changing the default temp area, it would solve the issue for everyone that does do it. A user's documents folder would work perfectly. Sorry if I'm a little inconsistent with information I'm tired and just about burnt out on this stuff (including a lack of sleep)