Enabling Enhanced Mode in the Windows Search

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 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

If your internet suddenly stops working on your Windows 10 computer and you get an error message saying, “Windows is still setting up the class configuration for this device (Code 56)”, then read on as this post will show you what you can do to resolve it. This kind of issue has something to do with the Network Adapter and you can see this error message in the Properties menu of the corresponding Network Adapter under the Device Manager. This kind of issue could be caused by many things. For one, it could be caused by your VPN connection if you are using one or it could also be due to an outdated driver. Whatever the cause may be, here are some suggestions you have to check out to fix the error.

Option 1 – Check your VPN

When you install a virtual machine or VPN software on your computer, a new setup will be added in the Network Connection settings and helps your computer in using that adapter setting each time the VPN is turned on. Assuming that you are using an Ethernet connection but your system is trying to use another adapter or settings, that’s when issues occur and one of them is the “Windows is still setting up the class configuration for this device” error. To fix it, you can try to disable your VPN temporarily and see if the error is resolved or not and if turns out that your VPN is the culprit, you have to uninstall it and install a new one or its latest version. To uninstall it, follow the steps below.

• Tap the Win + R keys to open the Run dialog box
• Then type “appwiz.cpl” in the field and hit Enter to open the Programs and Features in Control Panel.
• From there, look for the VPN service you are using, select it and then click on Uninstall to remove it.
• After that, restart your computer and try to install the latest version of the program again. It should work now. If not, proceed to the next available option below.

Option 2 – Try to update or rollback or uninstall the Network Adapter drivers

You might also want to update, roll back or disable your Network drivers to fix the “This operation failed as no adapter is in the state permissible for this operation” error.

• Tap the Win + R keys to launch the Run window and then type in the “devmgmt.msc” command and hit Enter to open the Device Manager window.
• Under the Device Manager, you will see a list of drivers. From there, look for the Network Adapters and expand it.
• Then right-click on each one of the Network drivers and depending on your preference, you can either select “Update driver”, “Disable device” or “Uninstall device”.
• After that, restart your PC and see if it helped in fixing the netio.sys Blue Screen error.

Option 3 – Try to run the Network Adapter troubleshooter

To run the Network Troubleshooter, refer to these steps:

• Open the Search bar on your computer and type in “troubleshoot” to open the Troubleshoot settings.
• Next, scroll down and select the “Network Adapter” option from the right pane.
• Then click on the Run Troubleshooter” button.
• After that, your computer will check for any possible errors and will pinpoint the root cause of the problem if possible.
• Restart your computer.

Option 4 – Try to reset the Network

You might perform a Network Reset to resolve the problem if none of the three given options above worked. This will reset the entire network configuration including your IP address. To perform Network Reset, follow these steps:

• Tap the Win + I keys to open Settings.
• From there, go to the Network and Internet section.
• Next, scroll down and look for “Network Reset” under the status pane.
• After that, click on Network Reset and then on Reset now to start resetting the network configuration. Once done, check if it is able to fix the error or not.

One of the great remote assistance software that helps you remotely access and control computers is TeamViewer. However, despite how efficient it is, there are still times when it throws up some errors and one of them is when TeamViewer is not able to connect and throws an error that says, “No connection to partner, Partner did not connect to router, Error Code WaitforConnectFailed”. This kind of error in TeamViewer mostly occurs when the Partner computer is not connected to a network. On the other hand, it could also occur when they are connected to a network so there are various causes for this issue. It could also be that the installation of the program itself was at fault or there is an incompatibility between the TeamViewer versions installed on both the computers and so on. Although there are several causes for this error, the potential fixes are still the same. You can try to restart the network or allow Full Access Control to TeamViewer or flush the DNS cache. For more information, refer to the following options but before you proceed, make sure that both your Windows 10 computer and TeamViewer program are updated to their latest stable versions.

Option 1 – Reboot your router

The first thing you can try to do to fix the error is to simply restart your router. All you need to do is reboot the router from its Admin panel or you can also turn it off manually and turn it back on after a couple of seconds so that it can completely reboot. Once you’re done, try accessing your server again and see if the error is now fixed.

Option 2 – Allow Full Access Control to TeamViewer

• First, open TeamViewer, and then from the Menu bar, click on Extras.
• After that, click on Options and select Advanced from the left side navigation panel.
• Next, click on the “Show advanced options” button located on the right-hand side.
• Then select Full Access from the drop-down menu of the Access Control option under the “Advanced settings for connection to this computer section”.
• Now click OK and check if the error is now fixed or not.

Option 3 – Try to flush the DNS configuration

You could also try to flush the DNS configuration in your computer to fix the error. How? Refer to these steps:

• Tap the Win + X key combination and click on the Command Prompt (Admin) option or you could also search “cmd” in the Cortana search box and right-click on Command Prompt from the search results and select the “Run as administrator” option.
• After opening Command Prompt with admin privileges, enter each one of the commands given below sequentially in order to flush the DNS cache.
  • ipconfig/release
  • ipconfig/renew
  • ipconfig/flushdns
• Now type the exit command to close Command Prompt and then restart your computer and see if the problem is fixed.

On the other hand, you could also try to reset Winsock as well as the TCP/IP.

Option 4 – Run the Network Adapter troubleshooter

To run the Network Troubleshooter, refer to these steps:

• Open the Search bar on your computer and type in “troubleshoot” to open the Troubleshoot settings.
• Next, scroll down and select the “Network Adapter” option from the right pane.
• Then click on the Run Troubleshooter” button.
• After that, your computer will check for any possible errors and will pinpoint the root cause of the problem if possible.
• Restart your computer.

Option 5 – Try to perform Network Reset

You might perform a Network Reset to resolve the problem if none of the four given options worked. This will reset the entire network configuration including your IP address. To perform Network Reset, follow these steps:

• Tap the Win + I keys to open Settings.
• From there, go to the Network and Internet section.
• Next, scroll down and look for “Network Reset” under the status pane.
• After that, click on Network Reset and then on Reset now to start resetting the network configuration. Once done, check if it is able to fix the error or not.

In case you don’t know, Microsoft Office uses a separate mechanism than the Windows operating system for specific purposes such as Updates and Activation which brings in the content dependencies of this mechanism on different services and processes. Thus, in such cases, you could encounter errors like the error code 0x80070426. When you get this error, you will see the following error message on your screen:

“An unexpected error has occurred. Your request cannot be processed at this time. Please try again later. (0x80070426)”

This kind of error is caused by various supporting processes and services that are not working or are not being triggered as they were supposed to. If you are currently facing this issue, worry not for this post will guide you in fixing it. There are two potential fixes you can try – you can either check the responsible services or manually run the Activation Script. For more details refer to the given options below.

Option 1 – Try checking the responsible Services

• In the Start search, type “services.msc” in the field and tap Enter or click OK to open the Windows Services Manager.
• If a User Account Control or UAC prompt appears, just click on Yes to proceed to the Windows Services Manager utility window.
• After that, look for the “Software Licensing Service” service entry from the given list of services inside the window.
• Then right-click on it and select Properties and from there, make sure that its Startup Type is set to Automatic.
• Once done, click on the Start button to start the service and then exit the Services Manager.
• Next, tap the Win + R keys to open the Run utility and then type “cmd” in the field and tap Enter to open an elevated Command Prompt.
• After that, type and enter each command below one after the other.
  • net start slsvc
  • sc qc slsvc
  • sc queryex slsvc
  • sc qprivs slsvc
  • sc qsidtype slsvc
  • sc sdshow slsvc
• Now check if the problem is fixed or not.

Option 2 – Try to manually run the Activation Script

• In the Start search, type “cmd” and right-click on Command Prompt from the given search results and then select the “Run as administrator” option to open Command Prompt with admin privileges.
• Next, navigate to the following location inside the Command Prompt command-line utility if you are using Office 16.
  • x86: C:/Program Files (x86)/Microsoft Office/Office16
  • x64: C:/Program Files/Microsoft Office/Office16

• On the other hand, if you are using an older version, go to the following location instead.
  • x86: C:/Program Files (x86)/Microsoft Office/OfficeXX
  • x64: C:/Program Files/Microsoft Office/OfficeXX
• Once you’re in the location, type the following command to run the Activation Script and then tap Enter.

cscript ospp.vbs/act

• The command you just entered will activate your copy of Microsoft Office.

Experiencing issues while using Remote Desktop connections is not uncommon. One of the issues that users encountered recently while trying to connect to their Remote Desktop network is the error saying, “Your credentials did not work, The login attempt failed”. If you are one of these users, then you’ve come to the right place as this post will walk you through fixing the problem. When facing this kind of problem, the first thing you can try before you do some troubleshooting steps is to verify the credentials. But if you are certain that you’ve entered the correct credentials just like what other users reported, then it’s completely a different matter. Based on the reports, this error is common on newly installed versions of Windows 10 or after reinstalling the operating system which could mean that the problem might be due to the Windows security policies or the username might have been recently modified. The latter case is a possibility especially if you’ve reinstalled Windows 10 and had entered a new username. In such a case, you will really have a difficult time connecting to your Remote Desktop connection since its credentials do not really automatically change. If you’ve verified that your credentials are correct, then now’s the time you troubleshoot the problem with the help of the potential fixes provided below. Just make sure that you follow each one of them in sequence.

Option 1 –Try to run the Network Adapter troubleshooter

To run the Network Troubleshooter, refer to these steps:

• Open the Search bar on your computer and type in “troubleshoot” to open the Troubleshoot settings.
• Next, scroll down and select the “Network Adapter” option from the right pane.
• Then click on the Run Troubleshooter” button.
• After that, your computer will check for any possible errors and will pinpoint the root cause of the problem if possible.
• Restart your computer.

Option 2 – Try to change the network profile from public to private

According to some reports, this error occurs on systems where the network profile was set to public. Thus, you need to change the network profile to private to resolve the problem. How? Refer to these steps:

• Go to Start and from there click on Settings > Network & Internet > Status.
• Next, click on the “Change connection properties” option.
• After that, set the radio button of Network Profile from Public to Private.
• Wait for a couple of seconds until the system is done applying the changes you’ve made and then see if you can now connect to the Remote Desktop connection.

Option 3 – Try changing the account username

As mentioned, one of the possible causes for this error is the reinstallation of the operating system. You might have changed the username for the system but it does not really change the username of the Remote Desktop connection as well. Thus, you have to change the username back to what it was before you’ve reinstalled Windows 10.

Option 4 – Try modifying the Windows Security Policy

You can also try to edit the Windows Security Policy as it could help in resolving the error. This Windows Security Policy, when enabled, will not allow non-admin users to log on to the Remote Desktop connection. So if you want to allow non-admin users to use the Remote Desktop connection, then you need to modify this policy. Note that you can only do that if you are the admin of the system yourself.

• Tap the Win + R keys to open the Run utility.
• Then type “secpol.msc” in the field and tap Enter or click OK to open the Local Security Policy.
• After opening the Local Security Policy window, select Local Policies > User Rights Agreement located on the left pane.
• Next, double click on “Allow log on through Remote Desktop Services” located in the right pane.
• And in the next window that appears, select Add user or group.
• After that, type in the username of the intended non-admin user under the “Enter the object names to select” column.
• Once done, click on the Check Names button to fix the username and then click OK to save the changes made.
• Restart your computer.

Option 5 – Use the Group Policy Editor

• Tap the Win + R keys to open the Run dialog box and then type “gpedit.msc” in the field and tap Enter to open the Group Policy Editor.
• Next, navigate to this path: Computer Configuration > Administrative Templates > System > Credentials Delegation.
• Double click on the “Allow delegating default credentials with NTLM-only server authentication” policy setting located on the right pane to edit it.
• After that, shift its radio button to Enabled and click on Show.
• Then type “TERMSRV/*” in the Value box and click OK.
• Now repeat the same for the following policy settings:
  • “Allow delegating default credentials”
  • “Allow delegating saved credentials”
  • “Allow delegating saved credentials with NTLM-only server authentication”

• Once you’re done, restart your computer and see if the problem is fixed.

The SearchUI.exe file is the one that manages the search feature of Cortana. However, a number of users have recently reported that this feature stops responding within minutes of booting their Windows 10 computer. This kind of problem could be caused by missing system files or some issues with the Cortana program itself. And so if the SearchUI.exe file is not responding, then you wouldn’t be able to use the search feature of Cortana. But worry not for this post will walk you through fixing this problem. Before you troubleshoot the problem, you can try to restart your computer and see if it helps, if it doesn’t, then proceed to the given options below.

Option 1 – Try to run the Search and Indexing troubleshooter

You might also want to run the Search and Indexing troubleshooter in Windows 10 as it checks whether the settings for Cortana are in place and automatically corrects any issues if the update or software installation has changed the settings. To run it just click on the Start button and select Settings > Updates and Security > Troubleshoot. From there, select the Search and Indexing Troubleshooter.

Option 2 – Restart Cortana’s process in the Task Manager

Restarting Cortana’s process in the Task Manager could also help you resolve the problem. Refer to the steps given below to do so.

• Tap the Ctrl + Alt + Del keys to open the Security options window.
• From there, look for the Task Manager in the given list and open it.
• Next, look for the process of Cortana and right-click on it, and then select the End Task option to end its process.
• After that, the Cortana process will restart by itself and re-initialize.

Option 3 – Try resetting Cortana

• Open Cortana and go to the Settings section where you’ll see the “Turning off Cortana clears what Cortana knows on this device, but won’t delete anything from the Notebook. After Cortana is off, you can decide what you’d like to do with anything still stored in the cloud” option. Turn this option off.
• Restart your PC.
• After your computer boots, launch Cortana again and check.

Option 4 – Try running the DISM tool

You can try running the Deployment Imaging and Servicing Management or DISM tool to fix the Windows Upgrade problem. Using this built-in tool, you have various options such as the “/ScanHealth”, “/CheckHealth”, and “/RestoreHealth”.

• Open the Command Prompt with admin privileges.
• Then type in the following commands and make sure to hit Enter right after you type each one of them:
  • Dism /Online /Cleanup-Image /CheckHealth
  • Dism /Online /Cleanup-Image /ScanHealth
  • exe /Online /Cleanup-image /Restorehealth
• Do not close the window if the process takes a while as it will probably take a few minutes to finish.

Option 5 – Try to reinstall Cortana

If none of the options given above works, you must consider reinstalling Cortana.

• First, right-click on the Start button and click on the Windows Powershell (Admin) option from the list.
• Next, type the following command and hit Enter to execute it:

Get-AppXPackage -Name Microsoft.Windows.Cortana | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)AppXManifest.xml"}

• Restart your computer and check if Cortana is now able to connect.

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

There are instances that some conflicting programs installed in your computer might be the one that’s causing some issues with Cortana or causing the SearchUI.exe process to stop. To identify which program is causing the problem, you need to put your computer in a Clean Boot State. To do so, follow the steps below.

• Log onto your PC 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.

One of the most useful tools you can use to repair bad or corrupted sectors in the hard disk of your computer is the CHKDSK utility. However, there are also instances when this Disk Checking tool could encounter some issues and one of them is the error that states, “The type of the file system are RAW, CHKDSK is not available for RAW drives”. This kind of issue is due to the RAW file format which is not recognized by the Windows operating system that you’ve installed which explains why you’re getting this error when running the CHKDSK utility. You can also encounter this error in case there is something wrong with the drive encryption. To fix this error, you have to change the File System of the drive. How? Refer to the steps given below. Step 1: The first thing you need to do is create a bootable Windows 10 media. Step 2: After that, click on Repair your computer on the first Windows 10 installation setup window. Step 3: Next, you have to select the operating system partition from the given options and then click on Next. Step 4: Now select Command Prompt from the System Recovery Options box and then type the following command and tap Enter to initiate the Diskpart utility inside Command Prompt.

diskpart

Step 5: Afterwards, type in either of the following commands to help you in either listing all the Disk connects or all the partitions on those disks formed.

diskpart or list volume

Step 6: Next, you need to select any of the two given commands below depending on the list you entered on the previous step.

select disk # or select volume #

Step 7: After you enter the command, it will select the Disk or the Partition you want to select. Now you have to type and enter the following command to clean your drive.

clean

Step 8: Now enter any of the two following commands.

list disk or list volume

Step 9: Then type the next command below to create a specified partition.

create partition primary

Step 10: Once done, type in the following command to select the newly created partition.

select partition 1

Step 11: Next, type the following command to mark the selected partition as active.

active

Step 12: Finally, restart your computer to successfully apply the changes made and then see if it has fixed the problem or not.

If you got an error message saying, “Folder Redirection Failed, Failed to build the list of regular subfolders, Access is Denied” after you configured a new Group Policy Object or GPO which redirects User folders to a new network share or when you click on Reset default location under the Windows File Explorer or Folder Options, then you’ve come to the right place as this post will show you how to resolve this kind of error on your Windows 10 computer. Follow the given options below carefully to fix the “Folder Redirection Failed” error.

Option 1 – Take Ownership of the folder

If you are not able to access the folder could be one of the reasons why you’re getting the “Folder Redirection Failed” error and so you need to take ownership of the folder to resolve the problem. Before you proceed, make sure that your account is an admin account.

• First, locate the concerned folder and right-click on it then select Properties.
• Next, click on the Edit button in the Properties window and click OK to confirm if you got a User Account Control elevation request.
• After that, select user/group from the permission windows or click on the Add button to add another user or group. It would be best if you add “Everyone” to give permission.
• Then check “Full Control” under the “Allow” column to assign full access rights control permissions.
• Now edit the permission to Full Control for “Everyone”.
• Click OK to save the changes made and then exit.

Option 2 – Try to add Authenticated Users or Domain Computers

Make sure that the Folder Redirection group policy removal option is set to “Redirect the folder back to the user profile location when the policy is removed” when using the Folder Redirection. After that, you have to add Authenticated Users group with the “Read” permissions on the Group Policy Objects or GPOs. And if the Domain computers are part of the group of “Authenticated Users”. Note that by default, the “Authenticated Users” have these permissions on any new Group Policy Objects or GPOs. Once again, you have to add just “Read” permissions and not “Apply Group Policy” for “Authenticated Users”. Furthermore, to fix the “Failed to build the list of regular subfolders” errors, here are some options that could help.

Option a – Try to clear disk space

You might have to check if your disk is running out of space because if it is, then it will fail to create a list abruptly. And so you need to free up some disk space. You can either check on the files manually especially if you tend to keep your files at random places in your disk drive.

Option b – Find the Target route

You need to find the target route of the folder and then restore it if you are getting the “Failed to build the list of regular subdirectories” when you try to relocate the folder to the original location.

Option c – Try to change Ownership/Reset Defaults for all the User folders

If the “Failed to build the list of regular subdirectories” error pops up when you are trying to move a large number of files from one location to another, then you need to change the ownership of the folders as pointed out earlier.

Steam Deck release is almost upon us and more news comes to light. The Latest officially confirmed technical detail is that the user will have access to device's BIOS and that dual booting will be officially supported. This, of course, means that you will be able to have both Proton and Windows on your device letting you play anything that you wish if the hardware is strong enough. Valve also said that you can launch OS from an SD card! This of course will save space available for games themselves, especially for entry models with less than one available. All of this information really pushes Deck into the territory of a handheld PC and not just another console and I must admit that this announcement left a smile on my face.

If you encountered an error message that says, “Unhandled exception has occurred in your application”, when you start your Windows 10 computer, read on as this post will guide you on how you can fix it. This kind of error usually appears in a Microsoft .NET Framework window and it mostly pops up as soon as you turn on your computer. Here’s the complete context of the error message:

“Unhandled exception has occurred in your application. If you click Continue, the application will ignore this error and attempt to continue. If you click Quit, the application will close immediately.”

When this error occurs, your computer may freeze or display other suspicious behavior at times. Either way, there are several options you can check out in this post to resolve this issue, so read on. This kind of error could be caused by several factors. It could be due to your antivirus program or other third-party programs installed on your computer. It is also possible that the installation of the Microsoft .NET framework id corrupted or some of its installation files are corrupted. Thus, to fix the error, there are a few suggestions you need to follow such as:

Option 1 – Try to temporarily disable your anti-virus program

As mentioned, the error could be due to the antivirus program or the Windows Defender Firewall installed on your computer. Thus, disabling them or any security software installed in your computer is always a good idea you can try when you’re not able to access the shared drive in your computer. There are times when you encounter problems like the “Unhandled exception has occurred in your application” error due to interference of antivirus or security programs. Thus, you have to disable both your antivirus program in the meantime and check if it fixes the error or not.

Option 2 – Put your computer in a Clean Boot State

As pointed out, it is possible that some third-party program or service is the one that’s behind the problem. To isolate this possibility and to identify the culprit, you have to put your computer into a Clean Boot State. To do so, follow the steps below.

• Log onto your PC 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.)
• Once your computer has restarted, check if the error is now gone. If it is, then the culprit is some third-party program. Thus, you have to enable the third-party programs one by one to find out which one of them is causing the the “Unhandled exception has occurred in your application” error.

Option 3 – Try to run a 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 with good system files that might be the cause why you’re getting the “Unhandled exception has occurred in your application” error. To run the SFC command, follow the steps given below.

• Type “cmd” in the Start search and then right-click on the appropriate search result.
• Next, select “Run as administrator” to open Command Prompt with admin privileges.
• 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.

• Now restart your computer and see if the problem is fixed or not.

Option 4 – Install and update Dependencies

There are times when programs and applications need to have drivers and supporting software installed for them to properly work. Although the installation usually takes care of it, it’s time for you to do some manual check especially if you are getting this issue of abnormal program termination.

• Install some qualified drivers – A number of high-end games and applications need to have correct and valid drivers for them to work. They just don’t work with general drivers though. Microsoft has this Windows Hardware Quality Labs testing also known as WHQL testing which makes sure that drivers meet the correct experience and pass through the proper testing before certification. Thus, when installing drivers, you need to ensure that they are qualified drivers for your Windows 10 PC.
• Download and install or Update DirectX – As you know, Microsoft DirectX is a suite of technologies developed by Microsoft to provide hardware acceleration for heavy multimedia applications like HD videos and 3D games. Since you are using Windows 10, you have the DirectX 12 version while the earlier Windows versions use the DirectX 11 version.
• Install the Microsoft DirectX End-user runtime – The Microsoft DirectX end-user runtime gives updates to version 9.0c as well as previous versions of DirectX. To install it, click on this link and download it.
• Update or install the .NET framework – The .NET framework is used by games and applications during development which means that without the runtime files that are installed in your computer, it definitely won’t work. Thus, you need to install or update this framework. You can also use the .NET setup verification tool to verify it.