How to Enable Last Active Click feature

If you are trying to install or upgrade your Windows 10 computer but suddenly encountered an error message saying, “Windows could not configure one or more system components”, read on as this post will show you how you can fix the problem. You are not alone in experiencing this problem as other users also reported having the same scenario. Some of them reported getting the following error message:

“Windows could not configure one or more system components. To install Windows restart the computer with error code 0xc1900101-0x30018.”

When you check on the Windows 10 rollback log, you will see a part with the “iisetup.exe” that’s related to the abort. Usually, the upgrade process completes over 50% and gets stuck and then rolls back later on and generates the error logs. This kind of error, in most cases, appears during the upgrade of Windows 10 and is related with the Internet Information Services or IIS in Windows 10. For some unknown reason, it restricts the installation or the upgrade which causes the error to appear. To fix the “Windows could not configure one or more system components” error, you can try to remove the IIS from the Windows Features or rename the “inetsrv” folder. You could also move all the folders related to IIS to another drive. For more details, refer to the options provided below.

Option 1 – Try to remove the IIS from Windows Features

The IIS is installed from the Windows Features and you can find it at Control Panel > Programs. From there, uncheck the checkbox for the Internet Information Services. Once done, click on the OK button to save the changes. Note that this process will get rid of all the related programs, services, and folders from Windows 10. So if you want to, you can just install them later on or use an offline installer from the official site of Microsoft.

Option 2 – Try renaming the inetsrv folder

The next option you can check out to resolve the problem is to rename the “inetsrv” folder. If you have uninstalled IIS from the Windows Features, this should remove the folders as well, however, it didn’t remove the folder then you have to delete the folders that are related to the IIS by following these steps:

• First, you have to boot into the Advanced Recovery Mode and from there, open Command Prompt.
• Next, execute this command to rename the folder from this location, C:Windowssystem32inetsrv: rename C:/Windows/system32/inetsrv/inetsrv.old
• Once done, boot into your computer normally and try to upgrade Windows 10 again, and check if the problem is fixed or not.

Option 3 – Try to move the folders related to IIS to a different drive

• Tap the Win + R keys to launch the Run utility and type “services.msc” in the field and hit Enter to open the Windows Services Manager.
• Next, look for the Application Host Helper Service from the list of services and stop it.
• Once done, take ownership of the “WinSxS” folder and then move the *windows-iis*.*” folders to another drive. You can just search using the “*windows-iis*.*” keyword in the Start Search.
• Next, tap the Ctrl + X keys and paste the folders to another drive.
• After that, start the update process for Windows 10 again.

We’ve already covered disabling Security Questions If you want to disable Security Questions on your Windows 10 computer then you’ve come to the right place as this post will guide you in doing exactly that. In this post, you will be disabling Security Questions using a PowerShell script. This PowerShell script is called “Update-AllUsersQA”. It is designed to remove or disable the security questions and answers for local users on a Windows 10 computer. It lets administrators take control of the security questions in the environment and at the same time minimizes the risk that comes with them. If a user has a Microsoft account that’s configured to sign in to Windows 10 then he will not probably notice the Password Recovery questions. On the other hand, if he has a chosen local account for installing Windows, he will e prompted to create three security questions that can be used to reset the password and log into the Windows 10 account in case there is any misfortune. However, if you do not have much use for these Security Questions, then you can definitely have them disabled using a simple PowerShell script which you can download from GitHub. For more details on how to disable security questions in a Windows 10 machine, refer to the steps provided below. Step 1: You need to first download the .ps1 file from the GitHub repository. Step 2: Once you’ve downloaded the file, open the PowerShell window with admin privileges. Step 3: After that, navigate to the folder where you had saved the .ps1 file. Then copy the address of the folder location. Step 4: Next, change the directory by using the following command:

cd "folder location address"

Step 5: After that, enter the following script to disable the security questions:

Update-AllUsersQA

Once you’ve completed the steps above, the Security Questions should be disabled and you will be notified with a message stating that the feature has been disabled. On the other hand, if you have a change of heart and you want to enable the Security Questions back, here are some steps you need to take: Step 1: First, open the PowerShell window as admin. Step 2: Next, run the same script with one more parameter such as:

Update-AllUsersQA -answer SecretAnswer

Step 3: And that’s about it. Do not forget to replace the Secret Answer with your preferred one and once you’re done, it will be set as the answer for all the Security Questions. Step 4: Now all that’s left to do is go to the Settings app to change the answer to the questions and you should be good to go.

What Is Sndvol32.exe Error?

Sndvol32.exe is actually an important part of the Windows operating system. Responsible for managing the sound-card volume and running programs properly, the problem occurs when error messages appear. The user will be unable to listen to music on the system. Usually, Windows XP users encounter the Sndvol32.exe error.

Solution

Error Causes

Sndvol32.exe error can be caused by any one or several of the reasons listed below.

• Accidental deletion of the DLL file from the system
• Damage to the DLL file due to spyware or virus infection
• Improper removal of software
• Unintentional overwriting on the DLL file by a mismatched version
• Obsolete hardware drivers
• Several obsolete/invalid registry entries
• Corrupt registry entries

Regardless of what triggers the Sndvol32.exe error, it is of utmost importance to take immediate measures to fix the problem and to keep it from occurring again.

Further Information and Manual Repair

If you are looking for ways to fix this error manually, the Windows functionality of System Restore will come into play in this particular scenario. In case the error is caused by a damaged or corrupt file, performing System Restore is an ideal choice as it will allow you to not only get a fresh copy of the operating system, it will be possible for you to remove the error at the same time as well. The procedure for performing System Restore is outlined below as follows.

• Click on the Start menu and type ‘System Restore’ in the search box.
• When the icon for ‘System Restore’ appears, click on it.
• Now type ‘Restore’ in the search box that appears on the start menu.
• The window for the System Restore center will now appear.
• Now you have two options. You can either opt for “Recommend Restore” which is the case where the system itself will choose a restore point for you or you can select “Choose a different restore point”. Users are advised to choose the latter option as it is more customizable.
• Users can now select from a list of restore points that have been created before. If you observe closely, you will realize that one of the restore points is prior to the occurrence of the Sndvol32.exe error.
• Click on the restore point. Once you have confirmed your selection, your system will restart and it will roll back to its previously selected restore point.

One recommendation is to perform the system restore in Windows Safe Mode. This is just to ensure that the System Restore is performed smoothly and any potential problems are kept at bay.

There are some new generation motherboards for laptops and PCs that bring in support for both the Unified Extensible Firmware Interface or UEFI as well as the Basic Input Output System or BIOS. The main advantage of UEFI over the traditional BIOS is the fact that UEFI supports a hard drive that has a capacity of more than 2 terabytes. However, the disadvantage of UEFI is that it only supports the x64 Windows operating system versions and that the hard drive is supposed to use the GPT structure. So if your PC is compatible with and supports UEFI and you want to change from Legacy to UEFI, then you’ve come to the right place as this post will guide you on how you can exactly do that without having to reinstall it. There are two ways to change Legacy to UEFI. You can convert MBR to GPT using either the built-in utilities in Windows or using the Recovery Environment. Before you proceed, make sure that your computer fulfills the following prerequisites:

• Your PC’s motherboard should support both Legacy and UEFI.
• Your PC should be running at least the 1703 Windows 10 version or newer on an MBR partition.

Once you’ve made sure that your computer covers the aforementioned prerequisites, refer to the given options below.

Option 1 – Convert MBR to GPT via Windows built-in utilities

• 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 UEFI Firmware Settings. This will take you to the BIOS. Boot Mode is typically available under Boot > Boot Configuration. Once you’re there, set it to UEFI and then save the changes you’ve made. After that, your computer will restart.

Option 2 – Convert MBR to GPT via the Recovery Environment

• When the message appears on your screen while running Windows Setup, you need to tap the Shift + F10 keys to open Command Prompt.
• Make sure to run Command Prompt as admin and then execute this command: exe /convert
• After that, wait until the process is completed. When it’s done, you have to go to the BIOS just like in the first given option above.
• As mentioned, you can usually find the Boot Mode under Boot > Boot Configuration. Once you’re there, set it to UEFI.
• Now save the changes made and exit as your computer will restart.

KMODE_EXCEPTION_NOT_HANDLED seems to be connected primarily to a third-party driver, e1d65x64.sys associated with the Intel(R) Gigabit adapter, NIC/Wired network NDIS (Network Driver Interface Specification) 6.x driver. Error is known to produce the dreaded blue screen of death or BSOD. Most usually error is connected with gaming on Windows 10 computer and it manifests itself during gaming sessions. If you are unlucky and you are faced with this unfortunate error we will be happy to try to help you and present with tips and tricks in order for you to find a solution for it. Before you proceed with the provided solutions, be sure you have sufficient disk space on the Windows drive, run Disk Cleanup and then run CHKDSK.

1) Run the Blue Screen Online Troubleshooter

Open Control Panel, change the view setting to icons. Click Troubleshooting, and click “View all” in the tasks pane. Click “Blue Screen”. This opens the Blue Screen Troubleshooter.

2) Run Driver Verifier

1. Start a Command Prompt window by selecting Run as an administrator, and type verifier to open Driver Verifier Manager.
2. Select Create standard settings (the default task), and select Next. You can also choose to Create custom settings to select from predefined settings, or to select individual options. For more information, see Driver Verifier options and rule classes and Selecting Driver Verifier Options.
3. Under Select what drivers to verify, choose one of the selection schemes described in the following table.

   Driver verifier table:

   Option	Recommended use
   Automatically select unsigned drivers	Useful for testing on computers that are running versions of Windows that do not require signed drivers.
   Automatically select drivers built for older versions of Windows	Useful for testing driver compatibility with newer versions of Windows.
   Automatically select all drivers installed on this computer	Provides maximum coverage in terms of the number of drivers that are tested on a system. This option is useful for test scenarios where a driver can interact with other devices or drivers on a system. This option can also exhaust the resources available for Special Pool and some resource tracking. Testing all drivers can also adversely affect system performance.
   Select driver names from a list	In most cases, you will want to specify which drivers to test. Selecting all drivers in a device stack allows the Enhanced I/O Verification option to track objects and check compliance because an I/O request packet (IRP) is passed between each of the drivers in the stack, which allows for a greater level of detail to be provided when an error is detected. Select a single driver if you are running a test scenario that measures system or driver performance metrics, or if you want to allocate the greatest number of resources available for detecting memory corruption or resource tracking issues (such as deadlocks or mutexes). The Special Pool and I/O Verification options are more effective when used on one driver at a time.

4. If you chose Select driver names from a list, select Next, and then select one or more specific drivers.
5. Select Finish, and then restart the computer.

3) Update network device drivers

Go to the official Intel website and try to find newer versions of drivers, if there are none perhaps you will need to revert back to the previous version.

4) Scan memory for issues

Run a memory test on your system, sometimes these errors can be traced back to a faulty RAM bank.

5) Stop over-clocking your PC

If you have overclocked your PC please reverse it back to its original state and see if that would solve the issue

6) Perform System Restore to the previous restore point

If none of the previous solutions have bared fruit, roll back to a previous restore point and that should solve the issue.

BSOD or Blue Screen of Death errors are one of the most common errors you can encounter on your Windows PC. One of these BSOD errors is the “ACPI_BIOS_ERROR”. If you suddenly get this error, it means that there is some problem in booting the operating system from your hard drive or Windows was not properly installed on your PC. In addition, this error could also mean that there is something wrong with the CMOS battery located in the motherboard. Unlike other BSOD errors, the workaround for this error is a bit different as these workarounds require a bit more expertise in updating the BIOS as well as setting the correct boot configuration. If you know are capable enough in troubleshooting the problem, refer to the instructions laid out below to fix the BSOD “ACPI_BIOS_ERROR”.

Option 1 – Try to remove the SSD and update the BIOS

The first thing you have to do is to check the primary storage devices on your PC. If you have just installed a new hard drive or SSD recently on your computer, then it’s most likely the cause of the BSOD error. Moreover, you should also ensure that your BIOS is up-to-date to the latest available build.

• Remove the SSD/HDD and inject a different HDD that was already preinstalled in your Windows PC.
• After that, update the BIOS to the latest available build. After updating it, insert the old SSD/HDD and then try to boot your PC again. The problem should be fixed now. If not, refer to the next given option.

Option 2 – Try to check the CMOS battery and reset the CMOS module

As mentioned earlier, the CMOS battery might also be the one that’s causing the problem. It is a physical component of the motherboard and is a memory chip that contains all the settings configuration on your computer and is also powered by a battery. So if your battery loses power, the CMOS will be reset and as a result, all the configurations will be gone as well. It is also possible that the CMOS module is not properly working and every time things are saved, they are properly written due to the battery. That’s why you have to consider changing the CMOS battery and see if it fixes the problem. In addition, you also have to make sure that you completely reset the CMOS module and then try booting your PC again.

Option 3 – Try to check the BIOS settings

If the BIOS settings are incorrect, chances are that’s the reason why you’re getting the “ACPI_BIOS_ERROR” BSOD error. Every BIOS has different settings which you can make use of to enhance your computer experience. So make sure that your BIOS is up-to-date and that the settings are in accordance with your requirement. Another thing you can try is to disable the Legacy USB and the Legacy BIOS in the BIOS settings if you are trying to install a 64 bit Windows version. Make sure that you also enable AHCI before plugging in the installation drive on your PC. Moreover, ensure that your PC is using IDE or Integrated Drive Electronics mode instead of SATA or Serial Advanced Technology Attachment. Aside from that, try to check the extracted setup if it is in NTFS format, if it is, you should extract the ISO in FAT32 and use it to install Windows.

Option 4 – Try to reset the ACPI Compliant Control Method

ACPI or Advanced Configuration and Power Interface provide an open standard that operating systems can use to detect hardware, perform power management, as well as monitor the status of your device and provide information for other processes. Chances are, there are some misconfigurations with this module on your PC that lead to believing that there is no battery present. That’s why you need to reset it and see if it fixes the BSOD error or not.

• Boot your PC into Safe Mode.
• Tap the Win + R keys to open the Run dialog box.
• Type in “devmgmt.msc” in the field and tap Enter to open the Device Manager.
• After opening the Device Manager, go to the “Batteries” section and click it to expand it and then right-click on the “Microsoft ACPI-Complaint Control Method Battery” option and click on Uninstall.
• After you disable the module, click on any empty space and then click the “Scan for hardware changes” option.
• Then check if you can now boot your PC normally and without the BSOD error.

Blizzard is one of the most beloved game company which brought some of the most and greatest titles in PC gaming. Blizzard has released its own launcher in which you can launch games, sadly sometimes launcher does not want to work and fails to connect. If this happens to you be sure to:

1. Reset your network devices to make sure your router hasn't become flooded with data.

   Power cycling your modem and router allows them to reset and re-establish a connection to your ISP. Follow these steps to completely power cycle the devices in your network connection:Note: If your modem has a battery backup, you will need to take the battery out or use the reset button on the modem.

   1. Shut down all computers connected to the modem/router.
   2. Power down and unplug the modem and the router if you're using one.
   3. Allow to sit for 60 seconds unplugged.
   4. Plug in and turn on the modem and router, and allow them to completely boot up until the front panel connection lights on the modem show a steady connection.
   5. Start the computer and allow it to completely boot up.

2. If you're using a wireless connection, optimize your internet connection to rule out a connection issue.

   If you're experiencing issues with your low-speed or wireless internet connection, follow the steps below to troubleshoot the problem.

   1. Try plugging your computer directly into your modem.
   2. Shut down other programs that access the internet, such as other games or download programs.
   3. Satellite, mobile phone, and WiMax internet connections are not stable connections and may cause further connection issues when playing Blizzard games. If possible, consider switching to a more stable connection.

3. Update your drivers and operating system to resolve any compatibility issues.

   Out-of-date drivers and operating systems can cause a variety of issues and are one of the first things to check when a game is having problems. The instructions below will help you check and update your drivers.

   • Even new computers can have out-of-date drivers and operating systems because updates are released routinely.
   • Some games and programs might run fine on a system with old drivers, but outdated drivers can still create technical issues with specific games or programs.
   • Check our supported video cards articles to make sure your hardware is compatible:
     • World of Warcraft
     • Hearthstone
     • StarCraft II
     • Diablo III
     • Heroes of the Storm
     • Overwatch

   Refer to the steps below to update drivers and software for your operating system.

4. Release and renew your IP and flush your DNS to resolve any network conflicts.

   1. While on the desktop, press Windows Key and type CMD.
   2. Right-click Command Prompt and select Run as administrator.
   3. Type ipconfig /release in the command prompt.
   4. Wait a few seconds for a reply that the IP address has been released.
   5. Type ipconfig /renew in the command prompt.
   6. Wait a few seconds for a reply that the IP address has been re-established.
   7. Type ipconfig /flushdns in the command prompt.
   8. Close the command prompt and attempt to make a connection.

5. Close all other applications to resolve software conflicts and free up resources.

   Before trying the steps below, close unnecessary programs and restart your computer. Identify Problematic Startup Items

   1. Press Ctrl+Shift+Esc to open the Task Manager.
   2. Click More Details.
   3. Select the Startup tab.
   4. Right-click on each item and select Disable.
   5. Restart the computer.

   If this resolves the issue, enable the startup application one at a time to determine which one is causing the problem. You will need to restart between each application you enable. Note: To re-enable startup applications, follow steps 1-4 and select Enable.

6. Delete the Battle.net Tools folder to automatically rebuild outdated or corrupt files.

   1. Close Blizzard processes.
      1. Press Ctrl + Shift + Esc to bring up the Task Manager.
      2. Click the Processes tab.
      3. Select all Agent, Blizzard Battle.net desktop app, and game processes, and click End Process.
   2. Navigate to the folder containing the Battle.net directory:
      1. Press Windows Key + R to open the Run dialogue.
      2. Type C:\ProgramData\ into the Open field and press Enter.
   3. Delete the Battle.net folder.
   4. Run Battle.net and update the game to see if the issue persists.

   If the error persists after you try these steps, another program may be causing the problem. Restart your computer and delete the Battle.net folder one more time.

   Note: The above steps may cause the Blizzard Battle.net desktop app to forget game install locations. If your games can’t be found, you will see Install on the Blizzard Battle.net desktop app game tab instead of Play. To find your installation, click Locate this game or run the game launcher.

When trying to run Computer Management, or when running mmc.exe or compmgmt.msc from a command prompt you get the error that the application has been blocked for your protection then keep reading in order to solve the issue. This is a permission issue where if a regular user tries to run such system tools will result in saying that it has been blocked. Along with this, you may have a Group Policy issue. This can be fixed, but you will need admin permission to achieve it. It’s because when they are run from the command prompt with elevated privileges, it works.

1. Change Group Policy Settings

   If your account is an admin account, and you are still facing the issue, then change the group policy settings: Open Group Policy Settings by typing gpedit.msc in the run prompt followed by pressing ENTER Navigate to User Configuration > Administrative Templates > Windows Components > Microsoft Management Console > Restricted/Permitted snap-ins Locate Computer Management policy, and double click to open it Enable it, exit Group Policy. When Enabled: The snap-in is permitted and can be added into the Microsoft Management Console or run from the command line as a standalone console. When Disabled: The snap-in is prohibited and cannot be added into the Microsoft Management Console or run from the command line as a standalone console. An error message is displayed stating that the policy is prohibiting the use of this snap-in.

2. Temporarily disable UAC

   UAC is the user access control panel, and if you need to run the command right away, you can choose to disable it for some time. Click on the Start button, and then type UAC to find the User Account Control Settings. Click to open, and then slide down the notification setting at the bottom. It will temporarily allow launching the application as there is no check. However, make sure to switch to default once you are done.

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.

Each time you open an application inside your Windows 11 operating system, it is opened with standard privileges. Now, please note that your account privileges and application privileges are two different things, you might be the administrator of the system but when you open the app, it still opens with standard privilege. Most of the time running applications with typical settings is fine but from time to time we might have some applications that will require running with administrator privilege in order to work properly. In this case, it is very easy to do it, you just right-click and choose run as administrator. Although a very easy solution, it can be quite annoying if running the app is on a daily basis or even more times per day. If this is the case then right-clicking and choosing to run as administrator can be a daunting task, sometimes you can even forget to run it like this in heat of work and some unforeseen consequences might occur. Luckily there is an easy hack so you can open the chosen application each time as an administrator with a simple double click each time.

Setting application to run as administrator always

1. Locate application executable file
2. Right-click on in and choose properties
3. Click on the Compatibility tab
4. Check the box next to Run this Program as an Administrator
5. Click on Apply
6. Click on OK

From now on each time you open an application normally with a double click, it will be opened as administrator privileges.