Some users installing or upgrading to Windows 10 experienced the theKMODE_EXCEPTION_NOT_HANDLED Blue Screen of Death (or commonly known as BSOD) error. This error can be due to different types of things, ranging from software to driver issues. When you experience this BSOD error while trying to install Windows 10, it will prompt you to restart your computer every single time you experience it. In most cases, you will also not be able to proceed with the Windows 10 set-up.
Error CausesThe “KMODE_EXCEPTION_NOT_HANDLED” error is normally caused by:
You won’t be able to successfully upgrade or set up Windows 10 if you continue to encounter this BSOD error. Note that this error will always prompt your computer to restart every time it happens, preventing you from completing the Windows 10 set-up.
If you’re not tech-savvy or not capable of debugging this issue, it’s highly advisable to proceed with the basic troubleshooting techniques available in this link.
After troubleshooting, below you’ll find a few solutions to rectify the issue.
Two common causes of the KMODE_EXCEPTION_NOT_HANDLED issue are hardware incompatibility and faulty device driver or system service.
If you experience this error, check first if any of your newly installed hardware is compatible with Windows 10. You can find the required hardware for Windows 10 from this link.
If all your hardware is compatible with Windows 10, you might need to check the device driver or system service. Review the bug check message. If any of the drivers you have is listed in the message, either disable or uninstall them before upgrading or setting up Windows 10.
You might also find it useful to check the System Log available in the Event Viewer for other error messages that can help you figure out the driver or device that’s causing the error. Running hardware diagnostics can also be useful.
If you’re upgrading Windows 10 from Windows 7 or Windows 8.1, you might need to disable or uninstall the software first.
First, try uninstalling your Antivirus utility before starting the upgrade. Restart a few times before starting the Windows 10 installation.
If you’re upgrading using the Windows 10 update, make sure that you disconnect from your Wi-Fi or Internet LAN (Ethernet) connection as soon as the download reaches 100% before attempting to start the set-up.
Other users also reported that the cause of the KMODE_EXCEPTION_NOT_HANDLED issue is BitDefender. If this is what happened in your case, it will show in the error message such as KMODE_EXCEPTION_NOT_HANDLED (bdselfpr.sys). Users reported that a common solution for this is renaming the file. In the case of BitDefender, try renaming it to bdselfpr.s__. However, make sure to do this cautiously. Sometimes, renaming a file will even do more damage than good.
If you’re connected to any general USB devices (such a smart card reader), disable it. If your computer is connected to other external devices, disconnect all of them. Examples of this include gaming controllers, printers, external hard disk, USB keys, and other non-essential devices).
Other troubleshooting steps include:
If you still experience the error after doing the methods above, you might want to try a powerful and trusted automated tool to fix the job.

Choosing default browser in settingsSafeSearch is an ad-supported, cross web browser plugin for Internet Explorer and Firefox/Chrome. The browser extension will modify the default or custom settings of the browser including the home page, search settings, and in some cases will modify Internet Explorer’s load time threshold, place a lock file within Firefox to prevent changing settings as well as disable the browser’s Content Security Policy in order to allow for cross-site scripting of the plugin. For these reasons, it has been classified as a browser hijacker.
From the publisher: SafeSearch created by AVSoftware is the unique search engine that filters malicious sites or sites with bad reputations. Every website is weighted on several critical factors – vendor reliability, child safety, privacy issues, user opinions, and ratings.
SafeSearch has been found to be bundled with 3rd party software and malware and therefore is not recommended to keep on your computer.
Error CausesIf you have a Runtime Error 339 issue on your computer, here is a great way how you can fix it right away:
Error CausesError Code 0x80004002 is a Windows-based error code that affects Windows 10 and previous operating systems, including Windows XP, Vista, Windows 7, and Windows 8. In most instances, the message box that shows Error Code 0x80004002 pops up as you attempt to install new software or programs on your machine.
Common symptoms include:
There are a number of different solutions that you can use to attempt to resolve Error Code 0x80004002. Because there are multiple causes to the issue, some of the methods used to successfully address the problems at hand are fairly simple, while others require advanced knowledge or abilities to complete. If the methods below are not successful in the resolution of the issue or if you aren’t confident in your skills to implement these methods, contact a qualified Windows repair technician to assist you. Once this error message is not rectified, you could be exposing your computer to other error messages, including error code 0x80240020.

There are many different issues that can contribute to the appearance of Error Code 0x80004002. The most common causes for this particular error message include:
Due to the number of causes that can contribute to Error Code 0x80004002, there are a number of methods that you can use to attempt to resolve the issues behind the error. While some of these methods are fairly easy to implement, others may require you to use programs like registry cleaners and driver installation wizards, so if you are not comfortable using these kinds of software, contact a certified Windows repair technician to assist you.
Here are the top ways that you can attempt to address Error Code 0x80004002:
Many different registry cleaning tools exist on the Internet, but not all of these are provided by trustworthy sources. Rather than trusting a file from an unknown publisher, you can use the registry cleaning program included in your Windows software package.
Run this tool to complete a scan of your files, discovering which ones may need to be repaired. In most cases, the registry cleaner itself can repair the necessary files and resolve the error.
It is always a good idea to restart your computer after you have run the registry cleaning tool to ensure that your machine can accurately assess the newly repaired files.
In some cases, Error Code 0x80004002 arises when drivers are out of date. If you believe that this is the case, you can check on the status of your various drivers by going into the settings for your operating system and selecting the “Update Drivers” option.
You can also check your system for any necessary updates to your Windows software, which may serve to address the error code.
After you have checked and installed any necessary drivers, make sure to restart your computer to fully apply any changes that the installation process has introduced.
In some cases, the best way to address the missing or corrupt files that can cause Error Code 0x80004002 is to simply reinstall your copy of Windows. Always make sure to back up your files before reinstalling your software.
Because Error Code 0x80004002 can also be caused by malware or a virus, you can run your virus scan software to detect and resolve the problem. After doing so, run the registry repair tool to fix any affected files and restart your computer.
Error 80070490 (Element not found)
Error Causes-file "C:/Users/Ayush/Desktop/Powershell Script Sample.ps1"Step 8: Once done, click on OK to save the changes made and see if the task is still giving you an error or not. On the other hand, if you are still getting the same error, you can try to repair the Task Scheduler by deleting corrupted tasks. Note that a single corrupted file can cause big problems so this option is quite important. And for you to delete a corrupted task or any task from the Task Scheduler, you have to use the Registry Editor if you are not able to use the Task Scheduler interface. To do so, follow these steps: