CEP-Resources
CEP-Resources copied to clipboard
Empty C:\Tempzxpsign<long number> directories created and not removed with Photoshop
I'm noticing that every time I start up Photoshop one or more of these directories is getting created. Currently running CC2017 with the latest updates. This is on windows, and I have enabled debugging via the registry entries.
it's Adobe's problem.. seems developer missed putting "" as a result instead of tmp\zxpsign it's now tmpzxpsign
Please do a google on "multiple folders in c drive with name tmpzxpsign*"... among multiple solutions I tried renaming the file "C:\Program Files (x86)\Adobe\Adobe Photoshop CC 2017 (32 Bit)\ZXPSignLib-minimal.dll" which does this... And so far no issue encountered.. You may give it try.. but on your own... :)
@AndrewMore1
Just set current user's TEMP same as global TEMP folder in your current user variables:
in CMD.exe
setx TMP ^%SystemRoot^%\TEMP
setx TMP ^%SystemRoot^%\TEMP
in .bat file as admin launched:
setx TEMP "%%SystemRoot%%\TEMP"
setx TMP "%%SystemRoot%%\TEMP"
@jharajnish30
it's Adobe's problem.. seems developer missed putting "" as a result instead of tmp\zxpsign it's now tmpzxpsign
Please do a google on "multiple folders in c drive with name tmpzxpsign*"... among multiple solutions I tried renaming the file "C:\Program Files (x86)\Adobe\Adobe Photoshop CC 2017 (32 Bit)\ZXPSignLib-minimal.dll" which does this... And so far no issue encountered.. You may give it try.. but on your own... :)
This wont work for Illustrator and Indesign CC 2017
@jharajnish30
it's Adobe's problem.. seems developer missed putting "" as a result instead of tmp\zxpsign it's now tmpzxpsign Please do a google on "multiple folders in c drive with name tmpzxpsign*"... among multiple solutions I tried renaming the file "C:\Program Files (x86)\Adobe\Adobe Photoshop CC 2017 (32 Bit)\ZXPSignLib-minimal.dll" which does this... And so far no issue encountered.. You may give it try.. but on your own... :)
This wont work for Illustrator and Indesign CC 2017
Are newer versions fixed or the problem remained within Adobe products?