Mail and Calendar not working with Cortana

In some cases, a couple of Windows 10 laptops, especially the newer ones that run the NVIDIA RTX series GPUs have been experiencing some problems, particularly with their headphone jacks which seem to be malfunctioning even though the internal speakers works just fine. And despite having all the drivers updated to their latest versions, the problem still occurs. According to security experts, this kind of problem occurs on laptop computers that are manufactured by MSI and since there is still no workaround or reliable fix released by the company, in this post you will be guided on how you can resolve the problem with the headphone jack. So if you are using a laptop made by MSI and are experiencing the same issue, then you’ve come to the right place. There are several potential fixes you can check out to resolve the problem, you can try to force reboot your computer or clean your headphone jack and then plug it back in properly. In addition, you could also try to update your Audio drivers or set your headphone as default. For more information, follow each one of the given options below.

Option 1 – Try to force reboot your computer

The first thing you can do is to force reboot your computer as this simple fix could help in fixing the problem. This option is quite simple, just make sure that before you do it, you have to save all your work.

• First, turn on your computer and press and hold the power button for at least 30 seconds. You might notice the screen flashing or making any changes, just ignore it.
• After that, plug out and plug in your computer and automatically turn it on.
• Once done, check if the headphone jack is now working fine.

Option 2 – Try to clean the headphone jack and plug it properly

The next thing you can do to fix the problem is to clean your headphone jack and plug it back in properly. Make sure that you use a cotton swab in cleaning the headphone jack as there are instances where some dust might have settled in the port which results in issues like your headphone jack no working.

Option 3 – Try to update, rollback or reinstall the Audio driver

If the glitch in your audio has something to do with software, chances are it might be related to the audio driver – it could be that the newest version of your Windows 10 does not work well with the old version of the driver. This is why you have to update your audio driver to the newest available version.

• Tap the Win + R keys to open the Run dialog box and then type in MSC and tap Enter or click OK to open the Device Manager.
• Expand the section for the outdated device drivers.
• And then select the 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 or reinstalling the Audio driver didn’t work, you can go to the website of MSI 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.

Option 4 – Try to set the headphone as the default device manually

There are times when you plug a headphone, it does not toggle the default audio device. Thus, to fix this issue, you have to set the default audio device to the headphones manually. To do that, follow these steps:

• First, right-click on the volume icon located on the system tray.
• Next, select the Open sound settings option to open the Sound section in the Windows 10 Settings app.
• From there, select the Control Panel for Sound on the rightmost column. This will open a new mini window.
• After that, select your headphone under the Playback tab and click on the Set default button.
• Once done, click on Apply and then OK buttons to save the changes made.

Option 5 – Try to run the Playing Audio Troubleshooter

Since the Windows 10 operating system has the Playing Audio Troubleshooter, you can use this troubleshooter to try and fix the problem with the headphones. You can access this tool in the Control Panel or in the Taskbar Search and even on the Troubleshooters page of Windows 10.

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

Error 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!

The use of Biometrics is supported by Windows 10. Aside from that, it also supports PIN, password, picture password on all computers and if your computer has the proper hardware, Windows 10 also supports facial scanning, iris scanning, and even fingerprint scanning. You can see all these exciting features inside Settings > Accounts > Sign In Options. On the other hand, you can’t really expect to make use of all the above-mentioned features since it depends if the hardware is available to support them. One of the most interesting features is the use of Biometrics which is really useful in workplaces and so this post will show you how you can enable or disable the Domain Users Sign In on Windows 10 using Biometrics via Registry Editor or Group Policy Editor. But before you go on, you need to create a System Restore Point first since the modifications you’re about to do might affect the functioning of your computer. So in case something went wrong, you can always undo the changes you’ve made.

Option 1 – via Registry Editor

• Tap the Win + R keys to open the Run dialog box.
• Next, type “Regedit” in the field and hit Enter to open the Registry Editor.
• After that, navigate to the following registry path:

HKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftBiometricsCredential Provider

• From there, right-click on the right-side panel and click on New > DWORD (32-bit) Value.
• And then set the name of the newly created DWORD as “Domain Accounts”.
• Afterward, click on “Domain Accounts” and set its value to “1”. This will allow the domain users to sign in to Windows 10 using Biometrics. While the value of 0 will disable the domain users sign in to Windows 10 using Biometrics.
• Exit the Registry Editor and restart your computer for the changes to take effect.

Option 2 – via Group Policy Editor

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

Computer Configuration > Administrative Templates > Windows Components > Biometrics

• Then double click on the following entries located on the right-side panel and set the radio button to Enabled on all of them.
  • Allow the use of Biometrics.
  • Allow users to log on using Biometrics.
  • Allow domain users to log on using biometrics.
• Now exit the Group Policy Editor and restart your computer to apply the changes made properly.

As you know, Airplane mode is the one that gets devices in such a state where all the wireless connections are turned off. However, recently, there are some reports from users claiming that the Airplane Mode turns on by itself in their Windows 10 computers. This kind of problem could be due to an error with the Network driver, third-party applications, and many other factors. Other users also reported that the Airplane Mode automatically flickers, while some stated that they aren’t able to toggle the option for Airplane mode. There are several options you can try to resolve this problem. You can try to configure the Power Management settings for the driver or run the Network troubleshooter. You could also roll back, reinstall or update the Network driver, as well as troubleshoot the problem in a Clean Boot State. For more details, follow each one of the given options below.

Option 1 – Try configuring the Power Management settings for the driver

The first thing you can do to fix the problem is to try configuring the Power Management settings for the driver. How? Refer to these steps:

• Tap the Win + X keys to open the WinX menu and from there, select the Device Manager to open it.
• Next, expand the Network adapters and select the entry for your Wi-Fi hardware.
• After that, right-click on it and select Properties.
• From there, go to the Power Management tab and uncheck the “Allow the computer to turn off this device to save power” option.
• Once done, restart your computer and see if it has fixed the problem.

Option 2 – Try to run the Network 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 3 – Try to update, rollback or reinstall the Network adapter drivers

The next thing you can do to resolve the problem is to update the Network Adapter drivers by following these steps:

• Tap the Win + R keys to launch the Run window and then type in the “devmgmt.msc” command and hit Enter to open the Device Manager window.
• Under the Device Manager, you will see a list of drivers. From there, look for the Network Adapters and expand them.
• Look for the Broadcom Network Adapter and right-click on it, as well as other network adapters that have an exclamation icon, and update them all.
• Restart your PC and see if it helped in fixing the problem.

Note: If updating the network drivers didn’t help in fixing the problem, you can also try to roll back the very same drivers from their previous versions and restart your Windows 10 PC. After that, the system itself will reinstall the drivers you just uninstalled. Alternatively, you can also download and install the drivers from the manufacturer’s website directly. To reinstall the network adapter drivers, refer to these steps:

• 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.

Option 4 – Try to reset the Network Adapter

You can also try to perform a Network Reset to resolve the problem. 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.

Option 5 – Try putting your computer in a Clean Boot State

You can also troubleshoot the problem in a Clean Boot state. It could be that there are some third-party applications in your computer that are causing the Airplane Mode to behave in a strange way. So, to isolate this possibility, you need to boot your computer in a Clean Boot State be using these steps:

• Log onto your PC as an administrator.
• Type in MSConfig in the Start Search to open the System Configuration utility.
• From there, go to the General tab and click “Selective startup”.
• Clear the “Load Startup items” check box and make sure that the “Load System Services” and “Use Original boot configuration” options are checked.
• Next, click the Services tab and select the “Hide All Microsoft Services” check box.
• Click Disable all.
• Click on Apply/OK and restart your PC. (This will put your PC into a Clean Boot State. And configure Windows to use the usual startup, just simply undo the changes.)
• After you’ve set your computer into a Clean Boot State, try to observe if the Airplane mode is now back to normal or not.

Error Code 0x8024402f What is it?

Error code 0x8024402f is a Windows Update error indicating some sort of connectivity issue. Windows may show you the Error 0x8024402f in Windows 10 whenever you try to download and install new updates. This error is caused by small interruptions in communications between the computer to be updated and the update to be downloaded. These issues usually resolve themselves. Windows Firewall settings may also be blamed for this problem. Common symptoms

• Error code 0x8024402f prevents you from installing the latest version of Windows 10
• This Error prevents you from downloading new and latest updates from Microsoft

Solution

Error Causes

• This error is caused by a problem with the Microsoft .NET Framework 4 Client Profile.
• This error can occur even if no changes are made to network settings.
• Your Firewall settings may cause this problem.
• A high number of update requests on the Windows Update server may cause this problem.

More Information and Manual Repair

Method 1:

1. Exit Windows Update. Wait for 10 to 15 minutes, and then restart Windows Update to check for updates. OR
2. Turn on Windows Automatic Update so that updates are installed automatically every 24 hours.

Method 2:

Uninstall the Microsoft .NET Framework 4 Client Profile:

1. Click Start>Control Panel>Programs and Features
2. Locate the Microsoft .NET Framework 4 Client Profile
3. Right-click and then select Uninstall/Change
4. Confirm that you want this component to be uninstalled. This may take a few minutes.
5. Reboot your computer
6. When the system has restarted, re-run Windows Update as you normally would.

Method 3:

Check your internet connection: As mentioned earlier the error code 0x8024402f is related to connection problems with Windows Update. It means that your computer isn’t able to connect with the Microsoft Update server; therefore you’re unable to receive any new updates. So, you either have a problem with the internet connection or the Microsoft Update server is corrupted. If the problem is caused by the Microsoft Update server, you just need to wait a while because Microsoft staff will most probably solve the problem quickly.

Method 4:

But, if the issue isn’t related to your internet connection, you should perform the following method:

1. Got to Search and enter Identify and Repair
2. Open Identify and repair network problems
3. Click on the Search Result.
4. It should automatically Start the identifying process
5. If your network has any issue then it will show you and ask you to fix it.

Now, establish your internet connection. The problem 0x8024402 should be solved by now and you’ll be able to update your Windows 10 Technical Preview to the latest 10049 builds.

Method 5:

Turn on Windows Firewall: If you have some anti-malware or antivirus on your Windows 10 PC, then it might turn off Windows Firewall on its own or create its own Firewall as default. If this is the case, you will need to turn on Windows Firewall.

• Search for "Firewall" OR
• Click on Windows Firewall from Control Panel.
• On the left pane, Click on Turn Windows Firewall ON or OFF.
• Click on Turn on Windows Firewall then Click Ok.
• That is it. Now, try again and see if you are still getting Windows Update Error 0x8024402f in your Windows 10.

Method 6:

This is an advanced method:

• If the above steps fail, then you might surely want to try this advanced method, which is Enabling ActiveX in your Router Firewall settings.
• If you had turned off ActiveX in your Router Firewall settings then this must be the culprit and so Error 0x8024402f is shown whenever you try to get Windows Update.
• All you need to do is Enable ActiveX by going to your Router Firewall settings and that should do it. The Error should be gone for good now and you will be easily able to install the Updates in your Windows 10.

If you do not possess the technical expertise required to accomplish this yourself or do not feel comfortable doing so, download and install a powerful automated tool to get the job done.

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.

If you receive the error code 0xc000014C while you boot up your computer, then this post might be of help. This kind of error usually points to the Registry of your computer that might be corrupted. As a result, the operating system was not able to read the BCD file and throws the 0xc000014C error. The error code 0xc000014C is triggered when your computer encounters an error in the first booting sector. You might receive any of these error messages:

“Info: An error occurred while attempting to read the boot configuration data.” with File: as “BootBCD” “File: Windowssystem32configsystem Info: Windows failed to load because the system registry file is missing or is corrupt” “Info: The Boot Configuration Data for your PC is missing or contains errors.”

To fix the error code 0xc000014C when booting your computer, you can check out the suggestions provided below.

Option 1 – Try running System Restore in Advanced Startup Options

Since you probably can’t boot into your Windows 10 computer, you can try to run System Restore again in the Advanced Startup Options.

• Boot your computer into the Advanced Startup Options screen.
• From there, you will see some options to troubleshoot when you can’t log in to Windows in the usual way.
• Now select Troubleshoot > Advanced Options > Command Prompt.
• After that, type “rstrui” and hit Enter to execute the command which will start the System Restore process.

Option 2 – Try to rebuild the BCD files

You can also try rebuilding the BCD files to resolve error 0xc000014C for corrupted Boot Configuration Data

• You can start by booting into the installation environment for Windows 10 from an installation media.
• After that, click on Repair your computer and on the blue screen, select Troubleshoot and then select the Advanced options menu.
• From there, select Command Prompt and once you open it, enter each one of the commands given below by sequence.
  • bootrec /FixMbr
  • bootrec /FixBoot
  • bootrec /ScanOS
  • bootrec /RebuildBcd
• Once you’re done executing the commands given above, type “exit” to close the Command Prompt window and then restart your computer and see if it fixed error code 0xc000014c.

Option 3 – Try restoring the default and uncorrupt Registry Values

This option is a bit tricky as you have to be sure about what you are doing here. However, if you are not sure, you might want to seek out a technician to fix the problem for you. But if you can handle it, then carefully follow the steps below.

• You have to first physically remove the hard drive of the computer that’s not booting up. You can refer to it as Hard drive 1 and Computer 1, respectively.
• After that, you need to have another computer which you can refer to as Computer 2, and refer to its hard drive as Hard drive 2. Make sure that this second computer is working properly.
• Next, you have to attach Hard drive 1 to Computer 2 with the Hard drive 2 attached as well.
• After that, boot Computer 2 from Hard drive 2 where Hard drive 1 will act as the second storage unit.
• Then navigate to the following location in the System Partition of the Hard drive 2.

C:/Windows/System32/config/RegBack

• From there, you have to replace all the files. Once you’re done, shut down your computer and then take out the Hard drive 1 from Computer 2 and put it back to Computer 1 as the only hard drive.
• Now boot your computer normally and check if the problem is fixed.

Experiencing issues while using Remote Desktop connections is not uncommon. One of the issues that users encountered recently while trying to connect to their Remote Desktop network is the error saying, “Your credentials did not work, The login attempt failed”. If you are one of these users, then you’ve come to the right place as this post will walk you through fixing the problem. When facing this kind of problem, the first thing you can try before you do some troubleshooting steps is to verify the credentials. But if you are certain that you’ve entered the correct credentials just like what other users reported, then it’s completely a different matter. Based on the reports, this error is common on newly installed versions of Windows 10 or after reinstalling the operating system which could mean that the problem might be due to the Windows security policies or the username might have been recently modified. The latter case is a possibility especially if you’ve reinstalled Windows 10 and had entered a new username. In such a case, you will really have a difficult time connecting to your Remote Desktop connection since its credentials do not really automatically change. If you’ve verified that your credentials are correct, then now’s the time you troubleshoot the problem with the help of the potential fixes provided below. Just make sure that you follow each one of them in sequence.

Option 1 –Try to 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 2 – Try to change the network profile from public to private

According to some reports, this error occurs on systems where the network profile was set to public. Thus, you need to change the network profile to private to resolve the problem. How? Refer to these steps:

• Go to Start and from there click on Settings > Network & Internet > Status.
• Next, click on the “Change connection properties” option.
• After that, set the radio button of Network Profile from Public to Private.
• Wait for a couple of seconds until the system is done applying the changes you’ve made and then see if you can now connect to the Remote Desktop connection.

Option 3 – Try changing the account username

As mentioned, one of the possible causes for this error is the reinstallation of the operating system. You might have changed the username for the system but it does not really change the username of the Remote Desktop connection as well. Thus, you have to change the username back to what it was before you’ve reinstalled Windows 10.

Option 4 – Try modifying the Windows Security Policy

You can also try to edit the Windows Security Policy as it could help in resolving the error. This Windows Security Policy, when enabled, will not allow non-admin users to log on to the Remote Desktop connection. So if you want to allow non-admin users to use the Remote Desktop connection, then you need to modify this policy. Note that you can only do that if you are the admin of the system yourself.

• Tap the Win + R keys to open the Run utility.
• Then type “secpol.msc” in the field and tap Enter or click OK to open the Local Security Policy.
• After opening the Local Security Policy window, select Local Policies > User Rights Agreement located on the left pane.
• Next, double click on “Allow log on through Remote Desktop Services” located in the right pane.
• And in the next window that appears, select Add user or group.
• After that, type in the username of the intended non-admin user under the “Enter the object names to select” column.
• Once done, click on the Check Names button to fix the username and then click OK to save the changes made.
• Restart your computer.

Option 5 – Use the Group Policy Editor

• Tap the Win + R keys to open the Run dialog box and then type “gpedit.msc” in the field and tap Enter to open the Group Policy Editor.
• Next, navigate to this path: Computer Configuration > Administrative Templates > System > Credentials Delegation.
• Double click on the “Allow delegating default credentials with NTLM-only server authentication” policy setting located on the right pane to edit it.
• After that, shift its radio button to Enabled and click on Show.
• Then type “TERMSRV/*” in the Value box and click OK.
• Now repeat the same for the following policy settings:
  • “Allow delegating default credentials”
  • “Allow delegating saved credentials”
  • “Allow delegating saved credentials with NTLM-only server authentication”

• Once you’re done, restart your computer and see if the problem is fixed.

Blue Yeti has gained popularity among streamers and users that want a high-quality mic for their setup. Without going into details of the hardware itself I will say it is a pretty good mic. Now the issues that have been reported with it are that Windows 11 can have issues with it resulting in the microphone not being recognized by the operating system. If you are one of the unfortunate Blue Yeti users and have this issue, do not despair because we have a solution for you, several to be more precise so you can easily fix the issue and get back to talking.

Check cables

Sometimes it is not a software problem at all. First thing is to check if by any chance cable of the mic is disconnected, damaged, or similar. If the cable seems fine next step is to plug in the mic into another port in order to eliminate faulty jack on the computer. If nothing happened the last thing to try is to connect the mic to another computer so we can be sure that the mic itself is in working order so we can focus on software. If by any chance mic is not working on another computer that some hardware inspection of it will be required.

Set Blue Yeti as a default device

There is a chance that Windows 11 has not set Blue Yeti as a default audio device for recording and therefore you can not use it. In order to eliminate and fix this issue, right-click on the speaker icon on the taskbar in the far-right part of it and choose sound settings. Go down to the input section and pick Blue Yeti beside Choose device for speaking or recording.

Update driver

More often than not device not working is tied to malfunctioning or a bad driver. In order to eliminate and resolve this issue right click on the Start icon and choose device manager. Inside device manager expand the Sound, video and game controllers section. Right-click on each device in the section and choose update driver. Wait for the update to complete and restart your system.

Run the troubleshooter

Press ⊞ WINDOWS + I to open Windows settings. Go to System in the left pane and click on it. In the right panel choose and click on troubleshoot. Inside troubleshoot click on Other. Scroll down and locate the Recording Audio troubleshooter and then click on Run next to it. Wait for the troubleshooter to finish and follow on-screen instructions to resolve the issue.

Check Blue Yeti microphone privacy setting

Not very often, but sometimes privacy settings can be the issue even when everything else is working perfectly. In order to check privacy settings press ⊞ WINDOWS + I to open Windows settings and go to Privacy & Security on the left panel and click on it. On the right panel click on the microphone. Make sure that toggle next to Let apps access your microphone is ON.

Lately on EA forums question has appeared on what to do when Origin client does not load library. It seems that the latest update for the Origin client has brought some issues as not properly showing one library which appears empty. Do not worry, we have a solution for you, several to be precise and it will fix the issue guaranteed. It is advisable to try solutions in order how they are presented since they go from the most simple and fastest and most common ones.

1. Delete the cache

   Close origin client completely Press ⊞ WINDOWS + R to bring the run dialog In the run dialog type in %ProgramData%/Origin and press ENTER Go into the Origin folder Delete all files and folders except the LocalContent folder Press ⊞ WINDOWS + R to bring the run dialog In the run dialog type in %AppData% and press ENTER Delete the Origin folder In the address bar click on AppData Go into the local folder Delete Origin folder Reboot your PC

2. Clear the temporary files

   Press ⊞ WINDOWS + R to bring the run dialog In the run dialog type in %AppData% and press ENTER Go into the roaming folder Delete Origin folder Go to the AppData folder and delete the Origin folder from there also Reboot system

3. Try Windows built-in tools to check compatibility

   Locate where Origin is installed and right-click on the executable file Click on properties Go to the compatibility tab Click on Run the compatibility troubleshooter and follow on-screen instructions

4. Update Origin

   Rarely this is the case but check manually to see if you can update your Origin client. Sometimes due to network issues client does not update automatically and can cause this strange behavior.

5. Add origin as an exception to antivirus and firewall

   Not rarely game clients can be detected as some form of malicious software and antivirus along with firewall can automatically block it. Go to your security software settings and add it as the exception.

6. Reinstall Origin

   If everything else fails, reinstall the Origin client