Five Ways of Fixing Error Code 37

One of the important functions in the Windows operating system is the Task Scheduler. It can automatically run various tasks at a certain time where you’ll have to add a task that needs to be executed and then choose the time it has to run at. So when that time comes, the Task Scheduler will run the task automatically. However, some users reported getting an Error 0x80070057 where the Task Scheduler fails to start. This kind of error may be due to a disabled service that prevents the service from running. It is also possible that the antivirus program interfered with the task – it could be that the Task Scheduler is somewhat in the block list since the antivirus adds it to the list automatically when it’s installed. On the other hand, it could be that you lack administrator-level privilege which is why the Task Scheduler was not able to carry out the task. To fix this issue, here are some suggestions you can try.

Option 1 – Try to restart the Task Scheduler service

As mentioned, it is possible that the Task Scheduler service could be disabled. You could have disabled it when trying to enhance your computer’s performance and whatnot. Thus, you need to verify if it’s running or not and then restart it.

• First, you need to tap the Win + R keys on your keyboard to open the Run dialog box.
• Next, type “services.msc” in the field and click OK or tap Enter to open the Windows Services Manager.
• You will see a list of Services and from there, look for the Task Scheduler service and double click on it.
• After that, go to the General tab and click on the Startup Type options and then select “Automatically” from the given list.
• Click on the “RUN” option and select the “Restart the Service” option.
• And click on the “After Second Failure” option and then select the “Restart-Service” option again.
• Now click on the “After Subsequent Failures” tab and select the “Restart the Service” option.
• Finally, click on the Apply and OK buttons and then run the Task Scheduler and see if the issue is now fixed.

Option 2 – Try to temporarily disable the anti-virus program

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

Option 3 – Run the Task Scheduler with an administrator account

Like pointed out, the Task Scheduler Error 0x80070057 may be due to the lack of admin privileges. Thus, you have to log in to an administrator account and try running the Task Scheduler again. It is also recommended that the administrator account you’re going to use as a password when logging in.

Option 4 – Repair the Task Scheduler by deleting corrupted tasks

Note that a single corrupted file can cause big problems so this option is quite important. And for you to delete a corrupted task or any task from the Task Scheduler, you have to use the Registry Editor if you are not able to use the Task Scheduler interface. To do so, follow these steps:

• Tap the Win + R keys to open the dialog box for Run.
• Next, type in Regedit and click on OK or tap Enter to open the Registry Editor.
• Then navigate to this path: ComputerHKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionScheduleTaskCacheTree

Note: In this path, you can see all the tasks that are currently set in the Task Scheduler. And since it would be hard to tell which one of them is corrupted, you have to delete the latest one in Task Scheduler last. But before you do so, make sure that you take note of the ID of the tasks. And for you to get the ID, you have to select the task you wish to delete and double click on the ID string located on your right-hand side, and then copy it in the Notepad.

• Right-click on the task name and then delete it.
• After that, delete the very same GUID which you have copied earlier from these folders:
• ComputerHKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionScheduleTaskCacheBoot
• ComputerHKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionScheduleTaskCacheLogon
• ComputerHKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionScheduleTaskCacheMaintenance
• ComputerHKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionScheduleTaskCachePlain
• ComputerHKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionScheduleTaskCacheTasks

Note: You might not see the same GUID from these folders but if you see it, delete it right away.

• Next, navigate to this location: C:/Windows/System32/Tasks
• Delete the very same tasks you just deleted from the Registry Editor.
• Restart your PC and check if the Task Scheduler is back to its normal state or not.

Hello everyone and welcome to another tutorial on errortools.com, Windows itself when it is installed has a general idea about certain file types and how to open them, for example, image files would be opened with application photos, web links with the edge, etc. So when we double click on the known file type, Windows will start the default application for that type and open the file in it. But what if we do not want to open files in applications Microsoft thinks we should? What if we want to open the website in firefox or images in photoshop, or whatever. Luckily we can easily change which application Windows uses for which file type. Click on ⊞ WINDOWS to open the start menu and choose settings. On the settings screen, choose Apps. When the Apps screen opens on the left click on Default apps. On right, you will get a list of Windows default applications for certain types of files. Click on any application you would like to change and choose from the drop-down list a new one. Click on it and you are done.

One of the most useful built-in tools in Windows 10 is the Check Disk or CHKDSK utility. It is the one that maintains the integrity of the disk that’s connected to a computer which can be launched using the GUI or graphical user interface and using the command line. There are a lot of things that warrant the running of this built-in utility and one of these things is the readability of the disk. Recently, a number of users reported that they encountered an error when they tried to run the CHKDSK utility – the error states, “Cannot open volume for direct access”. This kind of error in CHKDSK appears each time the command line is launched according to the affected users. As per the users who encountered this issue, they receive the following error messages when they tried running a ChkDsk command:

“C:WINDOWSsystem32>chkdsk /f g: Cannot open volume for direct access. C:WINDOWSsystem32>chkdsk /f f: The type of the file system is NTFS. Volume label is 0529357401.”

To fix the “Cannot open volume for direct user access” error, here are some suggestions that might help. Follow them carefully.

Option 1 – Try running the CHKDSK utility on Boot

On the other hand, you can also try to run the CHKDSK utility on Boot so you can fix the error and recover any damaged segments of the drive.

• Open an elevated Command Prompt and enter this command: chkdsk /x /f /r
• After that, you will a message that says, “Chkdsk cannot run because the volume is in use by another process. Would you like to schedule this volume to be checked the next time the system restarts? (Y/N)”
• Type Y and tap Enter to schedule a CHKDSK scan once your computer reboots next time.

Option 2 – Try to run the Primary Hard Disk Self Test

The next thing you can do to fix the problem is to run the Primary Hard Disk Self Test by following the steps below.

• You need to boot your computer into the BIOS first.
• After that, go to the Diagnostics tab and select the “Primary Hard Disk Self Test” option. Note that it may be different depending on the motherboard with different manufacturers but they should imply the same thing.
• Now, wait until the test is completed, and then boot your computer normally.

Option 3 – Try to check the hard drive’s health

The next thing you can do to resolve the issue is to check the health of your hard drive using the WMIC utility in the Windows Command Prompt. This utility will check if your hard drive has any problems which resulted in the “Cannot open volume for direct user access” error.

Option 4 – Try to disable various restrictions on your hard drive

You might also want to disable the various restrictions on your hard drive since it is possible that it is encrypted or restricted which explains why you are unable to perform any operations in it and throws the “Cannot open volume for direct user access” error instead. For instance, if you have BitLocker, you can try to disable it and see if it fixes the error or not.

Option 5 – Try to uninstall or disable the Drive Locking feature on your hard drive

You could also look for any Drive Locking feature on your hard drive that tricks disk changes as it might be the root cause of the problem. Thus, if you find one, you need to either uninstall or disable it and then execute a check disk command to resolve the problem.

Option 6 – Try to disable the application service

Disabling the application service can also help you fix the problem. How? Refer to these steps:

• Tap the Win + R keys to launch the Run utility and type “services.msc” in the field and then hit Enter to open the Services Manager.
• Next, scroll down among the list of services and look for the service related to the security software or disk checker software.
• Once you find it, right-click on that service and select Properties.
• After that, change its Startup type to Disabled and click on the OK and Apply buttons to save the changes made.
• Now restart your computer and don’t forget to enable the service back once the disk check is completed.

Option 7 – Try to use Repair Volume via Windows PowerShell

You could also try to use the Repair Volume using Windows PowerShell. All you have to do is open PowerShell as admin and type the “repair-volume -drive letter <DRIVE LETTER>” command and then tap Enter to run Repair Volume. This should resolve the error.

NDIS or Network Driver Interface Specification is a programming interface for the network interface cards that aids in the proper functioning of a system driver in a computer network. The NDIS helps the computer system in order to communicate with other connected devices and hardware components on a computer network. In relation, the ndis.sys file is a critical system file developed by Microsoft for the Windows operating system. As you know, sys files or system files are important parts of the Windows operating system as well as a repository of system driver settings used by Windows to communicate with the connected hardware and devices. The ndis.sys files are stored mostly in a driver folder at C:/Windows/System32/drivers and as mentioned, these files are essential for the system to function properly. Although the presence of ndis.sys system file is not yet known to affect the normal functioning of the Windows OS, some of the Windows 10 users reported that they encountered ndis.sys blue screen errors on their PCs. Blue Screen of Death errors or Stop errors usually occurs when you open a program or a function. Moreover, it could also occur when the driver gets loaded during the system startup or during system shutdown. It isn’t yet clear what really causes the ndis.sys blue screen error. However, like other Stop errors, it may occur due to corrupted files, misconfigured device drivers, bad drivers, corrupted Windows Registry, missing or damaged system files, and malicious programs. Aside from the aforementioned reasons, the ndis.sys blue screen error might also occur if your hard disk is damaged and if the RAM is corrupted. In such cases, a lot of users usually disable the ndis.sys file. However, it won’t really resolve the issue since the file is required for the normal functioning of the operating system and even when you disable the file, it’s pretty useless as the file will start all over again. In addition, you might want to disable security programs or firewalls and antivirus programs in the meantime to check if these programs are the ones that are causing the error. And if you’ve determined that none of the security programs or firewalls and antivirus programs are to blame, refer to the options below that might help you resolve the DRIVER_IRQL_NOT_LESS_OR_EQUAL or ndis.sys Blue Screen of Death error.

Option 1 – Try to update or reinstall the PC device driver

The Ndis.sys Blue screen error can occur when the device driver in your computer is outdated or corrupted. Thus, you either have to update or reinstall it to fix the issue.

• Tap the Win + R keys to launch Run.
• Type in devmgmt.msc into the box and tap Enter or click OK to open the Device Manager.
• After that, a list of device drivers will be displayed. If you see a red or yellow sign that shows up against the driver, right-click on the driver’s name and select “Update Driver Software” or “Uninstall”. And if you find any “Unknown device”, you need to update it as well.
• Select the “Search automatically for updated driver software” option and then follow the instructions to complete the process.
• Restart your PC.

Option 2 – Rollback your Network drivers

If you have updated the driver software as of late and you suddenly got this BSOD error, you might have to roll back the device driver – in other words, switch back to the previous working version. To do that, follow these steps:

• 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.
• Next, select the driver entries that are labeled appropriately other than anything in the context of the WAN Miniport.
• Then select each one of them and double-click to open a new mini window.
• After that, make sure that you’re on the Driver tab and if you are not, just navigate to it then click the Roll Back Driver button to switch back to the previous version of your Network adapters.
• Now restart your computer to successfully apply the changes made.

Option 3 – Try running the System File Checker

The SFC or System File Checker scan could detect and automatically repair damaged system files that could be causing the ndis.sys Blue Screen of Death error. 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 and hit Enter.

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 4 – Try running the CHKDSK utility

Running the CHKDSK utility might also help you resolve the Netwtw04.sys failed BSOD error. If your hard drive has issues with integrity, the update will really fail as the system will think that it’s not healthy and that’s where the CHKDSK utility comes in. The CHKDSK utility repairs hard drive errors that might be causing the problem.

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

chkdsk /f /r

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

Option 5 – Run the DISM Tool

The DISM tool is another command-line tool in the Windows operating system that could help users fix various corrupted system files. To use it, follow these steps:

• Open the Command Prompt as admin.
• Then type in this command: DISM /Online /Cleanup-Image /RestoreHealth
• The DISM command you entered will repair the corrupted system image. Do not close the window if the process takes a while as it will probably take a few minutes to finish.
• Restart your PC.

Option 6 – Perform a System Restore

Performing a System Restore on your computer can also help you fix the ndis.sys Blue Screen of Death error. 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.

What Is Error 1713?

Error 1713 is essentially a programming error. It has specifically been designed in Microsoft applications. This is intended to allow customers to continue using the appropriate setup tool. The error can be quite annoying and is used by manufacturers to determine what caused the error so that counteractive methods can be employed. The number 1713 is simply the hexadecimal code that informs where the instruction was loaded when the error occurred.

Solution

Error Causes

As far as the causes of Error 1713 are in question, the primary cause is damaged, misconfigured, or corrupt windows system files. There are several other factors that lead to the occurrence of Error 1713. For instance, if the applications or hardware on your system has been improperly deleted, installed, or uninstalled, Error 1713 will occur. Similarly, Error 1713 is triggered when the computer has recovered from an attack by some virus, spyware, malware, or adware only recently. This attack corrupts the file and so the error appears. Incorrect system shutdown can also be blamed for this error. All the scenarios listed above actually damages the registry entries in Windows system files. The corrupt or damaged files will then lead to improperly linked or missing information. It goes without saying that such problems will keep the applications from performing in the desired manner and this makes it even more crucial to fix this error as soon as it appears.

Further Information and Manual Repair

Two of the most useful workarounds for Error 1713 are listed below.

• This solution is for advanced users. Restart your computer. Log on to it as the admin in the safe mode. Now go to the Start button and follow this path All Programs-> Accessories-> System Tools->System Restore. Now an option will appear asking you to ‘Restore your computer to an earlier time’. Select it. This option will actually appear in a new window. Click Next. A list of restore points will be displayed to you. Select the most recent restore point before the occurrence of the error and press Next. Now click on the Next button that appears in the confirmation window. Restart your computer as soon as the restoration is finished.
• This solution is for novice users. Download a 1713 repair utility available online. Install this program and use it to scan your system. After the scan is complete, click on repair to fix the error.

As you know, the Windows 10 Action Center has a stack of all the notifications that come from different applications on your computer. So each time an app displays notifications, it will be displayed for about 5 seconds and then it disappears right away. Although the allotted time for the notifications to be displayed is quite enough to catch your attention and help you get a glance at the message, there are times when you might miss it and you hoped it could’ve been displayed a lot longer. So in this post, you will be guided on how you can increase or decrease the display time of the notification in Windows 10. The best way you can view the missed notification is to click on the Action Center. From there, you will see all the notifications that are grouped by the applications. This means that if you have a lot of notifications, it would be hard for you to find what you are looking for. Thus, in such cases, the best way you can do is to increase the display time for which notification to stay on the screen.

To get started, refer to the instructions given below.

Step 1: Tap the Win + I keys to open Settings. Step 2: Next, navigate to Home > Ease of Access > Display. Step 3: After that, scroll down to the end until you see the dropdown to change the notifications where you should see the “Show notifications for”. Step 4: Then you can change the time from the default 5 seconds to 7, 15, 30, and so on. Step 5: Once done, the display time of the notifications should stay longer but keep in mind that you must choose the length wisely so if you have notifications from a lot of apps, then the screen will also be filled with multiple notification cards.

Error 2 - What is it?

Error 2 is a typical Battle.net error code. Battle.net is a desktop app that allows you to access all Blizzard games. It enables Blizzard gamers around the world to play multiplayer matches together, online. Error 2 occurs when you are unable to connect to the login server. This error code is displayed in the following format:

Battle.net Error #2: Unable to connect. Please try again later. If the problem persists, please contact technical support.

Solution

Error Causes

Error 2 may be triggered due to several reasons. These include:

• Program conflict
• Security software conflict
• Bad DNS cache entry
• Issues with network devices
• Viruses and malware
• Registry corruption

Error 2 is not a fatal error like the blue screen of death error codes. However, this error may hamper your ability to play Blizzard multi-player games. To overcome this problem it is advisable to fix error 2 immediately.

Further Information and Manual Repair

To resolve this error you don’t need to spend hundreds of dollars to hire a professional and get it fixed. Here are some of the easy do-it-yourself methods to resolve this error on your PC. These methods require no technical expertise or knowledge. Let’s get started:

Method 1

Error 2 may sometimes pop up on the screen due to program conflict. This happens when you have Blizzard games and other programs running on your PC at the same time. In such a situation, it is advisable to close background applications to resolve conflicts between Blizzard games and other programs running in the background.

Method 2

Sometimes antivirus programs and firewalls can also hinder and interfere with the game’s connection to our servers. In this event, the best way to fix the error is to temporarily uninstall your security software.

Method 3

If error 2 is triggered by the issues with network devices then simply power cycle network devices to re-stabilize the connection. Power cycling router and modem allow you to reset and reestablish a connection to your ISP. To do this, shut down the computer then power down/unplug the router and the modem. Allow the modem to sit for 60 seconds, unplugged. Then turn it on and allow it to boot up till the front panel connection lights show a steady connection. Now turn on the router and do the same as you did with the modem. After that start the computer and allow it to completely boot up. Now try logging on to the Blizzard gaming server. This will hopefully resolve the issue.

Method 4

Viruses and malware infections can also trigger error 2. In such a situation install an antivirus and remove all malicious programs infecting your PC.

Method 5

If the cause of the error is related to registry corruption, then it is advisable to download Restoro. This is a user-friendly PC Fixer with a registry cleaner. The registry cleaner removes all unnecessary and obsolete files corrupting the registry, cleans and repairs the corrupted registry in a few minutes. Click here to download Restoro on your PC to resolve error 2. For further information you may be interested in these similar issues:

What is Error 0x8024a11a or 0x8024a112 ? If you are trying to update your Windows 10 computer and just when you were done downloading the feature update and about to install it, you encounter an error message saying:

“We’re having trouble restarting to finish the install, Error 0x8024a11a, 0x8024a112, 0x80070005 or 0x80070032”

And so to fix this problem, this post will give you a couple of possible solutions. Refer to the options given below to get started.

Option 1 – Restart your computer many times

This is the first thing you can try since there are instances when the Windows Update process gets stuck for a minor thing and restarting the computer usually helps in resolving the issue. All you have to do is click the Restart now button. However, if it does not work, you can use the Power buttons from the Start Menu or WinX Menu. Aside from that, you can also use your power buttons such as Alt + Ctrl + Del to restart your computer. And during the boot process, it is recommended that you restart your computer in Safe Mode or even in a Clean Boot State. After that, you can restart your computer in normal mode. This will make sure that no third-party processes will be able to interfere with the Windows Update process. To put your PC in a Clean Boot State, here’s what you have to do:

• 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 2 – Try running the Windows Module Installer

The Windows Module Installer is a built-in service in the Windows operating system that could help you resolve the Windows update error 0x8024a11a or 0x8024a112. You need to make sure that this service is Started and that its Startup type is set to Automatic – you can do this via Services Manager or by executing the command given below in an elevated Command Prompt.

• Tap the Win + R keys to open the Run dialog box.
• Then type “command prompt” in the field and hit Enter to open Command Prompt.
• And in the elevated Command Prompt type in the following command and hit Enter:

SC config trustedinstaller start=auto

• After executing the command successfully, you should see the “[SC] ChangeServiceConfig SUCCESS” message on the Command Prompt window.

Option 3 – Run the DISM tool

You can also run the DISM Tool as it helps in repairing the Windows System Image as well as the Windows Component Store in Windows 10. Using this built-in tool, you have various options such as the “/ScanHealth”, “/CheckHealth”, and “/RestoreHealth” which could help in fixing the Windows update error 0x8024a11a or 0x8024a112.

• 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 4 – Run the System File Checker

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 the cause why you’re getting the errors 0x8024a11a and 0x8024a112. 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 5 – Run the Windows Update Troubleshooter

Running the built-in Windows Update troubleshooter could also help you resolve the Windows update error 0xca00a000. 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 6 – Run Microsoft’s online troubleshooter

Running Microsoft’s online troubleshooter might also help you fix the Windows update error 0x8024a11a or 0x8024a112. This online troubleshooter is known to help in fixing Windows Update errors, it scans your computer for issues that might be causing the problem and then fixes them automatically.

In case you don’t know, the Windows Script Host provides capabilities such as batch files but it also includes many other features like it can be used by a user manual as well as created by the operating system to automate the flow of operations in the system. However, there are a lot of errors that could take place in such a process. One of them is the following error:

“Script: <PATH of the VBS Script> Line: x Char: x Error: The description of the error. Code: xxxxxxxx Source: (Source of the error)”

At the time of writing, it isn’t clear yet what the root cause of the error really is but there are several potential fixes you can check out to fix it. You can try to run the System File Checker or set the default value for the .vbs key, or troubleshoot the problem in a Clean Boot State. You could also try to repair Install Windows 10 or scan your computer for malware. For more detailed instructions refer to the following options.

Option 1 – Try to run a System File Checker scan

• In the Windows Start Search, type “command prompt” and right-click on Command Prompt from the search results, and then select the “Run as administrator” option.
• After opening Command Prompt with admin privileges, type the “sfc /scannow” and tap Enter to execute it.
• Once the scan is finished, restart your computer and see if the Windows Script Host error.

Option 2 – Try setting the default value for the .vbs key

• Tap the Win + R keys to open the Run dialog box and type “Regedit” in the field and tap Enter to open the Registry Editor.
• Next, navigate to this registry path: ComputerHKEY_CLASSES_ROOT.vbs
• From there, double click on the default string and change its Value data to “VBSFile”.
• Exit the Registry Editor and restart your computer for the changes to take effect.

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

Setting your computer in a Clean Boot State can help you diagnose and later troubleshoot the problems in your computer. During this state, the system will start with a minimal number of drivers and startup programs that help in isolating the problem with the interfering software. To put your computer in a Clean Boot State, follow the given steps below.

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

Option 4 – Try to repair install Windows 10

• First, you have to 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”.

Option 5 – Try scanning your computer using Windows Defender

It is possible that your computer is infected with malware which could be why you’re getting the Windows Host Script error. Thus, you need to scan your computer using Windows Defender.

• Tap the Win + I keys to open Update & Security.
• Then click on the Windows Security option and open Windows Defender Security Center.
• Next, click on Virus & threat protection > Run a new advanced scan.
• Now make sure that Full Scan is selected from the menu and then click the Scan Now button to get started.

Recently, a number of Windows 10 users reported that they were not able to use Cortana properly because it wasn’t able to connect to the internet. According to these users, Cortana won’t connect to the internet even when their internet connection is stable. According to security experts, this issue is confirmed to occur only with Microsoft accounts. This problem might have something to do with a proxy server that interferes with Cortana. There were reports that this issue was caused by a proxy that was filtering the network connection which also happens to interfere with Cortana’s ability to adapt search results and queries based on the user’s location. It could also be caused by some glitch in the home network or your Microsoft account information is inconsistent or your Microsoft account has to be verified. Here are some suggestions that could help fix the connection issue in Cortana, just start with the first one and work your way down until you encounter an option that fixes the problem.

Option 1 – Restart or reset your modem or router

The first thing you can try is restarting or resetting your modem or router. All you have to do is unplug the power cable of the modem and then plug it back in after a few seconds. You could also use the reset button of the modem at the back if it is one. But before you press the reset button, keep in mind that it will erase all the connection credentials and it will be set back to its default settings. After rebooting the network, you can restart your computer to force your modem or router to reassign an IP address to your computer.

Option 2 – Restart Cortana

Restarting Cortana can help you resolve the issue.

• To restart Cortana, open the Task Manager, right-click on Cortana and select the “End process” option.
• Then go to the File tab and select “Run new task”.
• After that, type in “cortana.exe” and press Enter to restart the process.

Option 3 – Try to remove Proxy

Removing the Proxy might also help you in fixing the connection issue in Cortana. Here’s how you can do it:

• 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 4 – Open another app that uses a Microsoft account

This might seem like an odd fix, however, a couple of users tried doing this and it worked for them as it allowed Cortana to connect to the internet again. In this option, you just have to launch another app that uses your Microsoft account information in the same way as Cortana, for instance, the Store app. Once you open the app, a prompt should appear along with a dialog box that allows you to update your Microsoft account with the information required. After that, restart your computer and check if Cortana is now able to connect to the internet or not.

Option 5 – Verify your Microsoft account

In some cases, Cortana might not be able to connect to the internet because your Microsoft account is no longer verified. This usually happens when you use a two-step authentication system with your Microsoft account. To verify it, just open Settings and click on Accounts. After that, check if you have a Verify hyperlink under your Microsoft account or not then click on Verify. Afterward, follow the next on-screen prompts to verify your Microsoft account. Once your account is verified, restart your computer.

Option 6 – Reset Cortana settings

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