What is Brother Printer Debug Logs?

Read more
by Brother

Overview

Brother Printer Debug Logs is published by Brother. You can find out more about Brother Printer Debug Logs at its official website or at Brother's website.


How do I clean Brother Printer Debug Logs?

Brother Printer Debug Logs may store excess, temporary data on your computer that can take up valuable space. It may also store private data such as passwords or browsing history in the registry or on the file system. The easiest way to erase this data is by downloading AppCleaner, it is 100% free and about 1MB in size. A portable version is also available.

Clean Brother Printer Debug Logs
with AppCleaner

If you want to clean Brother Printer Debug Logs manually, you can follow the steps outlined below. There are three locations in the file system where Brother Printer Debug Logs stores data that can be cleaned.

Files

To clean your file system from files stored by Brother Printer Debug Logs and to gain free disk space, examine the following file system locations. First of all, open a command prompt window:

  • Hit the Windows key , usually located in the lower left of your keyboard between the Ctrl and Alt keys.
  • Windows XP/Vista/7: Click Run...
  • Type cmd
  • Hit Enter

Now list all the files stored by Brother Printer Debug Logs that can be cleaned:

  1. Type dir %ALLUSERSPROFILE%\Brother\BrLog\*.log
    • Windows XP: Type dir %ALLUSERSPROFILE%\Application Data\Brother\BrLog\*.log
  2. Type dir /s %ProgramFiles%\Brother\*.tmp
    • On 64-Bit also: Type dir /s %ProgramFiles(x86)%\Brother\*.tmp
  3. Type dir %LOCALAPPDATA%\VirtualStore\Program Files*
    • Windows XP: Type dir %USERPROFILE%\Local Settings\Application Data\VirtualStore\Program Files*
  4. For all the folders that were listed in the previous step:
    Type dir /s {folder}\Brother\*.tmp where {folder} is one of the folders listed in the previous step.

Once you have identified the files stored by Brother Printer Debug Logs that you want to clean, delete them using the del command or Windows Explorer.

0 Comments