So, you have finished with work, game, movie, music, email, or whatever on your PC, you look at the clock, it is late, you decide to go to sleep or outside, you click on the power button and choose shutdown. Now when a PC is shut down you feel good and go with your business but the next time you power it up you get the same error like the computer never really shut down in the first place. You wonder why and reboot it, just in case and all of the sudden error is gone.
If something similar has happened to you or you had the feeling that after shutting down your computer has not really felt like shutting it down, do not seek professional help, everything is OK with you because when you click on shut down, your computer does not really shut down!
Truth is that Microsoft has changed how to shut down works and how rebooting works in Windows with an update but has not publicly said anything about it so some users may experience this feeling of not shutdown phenomenon and might even think there is something wrong with their PC.
Why this change?
A few years ago shutdown button and option in Windows were really shutting down OS, but things changed when Microsoft wanted to increase boot-up speed. Now when that decision was made shutdown option was changed. So, what was changed? Well in order to increase Windows booting time, the shutdown will now turn off power to PC components and it will look like everything is indeed shutdown but the Windows kernel will actually be saved to a hard drive with all settings and just awaken once the PC is turned back ON. This will result in all errors and other stuff being just still present same as they were once the system was instructed to be turned off.
Rebooting your PC will now clear kernel and file from the hard drive and you will get a clean system startup without any issues tied with the kernel itself.
Workaround
Now that we know why and what change has been made to Windows logical question is can we shut down our PC at all properly? Luckily for us, the answer is yes and we will not need any external application to do it, we can still do it inside Windows itself and it is quite quick and easy.
Bringing back the old shutdown
In order to bring the old shutdown functionality of your PC please follow the instructions but be aware that by doing this your PC will boot a little bit slower since it will have to load the kernel from scratch each time computer is turned ON.
First thing is to go to settings and go to System
Then once you are inside the system, navigate to the power and sleep and click on it to select it. Once you have it selected to all the way to the right and click on additional power settings.
When you click on advanced power settings you should be led to the control panel's power options. Inside this panel click on top left link where it says Choose what the power button does.
Inside options, you will need to untick the box next to Turn on fast startup (recommended), this option has been ticked ON by the Windows update and probably without notifying you. Option means exactly what was described, it will save kernel state on the hard drive for faster boot time but sadly it can cause some issues since it will never be reloaded from 0.
If you are unable to uncheck the box click on the text beside the shield icon that says: Change settings that are currently unavailable (you will have to be logged in as administrator).
Conclusion
Altho turning off fast startup and shutting down the PC completely will for sure extend your bootup time I still believe that it is the right choice since sometimes a lot of clutter and bad things accumulate over time inside the OS and can cause a vast variety of problems in a long run. So stay safe and shut down that PC as it used to be in the past.
There are times when the WMI Repository gets corrupted which results in the Provider Load Failure. To resolve this issue, you need to repair or rebuild the WMI Repository in your Windows 10 computer. In this post, you will be guided on how exactly you can do that.
In case you don’t know, the WMI which stands for Windows Management Instrumentation is a set of specifications from Microsoft to consolidate the management of devices and applications in a network. The WMI is a database that stores meta-information and definitions for WMI classes. Using only these, the conditions of the systems can be known.
You can find the WMI Repository in %windir%System32WbemRepository. It provides end-users with the status of the local or remote computer system. Keep in mind that you must not use this on the Server 2012 Cluster machine.
Although there are command-line tools that can fix or restore the Windows Management Instrumentation repository. However, Microsoft suggests that it’s better if you verify if there is corruption. Here are a list of errors as well as permission issues you might encounter:
Unable to connect to root default or rootcimv2 namespaces. It fails with the error code “0x80041002” pointing to “WBEM_E_NOT_FOUND.”
0x80041010 WBEM_E_INVALID_CLASS
When you open Computer Management and Right Click on Computer Management (Local) and select Properties, you get the following error: “ WMI: Not Found” or it hangs trying to connect
Trying to use wbemtest , and it hangs
Schemas/Objects missing
Strange connection/operation errors (0x8007054e)
To verify if there is corruption, you can try running the following command in an elevated Command Prompt:
winmgmt /verifyrepository
After you enter the command, if there is a response saying, “repository is not consistent”, then the repository has an issue. If not, then something else is causing the problem. Since you are certain that corruption exists in the WMI repository, then here are some suggestions you need to check out to repair or rebuild the WMI repository.
Option 1 – Try to reset WMI Repository
Type “command prompt” in the Start Search and right-click on Command Prompt from the search results and then select “Run as administrator”.
After opening Command Prompt with admin privileges, type and enter this command: winmmgmt /salvagerepository
The command you entered is used when the winmmgmt command performs a consistency check. So if an inconsistency is detected, it will rebuild the repository.
Next, execute this command to see if the WMI repository now comes back as consistent: winmgmt /verifyrepository
This command will perform a consistency check on the WMI repository.
If it states that the WMI repository is not consistent, then you need to type and enter this command: winmgmt /resetrepository
This command is used to reset the repository to its initial state when the operating system was first installed.
Option 2 – Try to force recover the WMI Repository
The WMI Repository comes with a built-in self-recovery process so when the WMI service restarts or detects any corruption, it will automatically trigger the self-recovery procedure. This can happen in two ways:
AutoRestore: This will use the backup images if the Volume Shadow copy or VSS backup is turned on.
AutoRecovery: The rebuilding process will generate fresh images of the WMI repository based on the registered MOFs. The MOFs are available in the registry located at HKLMSoftwareMicrosoftWBEMCIMOM: Autorecover MOFs
Note: Autorecover MOFs is a key so double click on it to check its value.
On the other hand, if the self-recovery procedure does not work, you can try to use the force-recovery process instead. How? Refer to these steps:
First, you need to check the reg key value is empty or not under this registry path: HKLMSoftwareMicrosoftWBEMCIMOMAutorecover MOFs
If the reg key value is empty, you have to copy-paste the reg key value from another computer. Just make sure that it’s from the System which is equivalent to the computer in question.
Next, type and enter this command: Winmgmt /resetrepository
After you enter the command, if you get an error that says, “WMI repository reset failed. Error code:0x8007041B. Facility: Win32”, then you have to stop all the Dependency Services on the WMI service by running the following commands:
Qtcore4.dll is a dynamic link library file that helps Microsoft Windows in loading several key components of the system.
The Qtcore4.dll error occurs when the Qtcore4.dll file cannot be loaded to run the application supported by this .dll file. The Qcore4.dll missing error message may occur while booting your system or launching a certain program.
It is a blue screen of death error type.
The Qtcore4.dll error code is often displayed as:
BLUE SCREEN ERROR - QtCore4.dll Not Found
Filei386QtCore4.dll could not be loaded. The error code is 7. Setup cannot continue. Press any key to exit.
Solution
Error Causes
This error code is triggered by a variety of reasons such as:
Windows file allocation file gets damaged
Your computer BIOS (Basic Input/Output System) are misconfigured
The Qtcore4.dll file gets corrupt
Registry gets damaged and corrupt
Non-Microsoft program not running in tandem with Windows
Malware attack
Improper hardware driver software
It is advisable to fix the Qtcore4.dll error code immediately as this error can pose serious threats to your system. Qtcore4.dll error can lead to system breakdown.
Further Information and Manual Repair
Here are some ways of fixing the Qtcore4.dll error on your system:
1. Re-install the Program Causing Qtcore4.dll error message to pop up
As dll files are shared files sometimes due to program deletion and installation .dll file settings can get misconfigured, damaged, and corrupt. In such a scenario, you can try reinstalling the program that is causing Qtcore4.dll error message to appear on the screen.
2. Reconfigure your Mis-configured BIOS
If BIOS misconfiguration is the cause of this error code on your system, then try reconfiguring your system’s misconfigured BIOS.
To do this boot the computer and then press the BIOS designated keys to enter the BIOS. The keys may vary from manufacture to manufacture but typically, the setup keys are F2, F10, F12, and Del.
Once you figure out the setup keys, press them rapidly when booting the computer.
After successfully hitting the setup keys, the BIOS will load and you will see the BIOS setting menu on your screen. Adjust settings. Go to SATA Operation and change RAID AHCI to RAID ATA. Save changes and then exit.
3. Scan Your PC with a Registry Cleaner and an Antivirus
However, after adjusting the BIOS if the error still pops up on your screen, then this indicates the problem is bigger than you think.
It triggers either malware attack or registry corruption. If these are the underlying causes for the Qtcore4.dll error on your system then you need to scan your PC with a registry cleaner and an antivirus.
Registry is the main database of your system; if this gets corrupt it is most likely to result in system failure and valuable data loss.
And as for malware, the biggest concern is data security threats. Today’s advanced and lethal malware like viruses and spyware can give easy access to hackers to enter your system from a remote location, browse through your confidential and private data and manipulate it to their advantage.
This has led to a surge in various types of cyber crime, data breaches, and identity theft cases over the years.
To avoid all this while resolving the error code Qtcore4.dll on your PC, registry cleaning and repair and antivirus scan are needed.
You can either download 2 separate tools on your system to scan your PC which by the way will take a lot of time and increase your chances of the system slow down or you can download Restoro.
Why Restoro?
Total System Care is an advanced, user-friendly, high, and multi-functional repair.
It is deployed with a powerful and intuitive registry cleaner. It also functions as a system optimizer. It spares you from downloading numerous tools to address and resolve different errors on your PC.
It is your one-stop solution for not only Qtcore4.dll problems but practically all PC-related issues.
The registry cleaner utility detects all the malicious, unnecessary, and obsolete files overloading and corrupting your RAM.
This includes junk and temporary files. It wipes them out thus clearing your disk space. Simultaneously, it also repairs the damaged and misconfigured dll files including the Qtcore4.dll file, and fixes the corrupt registry.
The privacy error utility has the properties of an antivirus. It detects and removes malware, viruses adware, and spyware from your system in seconds.
Total System Care resolves the Qtcore4.dll error on your system and boosts the performance of your system. It has a simple and neat interface which makes it quite easy for users to operate it, even those who are not technically adept.
It is compatible with all Windows versions
Click here to download Restoro and repair the Qtcore4.dll error on your PC.
One of the most important User Interface elements in a Windows 10 operating system is the Start Menu. Not too long ago, Microsoft has added some new features and redesigned the Start Menu a couple of times as well. Thus, it is not uncommon for Windows 10 users to use several monitors. That’s why in this post, you will be guided on how you can move the Start Menu to your second monitor in Windows 10.
There are a lot of advantages in using more than one monitor like a better and widescreen as well as help in improving and increasing productivity. Usually, the Start Menu and the taskbar is present in the original monitor only. In most cases, it helps users in moving the Start Menu to the second monitor and helps users in segregating tasks, and uses separate monitors for each kind of task.
There are two simple steps to move the Start Menu to the second monitor. You have the option to unlock and drag the taskbar, as well as make adjustments in the settings. To get started, refer to each one of the following options to move the Start Menu to the second monitor.
Option 1 – Move the second monitor by unlocking and dragging the taskbar
The first option you can try to move the Start Menu to the second display is to simply unlock and then drag the taskbar. To do so, follow these steps:
First, click on the Taskbar and unlock it.
Next, uncheck the Lock the taskbar feature in the menu of the Taskbar Settings. This will free the taskbar so you can move or drag it around.
After that, push the Start Menu to the furthermost corner of the screen and then transfer it to the second monitor.
Option 2 – Move the second monitor using the keyboard
The first thing you have to do is to tap the Windows key to open the Start Menu.
Next, close the Start Menu by tapping the Esc key.
After that, the controls will shift back to the taskbar.
Now open the context menu of the taskbar by tapping the Alt + space bar together. This will move the Start Menu to the second monitor.
Option 3 – Move the Start Menu to the second monitor via Settings
If you find that the Taskbar is moving to the wrong monitor automatically or if the program does not start on the same monitor as the taskbar, then you can try this option.
Click on Start first and click Run.
Then type “desk.cpl” in the field and click OK.
Alternatively, you could also right-click on the desktop and select the Screen Resolution option from the drop-down menu.
After that, click on the monitor that you want to use as the primary monitor and select the checkbox labeled “Make this my main display”.
Once done, you have to choose the “Show desktop” on only 1 from the drop-down menu of Multiple displays.
Now click the Keep Changes option and select the Extend these displays from the Multiple displays drop-down menu and then click on the Apply button to save the changes made.
Afterward, click the Keep changes option once the dialog box pops up.
To begin with, Cyclic Redundancy Check is basically an error checking technique. This technique is used for data verification. It detects accidental changes in the data. It is used by computers to specifically check the data stored in the hard drive or optical disks (DVD’s and CD’s).
The Cyclic Redundancy Check error occurs when the data being verified on the hard drive or optical disks is corrupt.
Symptoms for this error code include program lock-ups, slow PC performance, inability to run and execute the desired program, system freeze and shutdown and startup issues.
Error Causes
The Cyclic Redundancy Check error code occurs due to the following reasons:
Cluttered hard disk
Registry corruption
Misconfigured files
Unsuccessful program installation
All these causes points towards registry issues and poor PC maintenance. The registry is the main database of the computer. This part of the PC saves practically every activity you perform on it including activities like application installation and deletion and web browsing to name a few.
With time and frequent PC usage, the files generated from every activity you execute on your system begin to load the registry. These include even the unnecessary files like junk files, internet files and files of applications that you’ve uninstalled.
All these files overload the registry and acquire a lot of hard disk space. And when you don’t remove these files on your system, eventually it leads to file misconfiguration, cluttered disk, and registry corruption.
New program versions that you want to install and run on your system also don’t function because the files of the old program version still saved in the registry.
Further Information and Manual Repair
As the Cyclic Redundancy Check Error causes data corruption on the hard disk, it is advisable to fix this error right away. The reason is that it can have serious consequences. It can lead to data loss, fatal crashes, and system failures.
When it comes to resolving Cyclic Redundancy Check Error, there are two ways to fix it:
Run the CHKDSK application.
This is a built-in feature in your Windows system. It checks for hard disk damage and attempts to resolve it.
There are instances when there are multiple accounts which is the result when there are a lot of users who use the computer. Some may use it more often, while others may seldom use it. Having multiple accounts can be quite confusing and inconvenient especially if it takes a lot of space. Thus, in this post, you will be guided on how you can delete a User Account on your Windows 10 computer, as well as how you can create a backup of the existing profile data and files.
All the data of user accounts can be found at C:/Users, where its folder name will be exactly the same as the name of the user. You can check the exact user’s name by simply using the “net user” command either via Command Prompt or Windows PowerShell. Once you delete a user account, its folder, along with its files, will also be deleted. You can also create a backup for user files and the best way to do that is by copying the folder to other partitions or to an external drive.
Here are two methods you can check out to delete a user account in Windows 10 – you can do it via Windows Account settings or via the command line. For more details, follow each one of the options provided below.
Option 1 – Delete the user account using Windows Account settings
First, go to Settings > Accounts > Family & other users.
Next, select the account you want to delete and click on the Remove button. This will open a confirmation window along with a warning message and two buttons that say, “Delete account & data” and “Cancel”.
Click on the Delete account & data button to delete the user account.
Note: Once you remove a user account, it will also remove all its corresponding data such as items like Documents, Photos, Music, Desktop, and other related folders. Thus, if you have not created a backup, then you won’t be able to recover those files.
Option 2 – Delete the user account using the command line
If you want to delete several user accounts, then doing it via Command Prompt or Windows PowerShell is a lot quicker. To get started, follow these steps:
In the Start Search, type “command prompt” and from the search results that appear, right-click on Command Prompt and select the “Run as administrator” option.
Next, type the “net user” command and hit Enter to execute it. This will show you the exact usernames on the computer.
After that, type the “net user <username> /delete” command and hit Enter to execute it. This will delete the account and all of its data without any warning. You have to replace “<username>” with the name of the user account.
When you have to connect to a drive that’s on a different computer or on external storage, that’s where the mapped network drives come in. Mapped network drives make accessing files a lot easier. However, there are times when it won’t work for some reason.
Windows will notify you about the unavailability of mapped network drives in several ways. For one, Windows might display a red X on the network drives or it could be that its status will be unavailable when you try to use it from the Command Prompt or via a notification.
It is recommended that you run a few scripts when you log in to your PC as it may so happen that the network drive takes more than usual to connect. Before you start troubleshooting the problem using the given options below, keep in mind that some workouts might only work under certain scenarios. You might need some network access at logon or you might need access to the Group Policy settings. So you need to choose what you prefer more.
You can try the given workarounds below if the mapped network drives are not showing or connecting or working on your Windows 10 computer. These workarounds use scripts to make sure that you are connected to them as soon as you start to use your PC.
As mentioned, before you can troubleshoot, you need to create scripts first. There are two scripts here namely MapDrives.ps1 which is executed by the second script named MapDrives.cmd and is done at a regular and non-elevated Command Prompt. Follow the steps below to get started.
You have to create a script file named “MapDrives.cmd” first and then save it on a place where the files are safe. To do that, open a text editor like Notepad and then copy and paste the following script:
After that, save the file and name it “MapDrives.cmd”.
Next, create a script file named “MapDrives.ps1” and then copy and paste the following content. Just make sure to save both scripts in the same folder.
$i=3while($True){ $error.clear() $MappedDrives = Get-SmbMapping |where -property Status -Value Unavailable -EQ | select LocalPath,RemotePath foreach( $MappedDrive in $MappedDrives) { try { New-SmbMapping -LocalPath $MappedDrive.LocalPath -RemotePath $MappedDrive.RemotePath -Persistent $True } catch { Write-Host "There was an error mapping $MappedDrive.RemotePath to $MappedDrive.LocalPath" } } $i = $i - 1 if($error.Count -eq 0 -Or $i -eq 0) {break} Start-Sleep -Seconds 30}Note: Now that you’ve created the script files, it’s time for you to proceed to the options given below.
Option 1 – Try creating a startup item
Note that this option only works on devices that have network access at login. So if it’s not there, the script will fail to reconnect the network drivers automatically. To create a startup item, here’s what you have to do:
Open the Startup folder located at %ProgramData%MicrosoftWindowsStart MenuProgramsStartUp.
From there, copy and paste the MapDrives.cmd.
After that, open the Scripts folder located at %SystemDrive%Scripts copy-paste MapDrives.ps1 and then copy and paste MapDrives.ps1 in there.
Note: After you complete the steps above, a log file named “StartupLog.txt” will be created in the %TEMP% folder. Now all that’s left for you to do is to log out of your computer and then log back in. This will ensure that the mapped drives are open.
Option 2 – Create a scheduled task
It is possible to create a scheduled task that runs as soon as you log in to your computer. To create a scheduled task, follow the steps below.
You have to copy the MapDrives.ps1 script file to the scripts folder of Windows located at %SystemDrive%Scripts.
After that, open the Task Scheduler and select Action > Create Task.
Next, type a name and description of the task in the General tab.
Then click on the Change User or Group button and select a local user group and click OK.
Now check the box labeled “Run with highest privileges” and switch to the Triggers tab.
From there, create a new trigger with the “At Logon” option in the Begin the task drop-down menu and then click OK.
After that, switch to the Actions tab and create a new action then choose to Start a program.
Next, type “Powershell.exe” in the Program/Script field, and in the Add arguments (optional) field, type the following:
And in the Start in the (optional) field, type “%SystemDrive%Scripts” as the location of the script file.
Now under the Conditions tab, select the “Start only if the following network connection is available” option and then select Any connection and click OK.
Restart your computer or log off from your account and then log back in so that the task will be executed.
Option 3 – Use the Group Policy settings
You need this option if the mapped network drives are defined via Group Policy settings. You have to update the action of the drive maps to Replace. As a result, it will delete the existing mapped drive and create the mapping on each logon again. However, any settings on the mapped drive that are changed from the Group Policy settings will be gone on each logon. So if the changes don’t work, you need to run the gpupdate command together with the /force parameter in order to refresh the Group Policy setting quickly.
There are many times when you have to change the ownership of a folder or a file so that other users can use them as well or if you want to transfer files to them, or an old account has been removed and all the files need to be assigned to a new user. Windows 10 keeps all these files locked under the account by default which created a folder or file. So unless a user is an admin or if the file belongs to that particular user, other users won’t be able to access or edit the file. So if you want to change the ownership of a folder or a file, then you’ve come to the right place as this post will guide you on how exactly you can do that.
To get started, make sure to follow the instructions provided below carefully.
Step 1: First, you need to open File Explorer by tapping the Win + E keys. Once you’ve opened it, navigate to the folder or file that you want to change the ownership.
Step 2: Right-click on the folder or file and click on Properties and then go to the Security tab.
Step 3: From there, click on the Advanced button located at the bottom right part of the window to open the Advanced Security Settings of the folder or file.
Step 4: As you can see, the current owner will be listed with the Change link available next to the “Owner” label. Now click on this link to open the Select User or Group window.
Step 5: After that, click on the Advanced button once again and click on the “Find Now” button to see the list of all the users as well as groups that are available in the computer.
Step 6: Then select the user you want to give ownership to and click on the OK button and then click the OK button once more to save the changes made.
Step 7: This will take you back to the Advanced Security Settings window but this time, the owner will be changed to whoever user you’ve selected. But you’re not done yet as you still have to check two additional options to help you completely transfer the ownership of the sub-folders as well as the files. You have to check the checkbox of the following options:
Replace owner on sub-containers and objects
Replace all child permission entries with inheritable permission entries from the object.
Step 8: After that, you need to click the Apply and OK buttons to confirm and save the changes made. This will completely transfer the ownership of the file. However, there is still one last thing you have to do – you have to go back to the Advanced Security Settings window to remove the access of any other user on the folder or file. Once you’re there, remove the existing user to make sure that the only assigned user has the access to the folder or file.
The Windows 10 system allows users to change the default location of the User folders to another drive. This is probably to make sure that the files stay safe in case the system suddenly crashes. However, in some cases, while changing the path to another drive, for instance, the D drive or any folder, the Windows system recognized it as a hard drive as well so even though the files will be saved on that folder, it will appear as a hard drive in the Windows Explorer or look merged with another folder. It could also be that you had dragged and dropped a user folder to another user folder by accident. So if you’re wondering how you can unmerge the User folders, read on as this post will guide you on how exactly you can do that.
Take note that even if you try to use the File History to restore the User folders, it still won’t work and you won’t be able to move them back to their previous locations nor restore the folders back to their previous versions and it would only state that they are not available. In the instructions given below, we are using the Downloads folder as an example.
Step 1: Tap the Win + R keys to open the Run dialog box.
Step 2: Next, type “Regedit” in the field and hit Enter to open the Registry Editor.
Step 3: After opening the Registry Editor, navigate to the following registry key:
Step 4: Then double-click on the multi-string value {374DE290-123F-4565-9164-39C4925E467B} located in the right hand pane. And in the Value Data, copy and paste the following value:
%USERPROFILE%Downloads
Step 5: Now click OK and close the Registry Editor.
Note: Look close enough and you’ll see that the multi-string values belong to each one of the folders. From there, you have a Desktop, Favorites, Skydrive, Music, Pictures, and many more.
Step 6: Restart your computer. After that, the operating system will pick up the new folder location during the startup. Here are the values for the other folders:
Step 7: Now all you have to do is to change the location correctly. Start by tapping the Win + E keys to open the Windows File Explorer.
Step 8: After that, right-click on the Downloads folder located in the right-hand pane.
Step 9: Then click on Properties and go to the Location tab then type “D:\Downloads” in the location box.
Step 10: Click the Apply button and then the OK button to save the changes made. Doing so would ensure that not only the Downloads folder is restored but also that it does not stay merged to another folder or appear as a drive.
If you have suddenly run into a problem when trying to connect or pair your Bluetooth keyboard with your Windows 10 computer, read on as this post will guide you on how exactly you can resolve the problem.
This kind of problem typically occurs when you’ve disabled the Bluetooth option. However, this option is already enabled and you still encountered the same error message saying, “Check the PIN and try connecting again”, then you need to troubleshoot the problem further.
In most cases, this kind of issue can be fixed when you restart your computer and go to the Windows Settings and select the “Add Bluetooth or other devices” option and then put the keyboard into pairing mode. And when the keyboard appears in the “Add a device” dialog box, just select it. On the other hand, if your Bluetooth keyboard won’t get connected to your Windows 10 computer and you encounter an error that says, “Can’t pair Bluetooth keyboard, Check the PIN and try connecting again”, then you need to check out the options provided below but before you do so, make sure that you create a System Restore point first as some of the troubleshooting options provided involves the Windows Registry.
Option 1 – Try to use the Device Pairing Wizard
The Device Pairing Wizard is the one that allows your computer to look for any new devices and display them underneath it. All you have to do to use this wizard is to follow its instructions to connect your Bluetooth device to Windows 10. To get started, follow these steps:
First, tap the Win + R keys to launch the Run utility and type “devicepairingwizard” in the field, and then hit Enter to run the Device Pairing Wizard.
After that, wait for a couple of seconds until the devices appear. Once they do, select the Bluetooth device you wish to add.
A new screen with a passcode should appear instantly. You need to take note of the given passcode and type them on your Bluetooth keyboard.
Once done, tap Enter. This should help in pairing your computer to your Bluetooth keyboard.
Option 2 – Try to use the Registry Editor
The next thing you can do to resolve the pairing issue with your Bluetooth keyboard is to use the Registry Editor by following these steps:
Tap the Win + R keys to open the Run utility and type “Regedit” in the field and then hit Enter to open the Registry Editor.
Next, navigate to this registry path: HKEY_USERS/.DEFAULT/Software/Microsoft/Windows/CurrentVersion/Bluetooth/ExceptionDB
From there, look for the folder named “Addrs” and expand it. If you see any folders or keys under it, select them and delete them. These keys represent the MAC address of your Bluetooth devices.
Once you’re done, restart your computer and try to pair your Bluetooth keyboard once more.
Option 3 – Try running the Bluetooth Troubleshooter
As you know, Windows 10 has various troubleshooters with user-friendly interfaces where you can utilize them to fix issues in your PC. And since you’re dealing with some Bluetooth problem, you have to run the Bluetooth Troubleshooter.
Open the Windows 10 Settings.
Then go to Update & Security > Troubleshoot.
You should find the option for Bluetooth on your right-hand side – click on it then click on the “Run the troubleshooter” option.
Now follow the next screen options.
Option 4 – 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 you have trouble pairing your Bluetooth keyboard, you can update, rollback, 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.
If a program tried and failed to use the Graphics rendering capabilities of a computer, Windows 10 will most likely throw a Blue Screen error that says, “ THREAD_STUCK_IN_DEVICE_DRIVER ”. 0x000000EA is the Stop code for this particular Blue Screen error and could be caused by a bad display driver or bad video card. Whatever the cause is, here are some suggestions you need to check out to resolve this Blue Screen error.
Option 1 – Try to rollback, update, or disable the Graphics card drivers
Since the THREAD_STUCK_IN_DEVICE_DRIVER Blue Screen error has something to do with Graphics card drivers, you can either roll back, update or disable them depending on your preference in order to resolve the error.
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 the Display Adapters and click on them.
After that, right-click on each entry under the Display Adapters 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 have the option to go directly to the website of your graphics card manufacturers like NVIDIA, Intel, or AMD and go to the section called Drivers then check if there’s a new available update – if there is, download and install it.
Option 2 – Try removing hardware or drivers that you’ve installed recently
If you have recently installed some hardware or drivers, you might want to disable or remove them since external devices are proven to be one of the factors that trigger Blue Screen errors like THREAD_STUCK_IN_DEVICE_DRIVER. All you have to do is physically disconnect any external devices that are connected to your computer and then check if it fixes the BSOD error or not.
Option 3 – Run System File Checker at boot time
Once you get to the Welcome Screen part, click on Next.
Afterward, click on the Repair your computer option located on the bottom-left part of the window.
Then click on Troubleshoot.
Next, select the Advanced Options and then Command Prompt.
After opening Command Prompt, type the “sfc /scannow” command and hit Enter to run the System File Checker scan.
Wait until the process is completed and type “exit” to close Command Prompt and then restart your computer to successfully apply the changes made.
Option 4 – Try to run the Blue Screen Troubleshooter
As you know, the Blue Screen troubleshooter is a built-in tool in Windows 10 that helps users in fixing BSOD errors like the THREAD_STUCK_IN_DEVICE_DRIVER error. It can be found in the Settings Troubleshooters page. To use it, refer to these steps:
Tap the Win + I keys to open the Settings panel.
Then go to Update & Security > Troubleshoot.
After that, look for the option called “Blue Screen” on your right-hand side and then click the “Run the troubleshooter” button to run the Blue Screen Troubleshooter and then follow the next on-screen options. Note that you might have to boot your PC into Safe Mode.
Option 5 – Try to manually check the Graphics Card hardware
You might also want to check the physical status of your Graphics card and you can do this by disconnecting the Graphics card or any other external device connected to your computer. Once you’ve removed the external device, check it for any damages. If there’s none, connect it back to your computer and check if the THREAD_STUCK_IN_DEVICE_DRIVER Blue Screen error is fixed or not.
Option 6 – Uninstall any faulty drivers
You can also uninstall any faulty drivers via Device Manager. How? Refer to these steps:
Tap the Win + R keys to launch the Run dialog box.
Then type “devmgmt.msc” in the field and tap Enter to open the Device Manager.
From there, look for any faulty drivers. You can identify them easily as they will be marked with a yellow exclamation point. And then check which entries would not affect the normal functioning of your PC.
Now click on the entries of every faulty driver and click on the Uninstall option.
Once you’ve uninstalled them, restart your computer to allow your computer to reinstall the faulty drivers you’ve just removed.
