If you’re utilizing the Chromium-based browsers (Chrome, Edge, Courageous, and many others) on Home windows 10, you must be careful for a mysterious file known as “debug.log”.
It has been extensively reported by customers that Home windows 10 is making a debug.log file on desktop, however our analysis signifies that the file is created by Chromium browsers and this isn’t Microsoft’s fault in any respect.
For context, Chromium is an open-source platform and it dominates the world’s browser market share by powering your favorite browsers, corresponding to Google Chrome, Microsoft Edge, Courageous and Vivaldi.
Chromium open-source challenge generates the supply code utilized by these browsers and a bug in Chromium impacts all browsers utilizing its supply code.
What’s debug.log file on the desktop?
After a latest replace to Edge, Chrome and different Chromium-based browsers, customers observed that Home windows creates “debug.log” file with error “FindFirstFile: The system can’t discover the trail specified” and the file is pinned to the desktop.
“There’s a file known as debug.log that’s being created in a few of my folders. The information have traces of textual content indicating that the system can’t discover the trail specified,” one person famous within the Suggestions Hub.
It’s potential that Chromium builders have added a process that checks if there’s a drawback within the browser. Ideally, this could work with out the creation of the aforementioned file.
Chrome or Edge shouldn’t make a log file, or if there’s a failure of a service, it ought to log extra element about what’s going unsuitable.
This concern was first reported earlier this month, however I’m seeing others reporting the issue very lately.
I checked my gadgets working completely different variations of Home windows 10 with each Edge and Chrome, however I couldn’t find the file in my Desktop, Downloads, or Paperwork folder.
The best way to repair debug.log bug on Home windows 10
Luckily, you may stop Chromium browsers from creating the debug.log file on desktop by deleting a folder known as Crashpad.
To repair the debug.log bug, comply with these steps:
- Open Home windows Run by urgent Win+R.
- Should you use Edge, enter %localappdatapercentMicrosoftEdgeUser DataCrashpad
- Should you use Chrome, enter %localappdatapercentGoogleChromeUser DataCrashpad
- Delete all information and folders contained in the CrashPad folder.
- Restart Home windows.
If the steps labored out accurately, browsers ought to not create the file.