Windows 10 Setup says I need to uninstall a program or utility in order to continue setup. I cannot find program it ask for or it was already uninstalled

Microsoft is trying to make Windows into a personalized OS, more and more features and parts can be customized to user liking. From larger things to smaller ones nowadays you can almost personalize every detail of Windows itself. In this article, we will tackle how to bring back the names of running applications on the taskbar. Placing names beside icons on the taskbar is a pretty simple and straightforward task easily done. First, right-click the Taskbar and select Taskbar settings. In Taskbar settings, click the menu labeled Combine taskbar buttons. Select Never. That's it, now all of your running applications have a name beside them. If you change your mind, you can always undo it by selecting Always hide labels in the Combine taskbar buttons menu.

There is various Blue Screen of Death errors that you can encounter as you use your Windows 10 computer and some of these Stop errors have something to do with the win32kbase.sys file. This post will guide you in fixing the BSOD errors related to the win32kbase.sys file.

• A problem has been detected and Windows has been shut down to prevent damage to your computer. The problem seems to be caused by the following file: Win32kbase.sys.
• Your PC ran into a problem and needs to restart. If you would like to know more, you can search online later for this error: win32kbase.sys.
• SYSTEM_SERVICE_EXCEPTION (win32kbase.sys)
• STOP 0x0000000A: IRQL_NOT_LESS_EQUAL – win32kbase.sys
• STOP 0x0000001E:

KMODE_EXCEPTION_NOT_HANDLED – win32kbase.sys

• STOP 0×00000050:

PAGE_FAULT_IN_NONPAGED_AREA – win32kbase.sys

The win32kbase.sys file is a Windows operating system Base Win32 Kernel Driver file located in the System32 folder so if it ends up getting corrupted or if it went missing, your computer will throw up Blue Screen error. To fix BSOD errors that have something to do with the win32kbase.sys file, here are some possible fixes that could help. Worry not for these possible fixes are not complicated.

Option 1 – Run the Check Disk or CHDSK utility

One of the first things you can try to resolve the win32kbase.sys Blue Screen error is running the CHKDSK utility. If your hard drive has issues with integrity, the update will really fail as the system will think that it’s not healthy and that’s where the CHKDSK utility comes in. The CHKDSK utility repairs hard drive errors that might be causing the problem.

• Open Command Prompt with admin privileges.
• After opening Command Prompt, execute the following command and hit Enter:

chkdsk /f C:

• Wait for the process to be completed and then restart your computer.

Option 2 – Run SFC or System File Checker scan

System File Checker or SFC is a built-in command utility that helps in restoring corrupted files as well as missing files. It replaces bad and corrupted system files to good system files. To run the SFC command, follow the steps given below.

• Tap Win + R to launch Run.
• Type in cmd in the field and tap Enter.
• After opening Command Prompt, type in sfc /scannow

The command will start a system scan which will take a few whiles before it finishes. Once it’s done, you could get the following results:

1. Windows Resource Protection did not find any integrity violations.
2. Windows Resource Protection found corrupt files and successfully repaired them.
3. Windows Resource Protection found corrupt files but was unable to fix some of them.

 Restart your PC.

Option 3 – Try to run the DISM commands

You might want to repair potentially corrupted files in your system as having them could also trigger the win32kbase.sys Blue Screen error. To repair these corrupted system files, you can run the DISM commands:

• Tap the Win + X keys and click on the “Command Prompt (Admin)” option.
• After that, input each one of the commands listed below sequentially to execute them:
  • Dism /Online /Cleanup-Image /CheckHealth
  • Dism /Online /Cleanup-Image /ScanHealth
  • Dism /Online /Cleanup-Image /RestoreHealth

• Once you’ve executed the commands given above, restart your computer and check if the dxgkrnl.sys Blue Screen error is now fixed.

Option 4 – Try to run the Blue Screen Troubleshooter

As you know, the Blue Screen troubleshooter is a built-in tool in Windows 10 that helps users in fixing Blue Screen errors related to the win32kbase.sys file. It can be found in the Settings Troubleshooters page. To use it, refer to these steps:

• Tap the Win + I keys to open the Settings panel.
• Then go to Update & Security > Troubleshoot.
• From there, look for the option called “Blue Screen” on your right-hand side and then click the “Run the troubleshooter” button to run the Blue Screen Troubleshooter and then follow the next on-screen options. Note that you might have to boot your PC into Safe Mode.

Installing a Windows 10 upgrade is definitely not an easy task since the process is not always smooth sailing and you could encounter some errors when doing so. This isn’t unusual since there are various software configurations and hardware configurations as well as services it depends on in order to properly work. So if any of them malfunctions or becomes corrupted, it will affect the process which will result in errors like the error code 0x80300002. When you encounter this kind of Windows Update error, you will see the following error message on your screen:

“We couldn’t install Windows in the location you choose. Please check your media drive. Here’s more info about what happened: 0x80300002”

You can encounter this kind of error if there is corruption in the partition table of the drive where the installation is in progress. In addition, corruption on the Media device could also cause this problem. So if you encounter this error when running Windows Setup, read on as this post will guide you in fixing it. There are several ways to resolve this issue. The first thing you can do is to verify the compatibility between the BIOS and the installation media. You could also try recreating all the partitions as well as recreating the bootable USB drive. For more detailed information, follow the given options below.

Option 1 – Check if the BIOS is compatible with the installation media

The first thing you can do to fix the error is to check if there are any compatibility issues between the BIOS and the installation media you’re using. This is actually one of the most likely reasons why you’re getting the error since this is a complicated point for the Windows installation process. If the installation media is based on GPT, then your BIOS must be based on UEFI. So if you have your bootable media with the MBR partitioning, you need to set your BIOS to Legacy.

• In the Windows Search box, type “command prompt” and from the search results that appear, right-click on Command Prompt and select the “Run as administrator” option.
• After that, execute this command: exe /convert /allowfullOS
• Now, wait until the process is completed since you can track its process on your screen.
• Once it’s done, go to Settings > Update & Security > Advanced Startup options and from there, click on Restart Now. This will restart your computer and give you advanced options.
• Next, select Troubleshoot > Advanced Options where you will see further options including System Restore, Startup Repair, Go back to the previous version, Command Prompt, System Image Recovery, and UEFI Firmware Settings.
• Now select the “Legacy” option. This will take you to the BIOS. Boot Mode is typically available under Boot > Boot Configuration. Once you’re there, set it to Legacy and then save the changes you’ve made. After that, your computer will restart.

Option 2 – Try recreating a new bootable drive

• Insert your USB drive into your PC.
• Tap the Win + R keys to open the Run dialog box and type in “cmd” and tap Enter to open the Command Prompt. Alternatively, you can also search for “cmd” in the Cortana search box to open Command Prompt.
• Once you’ve opened CMD, type in this command to open the DISPART utility – diskpart
• After that, you should see a new black and white window that would say, “DISKPART>”.
• Next, type in “list disk” in the command line and tap Enter to see the list of all the Storage devices as well as your hard disk connected to your PC. Here, you have to identify your disk’s number.
• Type in this command where “X” is the disk number you have identified and then tap Enter – disk X
• Type in this command and hit Enter to clear the table records and all the visible data on the drive – clean
• Now you have to recreate a new primary partition of the drive so you’ll have to type in this command and tap Enter right after – create part pri
• A new primary partition has been created so you have to select it by typing this command and tapping Enter – select part 1
• Now you have to format it to make it visible to normal users by typing – format fs=ntfs quick

Note: If your platform supports the Unified Extensible Firmware Interface or UEFI, replace the “NTFS” with “FAT32” in the command on Step 10.

• After that, type in this command and tap Enter after – active
• Finally, type this command and hit Enter to exit the utility – exit
• After you prepare the image for the operating system, save it to the root of your USB Storage device.

Option 3 – Try to recreate all the partitions

If none of the first two options given above worked, then you can try to recreate all the partitions instead. All you have to do is restart the Windows installation process and wait until you get to the part that says, “Where do you want to install Windows?”. From there, you will see options like delete, format, extend, create new partitions, and many more. Now you have to select the Delete all the partitions options and then use the “New” button to create new partitions. Just make sure that you have one primary partition at least where you can install Windows 10. After that, continue the installation of Windows on the new partition. Keep in mind that when you create a new partition, it also recreates the partition table configuration which means that the chances of getting an error are very unlikely.

If you are trying to open a folder or run a program or delete a file but you encounter an error message instead saying, “Error (740), The requested operation requires elevation” on your Windows 10 computer, then this post should help. Make sure that you follow each one of the options given below carefully.

Option 1 – Always run the program as an administrator

There are some apps that require administrator privilege before they can be opened. So if you are got the “Error (740), The requested operation requires elevation” error when you try to open a particular app on your computer, you have to try opening it as administrator instead. On the other hand, if you are already using an administrator account or if you are a member of the administrator group, this option may not work for you so just proceed to the next one but if you’re only using a regular account, then follow these steps:

• First, right-click on the app you are trying to open and select Properties.
• After that, go to the Compatibility tab and check the checkbox labeled “Run this program as an administrator”.
• Next, click the Apply and OK buttons and see if the app opens without any problem.

Option 2 – Try to change the folder permissions

If you encounter Error 740 while opening a folder, then you need to try changing the folder permissions.

• First, right-click on the folder and click Properties.
• Next, go to the Security tab and click the Advanced button.
• After that, check the checkbox labeled, “Replace all child object permission entries with inheritable permission entries from this object” and then click the Apply and OK buttons to save the changes made.

Option 3 – Try disabling UAC

The User Account Control or UAC settings might be the one that’s responsible for Error 740 which is why you have to disable the User Account Control and then verify if it’s the one that triggers the error or not. To do that, simply search for “Change user account control settings” in the Taskbar search box and then drag the blue bar down to the bottom and click the OK button to save the change made.

Option 4 – Select the Elevate without prompting option in the Group Policy Editor

There is an option in the Group Policy Editor which allows you to disable the UAC prompt. Disabling the “Elevate without prompting” option can help in resolving Error 740 and to disable it, follow the steps below.

• Tap the Win + R keys to open the Run dialog box.
• Then type “gpedit.msc” in the field and hit Enter to open the Group Policy Editor.
• Next, navigate to the following path:

Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options

• From there, go to the Security Options folder where you can find a policy named “User Account Control: Behavior of the elevation prompt for administrators in Admin Approval Mode”. Double click on it to open its options.
• Now select the Elevate without prompting option from the drop-down menu and click OK.

Every time a new drive or any storage device is connected to a Windows 10 computer, the operating system tends to allot a drive letter to it automatically. Not only that, as the OS also maps the location of the drive which helps it point the letter to the exact port location of the drive and serve requests from the user. As a result, it builds up a bit of cache as per the pattern in which the user uses the storage of the computer. This whole process is known as “Auto Mounting” which works for hard disks or optical drive readers that are connected using the SATA ports and even for USB drives that are connected using the USB ports. There are several ways you can enable or disable the Auto-Mount feature in Windows 10. You can do it using the MountVol tool or the Registry Editor or the Diskpart utility. Before you proceed, it is recommended that you create a System Restore point first so that you can always undo the changes you made in case anything goes wrong.

Option 1 – Enable or disable Auto Mounting via MountVol tool

In this option, you will be using the mountvol command in the Command Prompt. Refer to the steps below.

• Tap the Wins key once and type in “command prompt” in the field.
• From the search results, right-click on Command Prompt and select the “Run as administrator” option to run it with admin privileges.
• Next, type the following command and tap Enter to enable the Auto Mount feature:

mountvol /E

• On the other hand, if you want to disable the Auto Mount feature, type the following command instead:

mountvol /N

• After that, type the command below to remove all the previously assigned drive letters:

mountvol /R

• Finally, restart your computer.

Option 2 – Enable or disable Auto Mounting via Registry Editor

• Tap the Win + R keys to open the Run dialog box.
• Then type “Regedit” in the field and tap Enter to open the Registry Editor.
• After that, navigate to this registry key: ComputerHKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesmountmgr
• Next, look for a DWORD named “NoAutoMount”. If you can’t find a DWORD with that name then simply create a new DWORD with the same name and make sure that the base is selected to Hexadecimal.
• Now double click on that DWORD and change its value to 0 if you want to enable it, otherwise, input 1 as its value to disable it.
• Restart your computer.

Option 3 – Enable or disable Auto Mounting via Diskpart utility

• Tap the Wins key once and type in “command prompt” in the field.
• From the search results, right-click on Command Prompt and select the “Run as administrator” option to run it with admin privileges.
• After opening Command Prompt as admin, type the following command and hit Enter to launch the Diskpart utility:

diskpart

• After that, a User Account Control prompt will appear. Just click on the Yes button.
• Next, type the following command and hit Enter:

automount

• Following the command you entered, you will an output that either says, “Automatic mounting of new volumes enabled” or “Automatic mounting of new volumes disabled” which means you can use it to check the status of Auto Mount.
• Now if you want to enable the Auto Mount feature, type the following command and tap Enter:

automount enable

• And if you want to disable the Auto Mount feature, just enter the following command:

automount disable

• To remove all the assigned letter and history of drives that were connected previously, type the following command:

automount scrub

• Finally, restart your computer.

New malware with extensive spyware capabilities steals data from infected Android devices and is designed to automatically trigger whenever new info is read to be exfiltrated. The spyware can only be installed as a 'System Update' app available via third-party Android app stores as it was never available on Google's Play Store. This drastically limits the number of devices it can infect, given that most experienced users will most likely avoid installing it in the first place. The malware also lacks a method to infect other Android devices on its own, adding to its limited spreading capabilities. However, when it comes to stealing your data, this remote access trojan (RAT) can collect and exfiltrate an extensive array of information to its command-and-control server. Zimperium researchers who spotted it observed it while "stealing data, messages, images and taking control of Android phones."

What happens when malicious software is installed

"Once in control, hackers can record audio and phone calls, take photos, review browser history, access WhatsApp messages, and more," they added. Zimperium said its extensive range of data theft capabilities includes:

• Stealing instant messenger messages;
• Stealing instant messenger database files (if the root is available);
• Inspecting the default browser's bookmarks and searches;
• Inspecting the bookmark and search history from Google Chrome, Mozilla Firefox, and Samsung Internet Browser;
• Searching for files with specific extensions (including .pdf, .doc, .docx, and .xls, .xlsx);
• Inspecting the clipboard data;
• Inspecting the content of the notifications;
• Recording audio;
• Recording phone calls;
• Periodically take pictures (either through the front or back cameras);
• Listing of the installed applications;
• Stealing images and videos;
• Monitoring the GPS location;
• Stealing SMS messages;
• Stealing phone contacts;
• Stealing call logs;
• Exfiltrating device information (e.g., installed applications, device name, storage stats).

How does it work?

Once installed on an Android device, the malware will send several pieces of info to its Firebase command-and-control (C2) server, including storage stats, the internet connection type, and the presence of various apps such as WhatsApp. The spyware harvests data directly if it has root access or will use Accessibility Services after tricking the victims into enabling the feature on the compromised device. It will also scan the external storage for any stored or cached data, harvest it, and deliver it to the C2 servers when the user connects to a Wi-Fi network. Unlike other malware designed to steal data, this one will get triggered using Android's contentObserver and Broadcast receivers only when some conditions are met, like the addition of a new contact, new text messages, or new apps being installed. "Commands received through the Firebase messaging service initiate actions such as recording of audio from the microphone and exfiltration of data such as SMS messages," Zimperium said. "The Firebase communication is only used to issue the commands, and a dedicated C&C server is used to collect the stolen data by using a POST request."

Camouflage

The malware will also display fake "Searching for the update.." system update notifications when it receives new commands from its masters to camouflage its malicious activity. The spyware also conceals its presence on infected Android devices by hiding the icon from the drawer/menu. To further evade detection, it will only steal thumbnails of videos and images it finds, thus reducing the victims' bandwidth consumption to avoid drawing their attention to the background data exfiltration activity. Unlike other malware that harvests data in bulk, this one will also make sure that it exfiltrates only the most recent data, collecting location data created and photos taken within the last few minutes. If you would like to read more helpful articles and tips about various software and hardware visit errortools.com daily.

Could not connect to the System Event explanation: Although logging into a Windows 10 computer may seem like a simple process, it’s actually not since the Windows operating system has built a mechanism in a way that any third party or malware intervention would not compromise access to the system. This mechanism is supported by numerous services, functions, and DLL files. And Microsoft has been taking this security to a whole new level with the introduction of Windows Hello. Recently, a number of users reported getting the “Windows could not connect to the System Event Notification Service service. Please consult your system administrator” error when logging into their computers. While some users also reported that although they can log in, they encounter the same error message from the Notification area. There are several options you can check out to resolve the error. You have to check the status of several Windows Services and make sure that they are running. You also have to reset Winsock as well as run the System File Checker scan.

Option 1 – Check for certain Windows Services

• First, you need to tap the Win + R keys on your keyboard to open the Run dialog box.
• Next, type “services.msc” in the field and click OK or tap Enter to open the Windows Services Manager.
• After that, you will see a list of services and from there, look for the following Windows Services:
  • DHCP Client
  • System Event Notification Service
  • Windows Font Cache Service
• Now make sure that the Startup Type of each service is started and running.

Option 2 – Try resetting the Winsock drivers

• In the 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, execute this command: netsh winsock reset

Note: If you are using IPv4, execute the “netsh int ipv4 reset” instead. On the other hand, if you are using IPv6, execute the “netsh int ipv6 reset”

• Now exit Command Prompt and see if the error is now fixed.

Option 3 – Try running System File Checker or SFC scan

You could also run System File Checker or SFC scan to fix the BSOD error. It is a built-in command utility that helps in restoring corrupted files as well as missing files. It replaces bad and corrupted system files with good system files. To run the SFC command, follow the steps given below.

• Tap Win + R to launch Run.
• Type in cmd in the field and tap Enter.
• After opening Command Prompt, type in sfc /scannow

The command will start a system scan which will take a few whiles before it finishes. Once it’s done, you could get the following results:

1. Windows Resource Protection did not find any integrity violations.
2. Windows Resource Protection found corrupt files and successfully repaired them.
3. Windows Resource Protection found corrupt files but was unable to fix some of them.

• Reboot your PC.

Error Code0x80070426 - What is it?

When Windows evolved into Windows 10, the program known as Windows Security Essentials is no longer. It is now the program known as Windows Defender. When a computer is upgraded from a previous version of Windows up to Windows 10, the Windows Defender takes over and will replace the Security Essentials. In a small percentage of Windows 10 upgrades, something will go wrong and the new program will fail to replace Security Essentials. The result will be that the operating system has both of the programs installed. In this case, Windows Defender will not offer any protection and Security Essentials will not be able to defend either. This error code will also present itself when the Windows Mail App in Windows 10 fail to retrieve and sync email from the user's account.

Common symptoms include:

• There will be an error message that says: “An error has occurred in the program initialization. If this problem does continue, contact your System Admin. Error code 0x80070426.”
• The computer will be left completely vulnerable to spyware and viruses.
• The Windows Mail App will not be able to retrieve mail and will not sync with the PC user's mail.
• The user can be doing anything on their computer and the error code will show up unprompted.
• The computer will lock up, become slow, crash, or even freeze when dealing with error code 0x80070426.
• The programs from an older version of Windows do not replace the newer version from Windows 10.

Solution

Error Causes

Error code 0x80070426 will present itself when a PC user has upgraded their OS from a previous version of Windows to the new Windows 10 version. When this happens, a small portion of users will experience the disconnect between older versions of specific programs, namely the virus protection. When the previous version of the program under a different name is not completely removed and the new virus protection program is installed, the programs will cancel each other out and collectively offer no protection.

This error code may also be found when Windows 10 tries to sync the user's email with the Windows Mail App.

Further Information and Manual Repair

There are a few methods to repair this problem. It should be noted that should anyone feel that the instructions are too complicated, they should contact a Windows repair technician to ensure that the error is fixed properly.

Method One: Uninstall Microsoft Essentials

Hold down the Windows Key and press R. Type in taskmgr into the run dialogue. You should locate the Windows Defender Service (this may show up as Windefend). Right-click on it and then choose Stop.

This will stop the program, but the program will start back up automatically when the computer restarts. While this program is stopped, uninstall Essentials.

To do this: go to Control Panel, Programs, and Features, Uninstall a Program. Alternately, you may hold down the Windows Key and press R, type in appwiz.cpl, click OK, and then locate Microsoft Essentials. Uninstall it, and then restart your computer.

After this is done, go to Settings, Update, and Security. Choose Windows Defender and ensure that Real-time protection is on. Refer back to the Task Manager, Services. Make sure that Defender service is on and running.

Method Two: If the problem occurs in the Windows Mail App

When error code 0x80070426 presents itself in the form of an error with the Mail app, it may be necessary to run an SFC scan.

Right-click on the Start menu or Windows icon, and select Command prompt. The command prompt may be navigated by using shortcut keys Win and X and then select it.

Run the command prompt and then type in sfc /scannow and then press enter. The SFC scan will be run, and be careful not to abort the process before it has finished. This will scan for any files that are lost or corrupt on the PC.

If the scan has found any corrupt files, type in this code and then hit Enter: findstr /c:”[SR]” %windir%LogsCBSCBS.log >”%userprofile%Desktopsfcdetails.txt.

To skip the repair of corrupt or missing files, type in: Dism /Online /Cleanup-Image /RestoreHealth. The details of the scan can be found on the sfcdetails.txt file that will be on the desktop.

Method Three: Use An Automated Tool

If you wish to always have at your disposal a utility tool to fix these Windows 10 and other related issues when they do arise, download and install a powerful automated tool.

One of the smoother things that Microsoft did with the Windows 10 operating system is to separate Cortana from Search. This means that Cortana is strictly now a voice assistant and many users have seen it coming since not everyone uses Cortana. In addition, it also paved the way for other virtual assistants like Alexa to get on board with Windows 10. And now in the newly released Windows 10 v1903, Windows has brought the Voice Activation under Privacy. In this post, you will be guided on how to perform the Voice Activation troubleshooting on your Windows 10 computer. To use Voice Activation in Windows 10, follow, in the Start Search, type “voice activation” and click on “Voice activation privacy settings” listed in the search results. And from there, you can choose to allow apps to use Microphone, like listen in the background as well as select which app can access it. Each time enabled voice assistants continue to listen via microphone for the voice keyword, the app will activate itself for the keyword and will react depending on what you ask it. So if you are using a voice assistant and it didn’t respond when you speak the keyword, just go to Settings > Privacy > Voice Activation and follow these steps:

Option 1: Check the App permission to use the voice activation feature.

You have to make sure that the toggle button for the Voice activation feature is turned on globally. It can be found under the “Allow apps to use voice activation” section. You also have to ensure that the microphone is available for apps that use this feature.

Option 2: Voice activation is not working under the lock screen.

If you tend to use the voice assistant even when your computer is locked, Microsoft has a specific setting that you have to turn on. You need to make sure that the toggle button for the “Allow apps to use voice activation when this device is locked” option is turned on. However, keep in mind that the voice assistants are not locked to only recognize your voice as they also answer to anyone who will use the voice keyword.

Option 3: Check the individual permissions of apps.

If the voice assistant is not working, you have to check each one of the apps’ permissions for voice keyword, and the option to work under locked condition works.

Option 4: Run the Microphone troubleshooter.

If you’ve verified that the settings are in place, then you have to run the Microphone troubleshooter by simply going to Settings > Privacy > Microphone. From there, make sure that the toggle button for the following options is turned on:

• Allow apps to access your microphone
• Enable microphone access for the voice assistant

And if it’s a desktop app, you have to enable the toggle on at the end.

If you are using a Windows 10 PC that has different processors clubbed together, chances are you might encounter an error saying, “MULTIPROCESSOR CONFIGURATION NOT SUPPORTED” during a Windows upgrade or software installation. This error is actually caused by a bug check with a value of 0x0000003E. This error also indicates that the processors in your computer are asymmetric in relation to one another. So if you want to upgrade you need to have all the processors of the same type and level. But worry not for this guide will help you in fixing this error. The MULTIPROCESSOR_CONFIGURATION_NOT_SUPPORTED error can occur in several cases such as during an installation of Windows 10, or when the driver is loaded, or when Windows Start or Shutdown and the chances of you getting a blue screen is very much high. To fix this error, refer to the options given below and make sure to follow them carefully.

Option 1 – Try to disable the Hyper-Threading in your BIOS

Hyper-Threading in the BIOS lets a processor (multi-threaded) run various tasks in a simultaneous manner. To disable this, here’s what you have to do:

• Restart your computer and boot into it right after. To do that, tap the F2 key.
• Once you’re in the BIOS, locate the Hyper-Threading option which should be located under the Performance section along with other options like Multi-core support, Rapid Start technology, and many more.
• Disable Hyper-Threading and then make sure to save the changes and exit BIOS.

Note: Although Hyper-Threading is only used when necessary, there are some OEMS that don’t have the option to disable it and if that’s the case, you need to try other options given below.

Option 2 – Try to disable the Virtualization in the BIOS

Virtualization in the BIOS allows users to run a single physical resource such as the server or storage device to appear that it is running as multiple logical resources. It is also properly termed as “HYPER-V”.  To disable it, refer to these steps:

• Boot into the BIOS as you did earlier.
• Then look for the Security options.
• After that, from Security options, look for Virtualization Technology or VTX among the options given.
• Then turn it off and restart your computer.

Note: Although Windows 10 offers features such as the Device Security for Core Isolation and Memory Integrity, if you turn them off at the software level, it will not help at all. If you’re able to resolve the error, you can do some further research and see what software or hardware you can use to further help you.

Option 3 – Try checking if there are any BIOS updates available for your PC

Updating the BIOS may help you resolve the MULTIPROCESSOR CONFIGURATION NOT SUPPORTED error. You can just go to the OEM’s website as they offer utility software that can download BIOS firmware and update it without any problem. BIOS updates usually offer enhancements and fixes to some issues like this one.