Failed to transfer logged messages to the log event with status 50

One of the most common hardware problems with any computer is usually with the hard drive. If the hard drive goes bad, you could lose a lot of important information stored on your system. Thus, Windows has provided users with the CHKDSK utility which could help in finding out bad sectors on the drive in advance. However, at times while using the CHKDSK utility, you might receive the following – Failed to transfer logged messages to the log event with status 50.

Failed to transfer logged messages to the log event with status 50

Failed to transfer logged messages to the log event with status 50

The possible causes behind this issue could be as follows:

  1. The hard drive or RAM is in a Read-only state.
  2. Problems with the physical hard drive.
  3. Some driver/service/malware could be preventing the system from creating logs.

If you face this issue, you can try the following methods to fix the issue:

  1. Verify if the hard disk is writable
  2. Try running CHKDSK in Safe Mode
  3. Check the hard disk/external drive physically.

1] Verify if the hard disk is writable.

The CHKDSK utility check for bad sectors in the hard drive; however, it also needs to create logs of the result. The error in the discussion is directly linked to the inability of the of the CHKDSK utility to log the logged messages. This error usually occurs when because the log cannot be written to an installation disk. The log is usually found here:

C:\Windows\System32\Logfiles\Srt\SrtTrail.txt.

Thus, verify if the drive is writable.

Log in as Administrator and right-click on the system drive and select Properties. Go to the Security tab and check if you are allowed to Modify the drive.

If not, click on Edit (as an administrator) and edit the permissions for SYSTEM and Administrators Group as shown above in the image. These are the default settings for these two groups or usernames only.

Click Apply and exit.

2] Try running CHKDSK in Safe Mode

Running the CHKDSK command after booting into the system in Safe Mode could be helpful in resolving the problem. Basically, in Safe Mode, the startup programs, add-ons, etc. settings, do not run. Once in Safe Mode use the command prompt to run the following chkdsk command:

chkdsk c: /f /r

Where ‘c’ is the Drive letter.

3] Check the hard disk/external drive physically

There’s not much we could do to fix the error if the above two solutions failed. You could tighten the wires connecting the hard disk to the motherboard. If it doesn’t help either, you might need the help of a hardware technician.

Hope something helps!

Posted by on , in Category Windows with Tags
Anand Khanse is the Admin of TheWindowsClub.com, a 10-year Microsoft MVP Awardee in Windows (2006-16) & a Windows Insider MVP. Please read the entire post & the comments first, create a System Restore Point before making any changes to your system & be careful about any 3rd-party offers while installing freeware.

Leave a Reply

Your email address will not be published. Required fields are marked *


2 + 1 =