Logo

Fix Failed to transfer logged messages ...

One of the most common hardware issues with any PC usually has something to do with the hard drive so if your hard drive experiences some errors, you could end up losing a lot of important information that’s stored in your computer. This is why Windows provided users with the CHKDSK utility which helps in looking for bad sectors on the drive. However, there are times when the CHKDSK utility could also face issues like the following error:

“Failed to transfer logged messages to the log event with status 50.”

According to security experts, this error is most likely due to the hard drive or RAM being in a “Read-only” state. It could also be due to some physical issues with the hard drive. On the other hand, it could be that the system is prevented from creating logs by some drive, service, or malware. To fix this error, you have to check if the hard disk is writable. You could also try to run the CHKDSK utility in Safe Mode or you could also check the physical status of your hard disk or external drive.

Option 1 – Check if the hard disk is writable

Although the CHKDSK utility checks for bad sectors in the hard drive, it also has to create logs of the result. And as states in the error message, the CHKDSK utility is not able to log the logged messages. This kind of error occurs when the log can’t be written to an installation disk. You can find the log in this location, “C:WindowsSystem32LogfilesSrtSrtTrail.txt”. Now you have to check if the drive writable by following these steps:

  • Log in as administrator and right-click on the system drive.
  • Select Properties and then go to the Security tab. Here, check if you are allowed to modify the drive. If not, click on Edit (as an administrator).
  • Now edit the permissions for the SYSTEM and Administrators group. Note that these are the only default settings for these two groups or usernames.
  • Then click on the Apply button save the changes made and exit.

Option 2 – Run the CHKDSK utility in Safe Mode

You could also try to run the CHKDSK utility in Safe Mode as this might solve the error.

  • Boot your computer in Safe Mode.
  • Next, open Command Prompt with admin privileges.
  • Then type and enter this command to execute it: chkdsk c: /f /r
  • Wait until the process is completed and boot your computer normally and then run the CHKDSK utility again and check if the “Failed to transfer logged messages to the log event with status 50” error is now fixed.

Option 3 – Try to check the hard disk or external drive physically

If the first two options didn’t work, you might want to check the physical status of your hard disk or external drive as the problem could root from there. You can try to tighten the wires that connect the hard disk to the motherboard. However, if it doesn’t help, you should seek out assistance from a hardware technician.

Do You Need Help with Your Device?

Our Team of Experts May Help
Troubleshoot.Tech Experts are There for You!
Replace damaged files
Restore performance
Free disk space
Remove Malware
Protects WEB browser
Remove Viruses
Stop PC freezing
GET HELP
Troubleshoot.Tech experts work with all versions of Microsoft Windows including Windows 11, with Android, Mac, and more.

Share this article:

You might also like

Rebuild Search Index in Windows 10
If by any chance your search result in Windows is misleading, missing, or incorrect then it is a high probability that your search index is out of date. To repair this issue follow this guide step by step. Please take note that rebuilding the whole search index can take a long time on some systems depending on the size of the index itself, CPU speed, HD speed, etc. Sometimes it can take even hours on large drives. First, press ⊞ WINDOWS + R to open the run dialog and type in it Control panel to open the control panel. keyboard with windows and r markedrun dialog with control panel typed in Once you are in the control panel, switch your view to large icons and locate Indexing options. Control panel with indexing options selectedInside indexing options, click on advanced. indexing options advanced button markedIn advanced options click on the rebuild and confirm. indexing options rebuild button markedLeave your computer to finish and your searches should be working fine now.
Read More
Fix Shell Infrastructure Host stopped working
The Windows 10 operating system supports the logging in of multiple users at the same time. Aside from that, it also allows administrators to create a Guest Account that has limited rights. However, there are some instances when you could encounter an error when you use the Guest Account. The error may state:
“Shell Infrastructure Host has stopped working. A problem caused the program to stop working correctly. Please close the program”.
This error indicates that the Shell Infrastructure Host or SiHost.exe process that is used for handling graphical elements, has crashed. And to fix this error, there are several options you can check out. You can try to reinstall the Microsoft Redistributable Packages or run a System File Checker scan. In addition, you can also use a new Guest Account or troubleshoot the problem in a Clean Boot State.

Option 1 – Try to install or repair Microsoft Visual C++ Redistributable 2013

A corrupted Microsoft Visual C++ Redistributable package or the absence of it can trigger the “Shell Infrastructure Host has stopped working” error – so if you do not have this package yet, you have to install it but if you already have it, follow the steps below to repair it.
  • Open Control Panel and proceed to Program and Features.
  • Under Programs and Features, look for Microsoft Visual C++ Redistributable package among the list.
  • Then right-click on it and click the Change button.
  • Next, you should see the Repair option – click on it to repair the installation of the Microsoft Visual C++ Redistributable package.
  • The process may take a couple of minutes before it finishes so once it does, you have to restart your PC.
After doing all these steps and you still encounter the problem, you might have to uninstall this package and download it directly from Microsoft’s website. However, if you are using Windows 10, you might not be able to do so since it only supports Windows versions up to Windows 8.1 so just proceed to the next option below.

Option 2 – Try to run a System File Checker scan

  • In the Windows Start Search, type “command prompt” and right-click on Command Prompt from the search results, and then select the “Run as administrator” option.
  • After opening Command Prompt with admin privileges, type the “sfc /scannow” and tap Enter to execute it.
  • Once the scan is finished, restart your computer and see if the Windows Script Host error.

Option 3 – Try using a new Guest Account

You might want to use a new Guest Account as it could help get rid of the error. All you have to do is have your admin delete the old Guest Account and create a new one and see if it helps in fixing the error.

Option 4 – Try troubleshooting the problem in a Clean Boot State

Setting your computer in a Clean Boot State can help you diagnose and later troubleshoot the problems in your computer. During this state, the system will start with a minimal number of drivers and startup programs that help in isolating the problem with the interfering software. To put your computer in a Clean Boot State, follow the given steps below.
  • Log onto your computer as an administrator.
  • Type in MSConfig in the Start Search to open the System Configuration utility.
  • From there, go to the General tab and click “Selective startup”.
  • Clear the “Load Startup items” check box and make sure that the “Load System Services” and “Use Original boot configuration” options are checked.
  • Next, click the Services tab and select the “Hide All Microsoft Services” check box.
  • Click Disable all.
  • Click on Apply/OK and restart your PC. (This will put your PC into a Clean Boot State. And configure Windows to use the usual startup, just simply undo the changes.)
  • From there, start to isolate the problem by checking which one of the programs you installed recently is the root cause of the problem.
Read More
Ventoy software review

There is a lot of software on the market today, but from time to time we discover something extraordinary and unique worth sharing and today we have a threat for you. Ventoy is a tool that will help you with system reinstallations and system maintenance once and for all.

If you are a computer user that has multiple operating systems or you are installing and maintaining different hardware via different OS there is a high chance that you have multiple USB sticks with different operating systems on them.

Now the problem with that is that there are probably too many unlabeled sticks around or you do not have enough so you keep making system USBs depending on which one you might need.

ventoy

Ventoy solves all of these problems by letting you have as many operating systems images as your USB has capacity. The only thing you need to do is get the software here: https://www.ventoy.net/en/index.html and make a USB with it, then you can freely just copy your ISO images onto the USB and once it is inserted into the computer you will be given a menu to choose which one you would like to start with, simple as that.

Features

  • 100% open source (license)
  • Very simple to use (Get started)
  • Fast (limited only by the speed of copying the iso file)
  • Can be installed in USB/Local Disk/SSD/NVMe/SD Card
  • Directly boot from ISO/WIM/IMG/VHD(x)/EFI files, no extraction needed
  • Support to browse and boot ISO/WIM/IMG/VHD(x)/EFI files in local disk Notes
  • No need to be continuous in disk for ISO/WIM/IMG/VHD(x)/EFI files
  • Both MBR and GPT partition styles are supported
  • x86 Legacy BIOS, IA32 UEFI, x86_64 UEFI, ARM64 UEFI, MIPS64EL UEFI supported
  • IA32/x86_64 UEFI Secure Boot supported Notes
  • Linux Persistence supported Notes
  • Windows auto installation supported Notes
  • Linux auto installation supported Notes
  • Variables Expansion supported for Windows/Linux auto-installation script Notes
  • FAT32/exFAT/NTFS/UDF/XFS/Ext2(3)(4) supported for main partition
  • ISO files larger than 4GB supported
  • Menu alias, Menu tip message supported
  • Password protect supported
  • Native boot menu style for Legacy & UEFI
  • Most types of OS supported, 1000+ iso files tested
  • Linux vDisk(vhd/vdi/raw...) boot solution Notes
  • Not only boot but also complete the installation process
  • Menu dynamically switchable between ListView and TreeView mode Notes
  • "Ventoy Compatible" concept
  • Plugin Framework and GUI plugin configurator
  • Injection of files into runtime environment
  • Boot configuration file dynamically replacement
  • Highly customizable theme and menu style
  • USB drive write-protected support
  • USB normal use unaffected
  • Data nondestructive during a version upgrade
  • No need to update Ventoy when a new distro is released
Read More
How to Fix Remote Desktop Black Screen issues
According to some reports, using RDP or Remote Desktop Protocol on recent versions of Windows 10 results in a black screen. One encounters this issue is when using the Remote Desktop Connection feature on Windows 10. The real causes of this black screen are either the display drivers or some misconfiguration with the Remote Desktop Connection utility. In most cases, the Remote Desktop in Windows 10 will display a black screen and then disconnects afterward. To fix this kind of issue on your Remote Desktop, there are two suggestions you need to check out. First, you can try to disable the persistent bitmap caching, and then you can also try to update your display driver. Follow the given options below for more troubleshooting instructions.

Option 1 – Try to disable Persistent Bitmap caching

The first thing you can do to resolve the black screen issue with the remote desktop is to disable the persistent bitmap caching. All you have to do is follow these steps:
  • First, open the Remote Desktop Connection client.
  • Next, click on the Show Options button to configure the Remote Desktop Connection.
  • After that, go to the Experience tab and uncheck the Persistent bitmap caching option.
  • Once done, you should now be able to connect to the remote computer without the black screen.

Option 2 – Try to update or rollback the Graphics driver

You can try to update your Graphics card driver using the Device Manager in your computer to resolve the blank dialog boxes problem or you can also go directly to the website of your graphics card manufacturers like NVIDIA, Intel, or AMD and go to the section called Drivers then check if there’s a new available update – if there is, download and install it. To update your Graphics driver via Device Manager, refer to these steps:
  • First, boot your computer into Safe Mode.
  • After that, tap the Win + R keys to launch Run.
  • Type in devmgmt.msc into the box and tap Enter or click OK to open the Device Manager.
  • After that, a list of device drivers will be displayed. From there, look for the Display Adapters and click on them.
  • After that, right-click on each entry under the Display Adapters and select the “Uninstall Device” option from the menu.
  • Now restart your computer.
  • After restarting your computer, go to the Settings app and Check for Updates in the Windows Update section.
Note: If updating the Graphics driver didn’t fix the problem, you can also try to roll back to its previous version and see if that helps or you could also try to roll back, update or reinstall the Network Adapter drivers.

Option 3 – Try performing a System Restore

You might also want to perform a System Restore that might help you in fixing the error. You can do this option either by booting into Safe Mode or in System Restore. If you are already in the Advanced Startup Options, just directly select System Restore and proceed with the next steps. And if you have just booted your PC into Safe Mode, refer to the steps below.
  • Tap the Win + R keys to open the Run dialog box.
  • After that, type in “sysdm.cpl” in the field and tap Enter.
  • Next, go to the System Protection tab then click the System Restore button. This will open a new window where you have to select your preferred System Restore point.
  • After that, follow the on-screen instructions to finish the process and then restart your computer and check if the problem is fixed or not.
Read More
STOP 0x00000050 - An Easy Fix Guide

Stop 0x00000050 is an error code that is popularly known as the Blue Screen of Death (BSoD) error. This error occurs when Windows crashes on your system. Stop 0x00000050 error is displayed in a blue screen which is why it is called the BSoD error.

The error message appears in the following form:

Stop 0X00000050 (parameter1, 0, parameter3, parameter4)

PAGE_FAULT_IN_NONPAGED_AREA”

However, the parameters within the Stop 0x0000005 error message sometimes vary depending on your PC configuration.

Solution

Restoro box imageError Causes

The most common causes of the Stop 0x0000005 error are:

  • Hardware malfunctioning
  • Overheating of the components
  • Installation of a faulty device driver
  • Incompatible DLL files
  • Corrupt Registry
  • Spyware and Virus Infection

Whatever the cause may be, the Stop 0x00000050 error message is alarming and should be fixed at the earliest as it indicates major system stability problems that can often lead to data loss and system corruption.

Further Information and Manual Repair

To fix and repair the Stop 0x0000005 error you don’t always have to hire an IT professional. In fact, fixing this error is quite easy and you can do it yourself regardless of whether you have a good know-how of computers or not.

So, let’s get started! Here are some the easy DIY solutions to fix the Stop 0x0000005 error:

Sometimes this error may occur due to a temporary issue like overheating of the computer components. When this happens all you need to do is switch off the computer and allow the components to cool down. Try starting up your computer after a couple of hours. If the blue screen of death does not occur again, then this means there is nothing to worry about and the problem is resolved.

However, if the error appears again on your screen, then you need to try something else to solve and fix this error on your PC. If the cause of the error is a faulty device driver, then it is advisable to disable and remove it. Try updating the latest version of the faulty device driver. Using updated software helps ensure your PC keeps running smoothly.

If the cause of the Stop 0x0000005 error code is your system's exposure to viruses and spyware, then you must immediately download a powerful antivirus program. After you download it, scan for viruses on your system. Once the scanning is complete, you will see a scan report showing viruses on your PC. Delete all of them and click on repair.

Furthermore, you can also add more RAM to prevent and fix the Stop 0x0000005 error message on your computer. This solution is suitable when you try to run a program on your PC and you get this error message.

Read More
Something went wrong, We couldn’t start
There are instances when you might encounter an error that says, “Something went wrong, We couldn’t start your program” when you open any Office program. This could be due to an issue with the Office file and any Office app you open throws the same error message. This applies to Office 2019/2016, Office 365 Home, Office for Business as well as Business editions. In this post, you will be guided in what you can do to resolve this error. There are several potential fixes for this error, you might only have to restart your computer or you may have to repair Office from Apps and Features or you could also uninstall and install it back again. For more details, follow each one of the provided options below.

Option 1 – Restart your computer

You might be unable to launch any Office app due to some background process that got stuck or there might be some glitch in the system. Thus, the first thing you can do to resolve the error is simply restarting your computer. Once you’ve restarted your computer, open the Office app again or you could also try to sign in back with your Microsoft account that’s connected to Office. If you’re not quite sure which account you were using, you can follow these steps:
  • Open any Office app.
  • Then click on File and look for your name located in the top-right portion.
  • Now click on it. This will display the email or Microsoft account that’s related to Office.

Option 2 – Try repairing Office from Apps and Features

Since Windows 10 offers some repair features that could replace some of the core files with the original files, you can take advantage of such a feature to fix the “Something went wrong, We couldn’t start your program” error when opening any Office app.
  • Open Windows settings and click the Apps and Features option.
  • Next, scroll down until you see the Microsoft Office installation option. Select it and click on Modify.
  • This will open a window and from there, select Quick Repair or Online Repair and click on the Repair button.
Note: When you choose to repair, you might be given two options which depend on how Microsoft Office was installed. For instance, it was installed via Web Installer or Offline Installer (MSI-based). In Web Installer, select Online Repair > Repair when you’re prompted on how you would like to repair Office. While in MSI-based, you have to select Repair under “Change your installation” and then click on Continue. The repair process makes sure that the app data remains untouched.

Option 3 – Try to uninstall and reinstall Office

If neither of the two given options above worked, then you might want to uninstall Office and reinstall it. All you have to do is download the Microsoft Office Uninstall tool from the official site of Microsoft and run it. This will remove any incomplete Office installation as well as unwanted files. It will also get rid of all the Office apps and settings on your computer.
Read More
Android security: 9 apps stealing your data!
Due to the latest android malware security analyst, there are alarmingly 5.8 million downloads of applications that will steal your Facebook data, your Facebook login credentials! Russian anti-malware company Dr.Web has found Trojan apps that steal your Facebook login credentials by tricking users into entering their private information in order to eliminate in-app ads. All of the applications have been removed from the play store and cannot be installed anymore but please do check your phone in order to remove them from your phone as well.

List of malware applications:

If by any chance you have any application from this list, consider uninstalling it from your phone for security reasons.
  • PIP Photo
  • Processing Photo
  • Rubbish Cleaner
  • Inwell Fitness
  • Horoscope Daily
  • App Lock Keep
  • Lockit Master
  • Horoscope Pi
  • App Lock Manager
During the investigation, Dr.Web analysts found an additional Trojan app that had previously made its way onto the Google Play Store. Image editing software app EditorPhotoPip had already been removed but could be downloaded through aggregator websites.
Read More
Fix Windows Update Error 0x80004005
As you know, Microsoft is consistent in pushing updates to its supported versions of the Windows operating systems in order to make it better and defend it from different kinds of vulnerabilities. And pushing billions of active Windows computers every now and then is really not an easy thing to do since it calls for a complex Windows Update delivery module. These complexities often give rise to various errors like the Windows Update error code 0x80004005. When you encounter this kind of Windows Update error, you will see the following error message on your screen:
“There were problems installing some updates, but we’ll try again later. If you keep seeing this and want to search the web or contact support for information, this may help 0x80004005.”
This kind of Windows Update error occurs due to an issue while either installing or downloading an update. There are several ways you can fix the problem. You can try to replace the dpcdll.dll file, reset the Windows Update-related services, run the Windows Update troubleshooter or manually install the Windows Updates. For more details, check out the options given below.

Option 1 – Try to replace the DLL file with a trusted source

The first thing you can do is to replace the dpcdll.dll file with a trusted source.
  • First, you need to get the new dpcdll.dll file from another computer with preferably the same file version number as your computer.
  • After that, you need to boot your PC into Safe Mode and navigate to the paths listed below and then replace the file using a USB drive or other external storage devices.
    • For x86: This PC > C:/Windows/System32
    • For x64: This PC > C:/Windows/SysWOW64
  • Next, type “cmd” in the Cortana search box and right-click on Command Prompt, and select “Run as administrator” to open it with administrator privileges.
  • Now type the “regsvr32 dpcdll.dll” command and hit Enter.
  • Restart your PC and check if the error is now fixed.

Option 2 – Try to reset the Windows Update components

If by any chance that the third option didn’t work, you can also try resetting the Windows Update components as it could also help you resolve the Windows Update error. How? Refer to the following steps:
  • Open Command Prompt with admin privileges.
  • After that, type each one of the following commands and hit Enter after you key in one after the other.
    • net stop wuauserv
    • net stop cryptsvc
    • net stop bits
    • net stop msiserver
Note: The commands you entered will stop the Windows Update components such as Windows Update service, Cryptographic services, BITS and MSI Installer.
  • After disabling WU components, you need to rename both the SoftwareDistribution and Catroot2 folders. To do that, type each one of the following commands below and don’t forget to hit Enter after you type one command after the other.
    • ren C:WindowsSoftwareDistribution SoftwareDistribution.old
    • ren C:WindowsSystem32catroot2 Catroot2.old
  • Next, restart the services you’ve stopped by entering another series of commands. Don’t forget to hit Enter after you key in one command after the other.
    • net start wuauserv
    • net start cryptsvc
    • net start bits
    • net start msiserver
  • Close Command Prompt and reboot your PC.

Option 3 – Run the Windows Update Troubleshooter

You might also want to run the Windows Update Troubleshooter as it could also help in fixing Windows Update error 0x80004005. To run it, go to Settings and then select Troubleshoot from the options. From there, click on Windows Update and then click the “Run the troubleshooter” button. After that, follow the next on-screen instructions and you should be good to go.

Option 4 – Try downloading and installing the Windows Updates manually

Windows Update Error 0x80004005 might be due to a Windows Update that has failed. So if it is not a feature update and only a cumulative update, you can download the Windows Update and install it manually. But first, you need to find out which update has failed, and to do so, refer to the following steps:
  • Go to Settings and from there go to Update and Security > View Update History.
  • Next, check which particular update has failed. Note that Updates that have failed to install will be displayed under the Status column which has a label of “Failed”.
  • After that, go to the Microsoft Download Center and look for that update using its KB number and once you find it, download and then install it manually.
Note: You can also use the Microsoft Update Catalog, a service from Microsoft that provides a list of software updates that can be distributed over a corporate network. With the help of this service, it can be easier for you to find Microsoft software updates, drivers as well as fixes.
Read More
Fix VSS Error Code 0x8004231f in Windows 10
VSSControl: 2147467259 Backup jobs failed. Cannot create a shadow copy of the volumes containing the writer’s data. VSS asynchronous operation is not completed. Code: [0x8004231f]
This message pops up when you are creating a snapshot system restore, usually, the issue is tied with insufficient space or service stopping. We will go into detail about how to fix both so you can finish the operation without any issue.
  1. Check Volume Shadow Copy Services

    Easier and faster fix than the next one. Launch Services from the Start Menu, look for Volume Shadow Copy, double-click on it, and check the Service status. If it is stopped, click on the Start button. If it’s running, restart it by clicking Stop > Start.
  2. Increase Shadow Storage Space

    If the first fix didn’t resolve the issue then you need to increase Shadow Storage Space. Launch Command Prompt as an administrator. Now, type the following command to check your Shadow Storage Space. vssadmin list shadowstorage Now, type the following command to allocate more storage (you can change 10GB with the amount of space you want to allocate) vssadmin resize shadowstorage /For=C: /On=C: /MaxSize=10GB
Read More
Fixing “The .NET Framework 4.7 is not supported on this operating system” Error in Windows 10
In case you don’t know, the .Net Framework is a programming infrastructure introduced by Microsoft. You will need it to run on lots of services and applications. Note that most of the applications that require the .Net Framework are packed with their installation files which is why it will be installed automatically on your computer when you install an application. However, there are instances when you’ll get an error message saying, “The .NET Framework 4.7 is not supported on this operating system” while trying to install the .NET Framework as a standalone service. The very reason why this error message appears is stated in the error message itself. Although the .Net Framework is supported on Windows 10, it is not actually compatible with some other Windows 10 versions. So it is most likely that you are seeing this error message because the .Net Framework in your computer is not compatible with the Windows 10 version you are running. Since that’s the case, you need to update Windows 10 to fix the problem. Updating your Windows 10 computer is the only solution you can try to fix this problem. Thus, it is advised that you check for Windows Updates even if you are now using the latest version of Windows 10. And since the issue is caused by an incompatible operating system version, once you install the exact version of Windows 10 required by the .Net Framework, the problem will be fixed. Simply follow the steps given below to do so.
  • Step 1: Tap the Win + R keys to open the Run dialog box.
  • Step 2: After that, type in “winver” in the field and tap Enter.
  • Step 3: Next, your Windows 10 version should be given in the new window that appears. Take note that the number after the Version which is in the second line is your version number of Windows 10. And that the number must be 1507 or 1709. The first two digits in these numbers are the year while the second two represent the month when the update was released. So if you are running a 1709 version, this means that the Windows 10 version you are using was released in September 2017.
  • Step 4: The next thing you have to do is to make sure that you have the Windows 10 version that’s compatible with the .Net Framework. To verify, you need to click here and click on the System Requirements.
After opening the link, take a look at the Supported Operating System section where it says, “Windows 10 Anniversary Update” and “Windows 10 Creators Update”. Since there are users who are not familiar with the version numbers related to both the Anniversary and Creators updates, refer to the list given below.
  • November Update (1511)
  • Anniversary Update (14393)
  • Creators Update (1703)
  • Fall Creators Update (1709)
  • Spring Creators Update (1803)
As you can see, the Creators Update has version 1703 while the Anniversary Update has version number 14393 so if you are using a version lower than the 14393 version then it’s no wonder you aren’t able to install the .Net Framework 4.7 on your Windows 10 PC. Now all that’s left to do is to update your Windows 10 version and make sure that you will be updating it to the latest version available and then try installing the .Net Framework again.
Read More
1 2 3 171
Logo
Copyright © 2023, ErrorTools. All Rights Reserved
Trademark: Microsoft Windows logos are registered trademarks of Microsoft. Disclaimer: ErrorTools.com is not affiliated with Microsoft, nor claims direct affiliation.
The information on this page is provided for information purposes only.
DMCA.com Protection Status