Do-It-Yourself Guide to Fixing Runtime Error 5

Microsoft just released Windows 11 Insider build 22000.71. Let’s dive in and see what it brings with you.

Changes and features

New entertainment widget. The entertainment widget allows you to see new and featured movie titles available in the Microsoft Store. Selecting a movie will direct you to the Microsoft Store to see more information about that title. Just open widgets and click or tap on the “Add widgets” button and choose the entertainment widget. For now, the entertainment widget is available for Insiders in the following countries: US, UK, CA, DE, FR, AU, JP. The new context menus and other right-click menus have been updated to use acrylic material. We are testing the usability of a SplitButton for making new folders and files in the File Explorer command bar. The Taskbar previews (when you mouse-over open apps on the Taskbar) have been updated to reflect the new visual design of Windows 11.

Fixes

Taskbar:

• We fixed an issue where if you drag app icons on the Taskbar to rearrange them, it was making the apps launch or minimize when you released the icon.
• Using a long press with a touch on an app icon in the Taskbar to open the jump list should now work.
• After right-clicking the Start icon in the Taskbar, clicking somewhere else should now dismiss the menu more reliably.
• Shift + Right-click on an app icon in the Taskbar will now bring up the window menu like it used to and not the jump list.
• We’ve addressed an issue that was making your mouse move slowly when hovering over the Taskbar previews.
• We’ve included the fix for an issue when using multiple Desktops where an app icon in the taskbar might give the appearance of multiple windows being open when that wasn’t the case on that Desktop.
• When using the Amharic IME you should no longer see an unexpected X next to the IME icon in the taskbar.
• The issue where if you click on the input indicator on the Taskbar and it would unexpectedly highlight Quick Settings has been fixed.
• When you hover over Task View, the preview flyout for your Desktops will no longer pop back up after using Esc to dismiss them.
• We made a fix to address an issue where explorer.exe might crash after hovering over the Task View icon in the Taskbar.
• We fixed an issue where the selected date in the calendar flyout was out of sync with the date in the Taskbar.
• We made an update to address a scenario resulting in some Insiders not seeing the lunar calendar text in the calendar flyout when enabled in Settings.
• This flight addressed an issue that could unexpectedly make the Taskbar background transparent.
• Right-clicking the focus assist icon in the taskbar should now show a context menu.
• The issue from the previous flight where icons in the taskbar corner were getting crushed against the top of the Taskbar has been addressed.
• The tooltip for the location in use icon in the Taskbar should no longer appear blank sometimes.

Settings:

• We fixed an issue making Settings crash on launch periodically.
• Using the volume mixer sliders in Sound Settings should be more responsive now, as well as the page responsiveness as a whole.
• We fixed an issue resulting in Disk and Volumes Settings’ change size option being clipped.
• There was a non-functional verify link under Backup Settings – this has been fixed.
• The Power and Battery Settings page should no longer be reporting that the battery saver is engaged if it’s not.
• The Power and Battery Settings page should also now not crash when launched from Quick Settings.
• We fixed a grammatical error in the Sign-in Settings text.
• The “I forgot my PIN” link was unexpectedly missing in Sign-in Settings when a PIN was set up and has now been returned.
• The issue where the Move option under Apps & Features in Settings wasn’t working reliably should be addressed in this build.
• We’ve mitigated a problem where some of the colors in Settings weren’t updating after switching between dark and light mode, leaving the unreadable text.
• We’ve done some work to help improve the performance of Settings when switching between light and dark mode.
• We addressed an issue where some of the elements of the Themes page in Settings would end up crowded together when the window size was small.
• We resolved an issue where the Pen menu toggle under Taskbar Settings was not in sync with the actual state of the feature.
• Changes made to “Dismiss notification after this amount of time” in Accessibility Settings should now persist.
• Some of the icons you could enable in Taskbar Settings were erroneously labeled Windows Explorer even though that’s not what they were – this should now be fixed.
• The Connect text in Quick Settings has been updated to say Cast.

File Explorer:

• Clicking the command bar button twice should now close any dropdown that appeared.
• The new command bar should now appear when “Open folders in a separate process” is enabled under File Explorer Options > View.
• This build addresses an issue where right-clicking a file and selecting Open With > Choose another app might launch the file in the default app rather than opening the Open With dialog.
• Fixed an issue the desktop and File Explorer context menu would stop launching.

Search:

• We fixed an issue where the option to verify your account in Search wasn’t working.
• Hovering over the Search icon on a secondary monitor will now show the flyout on the correct monitor.
• Search should now work if you open Start and start typing after having gone to the apps list and back.

Widgets:

• When using the Outlook client with a Microsoft account, Calendar, and To-Do updates should sync faster down to the widgets.
• We addressed an issue where if you added multiple widgets quickly from the widget's settings, it could result in some of the widgets not being visible on the board.
• We fixed a bug where widgets could all become stuck in a loading state (blank squares in the window).
• The traffic widget should now follow the Windows mode (light or dark).
• The title of the sports widget should no longer mismatch with the content of the widget.

Other:

• This build addresses an issue where ALT + Tab was getting stuck open sometimes after you released the keys and had to be manually dismissed.
• We made a fix for an issue where Narrator's focus wasn’t ending up on the emoji panel after using the keyboard shortcut to open it.
• Magnifier’s lens view has been updated so the lens now has rounded corners.
• We found an issue that was noticeably impacting Start launch reliability for some Insiders, and have addressed it with this flight.
• We’ve updated the “Most Used” text in the Start menu’s app list so it should no longer be getting clipped.
• Using the semantic zoom in Start’s app list should no longer result in the list being pushed down and to the right off the edge of the window.
• We fixed an issue where if you pressed ⊞ WIN + Z you would need to press Tab before you could use the arrow key to navigate through the snap layouts.
• We addressed an issue where an acrylic area could get left on the screen after repeatedly snapping and unsnapping a window with touch.
• We’ve done some work to mitigate an unexpected flash when moving a snapped window with touch.
• We made a change to help window borders have a little more contrast when “Show accent color on title bars and windows borders” was turned off.

Known issues in Windows 11 repaired

Start:

• In some cases, you might be unable to enter text when using Search from Start or the Taskbar. If you experience the issue, press ⊞ WIN + R on the keyboard to launch the Run dialog box, then close it.
• Based on feedback, we are working on adding access keys to ⊞ WIN + X so that you can do things like “⊞ WIN + X M” to launch Device Manager. Insiders may see this functionality in this build, however, we are currently investigating an issue in which sometimes the option is unexpectedly unavailable.

Taskbar:

• There is an issue in this build where Explorer.exe will crash when the date and time button on the Taskbar is clicked to access new notifications with Focus Assist turned off. The workaround for this is to enable Focus assist to priority or alarms mode. Note that when focus assist is turned on, notification popups won’t appear, but they will be in the notification center when opened.
• The Taskbar will sometimes flicker when switching input methods.
• Taskbar previews may draw partially offscreen.

Settings:

• When launching the Settings app, a brief green flash may appear.
• When using Quick Settings to modify Accessibility settings, the settings UI may not save the selected state.
• The button to rename your PC doesn’t work in this build. If needed, this can be done using sysdm.cpl.
• Settings will crash when clicking “Facial recognition (Windows Hello)” under Sign-in Settings if Windows Hello is already set up.
• Reset this PC and Go back buttons in Settings > System > Recovery does not function. Reset and rollback can be accessed from the Windows Recovery Environment by selecting System > Recovery > Advanced startup, and pressing Restart now. Once in Windows Recovery, choose Troubleshoot.
• Choose Reset this PC to perform a reset.
• Choose Advanced options > Uninstall Updates > Uninstall latest feature update to perform a rollback.

File Explorer:

• exe crashes in a loop for Insiders using the Turkish display language when the battery charge is at 100%.
• When right-clicking the desktop or File Explorer, the resulting context menu and submenus may appear partially off-screen.
• Clicking a desktop icon or context menu entry may result in the wrong item being selected.

Search:

• After clicking the Search icon on the Taskbar, the Search panel may not open. If this occurs, restart the “Windows Explorer” process, and open the search panel again.
• When you hover your mouse over the Search icon on the Taskbar, recent searches may not be displayed. To work around the issue, restart your PC.
• The search panel might appear black and not display any content below the search box.

Widgets:

• Widgets board may appear empty. To work around the issue, you can sign out and then sign back in again.
• Launching links from the widgets board may not invoke apps to the foreground.
• Widgets may be displayed in the wrong size on external monitors. If you encounter this, you can launch the widgets via touch or WIN + W shortcut on your actual PC display first and then launch on your secondary monitors.

Store:

• The install button might not be functional yet in some limited scenarios.
• Rating and reviews are not available for some apps.

Windows Security:

• Device Security is unexpectedly saying “Standard hardware security not supported” for Insiders with supported hardware.
• “Automatic sample submission” is unexpectedly turned off when you restart your PC.

Localization:

• There is an issue where some Insiders may be missing some translations from their user experience for a small subset of languages running the latest Insider Preview builds. To confirm if you have been impacted, please visit this Answers forum post and follow the steps for remediation.

That's is so far, the latest update information on Windows 11 insider build. Stay tuned for more information when it comes as it comes.

There are various components that take part during a Windows Upgrade process such as the CPU, Disk, Network, and many more. This is why the process of upgrading your Windows 10 computer can be quite complex and due to its complexity, there are times when you might encounter some errors like the Windows Upgrade error 0x800701E3. If you encounter this kind of error then it has something to do with the “disk” part of the whole upgrade process which could be due to a conflict with the storage of your Windows 10 computer. When you receive this error, you will see the following error message on your screen:

“Windows cannot install required files. Make sure all files required for installation are available and restart the installation. Error code: 0x800701e3.”

To fix this Windows Upgrade error, here are some suggestions that might help.

Option 1 – Delete Files from Software Distribution Folder & Catroot2 folders

The downloaded Windows Updates are placed in a folder called “SoftwareDistribution”. The files downloaded in this folder are automatically deleted once the installation is completed. However, if the files are not clean up or if the installation is still pending, you can delete all the files in this folder after you pause the Windows Update service. For complete instructions, refer to 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 start cryptSvc net start bits net start msiserver

• After entering these commands, it will stop the Windows Update Service, Background Intelligent Transfer Service (BITS), Cryptographic, and the MSI Installer
• 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.

After resetting the SoftwareDistribution folder, you need to reset the Catroot2 folder to restart the services you just stopped. To do that, follow these steps:

• Type each one of the following commands.

net start wuauserv net start cryptSvc net start bits net start msiserver

• After that, exit Command Prompt and restart your computer, and then try to run Windows Update once more.

Option 2 – Try running the DISM tool

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

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

Option 3 – Run 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 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.

• Restart your computer.

Option 4 – Try running the ChkDsk utility

You can also run the ChkDsk utility to fix the Windows Upgrade error 0x800701E3.

• First, open This PC and right-click on your operating system partition for Windows.
• Next, click on Properties and navigate to the Tools tab.
• Then click on Check under the Error Checking section.
• After that, a new mini window will be opened and from there click on Scan drive and let it scan your disk drive partition for any errors and then restart your computer.

Option 5 – Run the Windows Update Troubleshooter

Running the built-in Windows Update troubleshooter is one of the things you can first check out as it is known to automatically resolve any Windows Update or upgrade errors like error code 0x800701E3. 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 Upgrade error code 0x800701E3. 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.

There are times when system files get corrupted and if the Windows Update process finds the system’s integrity questionable, chances are, the update, upgrade or the installation may fail and you will only be getting an error code 0x80073712 instead of completing the process. The error code 0x80073712 indicates that a file needed by the Windows setup or the Windows Update is most likely missing or damaged. To resolve the problem, here are some suggestions you can try.

Option 1 – Try running the DISM Tool

Running the DISM Tool 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”.

• Open the Command Prompt as admin.
• Then type in this command: 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.

After you run this tool, a log file is created at C:WindowsLogsCBSCBS.log. On the other hand, if the Windows Update client is already broken, you will be prompted to use a running Windows installation as the repair source or use a Windows side-by-side folder from a network share, as the source of the files. Although the chances of this happening are less, if it turns out to be the case, you need to run an advanced command in the DISM tool to repair a broken Windows Update. Just repeat the process above but use the following command instead:

DISM.exe /Online /Cleanup-Image /RestoreHealth /Source:C:RepairSourceWindows /LimitAccess

Option 2 – Try running 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 with good system files that might be causing the error 0x80073712. 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 3 – Try running the Chkdsk utility

You can also try running the Chkdsk utility to resolve the Windows Update error 0x80073712. 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

Note: The Chkdsk function might take a while before it finishes its operations so you need to be patient and wait until the entire process is completed.

Option 4 – Try running the Windows Update Troubleshooter

Running the built-in Windows Update troubleshooter could also help you resolve the Windows Update error 0x80073712. 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 5 – Try running Microsoft’s online troubleshooter

You also have the option to run Microsoft’s online troubleshooter which could help you fix Windows Update errors.

A lot of users connect to the internet are using VPN on their Windows 10 computers which means that their regions could be different from the actual region of their Windows 10 computers. Thus, if you are facing some issues in updating your computer in this kind of environment, specifically the Windows Update error 0x800F0922, you need to follow the tips given in this guide to help you resolve the issue. When you encounter this kind of Windows Update error, you might see either of the following error messages on your screen:

“Windows could not search for updates, Code 0x800F0922 Windows Update encountered an unknown error” Or: “Windows failed to install the update with error 0x800F0922”

This issue might be caused by two possible reasons such as:

1. VPN issues
2. Not enough space on the System Reserved partition

To resolve the problem, here are some tips that might help:

Option 1 – Try disabling the VPN

As mentioned, if you are using VPN, this could be the reason why you’re getting the Windows Update error 0x800F0922 so the most obvious thing to do is for you to turn off the VPN and try to run the Windows Update once more. And if you use a VPN software that works using their software, you can just completely exit or log-off from its account. On the other hand, if you are using a built-in Windows 10 VPN, you can simply turn it off or delete all the settings you have created there. Although it’s understandable that you might have to use a VPN connection to connect to the work network, you really have to disable it at least until the Windows Update is no longer stuck in the error 0x800F0922. It would be best if you do this when you are not working.

Option 2 – Try to free up space in the System Reserved partition

The System Reserved partition is a part of the hard disk created when Windows is first installed on it. It is where the Boot Configuration Database, Boot Manager Code, Windows Recovery Environment, and the reserves space for the startup files are stored. And as mentioned early on, the error might be due to some insufficient space in the System Reserved partition so the next thing you can do is to increase the space in this partition. Note that it is a complex process so you need to make sure that you have made backups to all your data on the computer. So if ever something goes out of hand, at least you have copies of your important files in case you aren’t able to boot into the system at all.

Screen flickering in Windows 10 - What Is It?

Screen flickering when you’re using Windows 10 is quite a common problem. It is often caused by apps that are not compatible with the operating system, or faulty display drivers.

There are a lot of possibilities for why this issue occurs. If you are one of the many users that encounter this kind of problem, you might want to check on your task manager to see if everything is working fine. One common sign that something wrong has happened is if the task manager flickers, as well. To fix this, you will need to update an app, uninstall an app, or update your display driver.

Solution

Error Causes

Common causes of the screen flickering when running on Windows 10 are software issues. This is most likely caused by the following:

• Faulty display driver
• You have an application installed that is not compatible with your operating system

Further Information and Manual Repair

In order to fix the issue of your screen flickering when you have Windows 10 as your operating system, follow these simple steps.

Note: It is very important to consult with an authorized computer technician if you are not highly confident in solving this issue by yourself. Furthermore, you can also use software to fix this problem.

• The first method is by checking if your task manager is flickering. To open the task manager, all you have to do is right-click or press and hold the start button, then select task manager.

If you have confirmed that the task manager is the one causing the screen flickers, the display driver can possibly be your problem. To fix it, all you have to do is update your display driver.

How to update the display driver

1. You have to reset your computer and boot it on Safe Mode.

      -In order to do this, you have to hold the Shift key while selecting Power>Restart. When your computer boots up, you will be greeted by a Choose an option screen. From there, you have to select Troubleshoot, then Advanced Options, then Startup Settings, and then Restart. When your computer restarts, select 4 or hit the F4 key to enter into Safe Mode.

2. When your computer finally boots up in Safe Mode, right-click or press and hold the Start button. From there, click Device Manager.

3. From the Device Manager screen, you have to expand the Display Drivers section, right-click on the driver that might be causing the problem then select Uninstall. Don’t forget to tick the Delete the driver software for this device box, press the OK button, and then restart your computer.

            - When you have two, or more, drivers installed on your computer, all you have to do is disable the other drivers. You can do this by right-clicking on the driver in the Device Manager and click the Yes box next to disable. Shut down your PC after this, disconnect the installation, and boot your computer back on.

4. When your PC boots up after the restart, click on the Start button then click on Settings.

5. You need to go to Update & Security, then Windows Update, and then check for updates.

            - If you are using multiple drivers and this technique doesn’t work, repeat the process in Step 3 and try to disable a different driver.

Remove an incompatible app

There are two ways to remove an incompatible app to fix the issue of a screen flicker on Windows 10. Apps like Norton AV, iCloud, and IDT Audio are usually the ones causing the problem. Uninstalling these apps could solve the problem. Uninstall the apps by using the methods below:

First Solution: Uninstall an app in Settings

1. Click Start, and then click Settings.
2. Click on System, and then click on Apps & Features.
3. A window will pop up and from there you will need to select the application you wish to uninstall. Click the app, and then click uninstall. Follow the screen prompt to fully uninstall the program.

Second Solution: Uninstall an app in the Start Menu

1. Click Start, and then click All Apps.
2. Look for the application you will need to uninstall, right-click the said app, and then click Uninstall. Follow the screen prompt to fully uninstall the program.

[/section]

I often switch between my desktop speakers and headphones and because of this I very often use the volume adjustment bar to adjust sound levels so it is not too loud and each time when I set it I get annoying BEEP at the end. Now personally this might not bother you and you might want to leave it since it can be a useful feature to tell you how much volume is loud but if you are adjusting multiple times volume during the say it can become really frustrating to hear it each time, especially when switching to headphones and it beeps into your ears. In this guide, I will show you how to remove the beep so it is not heard anymore when you adjust the volume. Please know that beep is part of the Windows sound scheme and you can either remove specific sound with a completely silent wave or just turn off all windows alert sounds.

• Open Windows settings and go to system > sound
• in system sound, go to the right part of the screen and click on the sound control panel
• In the sound control panel click on the Sounds tab
• In the sounds, tab click on the drop-down menu under the sound scheme and choose no sounds.

There you go! You have successfully removed annoying BEEP each time you adjust the volume in Windows 10

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.

It seems that Microsoft is going to offer subscription and sales of individual office applications in the Windows Store. The office package will still be available as a package but for the first time, we will get single applications as standalone ones available for purchase. This is a very interesting decision by Microsoft and I fully support it, this time users will be able to pay less and to choose only applications that they need instead of paying for the whole package and not using it.

If you are familiar with the Dynamic Lock feature in Windows 10, then it has probably made it easier for you to lock your computer the instant you move away from it. This interesting feature does not need any special software like IR Cameras to use this feature as long as your Windows 10 computer supports Bluetooth which it most likely does. However there are times when the Dynamic lock feature is either missing or not working. When that happens, here are some suggestions that could help you. But before anything else, you need to create a System Restore point first since you will be modifying some critical system settings as well as registry files. After you’ve created a System Restore point, refer to the following options below to fix the issue with Dynamic Lock.

Option 1 – Try using the Settings app

• Tap the Win + I keys to open the Settings app and then navigate to Accounts > Sing-in options.
• After that, scroll down until you see the Dynamic Lock section.
• Next, make sure that the checkbox for “Allow Windows to automatically lock your device when you are away” is checked.
• Now that you’re all set, exit the Settings app.

Note: If for some reason the above-given solution didn’t work, you can try the next options below.

Option 2 – Try to pair your Bluetooth Device

If you get a message saying, “Allow Windows to automatically lock your device when you are away” in the Notifications Center or in the Settings app, then you need to pair your Bluetooth device. To do so, follow the steps below.

• Go to Settings > Devices > Bluetooth & other devices.
• From there, make sure that Bluetooth is turned On and then pair your Bluetooth device.
• And if you open the Windows Defender Security Center, you will see the following message as well.
• Simply click on the Add Bluetooth device button and it will open the Bluetooth settings where you can also pair the device.

Option 3 – Try to reinstall or update the Bluetooth driver

The issue might have something to do with the Bluetooth drivers. It could be that it is outdated and needs to be updated or that you recently updated it and since then you have trouble removing the Bluetooth device and so to fix the issue, you can update, roll back or uninstall the Bluetooth drivers. How? Follow the steps below.

• Tap the Win + X keys to open the Device Manager.
• Next, look for the Bluetooth device and right-click on it.
• Select the option “Update driver”.
• After that, a new popup window will appear. In there, select the option, “Search automatically for updated driver software”.

Note: Checking the update may take a few minutes so you’ll have to wait until it finishes. If it is able to find an update, you must install it. And if you want to reinstall the Bluetooth driver, just select the “Uninstall driver” option and follow the next on-screen instructions that follow.

Option 4 – Try to use the Registry Editor

• Tap the Win + R keys to open the Run dialog box and then type “Regedit” in the field and hit Enter to open the Registry Editor.
• If a User Account Control or UAC prompt appears, just click on Yes to proceed.
• After that, navigate to the following registry key:

HKEY_CURRENT_USERSoftwareMicrosoftWindows NTCurrentVersionWinlogon

• Next, look for a DWORD named “EnableGoodbye” located on the right-side panel and then make sure that its value is set to 1 which means that it is enabled while 0 indicates disabled.
• Now close the Registry Editor and restart your computer to apply the changes made successfully.

Option 5 – Try checking the Group Policy setting

If your Windows 10 version has the Group Policy Editor, you can use it to fix the Dynamic Lock issue as well. Simply follow the steps below to use it.

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

Computer ConfigurationAdministrative TemplatesWindows ComponentsWindows Hello for Business

• After that, look for an entry named “Configure dynamic lock factors” and double click on it to open a new window.
• Once you enable this Group Policy setting, the signal rules will be evaluated to detect the absence of a user and will lock the device automatically. On the other hand, if you disable or don’t configure this setting, you can continue locking your computer with existing locking options. Take note that it may be Not configured or Enabled but shouldn’t be set to Disabled.
• Now select the radio button for Enabled and set the Signal rules then click OK.
• Then exit the Group Policy Editor and restart your computer.

What Is Installation Error 1628?

Installation Error 1628 is, as the name suggests, an installation error. When it occurs, a generic 1628 message is displayed to the user. When this message appears, it is either a problem with the install files or an issue with the InstallShield.

Solution

Error Causes

Installation Error 1628 is caused because every Windows-based program or application has been designed that such that it has to be installed on the computer for use. This installation process is important because it not only moves files to the appropriate location on one’s hard drive but also because the process creates registry entries in Windows System files. A vast majority of these programs and applications have a built-in tool that’s responsible for aptly performing this installation. This built-in tool is the InstallShield. This establishes that when this error occurs, it is either because of some unforeseen issue that occurred during the installation process or because of some problem with the InstallShield.

Further Information and Manual Repair

In order to keep this error from occurring in the future, some recommendations are outlined below.

• Check the installation disc and determine if there are any smudges, scratches, or fingerprints on it. If the system is unable to read data from the disc, Installation Error 1628 will be generated. In order to ensure that the Installation Disc is clean, use a microfiber cloth. Dampen it lightly with water and clean the disc. Wipe the inside of the disc lightly in an outward direction, making sure that it is not wiped in a circular pattern. Try to reinstall the application or program after cleaning the disc. The issue should be resolved. However, if it persists, some problems may be with the InstallShield.
• The alternative solution is to repair the InstallShield and the procedure goes as follows.

1. Stop InstallShield’s running process. It may have been crashed and simply needs to be restarted. Now access task manager. Press Ctrl+Alt+Del and the task manager will open. Now go to the processes tab and disable ‘idriver.exe’ and ‘msiexec.exe’ from here.
2. Now go to ‘C: Program Files/Common Files’. Here you will find the ‘InstallShield’ folder. Select ‘rename’ and modify the folder name to ‘InstallShield1’. Confirm rename and start the installation process again. Now Windows will try to re-install any InstallShield files one needs.
3. If the error persists after renaming the InstallShield folder, download the Windows Installer from Microsoft’s website. This file will determine whether or not your version is valid. Old versions often have bugs that cause problems. Your system is now ready to be used.