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!
I read your message and I honestly can't tell which OS you're using. Perhaps that would be helpful.
I run with UAC disabled on Windows 7, myself, which is essentially running As Administrator all the time. I have no problem with drag and drop.
And as far as I can see, since I have C: set as my only scratch drive, Adobe uses my TEMP folder (which is pointed at C:\TEMP courtesy the TEMP and TMP environment variables).
Let's try to diagnose the problems you appear to be trying to work around first...
Exactly what does it do wrong if you don't run As Administrator? Maybe show screenshots.
What's your TEMP environment variable set to?
Is there anything special you've done to your system?
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):
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)
Photoshop does not create the TEMP folder - that is an OS variable, and the folder should already exist.
And drag and drop problems are most likely unrelated to permission levels or temp file location.
>> Temp is actually on my RAMdisk
Bad idea where Photoshop and Bridge are concerned. It would be faster to use actual RAM, then hit the disk only as needed. Right now you limit the RAM available, and force them to use scratch more often than they should (and even RAM disks have overhead).
When the temp file problem happens I'm not saying Photoshop or Bridge are creating a temp folder, they only create a file in the root directory. This question from this forum pretty much sums it up ( http://forums.adobe.com/message/4400549#4400549 ):
Can Bridge work if you run it as administrator? If yes, will it generate a temp file named like “Photoshop Tempxxxxxx” under the root of C drive when Bridge launch? If still yes, it should be a same issue as what others encountered. And we are investigating this issue now.
It will either create it under admin, or try to create it and crash as a normal user. However with all this tweaking I've tried it seems to have changed this behavior for both Bridge and PS now, but I just can't preview .mp4 files without admin in Bridge (which is weird in its own right) And Bridge x64 can't preview .mp4 alltogether no matter what user/settings are on it (I guess thats another issue/incompatibility)
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.
Therein lies the problem. If you try to trick things you run into trouble.
Yes, it seems like it should work.
Windows and all its apps always work best if everything, and I do mean everything is on drive C:.
In this particular case, relocating things elsewhere does NOT sit well with the Adobe software. You're not the first to see this. People with SSDs try to move things off the C: drive and it virtually always leads to trouble.
You could alleviate all these problems by reorganizing your system so that you have a 2 TB system drive, maybe have some additional drives for data you don't access much in your normal interactive operations, and forget about all the trickery. Trying additional trickery instead of doing this is just going to buy you more trouble down the line with something else.
The whole point of this is to increase performance not muck around on a mechanical HDD... and is there any reason specifically to use 2TB or is that a flexible #?
By the way, it works on CS4 absolutely perfectly. This is why others are frustrated because it has worked with all past versions of Photoshop until CS6 and Adobe just wants to throw it on the user that its our problem when every other version has not had this problem. I guess its our problem now if no one wants to actually listen and realize that its CS6.
2TB is the biggest partition Windows 7 can boot from using a MBR (Master Boot Record) setup. There are ways to go beyond that, but it involves requirements of the computer system that may not be avialable.
I have a 2 TB SSD array, by the way. With everything on the array - drive C: - the system just flies.
Yeah right now I'm not in the market for spending $500+ for two decent SSDs. I do have 2 HDD slots in this notebook, and I could put in 2x500MB/sec SSDs in but theres 24-28GB of free RAM just sitting there all day long when I have much more pressing things to spend $500 on atm. I don't know anymore... it just seems in the past PS tends to go to scratch quicker than I'd want it to but maybe I just used too many history states or whathaveyou and it goes to scratch because of that.... humm... I guess I should do more testing, lol. I just want to minimize unecessary writes to the SSD when there's 24-28GB of free sitting RAM in this thing and even more importantly it goes at 4GB+/sec bandwidth and my inner geek wants temp files to use that speed.
Well whatever luckily I barely use that much for day to day stuff and in the end running Bridge as admin is just going to have to be OK by me. I just wanted to communicate that the behavior of CS6 has most definitely changed from previous versions and is causing problems for geeks like me. (I'm sure you just LOVE me now, right?) Even if Adobe only released an official FAQ for this problem on this forum, it'd save the geeks a lot of headache! Like "Hey, we changed it and tough luck!" would be better than just brushing it off and letting us drown trying to figure out workarounds.
Europe, Middle East and Africa