Debug.log File Being Created After Update

[KellyCraven]

I updated to V8.5 from V8.2 and now TextPad is creating a file named debug.log every time I open a file for editing. Method to open the file is to right-click and use the context menu to open in TextPad.

Windows 10, Version 1909, Build 18363.1082
TextPad: 8.5.0 (64-bit Edition)

debug.log contains the below, but rarely it's an empty file:

[1012/133956.342:ERROR:directory_reader_win.cc(43)] FindFirstFile: The system cannot find the path specified. (0x3)
[1012/182849.450:ERROR:directory_reader_win.cc(43)] FindFirstFile: The system cannot find the path specified. (0x3)

[Mike Olds]

Hello Kelly,

First, I deleted the four previous responses as being useless.

I am now 90% sure the solution is to delete Chrome browser. Google this problem and Google comes up. There is apparently a solution not quite as drastic as removing Chrome (fiddle with some settings, delete some files, uninstall and re-install) so you might want to check that out.

I have removed Chrome and have done just about every routine that previously brought up the debug.logs.

The clue? The fact that the debug.log could not be deleted without closing an open file in Chrome.

EDIT: I am now certain that removing Chrome was one solution to this problem. I have had no instances since. But then the next question is why did this happen when upgrading TP? There must be something in the new upgrade that Chrome doesn't like.