Installers can not elevate user privileges. They can only temporarily request system privileges based on certificates and signatures. anyway, this shouldn't be necessary and since it affects so many files, I would simply assume that your file permissions are messy - since they are inherited, any invalid permissions ripple through. It's pretty much the only expleanation. So check your drive root properties and fix file permissions.
Thanks a lot for the response. Indeed, you are right; installers cannot elevate privileges..(should have known that).
Nothing has been changed in my root properties since CS5.5. It ran perfectly, whereas CS6 does not without changing permissions as a work-around. I am watching this forum to see if someone else encounters the same problem. With elevated privileges, everything works as advertised.
I've got the same problem and did not find a solution yet (except giving admin rights to the applications). For me, it concerns Bridge, InDesign and Encore [CS6 Master Collection, Win7 x64].
By the way: it's very much the same problem as here: http://forums.adobe.com/message/4317115
I fixed it in Photoshop by starting as admin and setting the scratch drive to another location than C:\
So, what's happening here as far as I found out:
It seems to come from a Photoshop problem. A file called "PhotoshopTemp[number]" is created in the root directory of C. Due to writing permissions, this file cannot be created if you do not start the software as an admin. All programs having trouble seem to create this or a similiar file. (Encore crashes while loading Photoshop library)
That makes sense: Bridge, InDesign, Encore (, Fireworks and I think also Dreamweaver) have a strong interaction with photoshop files. I wonder why After Effects does not have this problem. Perhaps psd-files are addressed in a different way?
While testing I noticed that full permissions for the C:\ root directory were not enough to fix the problem (even that would not be an acceptable solution). There might be more files that cannot be written?
Regarding the other post and my research, a problem could be:
The temp directory of windows is at another location than default - does this apply to you, Dave, as well? However, changing back to default does not help anymore.
A workaround is to start the software with admin rights. Of course, this cannot be a solution.
A solution could only be to change the pointer to the directory(s) which is not possible through the "preferences" of the programs except Photoshop.
This was a very unwelcoming introduction to CS6.
Hoping for a solution or a hint!
Many thanks for your post. It helps me to know I am not the only one experiencing this issue.
I agree with you. Although the work-around using elavated privileges for the CS6 applications does the trick, it certainly is not a long term solution I am happy with.
Affirmative: I also changed the location of the temp folder.
As soon as I installed Windows 7 (32-bit), I reconfigured the temp folder on another (data) partition and I have UAC on (always notify).
Thanks so much for helping me discover why I am having this problem.
It does, however, make me wonder if Adobe tests their software on Win7 x64. Writing to the root directory of a drive has not been allowed since the x64 version came out! Between that and Photoshop's dislike of the Users folder not being on C: (easy to fix, but why should I have to go through the extra steps, adn why doesn't Photoshop gracefully recover from it), I'm less than impressed with Adobe's testing.
I still love the software, but do some better testing, folks!!!
Perhaps, you've read it already:aochenglong, Adobe Employee 10.05.2012 04:46
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.
so, we can look forward to a solution within the next updates.
Just a quick update on this issue.
The work-around for Photoshop is fortunately a temporary fix. It is definitely related to the scratch disk loation. At its first start, use elevated privileges (run as admin) in order to change the scratch disk station. Once the correct station is set, remove the elevated privileges.
I discovered by accident that setting elevated privileges is not a permanent solution for Photoshop CS6. You may run into problems with some GPU acceleration for some filters. In my case, the Oil Paint filter gave a warning about a unknown error with the graphics card. Also all 3D functionality was disabled in Photoshop Extended. After I removed the elevated privileges (after the scratch disk station was already set of course) Photoshop runs normally.
However, my issues with InDesign and Bridge CS6 cannot be resolved. I need to run these applications with elevated privileges or else each application will crash.
Fireworks and Dreamweaver can work without elevated privileges if Bridge runs on elevated privileges, but that again is Bridge related.
I thought I should add to this thread so Adobe knows that this is an issue that they simply must fix!
I am the ICT administrator for a school - we have approx 250 computers which we install Adobe CS on. Every version including CS5.5 worked flawlessly. CS6 has been a nightmare!
I too encountered both the Photoshop and InDesign errors exactly as described here. I found the solution for Photoshop was also to change the scratch disk to a different drive than C - a little tip I figured out for anyone with multiple users or a domain environment, you can copy the directory C:\Users\<username>\AppData\Roaming\Adobe\Adobe Photoshop CS6\ from a user whose scratch disk has been changed to another drive and paste it to any other users, and their scratch disk will be changed without having to elevate privileges and manually changing each time.
As for InDesign, I have been working on this for three days solidly, and have found no solution, having tried literally hundreds of things including giving all users of my test machine full permissions to the entire C:\ drive. Nothing makes InDesign work except running it as the administrator (which I simply cannot do in my environment). It cites MSVCR100.DLL in the crash error, which is located in C:\Windows\SysWOW64 but updating this file and altering its permissions also does nothing (deleting it stops InDesign loading at all )
I have also tried redirecting InDesign file recovery to a different drive and setting permissions on all directories listed under InDesign support on Adobe.com (local and roaming data, cache). No effect.
Notably, InDesign fully loads up before crashing. It crashes once the application window has appeared, after about 2-3 seconds. The cursor changes to the loading wheel and immediately crashes. When running as an Administrator the loading wheel also appears after 2-3 seconds, so the error seems related to whatever InDesign is doing at this time, but I have no way to tell what this is.
Definitely need some updates regarding these issues, as I cannot roll out CS6 to our computers until this is fixed!
No news from me on fixing the InDesign CS6 problem. As soon as I have one, I will post it here.
The work-around using elevated privileges, is not possible for managed environments like in HT_Preveus' post.
Personally, I don't have to deal with a managed environment (yet) so the work-around is just a temporary fix until Adobe comes up with a patch that will resolve this issue.
InDesign seems to work if you give all users the permission to create directories on c:\
Seems to be the same error like in Photoshop.
This is a nightmare if you want to run it on a Terminal Server or in an hostile environment, but that's another issue.
P.S.: What are the TEMP and TMP environment variables good for if nobody is reading them?
for Photoshop work with the solution from HT_Peveus in this Discussion
I found the solution for Photoshop was also to change the scratch disk to a different drive than C - a little tip I figured out for anyone with multiple users or a domain environment, you can copy the directory C:\Users\<username>\AppData\Roaming\Adobe\Adobe Photoshop CS6\ from a user whose scratch disk has been changed to another drive and paste it to any other users, and their scratch disk will be changed without having to elevate privileges and manually changing each time
for Terminal Server, it´s ok for my, all users need the same settings
my problem is InDesign with Terminalserver
i have set the permission for all users on "c:\" to full, but i have the same problem, InDesign crash after it´s 3-4 seconds running
Hallo Herr Schneider,
ich Antworte und Frage auf Deutsch, ich hoffe, das ist Ok und vielleicht können Sie mir weiterhelfen.
Zum Überblick: Ich versuche im Moment einen Terminalserver 2008 r2 mit CS6 zum Testen (später Produktiv) zum Laufen zu bringen.
Wir haben Roaming Profiles und wir leiten beim Anmelden des Users, das Profile auf ein zusätzliches Laufwerk um.
Soweit auch alles kein Problem, funktioniert.
Ich hatte schon mit Photoshop das Problem, wie in dieser Diskussion. Gelöst hab ich das, nach langem Suchen, wie hier. Da gab´s diesen Eintrag noch gar nicht.
Nachdem bei uns eh alle User die gleichen Einstellungen haben sollen, hab ich Photoshop direkt auf dem TS konfiguriert. z. B. das Arbeitsvolume habe ich geändert und zwar auf das Laufwerk, wo unsere Profiles liegen. Per Skript kopier ich dann die Einstellungen von C:\Users\Administrator\AppData\Roaming\Adobe\Adobe Photoshop CS6\ in das Profil des Users. Funktioniert.
nun zum InDesign
Beim InDesign kann man wohl das Arbeitsvolume nicht anpassen!?
Das mit der PhotoShop Temp Datei von InDesign habe ich nun auch nachvollziehen können.
Könnten Sie mir vielleicht verraten, wie Sie die Berechtigungen genau zum anlegen und löschen von Ordner und Files gesetzt haben?
Ich denke aber, dass das auf einem TS schon gefährlich ist!?
noch ein Nachtrag: ich habe jetzt die Umleitung des Profiles auf das zusätzliche Laufwerk wieder rausgemacht. Jetzt fuktioniert´s!!! Auch wenn ich keine Berechtigungen setzte!!! Nun hab ich auch das Problem mit Photoshop und dem Arbeitsvolume nicht mehr!!!
Just another quick update on this issue.
Unfortunately, I discovered that I cannot run Illustrator CS6 without elevated privileges. Some functionality will cease to work (see: http://forums.adobe.com/message/4442699).
So as a work-around: Photoshop should not run as an admin, Illustrator should.
Hi, I had cs6 probs until:
- set Win7 system and user tmp and temp variables from x-drive to c:\temp
- relocated any cs6-related caches from x-drive to c.
Setup: win7 64-b, ssd as os-disk, ssd-raid0 used to be for caches.
Not gonna pinpoint the least amount of changes needed, I'll just wait Adobe to fix it and then return my settings.
Having a similar problem with Indesign and Encore. My windows user profile is on "D:\"and for some reason both apps want to write a temp file ( "photoshop temp" ) to the root of "C:\". This can only be achieved by running as an admin. If I run the programs logged in with a user profile that is stored on "C:\users.." they create the same ( "photoshop temp" ) in the correct location being "C:\Users\%username%\Appdata\Local\Temp" and the program works happily.
I am 98% sure this is the reason for the crashing at startup, but I cant find where Adobe has set this path. I dont want to flatten the file system just for these applications
Adobe Please Help!
I tried running indesign in XP SP3 compatability mode as you suggested above and it worked.
I'm running Win7 x64.
I should add to this that I have the Users and ProgramData folders located on the D: drive. I did place hard links on C: to redirect to D:, and this seems to work for every other piece of software I have installed on the system
After installation of Design Standard CS6 and the latest update, InDesign, if started "normally", still crashes with a Runtime error a few seconds after the opening screen appears; this does not happen when running it as an administrator or in XP SP3 mode. Apart from the UAC prompt that appears in these two work-arounds, it is just annoying that InDesign cannot be run "normally" like every other program I have installed (except Photoshop CS6 with its scratch disk problem that can be resolved by going the administrator route only once to change the scratch disk).
Apart from the above, Ilustrator CS6 starts with an error message about the Drop Shadow plug-in not being loaded due to an error, but it does not crash.
I want to share the solution of serious bug of all products Adobe CS6.
After 8 re-installation of Windows 7 x64, and clean install applications CS6 was found that:
changed the location of the temp folder to another disk. For example the
transfer of the Temp folder from the disk "C" on drive "D".
Use of NTFS junction points (mklink /D C:\Users\west\AppData\Local\Temp D:\All_temp\temp) after the transfer, also does not solve the problem.
Solution!!!: return everything back to default.
Important!!! for correct installation of applications CS6 need to be installed after
return paths of the variables by default, and reboot to apply the values.
p.s. Adobe solve this problem please!!!
OK, so I've spent several hours trying to figure this issue out (to get Encore to launch, in my case) and after reading several forum postings about it and testing things on my computer, here's the workaround I came up with. This is largely based off of wesstyless's post above, which gave me the idea to redirect it with a junction point.
My user profile and temp directories are on my D: drive (and I intend to keep them there!)
- I created a "dummy" user profile directory in the default location on drive C
- In this dummy directory, I created an NTFS junction named Temp which pointed to my actual temp directory on D
mklink /d C:\Users\Chris\AppData\Local\Temp D:\Temp\Chris
- I switched the TEMP and TMP environment variables (right-click computer, properties, advanced system settings, environment variables) to both point to the new junction point in the dummy user directory
After setting this up, I ran Encore and it launched just fine. I haven't actually used it for anything but configuring my settings yet, but it crashed on startup every time I ran it as a standard user before, so getting to the UI is significant progress.
Obviously, the best solution is for Adobe to fix the issue with an update (it boggles my mind how they could have hard-coded a temp directory on to drive C). Theoretically there's no downside to my workaround, because even though everything in Windows that uses the TMP or TEMP environment variables will be trying to write to the directory on drive C, the Junction point will *automagically* cause the reads and writes to happen on drive D where they belong. Still, it's kind of a hack.
I hope this helps!
- I created a "dummy" user profile directory in the default location on drive C
The problem is completely solved!!!!!!!!!
My Fault Productions, You are also grateful for the tip =)
The correct way to move the system variables using junction points. On the example of folder Temp.
1. Transferring the Temp folder to another drive as usual (for example: D:\temp). Reboot.
2. Delete the folder Temp, which is the default disk "C" (C:\Users\%username%\AppData\Local\Temp)
3. At the command prompt running with administrator privileges, enter the following command:
mklink /D C:\Users\west\AppData\Local\Temp D:\temp
(Everyone has his name) This will create a transition point.
4. In the setting of the location of the Temp folder restore the default path:
5. Reboot and enjoy. The system thinks that the Temp folder is the default, but really is on another drive.
All applications CS6 with this method of working.
It's important! Need to install the application after such manipulation.
Updates are working.
I was trying this and I got to the point of restoring the default path to the Temp folder and couldn't proceed.
I logged in as Administrator and followed steps 1-3, but when I got to step 4, the "Temp" folder that's in my "H:" drive does not have the location tab. So I am unable to change the default path.
Any reason why? Did I miss something that is causing me not to have this tab? Any assistance would be greatly appreciated.
Thanks for the reply. I have a problem in step 4-
"4. In the setting of the location of the Temp folder restore the default path:
When I go to the Temp folder properties, it does not give me the "Location" tab to change the path back to default. Maybe I'm doing this wrong.
The compatibility mode change to Windows XP SP3 from Manish-Sharmaworked for me as an alternative work-around. Alas it is still a work-around as we are already living in the post Windows XP era.
The alternative work-around using an NTFS junction is also much appreciated for those who cannot afford to use elevated privileges.
I think this post identifies the culprit of the problem we're experiencing: the inability of CS6 applications to recognise the custom location of a temp folder in the Windows 7 environment variables.
There was no such problem in CS4 or CS5 on another machine, or in CS5.5 or any non-Adobe application that uses the temp folder on my machine.
And here it is in CS6. It is sad to see it is still not fixed.
I confirm that it's not fixed yet but the weestyless solutions solves the problem ! Thanks.
To make it easy (not more secured but easier) and work with XP without admin right on C drive :
- I created a directory c:\temp with the create, modify rights for my users
- I created a wrapper batch script that
- save my TMP et TEMP variables in MYTMP and MYTEMP
- then "setx TMP c:\temp" and "setx TEMP c:\temp"
- Launch the adobe program
- set the 2 variables back to original values
- I used that script so when my user close it's adobe application, everything is back to normal envrionment.
What is amazing is the answer of adobe support that i'll share with you (it's in french, but i'll translate it after) :
Cher Monsieur Chambault,
Merci d'avoir contacté le service clientèle Adobe.
Je vous contacte suite à votre problème. Il semblerait que vous utilisez notre logiciel sur une session en domaine. Malheureusement, nous ne supportons pas techniquement une installation en domaine. Veuillez souscrire à un contrat d'assistance technique pour ce faire. Le problème que vous rencontrez est tout à fait normal, vous avez des droit limité, et ce, même si vous êtes administrateurs
Si jamais vous rencontrez le moindre souci, n'hésitez pas à nous recontacter et c'est avec plaisir qu'un de mes collègues ou moi-même tenterons de résoudre votre problème dans les plus brefs délais.
Afin de fournir un meilleur service à nos clients et pour améliorer le niveau de notre service clientèle, je vous invite à compléter l'enquête de satisfaction attachée à ce mail.
En vous souhaitant une excellente journée,
Adobe Service Clientèle.
Nous vous adressons ce message en réponse au cas de support n° 0209102993 ouvert par cedric chambault.
Pour répondre à cette mise à jour ou consulter l'historique des cas, connectez-vous au Portail du support technique Adobe et recherchez le numéro du cas dans la section des activités récentes. Pour ajouter des informations, ouvrez le cas et mettez-le à jour.
Si vous ne parvenez pas à vous connecter, consultez le forum aux questions sur les identifiants et les adhésions Adobe
Le service clientèle Adobe
So, if you don't understand french, i'll translate for you :
"The support says that you payd a lot to buy our software, but it's not supported in a professional environment. However, if you pay more in subscribing a support contract, we will help you"
Amazing answer !! When you create such a bug on a "professional" application, you must correct it ! it's not about support silver or gold or no support at all !
How can a company like Adobe officialy ignore domain networks ? Completely astonishing !!!
We have still not bough our CS6 updates (several thousands dollars) due to this temp directory bug and Adobe ignoring entirely the most elementary network security rules ... This really don't give trust into Adobe, for the least !
Yep I get this too. Thanks Adobe.
Not a chance in hell I can get a company of 14000+ to change it's policies because you can't write software correctly. Noticably Dreamweaver, Fireworks and Flash run just fine. Your new 64-Bit re-writes fair the worst. Also thanks to your custom downloaders I can't download the right installer through our network. I got the one from ftp.adobe.com and it turns out to be English/Hebrew, not what I wanted.
So yeah I will be running the apps as admin because of this debacle.
I've been using Photoshop since the late 90s in college. I thought you guys saw what happened to Quark when they treated their customers this way.
I got the same porblem since upgrading from cs5.5 to cs6.
But still not resolved for me.
I'm working under windows 7 x64
All my users profiles are on d:
So let say my user name is toto.
I have d:\Users\toto\AppData\...
And in my system vairables :
I tried making a d:\Temp and a mklink /D c:\Users\toto\Local\Temp d:\Temp
but still same problem importing psd file into ae.
Using processmonitor, I see that it tries making a 'Photoshop Tempxxxxx' file under c:\
What can I do ?