Fixed: CHKDSK Failed to Transfer Logged Messages to the Event Log with Status 50

Remain calm if you encounter issues transferring logged messages to the event log with status 50. On this page, you will discover four solutions to address this problem and one method to promptly recover your lost files:

Translate into English

"Failed to transfer logged messages to the Event Log with status 50."

"CHKDSK," short for "check disk," is a command utilized to scan and fix disk errors on a local hard drive or external storage device. Nevertheless, executing CHKDSK may not always proceed smoothly, and you might encounter various error messages, such as "Failed to transfer logged messages to the event log with status 50."

Symptoms refer to the signs or manifestations of a disease, disorder, or medical condition that a person may experience. These can include physical, psychological, or behavioral changes that indicate an issue within the body or mind. Examples of symptoms range from fever, headache, and fatigue to anxiety, depression, or difficulty in concentration. When experiencing symptoms, it is important to consult a healthcare professional for proper diagnosis and treatment.

When attempting to run CHKDSK on your computer, you might encounter a typical error message stating "Failed to transfer logged messages to the event log with status 50" during the hard drive repair process. This issue can occur in various Windows versions, including Windows 10, 8.1, 8, 7, 2008, XP, Vista, or others.

Translation: "CHKDSK failed to transfer logged messages to the event log with status 50"

Reasons refer to the causes or justifications behind a particular action, decision, belief, or phenomenon. They can be logical, emotional, or based on various factors that influence an individual's thought process or behavior. Reasons help individuals explain their choices, support their arguments, or understand the motivations behind certain actions or events.

The "Failed to transfer logged messages to the event log with status 50" error message typically occurs for one of the following three reasons:

• There are corruption or bad sectors (both logical bad sectors and physical bad sectors) in the Windows partition
• Your disk or partition is set to "read-only"
• The disk is physically damaged

Part 1. Recover Data Before Fixing 'Transfer Logged Messages Status 50' Error

If the command "chkdsk c: /r /f /v" fails to fix the corruption on the hard disk and instead displays a warning message stating "transfer logged messages... status 50," you will not be able to access or open the device.

To prevent unintentional data loss and protect your essential files, it's crucial to have a solution in place to recover your files in the event of an unexpected data disaster. In this scenario, the reliable Data Recovery Wizard tool comes in handy.

Note: If your internal hard drive is severely damaged and cannot boot into Windows, download the tool Data Recovery Wizard Pro with Bootable Media to recover your data.

Part 2: How to Resolve "CHKDSK Failed to Transfer Logged Messages Status 50"

Based on the potential causes outlined, here are the corresponding solutions to address the issue "failed to transfer logged messages to the event log with status 50" when running the CHKDSK command: 1. **Insufficient Permissions**: Ensure that you are executing the CHKDSK command with administrative privileges. To do this, right-click on the Command Prompt and choose "Run as administrator." 2. **Event Log Service Not Running**: Check if the Event Log service is running. If not, start it by following these steps: - Press `Win + R` to open the Run dialog. - Type `services.msc` and hit Enter. - Locate the "Windows Event Log" service in the list, right-click on it, and select "Start" or "Restart." 3. **Corrupted Event Log Files**: Sometimes, the event log files might be corrupted. You can try resetting them: - Open Command Prompt as an administrator. - Type `wevtutil el` and press Enter to list all the logs. - For each log listed, clear it using the command: `wevtutil cl ` (replace `` with the actual log name). 4. **Disk Errors**: If the issue persists, it could be due to disk errors. Run CHKDSK with the `/f` and `/r` switches to fix physical issues: - Open Command Prompt as an administrator. - Type `chkdsk /f /r C:` (replace `C:` with the affected drive letter) and press Enter. - Schedule the check for the next boot if the drive is in use. 5. **System File Checker (SFC)**: Run SFC to scan and repair system files: - Open Command Prompt as an administrator. - Type `sfc /scannow` and press Enter. Wait for the process to complete. 6. **DISM Tool**: If SFC fails, use the Deployment Imaging and Servicing Management (DISM) tool: - Open Command Prompt as an administrator. - Run the following commands one by one and wait for each to finish: - `DISM /Online /Cleanup-Image /RestoreHealth` - `sfc /scannow` After trying these solutions, restart your computer and check if the issue has been resolved. If the problem still persists, consider seeking professional assistance or updating your operating system.

Solution 1: Repair Bad Sectors

Since the error message "Failed to transfer logged messages to the event log with status 50" could be caused by corruption or bad sectors in the Windows partition, you can run the command "chkdsk c: /r /f /v" to recover readable data from faulty sectors and fix file system errors.

You might wonder why you can still use the CHKDSK command when an error is reported. Well, you might be aware that the CHKDSK utility can be employed with various parameters for different objectives. If the error message occurs when you utilize parameters other than those meant for checking disk errors, you still have the opportunity to repair bad sectors using the CHKDSK command.

If CHKDSK is unable to fix your disk, it might indicate the presence of physical bad sectors on your partition. In such a scenario, you would require third-party software to prevent these bad sectors from being accessed, thereby enabling the continued use of your hard drive.

Solution 2: Remove Write Protection

If your disk or partition is marked as read-only, the system will not be permitted to transfer logged messages. To proceed with the CHKDSK operation smoothly, you need to remove the read-only attribute from your disk. Doing so will prevent the error message "failed to transfer logged messages to the event log with status 50" from appearing. There are multiple methods to remove the write protection, and the simplest one is:

Step 1. Run "Command Prompt" as an administrator.

Step 2. Type diskpart and click "Yes" when prompted with a notification.

Step 3. Type the following command in sequence:

```javascript $(function() { $('.click_copy_box .click_button').click(function() { var self = $(this); var Url2 = $(this).parent().find('textarea'); Url2.val(Url2.val()); Url2.select(); document.execCommand("Copy"); $(this).html('Copied'); setTimeout(function() { self.html('Click to copy'); Url2.blur(); }, 3000); }) }) ``` This is a JavaScript code snippet using jQuery that enables copy functionality when a button with the class "click_button" inside a ".click_copy_box" div is clicked. It selects the text within the associated textarea, copies it to the clipboard, and then changes the button's text to "Copied" for 3 seconds before reverting back to "Click to copy". The textarea is also blurred after the copying action to remove the selection.

When your disk is write-protected, you might encounter the error "Windows cannot run disk checking on this volume because it is write protected" while attempting to run CHKDSK.

If you don't consider yourself a proficient computer user and are unfamiliar with command lines, don't worry. There are graphical user interface (GUI)-based solutions available to assist you in removing write-protection from your hard drives, USB drives, and even SD cards.

CleanGenius is one of these tools that helps you fix the aforementioned issues on your drives without knowing a thing about command-line.

Here's a simple step-by-step guide on how to utilize this tool to resolve your issues:

Step 1: DOWNLOAD and install the tool CleanGenius (free) on your computer.

Step 2: Run CleanGenius on your PC, select Optimization, and choose the Write Protection mode.

Step 3: Select the device that is write-protected and click on "Disable" to remove the protection.

Solution 3: Run CHKDSK After Booting into Safe Mode

If you're attempting to boot your PC from an installation disk and run CHKDSK, you might encounter the "Failed to transfer logged messages to the event log with status 50" error. This occurs because the log data cannot be written or copied to the installation disk. Fortunately, you can try running CHKDSK after booting into Safe Mode to resolve the issue. Safe Mode boots your computer with only essential drivers and services, restricting Windows operations to basic functionalities. This helps eliminate other factors that might cause the CHKDSK error.

The following steps are performed on a Windows 10 operating system:

Step 1. Disconnect any external peripherals from your computer.

Step 2. Click "Start" and select "Settings" (the gear icon).

Step 3. Navigate to "Update & Security" > "Recovery".

Step 4. Under "Advanced startup", click "Restart now".

Step 5. Your PC will then restart to the "Choose an option" screen. Select "Troubleshoot" > "Advanced options" > "Startup Settings" > "Restart".

Step 6. Your PC will then present you with a list of options. Select "Enable Safe Mode" to boot your computer into Safe Mode.

Step 7. Execute the CHKDSK command based on your requirements.

Failed to transfer logged messages to the event log with status 50 - Boot into Safe Mode

Solution 4: Send the Disk for Repair

If your hard disk is damaged, running CHKDSK might fail with an error message stating "failed to transfer logged messages to the event log with status 50." When your hard drive suffers physical damage, the only option to recover your data would be to send it for professional repair. Manual repair or a manual data recovery service might be able to salvage the disk or the data stored on it.

Bottom line.

While running CHKDSK, you might encounter other error messages, such as "cannot open volume for direct access", "chkdsk is not available for RAW drives", and more. "Failed to transfer logged messages to the event log with status 50" is just one among these issues. Typically, this error arises due to disk errors, including bad sectors, corruption, or file system issues. Develop a habit of using your disk responsibly to minimize damage and regularly back up your files to prevent complete data loss.