Fix Msvcr120.dll_clr0400.dll Missing Error

If you’re having some problem browsing multiple websites on the Firefox browser on your Windows 10 computer, then this post might be of help. One of the most common problems you could encounter in Firefox is mostly related to HTTPS and one of them is the MOZILLA PKIX ERROR MITM DETECTED or ERROR SELF SIGNED CERT or SEC ERROR UNKNOWN ISSUER error which means that Firefox was unable to trust certificates issued on secured websites. If you encounter the MOZILLA_PKIX_ERROR_MITM_DETECTED error in Firefox, this indicates that something in your network or system is interrupting your connection and injecting certificates and when that happens, Firefox won’t trust it. In such cases, one of the culprits is malware. Malware will try to replace a legitimate certificate with its certificate. Another cause is security software where it keeps a tab on a secure connection and creates a false positive, for instance:

“In Microsoft Windows accounts protected by Family Safety settings, secure connections on popular websites like Google, Facebook and YouTube might be intercepted and their certificates replaced by a certificate issued by Microsoft in order to filter and record search activity.”

And if you are connected to a corporate network, there might be a monitoring/filtering product that could be replacing certificates. Moreover, there are also users who reported getting this issue when they use the Nightly version of Firefox. And if that’s the case, you have to try accessing secure websites using only the stable build especially when it comes to payments. However, if you are not doing that, then here are some options you need to check out.

Option 1 – Try turning off HTTPS Scanning on your security and antivirus programs

Each security-based software has a security option that allows you to turn off the HTTPS scanning functionality. They may be available under different names such as HTTPS Scanning, Scan SSL, Show safe result, Do not scan encrypted connections, etc. Find what is applicable for your security or antivirus software and then try turning it off temporarily and see if it helps in fixing the MOZILLA_PKIX_ERROR_MITM_DETECTED error in Firefox.

Option 2 – Try to disable security.enterprise_roots.enabled

The next thing you can do if the first option didn’t work is to disable security.enterprise_roots.enabled which is an HTTPS certificate check on Firefox. Note that this is not recommended but you have to at least try in order to fix the error.

• Open Firefox and then type “about: config” in the Firefox address bar and hit Enter.
• After that, if an info message appears, confirm it.
• Next, search for the security.enterprise_roots.enabled preference and once you found it, double click on it.
• Then change its value to true and restart the Firefox browser once. This will import all the custom certificates from the other security software into Firefox. As a result, it will make sure to mark those sources as trusted and you won’t get the MOZILLA_PKIX_ERROR_MITM_DETECTED error.

Blizzard is one of the most beloved game company which brought some of the most and greatest titles in PC gaming. Blizzard has released its own launcher in which you can launch games, sadly sometimes launcher does not want to work and fails to connect. If this happens to you be sure to:

1. Reset your network devices to make sure your router hasn't become flooded with data.

   Power cycling your modem and router allows them to reset and re-establish a connection to your ISP. Follow these steps to completely power cycle the devices in your network connection:Note: If your modem has a battery backup, you will need to take the battery out or use the reset button on the modem.

   1. Shut down all computers connected to the modem/router.
   2. Power down and unplug the modem and the router if you're using one.
   3. Allow to sit for 60 seconds unplugged.
   4. Plug in and turn on the modem and router, and allow them to completely boot up until the front panel connection lights on the modem show a steady connection.
   5. Start the computer and allow it to completely boot up.

2. If you're using a wireless connection, optimize your internet connection to rule out a connection issue.

   If you're experiencing issues with your low-speed or wireless internet connection, follow the steps below to troubleshoot the problem.

   1. Try plugging your computer directly into your modem.
   2. Shut down other programs that access the internet, such as other games or download programs.
   3. Satellite, mobile phone, and WiMax internet connections are not stable connections and may cause further connection issues when playing Blizzard games. If possible, consider switching to a more stable connection.

3. Update your drivers and operating system to resolve any compatibility issues.

   Out-of-date drivers and operating systems can cause a variety of issues and are one of the first things to check when a game is having problems. The instructions below will help you check and update your drivers.

   • Even new computers can have out-of-date drivers and operating systems because updates are released routinely.
   • Some games and programs might run fine on a system with old drivers, but outdated drivers can still create technical issues with specific games or programs.
   • Check our supported video cards articles to make sure your hardware is compatible:
     • World of Warcraft
     • Hearthstone
     • StarCraft II
     • Diablo III
     • Heroes of the Storm
     • Overwatch

   Refer to the steps below to update drivers and software for your operating system.

4. Release and renew your IP and flush your DNS to resolve any network conflicts.

   1. While on the desktop, press Windows Key and type CMD.
   2. Right-click Command Prompt and select Run as administrator.
   3. Type ipconfig /release in the command prompt.
   4. Wait a few seconds for a reply that the IP address has been released.
   5. Type ipconfig /renew in the command prompt.
   6. Wait a few seconds for a reply that the IP address has been re-established.
   7. Type ipconfig /flushdns in the command prompt.
   8. Close the command prompt and attempt to make a connection.

5. Close all other applications to resolve software conflicts and free up resources.

   Before trying the steps below, close unnecessary programs and restart your computer. Identify Problematic Startup Items

   1. Press Ctrl+Shift+Esc to open the Task Manager.
   2. Click More Details.
   3. Select the Startup tab.
   4. Right-click on each item and select Disable.
   5. Restart the computer.

   If this resolves the issue, enable the startup application one at a time to determine which one is causing the problem. You will need to restart between each application you enable. Note: To re-enable startup applications, follow steps 1-4 and select Enable.

6. Delete the Battle.net Tools folder to automatically rebuild outdated or corrupt files.

   1. Close Blizzard processes.
      1. Press Ctrl + Shift + Esc to bring up the Task Manager.
      2. Click the Processes tab.
      3. Select all Agent, Blizzard Battle.net desktop app, and game processes, and click End Process.
   2. Navigate to the folder containing the Battle.net directory:
      1. Press Windows Key + R to open the Run dialogue.
      2. Type C:\ProgramData\ into the Open field and press Enter.
   3. Delete the Battle.net folder.
   4. Run Battle.net and update the game to see if the issue persists.

   If the error persists after you try these steps, another program may be causing the problem. Restart your computer and delete the Battle.net folder one more time.

   Note: The above steps may cause the Blizzard Battle.net desktop app to forget game install locations. If your games can’t be found, you will see Install on the Blizzard Battle.net desktop app game tab instead of Play. To find your installation, click Locate this game or run the game launcher.

Hello and welcome to errortools another tutorial which aims to make your computer life easier and more relaxed. This time we will be talking about how to switch sound output devices in Windows 10 in a matter of seconds between Headphones and external speakers, Between 2 different speakers, or any other audio output device in general. Windows 10 with its updates has really gone from OK to one of the greats, little hacks and shortcuts which every update has introduced have really made life easier. Now, your typical switching from one audio output device to another can be accomplished with your standard go to settings, go to devices, choose audio, pick one which you prefer and click on OK. This way altho nothing wrong with it is a little slow and if you need to switch your output devices several times in a single day often it can be time-consuming as well. Lucky for you we have a quick solution for you.

Switching guide

All right, now in order to be able to actually switch between your audio output devices make sure that all of them are working and that they are plugged in. For example, make sure that both of your headphones and speakers are turned ON and plugged in. Once you have confirmed that everything is in working order:

1. Click with a left mouse button on a speaker icon located on the right part of your taskbar next to the clock
2. Click on the small up arrow on the right next to your current audio output device.
3. The list will open, choose, and left click with the mouse button on your choice.

And that's it, you have changed your default audio output device in a matter of seconds. The good thing about this method is that Windows will remember output audio levels for each device.

Potential issue

If by any chance when switching your audio devices this way freezes volume control just go to the task manager and restart Windows Explorer. To restart Windows explorer:

1. Press CTRL + ESC to open task manager
2. Right-click on Windows Explorer
3. Left-click on restart

The Windows Subsystem for Linus, also known as WSL, is a useful and excellent tool for developers. However, it isn’t without flaws as users can still encounter some errors when using it. One of these errors is the error code WslRegisterDistribution, 0x8007019e,0x8000000d. Although it seems like the error is have something to do with the installation of WSL, it could be a false positive since some users who’ve installed WSL still encountered the same problem. Here’s the context of the error:

“Installing, this may take a few minutes… WslRegisterDistribution failed with error: 0x8007019e/0x8000000d Error: 0x8007019e/0x8000000d The parameter is incorrect. Press any key to continue.”

Error code 0x8007019e or 0x8000000d could be due to the absence of supporting Windows 10 features since the error does not even let one use the WSL-based command line. If you are one of the users facing this problem, then you’ve come to the right place as this post will provide you with a couple of suggestions to fix it. There are two options you can check out to fix the problem, but before you do that, you need to make sure that the Windows Subsystem for Linux feature is enabled. The two options include enabling WSL using the “Turn Windows features on or off” option and using the Windows PowerShell.

Option 1 – Try to enable the WSL using the “Turn Windows features on or off” option

• To get started, search for “Turn Windows Features on or off” in the Start Search and click on the appropriate result to open a dialog box.
• After that, you will see a populated list in the dialog box and from there, look for the “Windows Subsystem for Linux” option.
• Once you find it, select OK. This will search and install the system files needed and ask you to restart your computer.
• Restart your computer. The Linux distro should now work without any trouble.

Option 2 – Try to use Windows PowerShell

The next thing you can do to fix the error code 0x8007019e or 0x8000000d is to use Windows PowerShell.

• Tap the Win + X keys and click on the “Windows PowerShell (Admin)” option to open Windows PowerShell as admin.
• After that, execute this command to enable the Windows Subsystem for Linux feature: Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux
• The command you entered will start to search for the required system files and install them.
• If prompted, type “Y” to restart your computer. This should fix the problem.

In previous versions of Windows changing the system, the font was a pretty straightforward process, but it seems Microsoft did not want this feature to keep for whatever reason and there is no option as of the time of the writing of this article to do it in standard options in Windows 10. But do not worry, you are still able to customize your Windows and choose which font would you like to see inside it in all of its dialogs. You can choose whichever font you desire, the only prerequisite is it to be installed on your system. This guide will require you to change values in the registry of Windows itself so please follow step-by-step instructions and always make a backup of the registry before changing it in order to prevent some permanent Windows issues. All of that being said, let's start.

Setting new font

First thing is to open notepad, in the notepad paste the next block of code:

Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts] "Segoe UI (TrueType)"="" "Segoe UI Bold (TrueType)"="" "Segoe UI Bold Italic (TrueType)"="" "Segoe UI Italic (TrueType)"="" "Segoe UI Light (TrueType)"="" "Segoe UI Semibold (TrueType)"="" "Segoe UI Symbol (TrueType)"="" [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\FontSubstitutes] "Segoe UI"="NEW_FONT"

Where in "Segoe UI"="NEW_FONT" instead of NEW_FONT you need to write the exact name of the font that you wish to use as a system font. Once you have replaced the default system font with your desired one, go to File and save as, from file type drop-down menu, choose all files and save this file as .REG type giving it whatever name you wish. When the file is saved, close notepad, right-click on the saved file and choose the merge option. Confirm with YES and click on OK. Reboot your system and your Windows will now use the font of your choice as its default system font.

Restoring default font

If you wish to return the old default system font as it was, follow the same steps but in your notepad paste this code:

Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts] "Segoe UI (TrueType)"="segoeui.ttf" "Segoe UI Black (TrueType)"="seguibl.ttf" "Segoe UI Black Italic (TrueType)"="seguibli.ttf" "Segoe UI Bold (TrueType)"="segoeuib.ttf" "Segoe UI Bold Italic (TrueType)"="segoeuiz.ttf" "Segoe UI Emoji (TrueType)"="seguiemj.ttf" "Segoe UI Historic (TrueType)"="seguihis.ttf" "Segoe UI Italic (TrueType)"="segoeuii.ttf" "Segoe UI Light (TrueType)"="segoeuil.ttf" "Segoe UI Light Italic (TrueType)"="seguili.ttf" "Segoe UI Semibold (TrueType)"="seguisb.ttf" "Segoe UI Semibold Italic (TrueType)"="seguisbi.ttf" "Segoe UI Semilight (TrueType)"="segoeuisl.ttf" "Segoe UI Semilight Italic (TrueType)"="seguisli.ttf" "Segoe UI Symbol (TrueType)"="seguisym.ttf" "Segoe MDL2 Assets (TrueType)"="segmdl2.ttf" "Segoe Print (TrueType)"="segoepr.ttf" "Segoe Print Bold (TrueType)"="segoeprb.ttf" "Segoe Script (TrueType)"="segoesc.ttf" "Segoe Script Bold (TrueType)"="segoescb.ttf" [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\FontSubstitutes] "Segoe UI"=-

Reboot your system and your Windows will now revert the font of your choice as its default system font.

If you suddenly receive an error message that says, “The selected boot device failed, Press <Enter> to Continue” during an installation on your Windows 10 computer, you should know that this kind of error can occur when you use a USB stick as well as a DVD Disk to boot from. This error indicates that some settings inside your BIOS are not compatible with the bootable device that you have created. Note that fixing this kind of error does not vary from device to device at all. All you have to do is change some settings in the BIOS and create a proper bootable disk. Follow the options given below to fix the “The selected boot device failed, Press <Enter> to Continue” error. The options below do not have to be necessarily followed in the same sequence since you can create a bootable USB drive before you change some settings in the BIOS.

Option 1 – Disable the Secure Boot in the BIOS

Disabling the Secure Boot in the BIOS settings is definitely recommended to resolve the issue. To disable Secure Boot, here’s what you have to do:

• First, boot your computer into Windows 10.
• Next, go to Settings > Windows Update. From there, check if there is anything that you have to download and install if you see any available updates. Usually, OEMs send and update the list of trusted hardware, drivers, and operating systems for your computer.
• After that, go to the BIOS of your computer.
• Then go to Settings > Update & Security > Advanced Startup options. If you click on Restart Now, it will restart your computer and give you all the advanced options.
• Next, select Troubleshoot > Advanced Options. As you can see, this screen offers you further Options including System Restore, Startup repair, Go back to the previous version, Command Prompt, System Image Recovery, and UEFI Firmware Settings.
• Select the UEFI Firmware Settings which will take you to the BIOS.
• From there, go to the Security > Boot > Authentication tab where you should see Secure Boot. Note that every OEM has its own way of implementing the options so it varies.
• Next, set Secure Boot to Disabled and set Legacy Support to On or Enabled.
• Save the changes made and exit. Afterward, your computer will reboot.

Option 2 – Make a proper bootable USB Drive/Stick

To make a proper bootable USB drive, you need to use the Windows Media Creation tool. The Media Creation tool in Windows allows you to use the ISO installation file to make a bootable device that you can use to install Windows on your PC. Note that this is kind of different from the usual installation process as it could erase your computer’s current settings and data on the primary drive. Thus, before you proceed, you need to backup all your data into some removable drive and then use the Media Creation Tool to make a bootable drive.

• After making the bootable drive, you need to plug it into your computer and then reboot.
• Next, tap the F10 or Esc key to open the boot options.
• Now set the boot priority of the removable drive the highest. Once the setup comes forth, follow the next onscreen instructions and install Windows without any problems.

If your VPN software blocks and disconnects the Internet or Wi-Fi connection as soon as it is connected, read on as this post will give you fixes to resolve the problem. This kind of issue is odd but not unheard of. Many users use VPN for privacy and security but if it causes internet connection problems, you have to pin down the root cause of the problem and fix it in order to continue browsing the internet with privacy and security. Here are some suggestions you need to check out to resolve the issue between your VPN software and network.

Option 1 – Try installing the latest version of the TAP adapter

Since all VPN software uses a TAP adapter which is mostly from OpenVPN, you might want to download and install the TAP adapter driver to resolve the problem.

Option 2 – 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.

Option 3 – Configure the client computer to use the default gateway

This kind of connection problem can occur when you configure the VPN connection as the default gateway on the remote network. In such a case, the VPN settings override the default gateway settings (TCP/IP settings). Thus, you have to configure the client computers in order to use the default gateway setting on your local network for internet traffic as well as a static route on the remote network for VPN-based traffic.

Option 4 – Try to use the Google Public DNS

You might want to change your DNS to Google Public DNS as it could help you resolve the internet connection problem caused by your VPN. To do so, follow the steps below.

• The first thing you have to do is right-click on the network icon in the Taskbar and select Network and Sharing Center.
• Next, click on the “Change Adapter Settings” option.
• After that, search for the network connection that you are using to connect to the internet. Note that the option might be “Wireless Connection” or “Local Area Connection”.
• Right-click on your network connection and click on Properties.
• Then select the new window to choose the “Internet Protocol 4 (TCP/IPv4)” option.
• After that, click on the Properties button and click the checkbox in the new window for the option “Use the following DNS server addresses”.
• Type in “8.8.8.8” and “8.8.4.4” and click OK and exit.

Option 5 – Try checking the settings of your VPN software

If your VPN software has a built-in “kill switch” it prevents any internet usage every time there is a problem in connecting with the VPN server which explains why your internet connection is disconnected when your VPN software is connected. In addition, you could also try to change your VPN software’s protocol since all VPNs support multiple protocols. It could be that the protocol your VPN uses is blocked so try changing to another protocol and see if it fixes the problem.

Option 6 – Update the Network Adapter drivers

You might also want 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 it.
• Then right-click on each one of the Network drivers and update them all.
• Restart your PC and see if it helped in fixing the BSOD error.

Note: If updating the network drivers didn’t help in fixing the “Windows could not find a driver for your network adapter” error, you can also try to uninstall the very same drivers 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 driver, 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.

Could not connect to the System Event explanation: Although logging into a Windows 10 computer may seem like a simple process, it’s actually not since the Windows operating system has built a mechanism in a way that any third party or malware intervention would not compromise access to the system. This mechanism is supported by numerous services, functions, and DLL files. And Microsoft has been taking this security to a whole new level with the introduction of Windows Hello. Recently, a number of users reported getting the “Windows could not connect to the System Event Notification Service service. Please consult your system administrator” error when logging into their computers. While some users also reported that although they can log in, they encounter the same error message from the Notification area. There are several options you can check out to resolve the error. You have to check the status of several Windows Services and make sure that they are running. You also have to reset Winsock as well as run the System File Checker scan.

Option 1 – Check for certain Windows Services

• First, you need to tap the Win + R keys on your keyboard to open the Run dialog box.
• Next, type “services.msc” in the field and click OK or tap Enter to open the Windows Services Manager.
• After that, you will see a list of services and from there, look for the following Windows Services:
  • DHCP Client
  • System Event Notification Service
  • Windows Font Cache Service
• Now make sure that the Startup Type of each service is started and running.

Option 2 – Try resetting the Winsock drivers

• In the Start Search, type “command prompt” and right-click on Command Prompt from the search results, and then select the “Run as administrator” option.
• After opening Command Prompt, execute this command: netsh winsock reset

Note: If you are using IPv4, execute the “netsh int ipv4 reset” instead. On the other hand, if you are using IPv6, execute the “netsh int ipv6 reset”

• Now exit Command Prompt and see if the error is now fixed.

Option 3 – Try running System File Checker or SFC scan

You could also run System File Checker or SFC scan to fix the BSOD error. It is a built-in command utility that helps in restoring corrupted files as well as missing files. It replaces bad and corrupted system files with good system files. To run the SFC command, follow the steps given below.

• Tap Win + R to launch Run.
• Type in cmd in the field and tap Enter.
• After opening Command Prompt, type in sfc /scannow

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.

• Reboot your PC.

If you suddenly find the Windows Recovery Environment not working and you see an error message saying, “Could not find the recovery environment”, then you’ve come to the right place as this post will guide you on how you can fix it. In times when you can’t boot into the Windows Recovery Environment, there could be several reasons behind it. However, have you ever wondered where exactly the Windows Recovery Environment is in your computer? Windows initially places the Windows RE Image file in the installation partition during Windows Setup so if you have installed Windows in the C drive, you can find the Windows RE at the C:/Windows/System32/Recovery or C:/Recovery folder. Keep in mind that this folder is hidden and later on, the system copies the image file into the recovery tools partition to make sure that one can boot into recovery if there are any issues with the drive partition. The “Could not find the recovery environment” error mostly occurs if the Windows Recovery Environment is disabled or if the “Winre.wim” file is corrupted. Thus, to fix this error, you need to refer to the given suggestions below.

Option 1 – Try to enable Windows Recovery Environment

• In the Windows Start Search, type “PowerShell” and from the search results that appear, right-click on Windows PowerShell and then select the “Run as administrator” option to open it with admin privileges.
• Next, type the “reagentc /info” command and tap Enter to execute it.
• After that, if the output states that Status is enabled, then you’re all set.
• Now type the “reagentc /enable” command and tap Enter to enable the Windows Recovery Environment. You will see a success message at the end signifying that Windows RE is available.

Option 2 – Try to fix the corrupted or missing “Winre.wim” file

If the Winre.wim file is either corrupted or missing, you need to get a new copy of this file from another computer where the Windows RE is working. Once you’re able to get a new copy of the Winre.wim file, you have to set the image path to a new location. For more details, refer to these steps:

• First, type “Powershell” in Windows Start Search and right-click on Windows PowerShell from the results, and select Run as administrator.
• Next, execute the given command below to change the path of the WIM file to the new location. Note that the steps should be used when the file path of the Windows Recovery Environment is different from the usual spot.

Reagentc /setreimage /path C:RecoveryWindowsRE

• As mentioned, if the file is corrupted, you just have to get a new copy from another PC but before you do that, make sure that the WINRE on that computer is disabled (just enable it later on) and then place it in the C:/Recovery path and then set its path again using the command given above and then verify its path by executing the following command.

reagentc /info command

Note: Since the Recovery folder is hidden as well as the WINRE folder in it and you won’t be able to access them using the Windows File Explorer, you need to use the Windows PowerShell or Command Prompt so that you can access them.

Option 3 – Try checking and fixing the WinRE Reference in the Windows Boot Loader

The Windows Boot Loader is the one that determines if it has to load the Windows Recovery Environment. It could be that the boot loader is pointing to an incorrect location which is why you’re getting the error. To resolve it, you have to check and fix the WinRE Reference in the boot loader. How? Follow these steps:

• In the Windows Start Search, type “PowerShell” and from the search results that appear, right-click on Windows PowerShell and then select the “Run as administrator” option to open it with admin privileges.
• After that, execute the “bcdedit /enum all” command.
• Next, look for an entry in the Windows Boot Loader identifier set as Current and look for “recoverysequence” in that section and take note of the GUID.
• Ensure that the device and the osdevice items show the path for the Winre.wim file and that they are the same. If not, you need to point the current identifier to the one which has the same.
• Once you’ve found the new GUID, execute this command: bcdedit /set {current} recoverysequence {GUID_which_has_same_path_of_device_and_device}
• Now check if the error in the Recovery Environment is fixed or not.

Option 4 – Try creating a Recovery Media

You could also try creating a Recovery Media to resolve the error in the Windows RE. All you have to do is download the Windows 10 ISO file using the Media Creation tool and then create a recovery drive. Once you’re done, check if it fixes the problem or not.

People are becoming more and more concerned with their privacy and Facebook's flagship messaging application is caught between it all. While still widely popular it has becoming to lose its ground due to many unanswered questions about privacy encryption. Lucky for all of us there are alternatives for more secure messaging.

SIGNAL

Arguably the most secure of all well-regarded messaging apps, Signal is the favorite of the European Commission, as well as newsrooms around the world. While Signal doesn’t disclose how many daily or monthly users the app has, Google’s Play Store says it has been installed more than 50 million times. While using Signal, each voice or video call connected through the app includes full end-to-end encryption. Signal takes an extra step by hiding message metadata so that the location of the original message is missing. While it asks for your mobile number, that number isn’t used with your profile. Instead, it acts as a numeric username. Once registered, you will find 1-1 chat, audio, and video calls, disappearing or “secret” chats, and a privacy lock so nobody can access the app even if they have your phone. Best of all, it’s completely free to use.

TELEGRAM

One of the biggest competitors to Facebook Messenger (and WhatsApp), Telegram is a very strong alternative. With more than 400 million users, it offers an interface that should feel right at home for anyone coming from Messenger. Telegram offers some huge benefits over Messenger, including features like groups that can hold up to 200,000 members for a chat. There is no limit on your media or chat size, and you can share all types of files between users and in groups. From a privacy standpoint, Telegram has robust security, but it is worth noting that only “secret” messages are end-to-end encrypted and can self-destruct. Non-secret messages can be stored on Telegram’s servers so you can pick them up between your devices quickly. That’s a consideration worth knowing prior to making Telegram your default Messenger replacement. Telegram is free across all platforms.

THREEMA

Rising in popularity, Threema is another privacy-focused alternative that has quickly become a competitor to Facebook Messenger. This paid service ($2.99 on both App Store and Play Store) is a pay-once, use forever option. Once you pay the small fee, you gain all of Threema’s touted privacy options, like open-source end-to-end encryption for both messages and calls. Like Signal, Threema won’t require you to link any phone numbers or emails to your account. All chats are handled anonymously, and the service generates a random user ID when you first open and register for the app. No data is collected from any of your chats and no ads are shown. The Swiss-made app does have its own servers hosted in Switzerland, which do not store any chat messages. Another privacy benefit of Threema is the notion that all of your contact lists, groups, and user profiles are hosted on your device, not on the Swiss servers. Because of that, Threema can once again state that none of your personal info is stored anywhere they have access.