After investigating this particular issue, it turns out that there are actually several different underlying causes that might directly or indirectly cause this problem. Here’s a list of culprits you should be aware of: Now that we have gone over every potential reason why you might deal with this particular issue, let’s go over a series of fixes that other affected users have successfully used to get to the bottom of this issue.
1. Disable BitLocker
The most common cause of this kind of event fault occurring in Event Viewer at each startup is Bitlocker. A number of the impacted users who have reported the same type of behavior have confirmed that the issue was fixed when they really turned off this feature on their machine. The BitLocker Drive Encryption menu’s encryption can be turned off by going to the System and Security tab using the traditional Control Panel interface. This method is relatively simple to do, but depending on your OEM, you might find that if you disable and enable the secure boot option in your BIOS or UEFI settings, the encryption feature will re-enable. The automatic BitLocker Encryption can be turned off using the Control Panel by following the steps listed below: Note: The instructions below will work for both Windows 10 and Windows 11: If the issue is still not fixed, move down to the next method below.
2. Use System Restore
It turns out that this kind of Event Viewer report can be caused by a number of different drivers and programs. Most likely, this behavior could be brought on by installing a drive management app or updating the SSD firmware. The simplest approach to resolve this particular situation is to use System Restore to return your PC to a condition in which this problem was not occurring because there are numerous underlying factors that could cause it. To correct serious issues, you can use this utility to restore your complete Windows installation to a stable state where the issue never happened. However, in order to utilize this fix, your operating system must have previously taken a snapshot that may be used to restore the Windows installation to an earlier time. To preserve System Restore Snapshots frequently, Windows should be configured to do so if you haven’t modified the default setting (after every installed Windows update). Important: Before performing this method, be aware that it will essentially undo any changes done after the snapshot was first created. Any user preferences, game downloads, or program installations will have been erased after the snapshot was taken. If you decide to restore your system, use the steps below to see how to do it: If your machine continues to produce fresh instances of Event ID Error 24687, proceed to the next technique below.
3. Deploy SFC and DISM scans
If you’ve come this far without finding a fix, it’s likely that you’re dealing with some sort of system file corruption that keeps causing fresh occurrences of the Event ID Error 24687 at system startup. The next step should be to launch SFC (System File Checker) and DISM (Deployment Image Servicing and Management), two built-in programs that can address the most common causes of system file corruption. Despite the fact that SFC and DISM are roughly comparable, I suggest running both of them fast following one another to improve your chances of resolving the corruption issue. It should be noted that while SFC collects healthy system files from a local location, DISM retrieves files from Windows Update in order to replace faulty counterparts. Running an SFC scan from an elevated CMD prompt can be used to check for system file corruption. Even if the tool appears to have frozen, it is advisable not to interrupt this process midway (or prematurely quit the CMD window). You’ll eventually get the success notification after the operation is finished. Once the SFC scan is complete, restart your computer. Once the subsequent startup has been completed, run a DISM scan. Note: Before starting this process, make sure your Internet connection is strong. Restart your computer after properly executing the DISM command to see if the problem has been fixed. If the Event ID Error 24687 is still visible in Event Viewer after running both of these scans, go to the next potential repair below if the issue is still not resolved.
4. Deploy a CHKDSK scan
Many people who have experienced this issue claim that it can also occur if the HDD or SSD that is now housing your OS installation starts to fail. By running a CHKDSK scan to swap out faulty storage sectors with unused ones, you can confirm this scenario and extend the lifespan of your storage hardware (for a few more months). If you’re still using a standard HDD, the scenario in which portions of the storage sectors used to keep system files are beginning to degrade is what would result in these persistent Event Viewer errors. In this case, running a Check Disk Scan to replace defective sectors with healthy ones will help you extend the life of your HDD. Try launching a CHKDSK scan from an elevated CMD prompt to rule out this possibility. Note: Thankfully, Windows’ integrated CHKDSK program can check for faults and corruptions as well as fix any logical errors and damaged data that may have been left behind by a forceful deletion attempt. Open CHKDSK in an elevated CMD window to give it the rights it needs to fix damaged files. No matter which version of Windows you’re running, the instructions should work. Restart your computer when the CHKDSK scan is finished to check if the Event ID Error 24687 has been resolved. Try the following technique if the problem persists.
5. Perform a clean install or repair install
If none of the aforementioned techniques have helped you, your only remaining option is to entirely replace all of the impacted system file dependencies with healthy replacements. At this point, your only choices are to perform a clean install or a repair install (in-place upgrade). If you encounter issues, we strongly advise selecting an in-place update (repair installation) if you have a choice: • Repair install (in-place upgrade) – Only the system files will be changed during a repair install (while keeping your personal files, user preferences apps & games). • Clean install – This choice might be the best if only a small number of kernel processes are impacted, but it has the disadvantage of wiping out all user data from the OS disk. Nevertheless, you should be aware that if you do this, all of your personal data will be erased.
How to Fix Event 1000 Application Error on Windows 10How to Fix “Windows Kernel event ID 41 error"How To Fix Event ID 7031 or 7034 Error When The User Logs Off Windows 10Fix: Event ID 455 ESENT Error in Windows 10 1903
