Logo

How to Fix Windows 10 Error 0x8000222

Error Code 0x8000222 - What is it?

Error Code 0x8000222 is an error that occurs during the installation process for Windows 10. It is also present in past versions of the software, going all the way back to Windows 7 and even affecting Windows software products, including Microsoft Word, PowerPoint, and other items in the Microsoft Office Suite.

Common symptoms include:

  • Inability to complete the installation process for new versions of the operating system, Microsoft Office programs, or other Windows-based software

While there are several factors that can contribute to the appearance of Error Code 0x8000222 during the installation process, most of these factors can be addressed using a few high-level methods. These methods do require some advanced knowledge and computing skills, so if you are unable to complete the steps below successfully or do not have confidence in your ability to undertake these methods on your own, contact a qualified computer repair service that is familiar with the Windows 10 installation process.

Solution

Restoro box imageError Causes

There are a few different issues that can cause Error Code 0x8000222 to arise during the installation process on your Windows operating system. The first is a corrupted file in your system library or dynamic link library, also called the DLL. The second is interference by your proxy, firewall, or antivirus software that inhibits the machine from being able to access the files that it needs to successfully complete the installation of your Windows operating system or software.

Further Information and Manual Repair

To address and resolve Error Code 0x8000222 on your Windows operating system, regardless of the version of the software that you are using, there are a few steps that you can take. Keep in mind that these steps do require some advanced skills and knowledge about your computer, so if you don’t believe that you can undertake these steps on your own or if the following methods do not fully resolve the issue on your device, talk to a qualified computer repair technician for assistance.

Here are the best ways to address Error Code 0x8000222 on your Windows machine:

Method One:  Fix Your DLL Dependencies Registry

Before implementing this method, make sure that a proxy is not active on your computer. To check to see if there is an active proxy, simply press the Windows key together with the “R” key and type in the command “cmd”, then when the prompt opens up, type in the following command:  “netsh winhttp import proxy source=ie”. From the box that follows, if you see a message saying that there has been an error writing in the proxy settings and that access has been denied, it means that you can turn off the proxy setting in your Internet Explorer and the error will go away on its own.

If you do not have an active proxy, it is time to check and see whether your DLL dependencies are properly set up. To do so, open up the command prompt again by pressing the Windows key and “R” key at the same time and typing in “cmd”. Once the command prompt is active, simply typing in “regsvr32 Officevalidator.dll”, then attempt to resume your installation once it has been complete.

In some cases, you may need to restart your computer before attempting the Windows installation process.

Method Two:  Turn Off Firewalls and Antivirus Software Before Installing

If the above method did not successfully resolve the problem, you can go into your control panel and turn off any firewalls or antivirus programs that may be interfering with your ability to complete the Windows installation process. Depending on the programs that you use for your antivirus needs, you may need to restart your computer before you reattempt to do the installation process.

You should be able to turn your firewall and antivirus programs back on once the installation process has run through to completion.

In most cases, taking the steps above will fully resolve the appearance of Error Code 0x8000222 on your Windows 10 machine.

Method Three: Use An Automated Tool

If you wish to always have at your disposal a utility tool to fix these Windows 10 and other related issues when they do arise, download and install a powerful automated tool.

Do You Need Help with Your Device?

Our Team of Experts May Help
Troubleshoot.Tech Experts are There for You!
Replace damaged files
Restore performance
Free disk space
Remove Malware
Protects WEB browser
Remove Viruses
Stop PC freezing
GET HELP
Troubleshoot.Tech experts work with all versions of Microsoft Windows including Windows 11, with Android, Mac, and more.

Share this article:

You might also like

Intel’s GPU ARC coming aimed at AMD & Nvidia
intel ARCThis is not the first time that Intel is trying to enter the GPU field but its adventures so far were, well let us agree not so good. All of that is hoping to be changed with the upcoming ARC GPU. The first generation of Arc graphics, code-named Alchemist and previously known as DG2, will support desktop PCs and laptops and is set to arrive in the first quarter of 2022. Alchemist will have hardware-based Ray tracing and AI-driven supersampling. This indicates that GPU is aimed to compete in the Hi-end spectrum and battle side by side with Nvidia and AMD on the market. Alchemist will also pack full DirectX 12 Ultimate support. Intel also released names for the next upcoming future generations of ARC GPUs: Battlemage, Celestial & Druid. More information about ARC products will be released later this year. “Today marks a key moment in the graphics journey we started just a few years ago. The launch of the Intel Arc brand and the reveal of future hardware generations signifies Intel’s deep and continued commitment to gamers and creators everywhere,” Roger Chandler, Intel vice president, and general manager of client graphics products and solutions.
Read More
Attempt was made to reference a token
If you were trying to open File Explorer but it suddenly stopped working and you encounter an error message that states, “An attempt was made to reference a token that does not exist”, read on as this post will guide you in fixing this problem. This problem was initially reported after the April Update and Microsoft was able to fix it right after correcting the build. However, this effort seems futile for some users as recently, some reported getting the same error when they try to open not just Windows File Explorer but also with utilities like Microsoft Management Console or MMC, Visual Studio, Task Manager, Printer, Recycle Bin, etc. Two of the most likely causes of this error are a troublesome Windows Update and corrupted system files. Whatever the cause is, here are some suggestions you can follow to fix the “An attempt was made to reference a token that does not exist” error.

Option 1 – Try to re-register the problematic DLL file

You may have to re-register the ntdll.dll file using the regsvr32.exe before you can successfully install the program and fix the ntdll.dll file crash error. The Regsvr32 tool is a command-line utility that can be used to register and unregister OLE controls like DLL and ActiveX (OCX) control in the Windows operating system. Follow the steps below to use it.
  • Open Command Prompt as admin from the WinX menu.
  • Next, type the following commands in the elevated Command Prompt and hit Enter to execute the command. This will re-register the affected DLL file using the Windows operating system tool, regsvr32.exe.
    • exe /[DLL file]
    • exe [DLL file]
Note: Replace “[DLL file]” with the name of the DLL file that was pointed out in the error.
  • After you execute the given commands, you should see a message saying, “DllRegisterServer in vbscript.dll succeeded” if the Regsvr32 tool was able to run successfully. After that, try to install the program again and see if it now works.

Option 2 – Replace the DLL file from a trusted source

  • First, you need to get the new DLL file from another computer with preferably the same file version number.
  • After that, you need to boot your PC into Safe Mode and navigate to the paths listed below and then replace the file using a USB drive or other external storage devices.
    • x86: This PC > C:/Windows/System32
    • x64: This PC > C:/Windows/SysWOW64
  • Next, type “cmd” in the Cortana search box and right-click on Command Prompt, and select “Run as administrator” to open it with administrator privileges.
  • Now type the “regsvr32 ntdll.dll” command and hit Enter.
  • Restart your PC and check if the error is now fixed.

Option 3 – Perform a System File Checker scan

The System File Checker or SFC scan could detect and automatically repair damaged system files that could be causing the “An attempt was made to reference a token that does not exist” error to pop up. 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 reverting back to the previous build of Windows

This kind of error might have something to do with a Feature Update so you can try to revert your computer to a previous build of Windows 10 as it could help you fix the problem. In this case, it would better if you refrain from updating your Windows 10 computer until this problem is completely resolved by Microsoft.
Read More
Fixing the No such interface supported
If you are using File Explorer but suddenly encountered an error saying, “No such interface supported”, read on as this post will guide you on how to fix the problem. This kind of error occurs due to the corruption in the system files which supports several tasks in the system that works with the Windows File Explorer process or File Explorer. This kind of error can give you a hard time in browsing the files on your computer, or when you open important utilities like the Control Panel, or when you copy files and other inconveniences. Needless to say, it won’t bring you any productivity at all and can only leave you frustrated. To fix this problem, there are several options you can try. You can try to run the System File Checker scan or the DISM tool. You could also try to re-register the potentially corrupted DLL files or fix the User Profile. For more details, refer to each one of the given options below.

Option 1 – Try to run 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.
  • Type “cmd” in the Start search and then right-click on the appropriate search result.
  • Next, select “Run as administrator” to open Command Prompt with admin privileges.
  • After opening Command Prompt, type in sfc /scannow
The command will start a system scan which will take a few whiles before it finishes. Once it’s done, you could get the following results:
  1. Windows Resource Protection did not find any integrity violations.
  2. Windows Resource Protection found corrupt files and successfully repaired them.
  3. Windows Resource Protection found corrupt files but was unable to fix some of them.
  • Now restart your computer and see if the problem is fixed or not.

Option 2 – Try to fix the User Profile

The next thing you can do to fix the problem is to fix the User Profile. All you have to do is migrate to a new User Profile in Windows 10 by creating a new User Account and migrating all your personal files from the current user profile folder in the C:/Users location to the new user profile folder which is also located in the same folder.

Option 3 – Run the DISM tool

You can try running the Deployment Imaging and Servicing Management or DISM tool to fix the “No such interface supported” error. 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. Once it’s done, restart your computer.

Option 4 – Try to re-register the problematic DLL file

You may have to re-register the ntdll.dll file using the regsvr32.exe before you can successfully install the program and fix the error. The Regsvr32 tool is a command-line utility that can be used to register and unregister OLE controls like DLL and ActiveX (OCX) controls in the Windows operating system. Follow the steps below to use it.
  • Open Command Prompt as admin from the WinX menu.
  • Next, type the following command in the elevated Command Prompt and hit Enter to execute it. This will re-register the affected DLL file using the Windows operating system tool, regsvr32.exe.
regsvr32 c:windowssystem32actxprxy.dll
  • After you execute the given command, you should see a message saying, “DllRegisterServer in vbscript.dll succeeded” if the Regsvr32 tool was able to run successfully. If it didn’t work, you can try to execute this command instead: FOR /R C: %G IN (*.dll) DO "%systemroot%system32regsvr32.exe" /s "%G"
  • Once it’s done, restart your computer.
Read More
Enable or Disable Automatic Encryption
You might be familiar with the Encryption File System or EFS algorithm if you rather keep your files and folders encrypted. Encryption File System is a built-in feature in Windows 10 which allows users to secure their important files. Although there is an alternative way for you to secure your data on your Windows 10 computer, you can’t ignore the fact that the main advantage of an Encryption File System over BitLocker is that the former can help you encrypt a particular folder rather than encrypting the whole hard drive partition. If you move a file inside a folder encrypted with the Encrypting File System it will automatically get encrypted. There are some users who like this feature but unsurprisingly, there are some that don’t. So if whether you want your files encrypted when you place them in an encrypted folder or if you want to keep it as it is, read on as to how you can do it either way. You can enable or disable automatic encryption of files moved to encrypted folders in Windows 10 using the Registry Editor or the Group Policy Editor. Before you proceed, make sure to create a System Restore Point first because the modifications you’re about to make in your computer might affect its overall functioning so if anything goes wrong, you can always undo the changes. Once you have that covered, refer to the options given below to enable or disable automatic encryption in Windows 10.

Option 1 – Enable or disable automatic encryption using Registry Editor

  • Press the Win key + R key at the same time to open the Run dialog box.
  • Then type “Regedit” in the field and press Enter to open the Registry Editor and if a User Account Control or UAC prompt appears, just click Yes to proceed.
  • After opening the Registry Editor, navigate to this key location: HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionPoliciesExplorer
  • Next, right-click on Explorer and select New > DWORD (32-bit) Value and then name the newly create DWORD to “NoEncryptOnMove” and press Enter to save it.
  • After that, double click on the NoEncryptOnMove DWORD and set its value to the following preferences:
    • 1 – Disable Auto Encryption of files moved to encrypted folders.
    • 0 – Enable Auto Encryption of files moved to encrypted folders.
  • Now close the Registry Editor and restart your computer to successfully apply the changes made.

Option 2 – Enable or disable automatic encryption using the Group Policy Editor

  • Press the Win + R keys to open the Run box and type “gpedit.msc” in the field and press Enter to open the Group Policy Editor.
  • After that, navigate to this path: Computer ConfigurationAdministrative TemplatesSystem
  • Next, look for the “Do not automatically encrypt files moved to encrypted folders” option and double click on it to set the policy. From there, you will see the following description:
“This policy setting prevents File Explorer from encrypting files that are moved to an encrypted folder. If you enable this policy setting, File Explorer will not automatically encrypt files that are moved to an encrypted folder. If you disable or do not configure this policy setting, File Explorer automatically encrypts files that are moved to an encrypted folder. This setting applies only to files moved within a volume. When files are moved to other volumes, or if you create a new file in an encrypted folder, File Explorer encrypts those files automatically.”
  • Now select one of the radio buttons below depending on your preference:
    • Not Configured or Disabled: Enable Auto Encrypt of files moved to EFS Encrypted folders.
    • Enabled: Disable Auto Encrypt of files moved to EFS Encrypted folders.
  • Then click on the Apply and OK buttons to save the changes made.
  • Exit the Group Policy Editor and restart your computer.
Read More
4 Methods of Fixing Error Code 49

Error Code 49 – What is it?

Error Code 49 is a common device driver error that users encounter on any Windows 2000 and later operating system versions. The error occurs when the connected peripheral devices fail to function properly due to an overload of the system hive’s size. The error when prompted pops up on your screen with the following message:
"Windows cannot start new hardware devices because the system hive is too large (exceeds the Registry Size Limit). (Code 49)”
The error causes unattached devices to be displayed on the system hive list.

Solution

driverfix boxError Causes

Error Code 49 mainly results from problems in Windows registry system files; the system hive in the Windows registry exceeds its size limit. The system hive is part of the Windows registry and it is where files regarding devices are contained along with user preferences and applications. The devices will not work until the system hive size is brought back to normal levels.

Further Information and Manual Repair

There are several ways you can use to fix your error code. Here are the following.

Method 1 – Uninstall unused devices

One of the best ways to address the error code is to uninstall the unused devices which are listed on your computer’s system hive. To do this:
  • Log in using an Administrator account
  • Click the Start button and then click ‘Run’
  • In the box, enter the command:
  • "set devmgr_show_nonpresent_devices=1 cd%SystemRoot%System32 exit" and click enter
  • Open Device Manager, click ‘View’, and then choose ‘Show hidden devices’ to see unused devices.
  • When you can see the list, click on the device you want to uninstall by selecting the ‘Driver’ tab and then select ‘Uninstall’.
  • After uninstall is complete, restart your computer.

Method 2 – Use System Restore

If the error still persists, you can use system restore to eliminate the problem. Here is how you can do so:
  1. Log in using an Administrator account
  2. Click ‘Start’ button and select All Programs > Accessories > System Tools > System Restore
  3. Click ‘Restore my computer to an earlier time’ and click ‘Next’
  4. Select the last Windows restore point from the ‘On this list, click a restore point’ list, and click ‘Next’
  5. Click ‘Next’ on the confirmation window to proceed
  6. Restart your PC after restoration is complete
By restoring the system via a last saved system checkpoint, you can obtain undamaged Windows system files that can help avert the error code.

Method 3 – Manually uninstall and reinstall the device driver

If using system restore does not work in resolving the error code either, you may have to resort to manually uninstalling and then reinstalling the device driver causing the problem. This would be necessary since the remaining incomplete files due to a partial removal or installation of programs is what results in the error code. By uninstall and reinstalling the device driver program, it would lead to the completion of the files. You can do this by firstly logging in as Administrator and open Device Manager. Select the device that is causing the problem and double click it and make sure that the peripheral is connected properly to the PC. Upon opening, click on the ‘Driver’ tab and then select ‘Update Driver’. Make sure to refer to the system documentation that you received with your PC or computer to check for the motherboard details and driver specifics.

Method 4 – Use software to automatically download the driver

Manually uninstalling and reinstalling the driver will do the trick; however, it may be time-consuming, especially when you would have to resort to your hardware user manual. Therefore, using a program such as DriverFIX can save you a lot of time and frustration in having your device work properly on your computer. DriverFIX, with its user-friendly approach to help you fix your PC issues, comes with an integrated database that detects which drivers you need to reconfigure within just a few seconds and downloads it automatically. It further ensures that your drivers are installed in their entirety leaving no room for any incomplete files to remain that create Error Code 49. It also has the added advantage of being able to backup and restore your files should there be the slightest possibility of system file damage. DriverFIX is the answer to fixing your PC error codes accurately and quickly. Click here to download DriverFIX to fix Error Code 49 quickly and effectively!
Read More
How to Fix Media disconnected error message on Windows 10
A computer with no internet connection is like a mobile phone that can’t call nor text though you can still use it for other things. So if you are having problems with your computer’s internet connection, worry not as there are some basic things you can try before you go over the actual troubleshooting. Just make sure that you really have working internet. To verify it, try connecting your other devices. Aside from that, you must also make sure that your computer is connected properly over cable or connected to the router over the Wi-Fi. Once you have all these things covered, now’s the time to start troubleshooting the problem with the help of the instructions prepared below. To be more specific, this guide will walk you through what you can do when you encounter a particular internet connection problem where you get the Media State Media disconnected error message on your Windows 10 computer.

Before you troubleshoot the problem, you need to first check the internet connection status on your computer. To do that, follow these steps:

  • Type in “cmd” in the Cortana search box.
  • From the search results, right-click on Command Prompt and select “Run as administrator” from the context menu.
  • After opening Command Prompt with administrator privileges, type in the ipconfig /all command and hit Enter.
  • After you enter the command, you will see a list of all the connected media like the Ethernet, Wi-Fi along with its status, and more. From there, you need to check everything closely. I notice a message that says, “Media State . . . . . Media disconnected”, then your internet connection is indeed having issues.
Refer to the options below to fix the Media State Media disconnected error message on your Windows 10 PC.

Option 1 – Try resetting WINSOCK and IP Stack

  • Type in “cmd” in the Cortana search box.
  • From the search results, right-click on Command Prompt and select “Run as administrator” from the context menu.
  • After opening Command Prompt, type in each one of the commands listed below
    • netsh winsock reset catalog – This command will reset the WINSOCK entries.
    • netsh int ipv4 reset reset.log – This command will reset the IPv4 TCP/IP stack.
    • netsh int ipv6 reset reset.log – This command will reset the IPv6 TCP/IP stack
  • Once you’ve executed the commands listed above, restart your PC to successfully apply the changes made.

Option 2 – Check if your Network Adapter is disabled

If you’ve disabled the network adapters on your computer, then it’s most likely the reason why you’re getting the Media State Media disconnected error message. Thus, you need to enable it back.
  • Open Settings and go to Network and Internet > Select Ethernet > Change adapter options.
  • From there, right-click on the adapter and enable it.

Option 3 – Check the Wi-Fi Properties

Though this case is not common, Wi-Fi sharing has actually caused issues for some users. That’s why you need to check the Wi-Fi properties. Go to Network Connections and right-click on Wi-Fi and select Properties. From Properties, go to the Sharing tab and select the first option and click OK.

Option 4 – Try updating the Network driver

  • Tap the Win + R keys to open the Run dialog box and then type in devmgmt.msc and tap Enter or click OK to open the Device Manager.
  • Expand the section for the outdated device drivers.
  • And then select the Network driver or any other outdated driver(s) and right-click on it/them.
  • From the drop-down menu, select the Update Driver option and follow the on-screen instructions to install the latest version of the driver.
  • Then also click on the option, “Search automatically for updated driver software.
  • Restart your PC after the installation.
Note: If updating the Network driver didn’t work, you can go to the website of your PC manufacturer and look for the support section where you can download the drivers for your computer. You just need to take note of your PC’s correct model and model number so you can find the appropriate driver.
Read More
Telnet not recognized as internal/external
In case you don’t know, a teletype network, also known as Telnet, is a protocol that is meant for internet or LAN communication which is used primarily to control other computers effortlessly. And it is available as a command-line utility in Windows and helps users in opening a command-line interface for the remote computer. However, a lot of users have reported an error that states, “Telnet is not recognized as an internal or external command, operable program, or batch file” when you try to use it. If you are one of these users, then you’ve come to the right place as this post will guide you on how to fix this error in Windows 10. This kind of error means that the Telnet utility is not installed on your computer but Telnet is a default feature in Windows 10 so the protocol mainly is not enabled yet. The Telnet client is disabled by default in Windows 10 and to fix this error, you can try to enable the Telnet Client via Programs and Features or try to install Telnet using an elevated Command Prompt.

Option 1 – Try to enable the Telnet Client via Programs and Features

The first thing you can do is to enable the Telnet client using Programs and Features since it is disabled by default. To do that, follow the steps below.
  • Tap the Win + R keys to open the Run dialog box and type “appwiz.cpl” in the field and hit Enter to open the Programs and Features window.
  • Next, select the “Turn Windows features on or off” from the options given on the left-hand side.
  • After that, look for the Telnet client from the list and check the checkbox next to it and then click on OK to save the changes made.
  • Now restart your computer.

Option 2 – Try to install Telnet via an elevated Command Prompt

If enabling the Telnet client using Programs and Features didn’t work, then you can try to do it using Command Prompt instead. To get started, follow the steps given below.
  • In the Windows Search bar, type “command prompt” in the field and right-click on Command Prompt from the search results, and select the “Run as administrator” option.
  • Next, execute this command to enable the Telnet client: dism /online /Enable-Feature /FeatureName:TelnetClient
  • Once the command has been executed, close the Command Prompt and restart your computer.
Read More
Fix Device requires further installation Error
If you are trying to connect an external device to your computer but you suddenly encounter an error that says, “Device requires further installation”, then you’ve come to the right place as this post will guide you on how exactly you can fix this error. In most cases, USB sticks, headphones, speakers, and other external devices, install drivers automatically once you connect them to your computer which means that the drivers are downloaded and installed in the system as soon as the external device is plugged in. However, if the driver has become corrupted or outdated, you might encounter an error like the
“Device requires further installation”
Aside from corrupted or outdated drivers, the error could also be caused by pending updates, an incorrect version of the Intel PROSet Wireless driver, or checking the wrong event. Whatever the cause is, this post will provide you with some potential fixes that can help you resolve the problem. But before you troubleshoot the problem, ensure that your Windows 10 computer is updated to its latest version and you must also not forget to check that you’re checking the correct event on the Event Viewer. Once you have these things covered, proceed to the instructions below.

Option 1 – Try to update the device drivers to the latest version

One of the most likely root causes of the “Device requires further installation” error is either outdated or corrupted drivers in your computer. This kind of problem is more common on several devices like scanners and printers for which the drivers are provided with them.
  • First, boot your computer into Safe Mode.
  • After that, 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. From there, look for any outdated device drivers and click on each one of them.
  • After that, right-click on each entry of the device drivers and select the “Uninstall Device” option from the menu.
  • Now restart your computer.
  • After restarting your computer, go to the Settings app and Check for Updates in the Windows Update section.
Note: You also opt to download the latest versions of the device drivers directly from the website of the manufacturer. Once you’ve downloaded them, you can install them into your computer right away and then try connecting the external device again. On the other hand, you can also try to reinstall the device drivers.

Option 2 – Try to install the latest version of the Intel PROSet Wireless driver

A lot of users who experience the problem reported that their wireless driver wasn’t also working properly and it was then found that it was caused by the outdated Intel PROSet wireless driver. Thus, to fix the problem, you need to install the latest version of this driver from the intel.com website and install it on your computer. When you download the driver, make sure that your computer is running an Intel system and then download the correct driver depending on whether your computer is a 64-bit system or a 32-bit one.
Read More
Windows Dynamic Lock is missing or not working
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.
Read More
Windows got stuck on Preparing Windows screen
You might have experienced a situation when you restarted your Windows 10 PC after an upgrade and you tried logging into your account but only a screen with a message saying, “Preparing Windows”. If the screen only stays that way, this indicates that Windows 10 is trying to complete the upgrade or waiting for some files to load up so that you can use your account. Some users also reported that when they tried logging into their accounts, they also get the same message on their screens. To resolve this issue, read on as this post will show you what you can do if your Windows 10 PC is stuck on the “Preparing Windows” screen. A lot of users have tried logging back into their account once more but to no avail as the same screen still greets them. And even when they tried the Ctrl + Alt + Del combo, it still didn’t work. This only goes to show that your account might somehow be corrupted.

Option 1 – Try booting your PC into Safe Mode

The first thing you can do to resolve the issue is to try booting your computer into Safe Mode and then log in using an Admin account. If it seems like your admin account has caused the problem, you need to create an admin account first and then log in after you reboot into the account and then log off. After that, restart your PC normally and check if the problem’s resolved or not. If not, refer to the next given option below.

Option 2 – Try to repair your corrupted profile via Registry

In this second option, you can try to repair the corrupted profile using the Registry but before you proceed, make sure to create a System Restore Point and then follow the steps below.
  • Tap the Win + R keys to open the Run dialog box.
  • Then type “regedit” in the field and hit Enter or click OK to open the Registry Editor.
  • Next, go to this registry key: ComputerHKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionProfileList
  • Once you’ve opened the registry key, you should see a list of all the user profiles on your computer. Now click on each S-1-5 folder and look for the “ProfileImagePath” entry and double-click on it to check which user account it is related to. You will see a path like “CUsersACK” where “ACK” is the username.
  • You should know which among the user account is corrupted. Just look for a key named “RefCount” and change its Value data to “0” and click OK. And if it isn’t available, simply right-click on the right pane and create it.
  • After that, double click on the key named “State” and make sure that the Value data is “0” and click OK.
  • Exit the Registry Editor and restart your computer to apply the changes made.

Option 3 – 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 the cause why your screen is stuck at “Preparing Windows”. 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 4 – Try to repair hard disk errors using the Chkdsk utility

You can also run the Chkdsk utility to resolve the problem. 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.
  • chkntfs /t
  • chkntfs /t:10
Read More
1 2 3 171
Logo
Copyright © 2023, ErrorTools. All Rights Reserved
Trademark: Microsoft Windows logos are registered trademarks of Microsoft. Disclaimer: ErrorTools.com is not affiliated with Microsoft, nor claims direct affiliation.
The information on this page is provided for information purposes only.
DMCA.com Protection Status