Skip to main content
Participant
April 14, 2022

P: Photoshop creates a gude log while working with files

  • April 14, 2022
  • 408 replies
  • 163390 views

Beim Arbeiten mit der aktuellen Photoshop-Version hängt sich Photoshop nach kürzester Zeit auf, d.h. die Bedienoberfläche und Menüs verschwinden und ein speichern ist nicht möglich. Folgende Fehlermeldung schreibt er in die log-Datei (gude-2022-04-14.log):

 

[WARN] WGudeRequest::applyAutoDetectProxyAutoConfigSettings Failed to autodetect proxy settings. WinHTTP Unable To Download Script. last error code = 12167

 

Hat jemand ein ähnliches Problem und kann mir helfen? Vielen Dank.

This topic has been closed for replies.

408 replies

Beachcolonist
Inspiring
December 31, 2022

You will be happy to learn,

1. Your reason you say you won't use Bridge is a myth: there is no requirement for what you call, "a system scan for listable files in Bridge" in order to use Bridge. You can just add Bridge to your "open with" options.

2. You don't have to use Bridge at all (though it is a fantastic software and is exactly what the name implies, the bridge between file collections and Photoshop) you can just use "open with" Photoshop.

 

3. Or you can open Photoshop first.

 

There you go, no need to thank me have a productive time creating in Photoshop!

Participant
December 31, 2022

Hello everyone who deals with the automatic creation of Photoshop 24.1 Gude log files.
A visible log file is pathetic for a company like Adobe (not that I would prefer hidden log files).
No, I don't want to use 'Bridge' because I don't want a system scan for listable files in Bridge.

Exciting I find the reaction of Adobe - just not a useful response. Is there maybe an admin in this forum? Maybe someone who could provide us with patches?! Users should go around in circles here until there is an update. What are the connections between file control and the manufacturers of the operating systems? This is not a freeware Program - we rented it for money.
Maybe we wait until version PS 25?. I'm opting out now and will wait for Adobe's kindness, unfortunately I have no other choice.
Thank you for some good tips from members. Beautiful celebration in anticipation of the year 2023.

Beachcolonist
Inspiring
December 31, 2022

See my post "Solved! - Unwanted "gude.log" file creation issue in Photoshop - Solved!"

Beachcolonist
Inspiring
December 31, 2022

 

 

[Abuse removed by moderator. Please follow forum guidelines to be kind and respectful.]

 

 

Jean-Pierre-BRUNEAU
Inspiring
December 31, 2022

Oui je penses comme toi !

RosaPerry
Inspiring
December 31, 2022

@Ged_Traynor 

I had no way of knowing. I've not experienced this until the recent update and that's why I thought it was a re-occurrence of that bug. This has not happened to me in the previous versions and I would know, as it something I always do by double clicking a PSD file if PS is closed. Interesting that this has only happened to me in this v of PS. Something for the engineers to think about. Windows OS, latest build.

I started a new thread since this one is cluttered, but it seems someone merged my new thread with this.

Rosa
Gebruenn
Participating Frequently
December 31, 2022

@Beachcolonist 

Please stop it. Your solution is no solution, but only a workaround. You obviously have no idea about developing applications. This is a bug and has to be fixed.

But thank you for your good willing.

Beachcolonist
Inspiring
December 31, 2022

Are you trying to actually get work done in Photoshop? Of just interesting in commenting on the oddball creation of gude*.log and when Adobe will patch the software?

If you are trying to get work done, just improve your Photoshop use practices by opening files either with Bridge (the best practice) or by right clicking, then "open with Photoshop."

 

No need to thank me! And for the record you can, if you have put a shortcut to notepad.exe in the "send to" folder, right click a *.log file and send to notepad to see in this case it's ... guess what? That's right, a log file.

Ged_Traynor
Community Expert
Community Expert
December 31, 2022

@RosaPerry the issue was reported as been fixed, but the update didn't actually fix it, it's been ongoing since then

Gebruenn
Participating Frequently
December 31, 2022

Thank you. I didn't know that this is a new bug and was already solved.