If it works as Admin, but not as a user - then the problem could be preferences, or bad disk permissions.
We know of one crash that occurs if you do not have permission to create or write to files in the user's home directory (and we are testing a fix for it).
Hi and thanks for the swift reply.
Myself and a colleague of mine have been looking through permissions on the disk. As far as i can tell all users have full permissions to their home directory. I also ran Process Monitor to see if i could spot any other locations a user may need rights too but to no avail.
The areas i tested included SL_Cache; renaming to .old and allowing the program to recreate the directory seemed to make no difference, even running Photoshop as a 30 day trial. giving users full access to a few directories on common files and program files didnt seem to help either. Are there many areas of either the registry or file system that need special permissions? and when you say preferences do you mean user preferences or something else? we did try deleting user settings by running with shift ctrl alt. and also with a clean profile without luck.
Sorry for all the questions and thank you for any help!
Yes, your preferences directory also needs permission to create files, as well as the application support directory.
Just for anyone else who gets the same issue we have i believe i have found the solution, in our case at least.
I ran process monitor again to see if i could spot anything odd that Photoshop was trying to do and then i found this:
it looks like Photoshop is trying to create a new file on the root of the windows directory called pslog.txt and when it fails to do this the program crashes.
So i created a script that creates this file and then give all users write access and this has stopped the crashing.
Hope this helps anybody else that finds themselves in the same situation as us trying to get the program to work in a domain environment.
pslog.txt should go in your user directory, so something is royally hosed on your system.
(the fact that it exists at all is a bug that we just fixed)
I can confirm that pslog.txt is created in %HOMEDRIVE%%HOMEPATH% so your user profile config may have HOMEDRIVE=C: and HOMEPATH=\.
I've got the same error on photoshop on domain users because I have HOMEDRIVE=Y and HOMEPATH=\ (a networked drive).
For security reasons on my environment my users doesn't have permissions to write to y:\, only to subfolders, then photoshop cc 2014 crash.
I've created the pslog.txt on the y:\ drive with write permissions for every user and now all works with no problems.
My users are normal domain users (not domain admins, nor local admins)
We are seeing this issue as well, except Photoshop CC 2014 is trying to write into C:\Shortcuts, which is the location we redirect our desktops and start menus too.
So far the only work around has been to use group policy to deploy the log file to the location Photoshop is trying to write to and set permission so all users can write to it.
I've opened a support case with Adobe (Case number: 185963856 ) however their initial response is pathetic...."We may not consider this a bug" and they sent me the locations below which "need" read/write access, which is not true and not helpful!
C:\Program Files\Common Files\Adobe*
C:\Program Files\Common Files\Macrovision Shared
C:\Program Files (x86)\Adobe*
C:\Program Files (x86)\Common Files\Adobe*
C:\Program Files (x86)\Common Files\Macrovision Shared
C:\Users\<user_name>\AppData\Local\VirtualStore\Program Files\Common Files\Adobe*
~ Registry Keys ~
That information is pretty dated. Several of those paths are no longer used.