Uneraser™
Restore any deleted or corrupted file from NTFS, FAT32/exFAT/FAT, APFS, etc.

Pew Pew madafakas!

Restore any deleted or corrupted file from NTFS, FAT32/exFAT/FAT, APFS, etc.
Last updated: Mar 08, 2022

Windows Issue: Failed to Transfer Logged Messages with Status 50

Here you will find out:

  • about failed to transfer logged messages with status 50 issue
  • how to fix this error
  • how DiskInternals can help you

Are you ready? Let's read!

About the “failed to transfer logged messages with status 50” error

If you have received this message, then you used the chkdsk utility to check the disk.

At the risk of upsetting you, this is a very grave situation, since you have very few chances to save the hard drive; but they still exist. It must be resolved with extreme caution and thrift.

Reasons behind the issue

So, why do you see the error “failed to transfer logging messages to the event log”?

The best scenario is if the problem is the disk is in reader mode. In this case, chkdsk is unable to verify the drive.

A less positive outcome of events is if chkdsk was opened from the boot disk. Then a conflict may also occur due to reader mode.

In all other cases, there is little good to say, since almost always the message “failed to transfer event log with status 50” means an almost dead disk with many bad sectors and a damaged file system.

And even worse, this means there is mechanical damage to the hard drive. This is often due to improper handling of the computer.

Method 1. If the hard drive has read-only attributes

As mentioned above, read mode can be the cause of the error. This can be easily fixed using the command line.

You only need to specify a few commands and the protection will be removed, after which you can freely use chkdsk. So, run the diskpart and use these commands:

list volume — then press Enter.

select volume Е (E being a drive letter) — then press Enter.

attributes disk clear readonly — then press Enter.

Clear read only attributes.

After these three commands, restart your computer and proceed as before.

Method 2. Use chkdsk for the “failed to transfer logged messages status 50” issue

Chkdsk can damage the data that can be recovered (most likely it will do so by chopping them into small fragments - up to 512Kb).

Therefore, before you run it, start DiskInternals Uneraser and restore the data.

This is the gold standard for working with the chkdsk utility. DiskInternals Uneraser will quickly make a copy of your data in all formats. At the same time, the program will not bother with recovery limits; this is very useful for recovering hard drives. Scanning is high quality, so a deep search allows you to find even the most outdated files. The recovery wizard will give you the opportunity to view all found data for free, and only after that will you offer to save them.

In addition, you will not even notice how the files are restored, because this process is completely automatic.

As for export, this is already a paid service, but for a little money you will get back your entire hard drive; it's worth it.

Method 3. Last resort

If the “chkdsk status 50” problem is still bothering you, you can reinstall Windows.

All the information from the hard drive has already been saved elsewhere using DiskInternals Uneraser. Now you just have to start the installation disk and reinstall the OS.

Note: if your data was initially available, then you can make a copy of it in safe mode.

In any case, there is a way out in this situation.

Related articles

FREE DOWNLOADVer 8.19, WinBUY NOWFrom $39.95

Please rate this article.
46 reviews