Fix Unknown USB Device error message

If you are trying to log into your user account on your Windows 10 computer but encountered an error message instead that says, “Your account has been disabled, Please see your system administrator”, read on as this post will guide you on how you can fix this problem. In this kind of scenario, you won’t be able to access your data unless you have access to the administrator account. This problem could be caused by several problems. It is possible that malware has infected your computer and has changed some settings in your computer, especially if your system has been under a malware attack not too long ago. The malware could’ve changed the “Account is disabled” option. The only thing you can do to resolve this kind of problem is to log into your computer using another administrator account and then change the setting. However, if you don’t have a second administrator account, you can just enable the built-in hidden administrator account on your computer. You shouldn’t have any problem enabling the hidden administrator account as it is quite easy when you can log into your account. And in this post, you will be guided on how you can enable the hidden administrator account using the Registry Editor to fix the “Your account has been disabled, Please see your system administrator” error.

To get started, follow the instructions given below.

1. First, you need to start your computer and ensure that you are on the error screen. From there, you will see the Power options located on the right-hand side.
2. Click on the Power options and tap and hold the Shift key and then select Restart.
3. After that, the Advanced Boot Options will appear and from there select Troubleshoot > Command Prompt.
4. Next, you have to select your user account and enter the user account’s password to open Command Prompt.
5. After opening Command Prompt, open your screen and type “Regedit” and then tap Enter on your keyboard.
6. Now select the HKEY_LOCAL_MACHINE in the Registry Editor and go to File > Load Hive.
7. Afterward, you have to open the Windows installation drive and go to the location – WindowsSystem32Config
8. From there, you should find a file named “SAM” – select this file and click the Open button.
9. Next, you have to enter a key name. You can just input whatever you prefer.
10. Once done, navigate to this path: HKEY_LOCAL_MACHINEkey_nameSAMDomainsAccountUsers
11. From this path, you will see a key named “000001F4” – select this key and double click on the “F” entry that you can find on the right-hand side of the screen.
12. After that, look for the value data line labeled “0038” which should show 11 in the first column. You have to replace it with 10.
13. Once done, click on the OK button and close the Registry Editor and the Command Prompt to restart your computer.
14. Now once your computer has restarted, sign in to the Administrator account and open the Computer Management window. You can just search for it using the search bar in the Taskbar.
15. After you open Computer Management, go to Local Users and Groups > Users – where you can find all the user accounts. Look for your deleted user account and right-click on it and select Properties and then unmark the checkbox that says “Account is disabled”. This should fix the problem.

Windows and Devices chief Panos Panay has revealed new focus sessions feature that will be in Windows 11 on his Twitter account today. He himself is referring to it as a game-changer especially with Spotify integration.

So what is a focus session?

From the video clip provided on Twitter, we can see that focus session users will be able to choose a specific task from the previously made task list, choose songs that will play in the background while the task is active, and set a timer for the chosen task with breaks. Maybe the best comparison and explanation would be a desktop google calendar task with music, basically, that’s it. A neat and good organizer inside your Windows 11 operating system. I think that this is generally a good idea and for sure it will find its audience.

If you suddenly encounter the DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL Blue Screen error on your Windows 10 computer along with the error codes, 0x000000D5, 0xb10BBD9E, 0x0D82DA24, 0Xfecd479D, 0x779827CB then read on as this post will provide you some troubleshooting tips that could help you resolve the BSOD error. Getting this kind of BSOD error means that a driver has referenced memory that was freed earlier and it could also mean that the Driver Verifier Special Pool option has caught the driver accessing memory which was freed earlier. Follow the given options below to fix the DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL BSOD error.

Option 1 – Use the Driver Verifier Manager

The Driver Verifier Manager is another tool in Windows that could help you fix driver-related issues.

• Type in the keyword “Verifier” in the Cortana search box to search for Verifier in Windows 10.
• After that, select the option “Create custom settings”.
• Make sure that you have checked everything except the options “DDI compliance checking” and “Randomized low resources simulation”.
• Next, select the option “Select driver names from a list” option.
• Afterward, you have to select all the drivers from any unofficial or third-party provider. To simply put it, you have to select all the drivers that are not supplied by Microsoft.
• Then click on the Finish button.
• Open Command Prompt as administrator and execute this command – verifier /querysettings
• The command you just executed will display the Driver Verifier settings so if you see any of the flags enabled boot your Windows 10 PC into Safe Mode.
• Open the Command Prompt as admin again and run this command – verifier /reset
• The command will reset the Driver Verifier. Once the process is done, restart your PC and check.

Option 2 – Try updating SSD firmware

If you have installed SSD on your computer recently and you have started getting the DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL Blue Screen error since then you may have to update the SSD firmware. To fix this, you can download the Intel Solid-State Drive Toolbox from the official website. This toolbox is compatible with Windows 10 and Windows 7 and later versions.

Option 3 – Try running the Blue Screen Troubleshooter

The Blue Screen troubleshooter is a built-in tool in Windows 10 that helps users in fixing BSOD errors like DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL. 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.
• From there, 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 4 – Try running Microsoft’s online Blue Screen Troubleshooter

If running the built-in Blue Screen Troubleshooter didn’t work, you can also try running Microsoft’s online Blue Screen Troubleshooter. All you have to do is go to Microsoft’s website and from there, you will see a simple wizard that will walk you through the troubleshooting process.

Option 5 – Try to reinstall or update device drivers of recently installed hardware

If the first few options didn’t work for you, then it’s time to either update or roll back the device drivers. It is most likely that after you updated your Windows computer that your driver also needs a refresh. On the other hand, if you have just updated your device drivers then you need to roll back the drivers to their previous versions. Whichever applies to you, refer to the steps below.

• Open the Devices Manager from the Win X Menu.
• Then locate the device drivers and right-click on them to open the Properties.
• After that, switch to the Driver tab and click on the Uninstall Device button.
• Follow the screen option to completely uninstall it.
• Finally, restart your computer. It will just reinstall the device drivers automatically.

Note: You can install a dedicated driver on your computer in case you have it or you could also look for it directly from the website of the manufacturer.

Option 6 – Try disabling Hardware Acceleration

You might want to disable Hardware Acceleration system-wide or for a particular program like Google Chrome and see if it resolves the DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL BSOD error

As you know, Windows Update is the source for everything latest for Windows from Microsoft. Your computer receives essential updates frequently because of the Windows Update service and this Windows Update mechanism depends on various services such as Background Intelligent Transfer Service or BITS, Windows Server Update Service, Windows Update service, and many more. Although it may seem like a complex delivery system, it is a very efficient one. However, it is not without its issues as it still encounters errors every now and then. One of these errors is 80244019 which applies only to the Windows Server operating systems and to resolve it, you need to determine its cause. The Windows Update Error 80244019 is most likely caused by faulty and corrupted DLL files or Registry Entries, connectivity issues, and outdated configuration of Windows Update service on the client end. Moreover, the error can also be caused by malware or if a file is not found on the server. This error can lead to a number of system issues like Startup and shutdown issues, software installation errors, external devices connection, system lags, unexpected application, and program issues, and many more. To resolve the problem, refer to the options given below.

Option 1 – Restart some Windows Update services

The first thing you have to do is to restart Windows Update-related services. Refer to the steps below to do so.

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

net stop wuauserv net stop bits

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

net start wuauserv net start bits

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

Option 2 – Try turning on the Data Execution Prevention or DEP

The problem might be caused by disabled Data Execution Prevention which is why you have to make sure that it’s turned on.

Option 3 – Run the Windows Update Troubleshooter

You might also want to run the Windows Update Troubleshooter as it could also help in fixing Windows Update Error 80244019. 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 4 – Try reconfiguring the Windows Update Settings

You can also try to reconfigure the settings in the Windows Update section to resolve the error.

• Tap the Win + I keys to open the Windows Settings.
• Next, click on Update & Security > Windows Updates > Update Settings and from there, click on the Advanced Options.
• After that, uncheck the “Give me updates for other Microsoft Products when I update Windows” option.
• Now restart your computer to successfully apply the changes made and then check if the Windows Update error is now fixed.

Option 5 – Try to manually install the Windows Updates

Windows Update Error 80244019 might be due to a Windows Update that has failed. So if it is not a feature update and only a cumulative update, you can download the Windows Update and install it manually. But first, you need to find out which update has failed, and to do so, refer to the following steps:

• Go to Settings and from there go to Update and Security > View Update History.
• Next, check which particular update has failed. Note that Updates that have failed to install will be displayed under the Status column which has a label of “Failed”.
• After that, go to the Microsoft Download Center and look for that update using its KB number and once you find it, download and then install it manually.

Note: You can also use the Microsoft Update Catalog, a service from Microsoft that provides a list of software updates that can be distributed over a corporate network. With the help of this service, it can be easier for you to find Microsoft software updates, drivers as well as fixes.

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.

One of the great remote assistance software that helps you remotely access and control computers is TeamViewer. However, despite how efficient it is, there are still times when it throws up some errors and one of them is when TeamViewer is not able to connect and throws an error that says, “No connection to partner, Partner did not connect to router, Error Code WaitforConnectFailed”. This kind of error in TeamViewer mostly occurs when the Partner computer is not connected to a network. On the other hand, it could also occur when they are connected to a network so there are various causes for this issue. It could also be that the installation of the program itself was at fault or there is an incompatibility between the TeamViewer versions installed on both the computers and so on. Although there are several causes for this error, the potential fixes are still the same. You can try to restart the network or allow Full Access Control to TeamViewer or flush the DNS cache. For more information, refer to the following options but before you proceed, make sure that both your Windows 10 computer and TeamViewer program are updated to their latest stable versions.

Option 1 – Reboot your router

The first thing you can try to do to fix the error is to simply restart your router. All you need to do is reboot the router from its Admin panel or you can also turn it off manually and turn it back on after a couple of seconds so that it can completely reboot. Once you’re done, try accessing your server again and see if the error is now fixed.

Option 2 – Allow Full Access Control to TeamViewer

• First, open TeamViewer, and then from the Menu bar, click on Extras.
• After that, click on Options and select Advanced from the left side navigation panel.
• Next, click on the “Show advanced options” button located on the right-hand side.
• Then select Full Access from the drop-down menu of the Access Control option under the “Advanced settings for connection to this computer section”.
• Now click OK and check if the error is now fixed or not.

Option 3 – Try to flush the DNS configuration

You could also try to flush the DNS configuration in your computer to fix the error. How? Refer to these steps:

• Tap the Win + X key combination and click on the Command Prompt (Admin) option or you could also search “cmd” in the Cortana search box and right-click on Command Prompt from the search results and select the “Run as administrator” option.
• After opening Command Prompt with admin privileges, enter each one of the commands given below sequentially in order to flush the DNS cache.
  • ipconfig/release
  • ipconfig/renew
  • ipconfig/flushdns
• Now type the exit command to close Command Prompt and then restart your computer and see if the problem is fixed.

On the other hand, you could also try to reset Winsock as well as the TCP/IP.

Option 4 – Run the Network Adapter troubleshooter

To run the Network Troubleshooter, refer to these steps:

• Open the Search bar on your computer and type in “troubleshoot” to open the Troubleshoot settings.
• Next, scroll down and select the “Network Adapter” option from the right pane.
• Then click on the Run Troubleshooter” button.
• After that, your computer will check for any possible errors and will pinpoint the root cause of the problem if possible.
• Restart your computer.

Option 5 – Try to perform Network Reset

You might perform a Network Reset to resolve the problem if none of the four given options worked. This will reset the entire network configuration including your IP address. To perform Network Reset, follow these steps:

• Tap the Win + I keys to open Settings.
• From there, go to the Network and Internet section.
• Next, scroll down and look for “Network Reset” under the status pane.
• After that, click on Network Reset and then on Reset now to start resetting the network configuration. Once done, check if it is able to fix the error or not.

Libmysql.dll is missing or not found error appears in Windows when the user is trying to open and run the application. In this guide, we will offer you solutions on how to fix and remove this annoying error.

1. Check recycle bin

   Some applications or purely by accident itself libmysql.dll gets deleted. If you have not turned recycle bin off go to it and check to see if the file is by any chance there. If you find it, right-click on it, choose restore, the error will be gone.

2. Update drivers

   Press ⊞ WINDOWS + X to open the Windows menu and click on Device manager In device manager locate device which has alert mark next to it Right-click on it and choose update driver Reboot your computer

3. Run SFC scan

   Press ⊞ WINDOWS + X and choose command prompt (admin) In command prompt type in sfc /scannow and press ENTER wait for the operation to complete and Reboot your system

4. Reinstall application

   if you are getting an error only on one application or an error has started to appear after the installation of a particular application go to Windows applications, uninstall it and then install it again. There is a chance that the file has been corrupted during the installation process.

BSOD or Blue Screen of Death errors are one of the most common errors you can encounter on your Windows PC. One of these BSOD errors is the “ACPI_BIOS_ERROR”. If you suddenly get this error, it means that there is some problem in booting the operating system from your hard drive or Windows was not properly installed on your PC. In addition, this error could also mean that there is something wrong with the CMOS battery located in the motherboard. Unlike other BSOD errors, the workaround for this error is a bit different as these workarounds require a bit more expertise in updating the BIOS as well as setting the correct boot configuration. If you know are capable enough in troubleshooting the problem, refer to the instructions laid out below to fix the BSOD “ACPI_BIOS_ERROR”.

Option 1 – Try to remove the SSD and update the BIOS

The first thing you have to do is to check the primary storage devices on your PC. If you have just installed a new hard drive or SSD recently on your computer, then it’s most likely the cause of the BSOD error. Moreover, you should also ensure that your BIOS is up-to-date to the latest available build.

• Remove the SSD/HDD and inject a different HDD that was already preinstalled in your Windows PC.
• After that, update the BIOS to the latest available build. After updating it, insert the old SSD/HDD and then try to boot your PC again. The problem should be fixed now. If not, refer to the next given option.

Option 2 – Try to check the CMOS battery and reset the CMOS module

As mentioned earlier, the CMOS battery might also be the one that’s causing the problem. It is a physical component of the motherboard and is a memory chip that contains all the settings configuration on your computer and is also powered by a battery. So if your battery loses power, the CMOS will be reset and as a result, all the configurations will be gone as well. It is also possible that the CMOS module is not properly working and every time things are saved, they are properly written due to the battery. That’s why you have to consider changing the CMOS battery and see if it fixes the problem. In addition, you also have to make sure that you completely reset the CMOS module and then try booting your PC again.

Option 3 – Try to check the BIOS settings

If the BIOS settings are incorrect, chances are that’s the reason why you’re getting the “ACPI_BIOS_ERROR” BSOD error. Every BIOS has different settings which you can make use of to enhance your computer experience. So make sure that your BIOS is up-to-date and that the settings are in accordance with your requirement. Another thing you can try is to disable the Legacy USB and the Legacy BIOS in the BIOS settings if you are trying to install a 64 bit Windows version. Make sure that you also enable AHCI before plugging in the installation drive on your PC. Moreover, ensure that your PC is using IDE or Integrated Drive Electronics mode instead of SATA or Serial Advanced Technology Attachment. Aside from that, try to check the extracted setup if it is in NTFS format, if it is, you should extract the ISO in FAT32 and use it to install Windows.

Option 4 – Try to reset the ACPI Compliant Control Method

ACPI or Advanced Configuration and Power Interface provide an open standard that operating systems can use to detect hardware, perform power management, as well as monitor the status of your device and provide information for other processes. Chances are, there are some misconfigurations with this module on your PC that lead to believing that there is no battery present. That’s why you need to reset it and see if it fixes the BSOD error or not.

• Boot your PC into Safe Mode.
• Tap the Win + R keys to open the Run dialog box.
• Type in “devmgmt.msc” in the field and tap Enter to open the Device Manager.
• After opening the Device Manager, go to the “Batteries” section and click it to expand it and then right-click on the “Microsoft ACPI-Complaint Control Method Battery” option and click on Uninstall.
• After you disable the module, click on any empty space and then click the “Scan for hardware changes” option.
• Then check if you can now boot your PC normally and without the BSOD error.

There are a lot of users who use their Windows 10 PCs to create and access data on their servers using their network. However, some of them reported getting an error saying that the server is not accessible. Here’s the full content of the error message:

“\server is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions. Logon Failure: The target account name is incorrect.”

If you are among the users who experience the same issue, read on as this post will help you resolve this error when accessing your server. But before you start troubleshooting the problem, you might want to perform System Restore, especially if tend to create one. To use System Restore, here’s what you have to do:

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

If System Restore didn’t help in fixing the ACPI.sys Blue Screen error now’s the time for you to make use of the potential fixes laid out below.

Option 1 – Try rebooting your router

The first thing you can try to do to fix the error is to simply restart your router. All you need to do is reboot the router from its Admin panel or you can also turn it off manually and turn it back on after a couple of seconds so that it can completely reboot. Once you’re done, try accessing your server again and see if the error is now fixed.

Option 2 – Try checking the status of the Workstation Service

You might want to check the status of the Workstation Service as the error might have something to do with it.

• Tap the Win + R keys on your keyboard to launch the Run utility.
• Then type “services.msc” in the field and click OK or hit Enter to open the Windows Services Manager.
• After opening the Services Manager, you will see a list of all the services on your computer and from there, locate the Workstation Service.
• Double click on the Workstation Service to open its Properties.
• Next, Stop the Service and Start it again or you can also right-click on it and select Restart and then make sure that its Startup type is set to Automatic.
• Now restart your computer and check if the error is fixed.

Option 3 – Try to change the File Sharing Connections setting

You can also try to change the File Sharing connections setting. All you have to do is go to Control Panel > Network and sharing center > Advanced sharing settings > File sharing connections. From there, you need to select “Enable file sharing for devices that use 40 or 56-bit encryption and check if it helps in fixing the problem. If not, undo the changes you’ve made and proceed to the next given option.

Option 4 – Try checking the Network Configuration

Checking the Network Configuration can also help you fix the error. Refer to the steps below to do so:

• Right-click on the Wi-Fi connection or on the Ethernet connection icon located in the system tray.
• Then select open Network and Internet Settings and then click on the “Change Adapter Options”.
• After that, a new window will appear and from there, select the network connection that connects your computer to your network – this can either be a Wi-Fi connection or Ethernet connection.
• Right-click on that connection and select Properties where you will see a list of items.
• Select the Internet Protocol Version 4 or Internet Protocol Version 6 from those items according to your system requirement.
• Then click on the Properties button.
• Check if everything is now configured as to how it is supposed to be and then check if the error is resolved.

Option 5 – Try to reset Winsock, TCP/IP & Flush DNS

You might also want to try resetting Winsock, TCP/IP, and flushing DNS might help you resolve errors. To do so, follow these steps:

• Right-click on the Start button and click on Command Prompt (administrator) so you can pull up an elevated Command Prompt.
• After that, execute each one of the commands listed below. And after you typed in one after the other, you have to hit Enter.

1. netsh winsock reset – type in this command to reset Winsock
2. netsh int ip reset resettcpip.txt – type in this command to reset TCP/IP
3. ipconfig /flushdns – type in this command to flush the DNS cache

• Next, restart your PC and check if the problem’s fixed.

Option 6 – Run the Network Adapter Troubleshooter

• Open the Search bar on your computer and type in “troubleshoot” to open the Troubleshoot settings.
• Next, scroll down and select the “Network Adapter” option from the right pane.
• Then click on the Run Troubleshooter” button.
• After that, your computer will check for any possible errors and will pinpoint the root cause of the problem if possible.

One of the smoother things that Microsoft did with the Windows 10 operating system is to separate Cortana from Search. This means that Cortana is strictly now a voice assistant and many users have seen it coming since not everyone uses Cortana. In addition, it also paved the way for other virtual assistants like Alexa to get on board with Windows 10. And now in the newly released Windows 10 v1903, Windows has brought the Voice Activation under Privacy. In this post, you will be guided on how to perform the Voice Activation troubleshooting on your Windows 10 computer. To use Voice Activation in Windows 10, follow, in the Start Search, type “voice activation” and click on “Voice activation privacy settings” listed in the search results. And from there, you can choose to allow apps to use Microphone, like listen in the background as well as select which app can access it. Each time enabled voice assistants continue to listen via microphone for the voice keyword, the app will activate itself for the keyword and will react depending on what you ask it. So if you are using a voice assistant and it didn’t respond when you speak the keyword, just go to Settings > Privacy > Voice Activation and follow these steps:

Option 1: Check the App permission to use the voice activation feature.

You have to make sure that the toggle button for the Voice activation feature is turned on globally. It can be found under the “Allow apps to use voice activation” section. You also have to ensure that the microphone is available for apps that use this feature.

Option 2: Voice activation is not working under the lock screen.

If you tend to use the voice assistant even when your computer is locked, Microsoft has a specific setting that you have to turn on. You need to make sure that the toggle button for the “Allow apps to use voice activation when this device is locked” option is turned on. However, keep in mind that the voice assistants are not locked to only recognize your voice as they also answer to anyone who will use the voice keyword.

Option 3: Check the individual permissions of apps.

If the voice assistant is not working, you have to check each one of the apps’ permissions for voice keyword, and the option to work under locked condition works.

Option 4: Run the Microphone troubleshooter.

If you’ve verified that the settings are in place, then you have to run the Microphone troubleshooter by simply going to Settings > Privacy > Microphone. From there, make sure that the toggle button for the following options is turned on:

• Allow apps to access your microphone
• Enable microphone access for the voice assistant

And if it’s a desktop app, you have to enable the toggle on at the end.