Perform Voice Activation Troubleshooting

Booting the Windows computer system includes loading it from the various boot devices such as drivers, network as well as USB drives when the computer is turned on. The instant the startup sequence is done loading the operating system the system hardware will be ready to perform some complex operations – in this process, the Boot Log in Windows 10 is a record that maintains the list of success or failure of many pieces of Windows 10 system during the booting process. In other words, the Boot Log is the one that keeps a record of all that has happened while loading from the computer storage system to the memory during the boot process. It is available for several devices like network, hardware devices, and the operating system which assist in detecting issues during the boot process and other issues with regards to troubleshooting. Through Boot Log, you’ll know which drivers were unloaded and loaded from the start of the system during the boot process. You have the option to either disable or enable this feature on your Windows 10 PC. Named as “ntbtlog.txt”, the log file lists all the successfully loaded processes and the unsuccessful ones during the boot process. It is saved to the drive C:Windowsntbtlog.txt. As mentioned, you can enable or disable this feature in two ways – the first one is by using the System Configuration or MSConfig while the second one is using the Command Prompt. In this post, we’ll show you how you can enable or disable Boot Log in Windows 10 either way.

Option 1 – Enable or Disable Boot Log using System Configuration

Enable Boot Log:

• Tap the Win + R keys to open the Run dialog box.
• Then type in “msconfig” and click OK to open System Configuration.
• After that, go to the boot tab and check the checkbox labeled “Boot Log” under the Boot options so that you can enable the Boot Log feature.
• Then click on OK to save the changes made.
• Next, click on the Restart button in the prompt window to get started with the Boot Log process.
• After restarting your PC, go to C:Windowsntbtlog.txt to open the boot log.

Note: As pointed out earlier, the log file contains a list of all the successfully loaded drivers and also the list of drivers that failed to load during the boot process and every time you restart the system, the boot log file will keep on updating and will eventually increase the list of entries. For you to locate the drivers and make your troubleshooting a lot easier, I advised disabling the boot log after troubleshooting. To disable the boot log using System Configuration, refer to the steps below. Disable Boot Log:

• Tap the Win + R keys to open the Run dialog box.
• Then type in “msconfig” and click OK to open System Configuration.
• After that, go to the boot tab and unmark or uncheck the checkbox labeled “Boot Log” under the Boot options so that you can disable the Boot Log feature.
• Then click on OK to save the changes made.

Option 2 – Enable or Disable Boot Log using Command Prompt

Enable Boot Log:

• Go to the Start Menu and then type in “command prompt” in the search bar.
• After that, right-click on the Command Prompt option and select the “Run as administrator” option.
• After opening Command Prompt, type in “bcdedit” and tap Enter.

Note: You have to find the Identifier of the current operating system first to enable the Boot log. You can find it under the Windows Boot Loader section in the “Description” field and in this case, it’s Windows 10. You can also find the operating system identifier under the Windows Boot Loader section next to the field name identifier.

• To check if the boot log entry is disabled or enabled, go check the “Bootlog” field under the Windows Boot Loader. And if it turns out that the “bootlog” entry is enabled, the entry will be “Yes”. Otherwise, the entry will be “No”.
• Next, type in the following command with the operating system identifier to enable the boot log.

bcdedit /set {identifier} bootlog Yes

Note: In the command given above, make sure that you replace the given system identifier with your computer’s system identifier. For instance: In this example, the identifier was replaced with the actual operating system identifier as current.

bcdedit /set {current} bootlog Yes

• Afterward, restart the system to start the Boot log process.
• After the restart, go to C:Windowsntbtlog.txt to open the boot log.

Note: Every time you restart your computer, the boot log file will keep on updating which will increase the size of the log eventually. So if you want seamless and easier troubleshooting, it is advised to disable the Boot log after you troubleshoot. To disable it using the Command Prompt, here’s what you have to do. Disable Boot Log:

• Go to the Start Menu and then type in “command prompt” in the search bar.
• After that, right-click on the Command Prompt option and select the “Run as administrator” option.
• Once the Command Prompt is opened, type in the following command and then tap Enter to disable the boot log feature.

bcdedit/ set {identifier} bootlog No

Note: In the command given above, you need to replace the given system identifier with your computer’s system identifier. For instance: In this example, the {identifier} was replaced with the actual operating system identifier as {current}.

bcdedit /set {current} bootlog No

• Now close the Command Prompt.

What is Error 1723?

Error Code 1723 is a peculiar error type common in Windows PC. It is related to the Windows Installer package. This error is displayed in the following format:

"Error 1723- There is a problem with this Windows Installer package. A DLL required for this install could not be run. Contact your support personnel or package vendor...”

You are most likely to come across the error code 1723 if the Java installation is not completed successfully. In other words, the error indicates that the installation process has failed.

Solution

Error Causes

The 1723 error may occur due to several reasons, the most common being:

• Corrupted installers
• Files are not extracted successfully
• Registry problems
• Missing DLL files

Further Information and Manual Repair

To resolve this issue on your PC, you don’t always have to hire a professional technician and pay hundreds of dollars to get it fixed. The error code 1723 may not be a common Windows PC error but it is easy to fix. Here we have listed some of the best and easiest DIY ways to resolve this error on your system. These solutions are so easy to perform that even if you are not a computer programmer or technically adept, you can work through them and resolve the error in just a few simple clicks. So, let’s get started:

Solution 1: Install the latest Java Version

If the Java version previously installed on your system is not working properly and showing 1723 error messages then it is advisable to install the latest Java version. However, to do this first you will have to uninstall the old version and then download the latest Java version on your PC from a trusted website to ensure it does not contain malicious viruses and malware.

Solution 2: Ensure the Required Files are extracted in the ‘Temp’ Folder for Installers

Another method to resolve the 1723 error code is to check whether the required files are extracted in the temp folder for installers or not. The error may occur if the location is incorrect and the account is not permitted to extract files in the temp folder. In this scenario, the best way to resolve the issue is to change the permissions of the temp folder. This can be done by logging in to your account and opening file explorer or ‘My Computer’. Now copy and paste this link address in the address bar: DL:UsersUSERNAMEAppDataLocal. Please note, here DL is the drive letter of the Windows drive, and in the username insert the username of the account that you are using. Now right-click the ‘temp’ folder. Select properties and click on the Security tab. After that click edit below the list and press add. Again type the username here and click OK. The next step is to select the added account from the list and tick ‘FULL CONTROL’ box under ‘Permissions for Username’. Click OK and then close the properties. Once this process is complete, now try running the installer again. This will most likely resolve the issue. Nonetheless, if the error still persists, then this means the underlying cause of the error is deeper than you think. The error may be related to registry issues. In such situations, try solution 3 to fix the error 1723 on your system.

Solution 3: Download Restoro.

When the error code 1723 is triggered due to registry issues, then it is advisable to scan your PC with Restoro. Registry issues should be resolved immediately because they pose serious threats to your system. It can lead to system failure, crash and valuable data loss. Registry basically saves practically all the information and activities performed on your PC including the unnecessary and obsolete files like junk files, cookies, temporary files, and invalid entries. If these files are not removed they can corrupt the registry, damage dll files and installers thereby generating error codes like 1723 on your system. The easiest way to repair and clean the registry in seconds is to run Restoro on your PC. It is a smart, intuitive, advanced, and multi-functional PC repair tool. It is embedded with multiple powerful utilities and is a one-stop solution for all PC related issues. This software is compatible with all Windows versions. It is deployed with a highly functional registry cleaner that scans and detects all registry issues on your PC and removes them right away. It wipes out the unwanted files, repairs the damaged dll files and restores the registry. Other powerful utilities that are embedded in this software include an antivirus, a system optimizer and Active X controls and class modules. To resolve 1723 error code on your PC today, click here to download Restoro.

You might have experienced a situation where your Windows computer was interrupted due to some battery issues or power failure. It could be that the upgrade process was interrupted because you’ve signed out of your computer or you restarted it by accident. In this case, you will most likely get a Windows Update or Upgrade error 0x80200056. If you are getting this error, read on as this post will guide you in fixing it. This kind of error pops up when the upgrade process was interrupted and could be caused by anything but the baseline here is that your computer was restarted accidentally or someone could have signed out your PC. To resolve the problem, here are some fixes you ought to try:

Option 1 – Try updating or upgrading your computer again

This is the basic thing to do since the process was suddenly interrupted. Just log in to your account and restart the Windows Update or Upgrade process but make sure that your internet connection is stable and that you don’t touch anything so as not to interrupt the upgrade/update process again.

Option 2 – Check if your PC is plugged in or if the battery is full

It is always best to update your computer always when you’re really sure that the power won’t fail. If you’re using a desktop computer, make sure that everything is plugged in. And if you’re using a laptop when this error occurred, make sure that its battery is at 100% but it’s better if you just plug it into power just in case as there are times when the Windows update or upgrade gets stuck for too long like for hours so it will really help if your device is connected to power.

Option 3 – Try running the Windows Update Troubleshooter

Running the built-in Windows Update troubleshooter could also help you resolve the Windows Update errors as well as the error 0x80200056. To run it, go to Settings and then select Troubleshoot from the options. From there, click on Windows Update and then click the “Run the troubleshooter” button.

Option 4 – Delete the contents in the SoftwareDistribution folder

The Software Distribution folder in the Windows operating system is a folder that can be found in the Windows directory and is used to store files temporarily which might be required to install the Windows Update on your PC. Thus, it is required by the Windows Update and maintained by WUAgent. A lot of users tried deleting the files in this folder to fix the problem and so far it has worked. Like them, you can try clearing the Windows Update cache by simply deleting the contents of the folder named “SoftwareDistribution” since Windows apparently can’t clear and re-download the update contents once they are corrupted. Thus, deleting the contents of this folder will make Windows download the contents again which will fix the problem. To do that, follow the steps below.

• Open the WinX Menu.
• From there, open Command Prompt as admin.
• Then type in the following command – don’t forget to hit Enter right after typing each one of them.

net stop wuauserv net stop bits

• After entering these commands, it will stop the Windows Update Service and the Background Intelligent Transfer Service.
• Next, got to the C:\Windows\Software\Distribution folder and get rid of all the folders and files thereby tapping the Ctrl + A keys to select them all and then click on Delete. Note that if the files are in use, you won’t be able to delete them.
• Once all the contents in the Software Distribution folder are deleted, restart your PC and then go back to Command Prompt and input the following commands again.

net start wuauserv net start bits

Since the folder has already been flushed, it will be populated afresh the instant your restart your computer and open Windows Update.

Option 5 – Try running the 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 that might be causing the error 0x80200056. 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.

Option 6 – Run the Chkdsk utility to repair hard disk errors

You can also run the Chkdsk utility to resolve the Windows Update error 0x80200056. 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 commands listed below, and don’t forget to hit Enter right after you type in each one of them and if you have installed Windows to some different directory, you must replace “C” with the name of the drive you’ve installed Windows with.
• chkdsk C: /r /x
• chkdsk C: /f

Option 7 – Run the DISM tool to repair the Windows Update client

The Windows update/upgrade error 0x80200056 might be caused by some issues in the Windows Update client so you need to run the DISM tool to repair it. Note that you have to use another computer or another Windows from a shared network to fix it.

Creating a new Windows 10 account comes with options related to privacy. For instance, you will see the options to disable or enable Speech recognition, Find my device, Location service, Inking & typing, and many more. And if you often have to create a test account in Windows 10 v1809 and you don’t want to give this option, you can just disable the Privacy Settings Experience at sign-in on your Windows 10 PC using a couple of instructions given in this guide. To disable the Privacy Settings Experience, you can use the Registry Editor and the Group Policy Editor. But before you get started, you need to log in as an administrator. Moreover, it would also be better if you create a backup copy of the Registry files as well as create a System Restore Point before you make any changes. After you have those things covered, refer to the steps given below to disable the Privacy Settings Experience at sign-in on your Windows 10 PC. Since there are two ways to get things done, choose one option that you prefer.

Option 1 – via Registry Editor

• Tap the Win + R keys to open the Run dialog box and type “Regedit” in the field and hit Enter to open the Registry Editor.
• Next, navigate to this path: HKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftWindowsOOBE
• From there, look for the OOBE value and if you can’t find it there, you can just create it. To do so, right-click on the Windows key and select New > Key, and then name it “OOBE”.
• After that, right-click on the OOBE value and select New > DWORD (32-bit) value, and name it “DisablePrivacyExperience”.
• Then double click on DisablePrivacyExperience and set its value to “1”.
• Now exit the Registry Editor and restart your PC for the changes to take effect.

Option 2 – via the Group Policy Editor

• 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.
• After that, navigate to this path: Computer Configuration > Administrative Templates > Windows Components > OOBE
• Next, look for a setting named “Don’t launch privacy settings experience on user login” located on your right-hand side and then double click on it and select Enabled.
• Now click on the Apply and OK buttons to save the changes made.
• Restart your PC.

Getting a few errors here and there when updating your Windows 10 computer is not uncommon. Some of these errors won’t allow the Windows Update service to initiate while the other ones will halt the process while it’s running. So in this post, we’ll show you what you can do to fix the Windows Update error 0x80070020. The Windows Update error 0x80070020 is most likely caused by some programs installed in the system which interferes with the Windows Update process. It might be an antivirus program, an incompatible program, a potentially unwanted program, or worse, malware. In addition, corrupted or missing files might also be the culprit. Whichever the cause may be, here are some suggestions you need to check out to resolve the problem.

Option 1 – Try to reset the Windows Update components manually

• To manually reset the Windows Update components, first, you need to stop the Background Intelligent Transfer Service, Windows Update, and the Cryptographic Services. To do so, run the following command in Command Prompt and make sure to press Enter after you enter each one of them:
  • net stop bits
  • net stop wuauserv
  • net stop cryptsvc
• Next, delete the “qmgr*.dat” file in order to reset the Windows Update components. To do delete this file, run the following command in Command Prompt:
  • Del “%ALLUSERSPROFILE%Application DataMicrosoftNetworkDownloaderqmgr*.dat
• Now you have to rename both the SoftwareDistribution and Catroot2 folders by entering the following command in Command Prompt:
  • Ren %systemroot%SoftwareDistributionSoftwareDistribution.bak
  • Ren %systemroot%system32catroot2catroot2.bak
• Reset BITS and Windows Update service by entering the following commands in Command Prompt:

• • sc.exe sdset bits D:(A;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCLCSWLOCRRC;;;AU)(A;;CCLCSWRPWPDTLOCRRC;;;PU)
  • sc.exe sdset wuauserv D:(A;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCLCSWLOCRRC;;;AU)(A;;CCLCSWRPWPDTLOCRRC;;;PU)
• Now enter the following command:

• cd /d %windir%system32

• RE-register BITS and other Windows Update related files by typing each one of the following commands:

• • regsvr32.exe atl.dll
  • regsvr32.exe urlmon.dll
  • regsvr32.exe mshtml.dll
  • regsvr32.exe shdocvw.dll
  • regsvr32.exe browseui.dll
  • regsvr32.exe jscript.dll
  • regsvr32.exe vbscript.dll
  • regsvr32.exe scrrun.dll
  • regsvr32.exe msxml.dll
  • regsvr32.exe msxml3.dll
  • regsvr32.exe msxml6.dll
  • regsvr32.exe actxprxy.dll
  • regsvr32.exe softpub.dll
  • regsvr32.exe wintrust.dll
  • regsvr32.exe dssenh.dll
  • regsvr32.exe rsaenh.dll
  • regsvr32.exe gpkcsp.dll
  • regsvr32.exe sccbase.dll
  • regsvr32.exe slbcsp.dll
  • regsvr32.exe cryptdlg.dll
  • regsvr32.exe oleaut32.dll
  • regsvr32.exe ole32.dll
  • regsvr32.exe shell32.dll
  • regsvr32.exe initpki.dll
  • regsvr32.exe wuapi.dll
  • regsvr32.exe wuaueng.dll
  • regsvr32.exe wuaueng1.dll
  • regsvr32.exe wucltui.dll
  • regsvr32.exe wups.dll
  • regsvr32.exe wups2.dll
  • regsvr32.exe wuweb.dll
  • regsvr32.exe qmgr.dll
  • regsvr32.exe qmgrprxy.dll
  • regsvr32.exe wucltux.dll
  • regsvr32.exe muweb.dll
  • regsvr32.exe wuwebv.dll
• Now type each one of those commands below.
  • net start bits
  • net start wuauserv
  • net start cryptsvc

Option 2 – Install the updates in a Clean Boot State

You might want to try putting your computer in a Clean Boot state and then install Windows Updates again without any trouble. During this state, you can start the system with a minimum number of drivers and startup programs that will surely help you in isolating the root cause of the issue.

• 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.)
• After that, try to install the Windows Updates or upgrade again.

Option 3 – Clear the contents of both the SoftwareDistribution and Catroot2 folders

• Open the WinX Menu.
• From there, open Command Prompt as admin.
• Then type in the following command – don’t forget to hit Enter right after typing each one of them.

net stop wuauserv net stop bits

• After entering these commands, it will stop the Windows Update Service and the Background Intelligent Transfer Service.
• Next, go to the C:/Windows/SoftwareDistribution folder and get rid of all the folders and files thereby tapping the Ctrl + A keys to select them all and then click on Delete. Note that if the files are in use, you won’t be able to delete them.
• Once all the contents in the Software Distribution folder are deleted, restart your PC and then go back to Command Prompt and input the following commands again.

net start wuauserv net start bits

 Since the folder has already been flushed, it will be populated afresh the instant your restart your computer and open Windows Update.

Option 4 – Try to run the Windows Update Troubleshooter

Running the built-in Windows Update troubleshooter could also help you resolve the Windows Update error 0x80070020. To run it, go to Settings and then select Troubleshoot from the options. From there, click on Windows Update and then click the “Run the troubleshooter” button. After that, follow the next on-screen instructions and you should be good to go.

Option 5 – Try restarting the Windows Update Services

• Open the Services Manager.

From there, make sure that you set the following services and Startup types:

• Background Intelligent Transfer Service: Manual
• Cryptographic Service: Automatic
• Windows Update Service: Manual (Triggered)

If you encounter an error saying, “error accessing the registry” when you try to merge a registry key on your Windows 10 computer, you’re not alone as some users also experienced the same problem. According to these users, they encounter the error after they’ve re-installed their Windows version and tried to open a .reg file. Based on the reports, this error could occur if the registry file does not have administrative privileges. Meaning to say, the program does not have the necessary permission to merge the .reg file. This is common with fresh installs as well as reinstalls. Moreover, this kind of issue could also occur due to system file corruption. Whichever the case may be, here are some troubleshooting tips you can check out to resolve the error.

Option 1 – Try to import the .reg file with admin privileges

As pointed out, the error may be due to a lack of admin privileges. It could be that the Registry Editor does not have admin privileges to merge the registry file. This is common with new Windows installations especially since the Registry Editor hasn’t been opened before. So you need to import the .reg file again and this time, with admin privileges.

• Tap the Win + R keys to open the Run dialog box.
• Then type “Regedit” in the field and tap the Ctrl + Shift + Enter keys to open the Registry Editor with admin privileges.
• A User Account Control or UAC prompt will appear where you have to click Yes to proceed.
• After opening the Registry Editor, go to File > Import using the ribbon bar at the top.
• Next, use the import menu to go to the location of the file you were trying to merge. Once you’ve found it, click Open to merge it with your current registry. This should fix the problem. If not, refer to the next options below.

Option 2 – Try performing a System Restore

Running System Restore can also help you fix the error when accessing the Registry. You can do this option either by booting into Safe Mode or in System Restore. If you are already in the Advanced Startup Options, just directly select System Restore and proceed with the next steps. And if you have just booted your PC into Safe Mode, refer to the steps below.

• Tap the Win + R keys to open the Run dialog box.
• After that, type in “sysdm.cpl” in the field and tap Enter.
• Next, go to the System Protection tab then click the System Restore button. This will open a new window where you have to select your preferred System Restore point.
• After that, follow the on-screen instructions to finish the process and then restart your computer and check if the problem is fixed or not.
• Once the next startup is complete, you have to merge or import the file again and see if the error is now fixed or not.

Option 3 – Try to perform repair install by creating a Windows 10 installation media

• Click this link and then click the Download Tool Now button.
• Next, click the “Use the tool to create installation media (USB flash drive, DVD, or ISO file)…” option and follow the next given instructions on the screen.
• Now select the ISO file option in step 5.
• After that, you should now have an ISO file.
• Next, go to the location where you’ve downloaded the ISO file.
• Then right-click on the Windows 10 ISO file and select the Open with option and then select File Explorer.
• Now click on “setup.exe” and follow the next instructions that appear on the screen. When asked, you have to select either Nothing (clean install) or Keep personal files only option. Take note that you must not select the “Keep personal files, apps, and Windows settings since it doesn’t really work.

Option 4 – Try running the System File Checker Scan

As mentioned, the error when accessing the Registry might be caused by file corruption. And that’s where the SFC scan comes in. The SFC or System File Checker scan could detect and automatically repair damaged system files. 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. 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.

• Now restart your computer.

In this post, you will be guided on how to import and export the WSL distros in your Windows 10 computer. WSL, also known as Windows Subsystem for Linux, is a compatibility layer needed to run Linux binary executable in Windows 10, as well as the Windows Server 2019. In case you don’t know, when you reinstall or reset Windows 10, all of its configuration data stored with the WSL distros gets deleted. Going back or restoring the configuration can be quite challenging but worry not for Microsoft has already got this covered as you can now import and export the WSL or Windows Subsystem for Linux distros. There are three aspects that you have to deal with when you import or export WSL distros in your Windows 10 computer, such as importing WSL distro, exporting WSL distro, and uninstalling the imported WSL distros. Before you proceed to the instructions provided below, make sure that all your installed distros are updated via Microsoft Store. Once you have this covered, follow the options below.

Option 1 – Import the WSL distro

• Type “command prompt” in the Start Search and from the search results, right-click on Command Prompt and then select the “Run as administrator” option.
• After opening Command Prompt as admin, execute this command: wsl --list –all
• The command you entered will list all the installed WSL distros on your computer. And now it’s time for you to import a WSL distro by executing this command: wsl --import <Name of the distro> <Fill path to save the backup .tar file>

Note: In the given command above, replace “<Name of the distro>” with the name of the distro you want to import and replace “<Fill the path to save the backup .tar file>” with the location where you want to save the .tar file.

Option 2 – Export the WSL distro

• Type “command prompt” in the Start Search and from the search results, right-click on Command Prompt and then select the “Run as administrator” option.
• After opening Command Prompt as admin, execute this command to see the list of all the installed WSL distros in your computer: wsl --list –all
• After that, execute this command to export a WSL distro: wsl --export <Name of the distro> <Fill path to save the backup .tar file>

Option 3 – Uninstall the imported WSL distro

• Open Command Prompt with admin privileges.
• Next, execute this command to view the list of all the installed WSL distros: wsl --list –all
• After that, execute this command to uninstall an imported WSL distro: wsl --unregister <Name of the distro>
• Once it’s done, close Command Prompt and restart your computer.

Error Code 0x80240017 – What is it?

Error code 0x80240017 is associated with installing or updating a Windows Store app. This error is more common in Windows 8 and Windows 8.1. It appears due to missing certain system files and also corrupt registry.

Common symptoms

• When you try to install a Windows Store app on a PC running Windows RT 8.1, Windows 8.1, or Windows Server 2012 R2, the installation fails and you receive an error message: 0x80240017
• Certain apps may become unresponsive.
• You may not be able to download apps or Windows update
• You may have difficulty updating or installing and uninstalling other built-in programs inside Windows 8 and Windows 8.1.
• When you have multiple applications running, you may experience crashes and freezes.

Solution

Error Causes

The error code 0x80240017 in Windows 8.1 or Windows 8 usually appears due to the fact that your system has changed after you installed a third-party application. It might also appear if registry entry has changed after a reboot of the operating system and you do not have the required permissions. Other causes may be due to:

• Corrupted, broken, or missing system files.
• Malware/spyware infection or virus attack
• Hardware/RAM decline
• Fragmented file
• Unnecessary or redundant program installations

Further Information and Manual Repair

Repairing Error Code 0x80240017 in Windows 8/Windows 8.1

Method 1:

Resetting Windows Store app:

1. Press and hold the Windows key and press R. This will open up the Run command
2. Now, type exe and hit Enter
3. Just wait for it to finish and it will re-launch Windows Store. Now, try and install the app you were trying to install which was previously showing an error.

This basic solution will delete the cache and reset Windows Store.

Method 2:

Using Windows troubleshooter:

1. Click on Search on the Charm bar and type Troubleshooting. Click on the very first option.
2. A new window will open. Click View all from the left pane.
3. Scroll down to the bottom and click on Windows update.
4. Troubleshooter window for Windows update will pop up. Click on NEXT. It may ask you for administrative permission.
5. The troubleshooter will automatically detect problems and fix them.
6. Now, close this window and try download/install the app which was previously showing an error.

Method 3:

Disable Proxy Settings: Disable proxy server on Internet Explorer

1. Press the Windows + R Run window will appear.
2. Type cpl and hit Enter
3. Click the Connections tab and click LAN settings
4. Under proxy server uncheck “Use a proxy server for your LAN”
5. Click OK

Now try to install apps from Windows Store.

Method 4:

Boot in Safe Mode:

1. Open Run command as previously described
2. Type MSConfig
3. Click on the Boot tab
4. Tick Safe boot in Boot option
5. Select Network
6. Click Apply and OK
7. Reboot your system

Your system will boot in Safe mode with Networking. You may now try and open Windows Store and should not see any errors.

Method 5:

Note: It is recommended that you back up your files and folders before attempting this step:

1. Move the mouse cursor over to the upper right side of the screen.
2. A menu will pop up on the left. Click on the “Settings” feature on the menu.
3. On the Settings window, click on the “Change PC settings.”
4. Now, left-click on the “Update and recovery” feature.
5. For the next step, left-click on the “Recovery” feature.
6. There is an option here saying “Refresh your PC without affecting your files.” There, left-click on the “Get started” button.
7. Now, follow the instructions on the screen to finish the Refresh process.
8. After the Refresh process has finished restart your Windows 8.1 or Windows 8 device.
9. Check again to see if the error 0x80240017 has been fixed.

If you do not possess the technical expertise required to accomplish this yourself or do not feel comfortable doing so, download and install a powerful automated tool to get the job done.

If you have encountered the “YOU ARE NOT AUTHORIZED TO ACCESS THIS WEB PAGE AS PER THE DOT COMPLIANCE” error while trying to visit a website using either Firefox or Chrome browser, then read on as this post will guide you on how you can fix this error. Apart from this error message, you might also see an alternative message that says, “Web Page Blocked! The page you have requested has been blocked because the URL is banned as per the Government Rules”. When you get any of the aforementioned error messages when visiting a website, this means that it has been marked. It is mostly recommended to not access the site as it might be blocked for some illegal reason. However, if you are certain that the website is legitimate and safe and you believe that it has been blocked by accident, then you can check out the given methods in this post to unblock and access the blocked or restricted website. There isn’t actually a straightforward way to remove the restriction on the website or the DOT compliance. And it won’t matter what browser you use as you will still get the same error. Thus, the best way to go about this issue is for you to bypass the ISP restriction. But before you proceed, keep in mind that the ISPs (Internet Service Providers) can block any website when a request goes through their servers.

Option 1 – Try changing the DNS

If the request to access the website does not go through the ISP’s DNS server, you might have a chance in accessing it by changing your DNS settings. You can try using the Google Public DNS.

• Tap the Win + R keys to open the Run dialog box.
• Then type “inetcpl.cpl” in the field and hit Enter to pull up the Internet Properties.
• After that, go to the Connections tab and select the LAN settings.
• From there. Uncheck the “Use a Proxy Server” option for your LAN and then make sure that the “Automatically detect settings” option is checked.
• Now click the OK and the Apply buttons.
• Restart your PC.

Note: If you are using a third-party proxy service, you have to disable it.

Option 2 – Try to install a Proxy Extension

You could also try installing a Proxy extension or Proxy software as it could also help you access the website you are trying to open as it allows you to access the blocked websites by routing the request through their server. Aside from that, it can also hide it from ISPs to make them look like the content is coming from the proxy servers.

Option 3 – Try using a VPN connection

There are instances when the network that your computer is logged on might have blocked your access to the website you are trying to open and so to fix it, you can try to use a VPN connection. There is a lot of free VPN software out there but just make sure that you install a trusted one. Once you’ve connected using VPN, try to open the website again and see if you can now access it.

Option 4 – Check the Windows Host file

You can also try to cross check the Windows Hosts file to find out if the website you are trying to open has been blocked because if it is, then it’s no wonder why you’re getting the ERR CONNECTION TIMED OUT error in Chrome. There are instances when some third party application modifies the file and add some websites to the block lists. So if the website is indeed blocked, you need to remove it from the list.

Option 5 – Try to contact your ISP

If none of the options given above worked, then you can try to contact your ISP as there are times when DOT clears a website, the ISPs are still blocking it. Thus, it’s probably better if you reach out to them and ask them to unblock the website from their end.

Isn’t it annoying when you get an error message pop up stating ‘Cannot find propsys.dll” or “propsys.dll not found” when you start your computer or open a particular program? The propsys.dll file is crucial to the Windows operating system. This file is located in one of the following locations: "C:\Windows", C:\Program Files, C:\WINDOWS\system32, or C:\Program Files\Common Files". And the propsys.dll error indicates that the propsys digital library file is damaged and corrupt. The propsys.dll error may lead to a very unstable operating system. It may also hamper your ability to access many programs on your computer, lead to program and system crash and slow down the system’s performance. Therefore, to avoid these system threats, it is advisable to fix the error immediately.

Solution

Error Causes

The common causes of propsys.dll file error are:

• Registry problem
• The propsys.dll file is damaged due to a virus or spyware
• Improper software removal
• Hardware Failure

The propsys.dll error message is displayed in either of the following forms:

• Propsys.dll not found
• Cannot find [Path]propsys.dll
• This application failed to start because propsys.dll was not found. Reinstalling the application may fix this problem
• The propsys.dll file is missing

Further Information and Manual Repair

There are many ways to fix the propsys.dll error. However, for optimum results from the fix, you must first identify the cause of the error and then choose the solution accordingly.

• Recommended Solution for Registry Issue

If you use your system daily the resulting wasted/invalid/junk entries may dilate the registries. This can result in registry malfunctioning which may result in a propsys.dll error on your screen. When this happens, it is advisable to use a registry cleaner to fix the problem. Registry cleaner helps clean up the junk entries and repairing the corrupted registries. For this, you will first have to download a registry cleaner repair tool. Download and install the software on your computer. After downloading it, click the start scan button to run. This helps scan and diagnose system errors on your computer in seconds. Once the scanning is complete, click on the fix button to repair the registry problem.

• Recommended Solution for File Damage and Corruption

Use the ‘System Restore’ option to restore corrupt and damaged files.  The ‘System Restore’ function will help you get a fresh copy back and simultaneously help fix the error. Here’s how to use and access the ‘System Restore’ function on your computer: Simply go to the start menu and in the search box type restore. Once you type, it will show you the system restore option. Now select ‘choose a different restore point’. After this, you will be presented with a list of restore points. Choose a point that you believe happened before the propsys.dll error. Confirm your selection and restart. Another alternative solution for file damage is to run a virus scan of your entire system; the damage could be related to a virus or malware infection.

• Recommended Solution for Hardware Failure

If a propsys.dll error occurs due to hardware failure, then it is advisable to update the drivers for hardware devices that you think are related to propsys.dll. For example, if you receive the propsys.dll error when you play a 3D video game, then try updating the driver for your video card.