P: Photoshop creates a gude log while working with files

Thanks for the suggestion. Unfortunately it didn't work for me.

That didn't help.  As soon as I started editing an image in PS, the GUDE logging occurs.

"GUDE Logging Started"

It seems I may have found an alternative solution.

Disabling proxy auto settings and changing default program for impacted files (.psd or .ai) seems to have worked for me.

For my case, changing .psd default program and setting it back again has done the trick for me.

I don't know if both actions have made it possible or it's the proxy setting change.

How long is this "investigation" going to take?  I have the exact same issue when I double click from File Explorer (Win11) on a .HEIC file that Photoshop opens then I get a new file called gude-2022-12-23.log:

11:16:06:953 [ALWAYS] GUDE Logging Started
11:16:06:953 [INFO] SqliteResumeCache::SqliteResumeCache basedirectory is null/empty
11:16:06:953 [ERROR] SqliteResumeCache::CreateSqliteResumeCache creating resume cache pointer failure
11:16:06:953 [ERROR] Initialize resume cache pointer failure
11:16:06:953 [INFO] gude policy POLICY_USER limit (2,2,1) chunk 2097152, chunking (UL 0 DL 1), resXfer 1, adapt 0, NSURL 0, timeout 86400
11:16:06:953 [INFO] Initialized -- gude-lib version: v0.12.1 app: gude
11:16:08:209 [WARN] Ignoring attempt to reinit logging to \gude at level 4 retaining 3 days of logs
11:16:08:210 [INFO] SqliteResumeCache::SqliteResumeCache basedirectory is null/empty
11:16:08:210 [ERROR] SqliteResumeCache::CreateSqliteResumeCache creating resume cache pointer failure
11:16:08:210 [ERROR] Initialize resume cache pointer failure
11:16:08:210 [INFO] gude policy POLICY_USER limit (4,4,1) chunk 2097152, chunking (UL 0 DL 1), resXfer 1, adapt 0, NSURL 1, timeout 86400
11:16:08:210 [INFO] Initialized -- gude-lib version: v0.12.1 app: gude
11:20:07:793 [ALWAYS] GUDE Logging Started
11:20:07:794 [INFO] SqliteResumeCache::SqliteResumeCache basedirectory is null/empty
11:20:07:794 [ERROR] SqliteResumeCache::CreateSqliteResumeCache creating resume cache pointer failure
11:20:07:794 [ERROR] Initialize resume cache pointer failure
11:20:07:794 [INFO] gude policy POLICY_USER limit (2,2,1) chunk 2097152, chunking (UL 0 DL 1), resXfer 1, adapt 0, NSURL 0, timeout 86400
11:20:07:794 [INFO] Initialized -- gude-lib version: v0.12.1 app: gude
11:20:09:123 [WARN] Ignoring attempt to reinit logging to \gude at level 4 retaining 3 days of logs
11:20:09:123 [INFO] SqliteResumeCache::SqliteResumeCache basedirectory is null/empty
11:20:09:123 [ERROR] SqliteResumeCache::CreateSqliteResumeCache creating resume cache pointer failure
11:20:09:123 [ERROR] Initialize resume cache pointer failure
11:20:09:124 [INFO] gude policy POLICY_USER limit (4,4,1) chunk 2097152, chunking (UL 0 DL 1), resXfer 1, adapt 0, NSURL 1, timeout 86400
11:20:09:124 [INFO] Initialized -- gude-lib version: v0.12.1 app: gude

I'm running Ps v24.1.0

8 months since this was reported and several versions later and problem still persists?

Adobe doesn't care because customers need the product and will pay to use it, either with bug or not, people will pay, that's what Adobe needs.

Die Meldung von Fehlern auf dieser Plattform ist völlig sinnlos. Adobe ist das Problem seit Mai bekannt, aber anscheinend nicht an einer Fehlerbehebung interessiert. Auch die Aufforderung genaue Daten zum Betriebssystem etc. zu posten, ist nur Beschäftigungstherapie. Der Fehler ist reproduzierbar und kann somit von Adobe jederzeit selbst nachvollzogen werden. Auch die angebotenen Workarounds wie das Umschalten des Proxyservers auf manuell oder das Öffnen der Datei mit Rechtsklick sind nicht die Lösung des Problems, zumal der Fehler erst durch das Update im Mai auftrat. Auch der deutsche Telefonsupport von Adobe scheint mir wenig Einfluss auf die Entwicklerabteilung zu haben.

Reporting bugs on this platform is completely pointless. Adobe has been aware of the problem since May, but is apparently not interested in fixing it. Even the request to post exact data about the operating system etc. is just occupational therapy. The error is reproducible and can therefore be reproduced by Adobe itself at any time. Even the workarounds offered, such as switching the proxy server to manual or opening the file with a right-click, are not the solution to the problem, especially since the error only occurred with the update in May. Adobe's German phone support also seems to me to have little influence on the developer department.

I just installed a new Adobe Creative Cloud subscription of Photoshop 24.1.0 on Windows 11 (Home), and confirm that if you double-click to open a .PSD file, it will cause a GUDE log text file to be created in the same folder. If you right-click and open the file with PS, no log file will be created. There are useless GUDE files all over my image folders. Can Adobe please fix this in the next release? Thanks.

It's just a bug Adobe hasn't seemed to have fixed yet. The pinned reply on this issue from Adobe has a date of May 13. I hope the amount of attention from customers in this thread will spur some attention on Adobe's part.

Temporary fix until Adobe gets their act together: Instead of opening images by double-clicking from Windows Explorer: Right-click the file and select Open with Photoshop. Or open the file from within Photoshop, as mentioned elsewhere in this thread. This will avoid the whole gude log-file-thingy issue.

Set up a new pc and the issue happened for the first time ever since.

What solved it for me was downgrading the PS version from 24.1  to 24.01

The original troubleshoot at the start of the thread (uncheck gpu, delete presets) didn't work for me.

System: Windows Home 22H2