WorksOnMyPC Posted February 14, 2019 Posted February 14, 2019 Afternoon, I am having a battle with Adobe Photoshop CC 2018 on vanilla Windows 10 1809 fully upto date. I can install it just fine with SCCM and it works fine as a normal user (no UAC prompt) however when it loads I receive the error. "There is a problem with Generator, Please quit Photoshop and try again" Ive been through every adobe message board post I can find but it doesn't generate error logs. Ive had procmon and procexplorer on the go and dug into the depths of the unknown and allowed access to all the files and registry it attempts to read/write. But alas it still doesn't work for a normal user who are not a domain admin or a local admin of the machine. Has anyone gotten the latest version of Photoshop working on a domain that still has UAC enabled? Any help is appreciated! Thanks, Chris
robyholmes Posted February 14, 2019 Posted February 14, 2019 Do you have AppData redirected by any chance? We had to get rid before CC would work. We've also had to disable it running on startup and disable the updater service as it kept locking up the machines on log off or on for the next user.
WorksOnMyPC Posted February 14, 2019 Author Posted February 14, 2019 No AppData isnt redirected, I am using UE-V instead of roaming profiles but I didn't think that would make a difference.
robyholmes Posted February 14, 2019 Posted February 14, 2019 We're running 1803 + UEV + UAC with no roaming profiles or AppData redirected and its working fine. Hope that helps a little bit.
WorksOnMyPC Posted February 14, 2019 Author Posted February 14, 2019 Thank you that does give me some faith! Have you generated a UEV profile for Photoshop?
robyholmes Posted February 14, 2019 Posted February 14, 2019 Thank you that does give me some faith! Have you generated a UEV profile for Photoshop? No, I don't think I students change anything they really want to keep changed so not bothered.
WorksOnMyPC Posted February 14, 2019 Author Posted February 14, 2019 Thank you for the advice, I managed to sort it out. Ended up it was trying to save to the full user path instead of the user share and causing some read write errors. Learned something today!
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now