[ad_1]
Google Chrome and other Chromium-based browsers have started dropping a mysterious file called “debug.log” on Windows 10 users’ desktops.
Although it has been widely reported by users who have discovered the file that Windows 10 created, new research from Latest Windows has revealed that Chromium browsers and not Microsoft are responsible.
The open source Chromium platform powers many of today’s most popular web browsers, including Chrome, Brave, Opera, Vivaldi, and Edge. As the source code created by the open source project is used by all of these browsers, a bug in Chromium will affect all of them, which seems to be the case in this case.
Mysterious debug file
After a recent update to Microsoft Edge, Google Chrome, and other Chromium-based browsers earlier this month, users noticed that a file called “debug.log” started to appear on their desktops along with an error message that It said: “FindFirstFile: The System can’t find the specified path.”
While the file itself appears to be harmless, manually removing it from a user’s desktop is ineffective as the file is recreated upon deletion.
Fortunately, however, there is a way that users can prevent Chromium browsers from creating the debug.log file on their desktops.
To fix the debug.log file error, users must first open Windows Run by pressing Win + R or by typing “Run” in the Windows 10 start menu. From there, you will need to enter% localappdata% Microsoft Edge User Data Crashpad if you are running Microsoft Edge or% localappdata% Google Chrome User Data Crashpad if you are running Chrome to locate a folder named Crashpad.
Once you have found the folder, you will need to delete all the files and folders it contains before restarting your computer. This will fix the problem and prevent your browser from leaving a debug.log file on your desktop.
Through Windows Latest
