
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:
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.
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.
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.
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:
And if it’s a desktop app, you have to enable the toggle on at the end.
Digital Publisher: Blueis Product Version: 4.0.0.1 Original File Name: DownloadAdmin Entry Point: 0x0000234A
Users, when upgrading to Windows 10 from Windows 7 or Windows 8/8.1, or when upgrading to a new version, build, service pack, or major update of Windows 10, can encounter error code 0xC1900101, 0x30018. Windows 10 installation fails and stops or hangs. During the installation process, it will reach a certain maximum limit (normally at 6% or 32%) then reverts back to the previous version of the operating system and displays the following message:
We couldn’t install Windows 10. We’ve set your PC back to the way it was right before you started installing Windows 10.
0xC1900101 – 0x30018 The installation failed in the FIRST_BOOT phase with the error during the SYSPREP operation.
In attempting to fix Error Code 0xC1900101-0x30018, it is vital to know what causes this issue. The most probable causes of this error are:
NOTE: If this fails, if possible, you can try using the .ISO file in upgrading.
If you’re using Windows Update in installing Windows 10, you can implement the following:
NOTE: Don’t forget to hit Enter after every command.
net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver
NOTE: Don’t forget to hit Enter after every command.
ren
C:WindowsSoftwareDistribution SoftwareDistribution.old
ren
C:WindowsSystem32catroot2 Catroot2.old
NOTE: Don’t forget to hit Enter after every command.
net start wuauserv
net start cryptSvc
net start bits
net start msiserver
sfc/scannowWhen it is done, a message will confirm that Windows found some corrupt or missing files and it has successfully repaired those. Check the Outlook and see if your emails are sending. If the problem persists, don’t worry there is another way to solve this. Users have found another command helpful is using the NetShell utility from the command prompt, which is similar to the above solution.
netshwinsosk resetThis helpful command will reset the network adapter to its default settings. Hope this will solve your problem. If not, you may want to try the Method 2 listed below.