TeamViewer stuck on Initializing Display

Sometimes we need and want some apps that are not part of the official Amazon Appstore but having their Fire TV stick prevents us from installing anything that's not in their store, or does it?

You can quickly "jailbreak" given stick and unlock additional installations via different providers. Although the term jailbreaking is associated with illegal and hacker activities rest assured that in this case there is nothing illegal about this procedure and that you are entirely safe.

Jailbreaking process

In order to do this procedure firstly you will have to allow the installation of apps obtained from outside the Amazon Appstore. To do this open the settings menu on your Fire TV Stick and inside settings choose My Fire TV. On the My Fire TV page select Developer Options and inside select Apps From Unknown Sources. The prompt screen will open, choose Turn On to activate the option.

APK installation is enabled now and the next step is to download an app like Downloader that will allow you to get your favorite apps. Downloader is free to download manager fully available on the Amazon Appstore and with it, you can download any kind of file to your device including APKs.

Once installed open the Downloader app and type in the URL or search term in order to find your application of choice but please do get all of your APK from trusted sources in order to avoid exploits and getting malware.

You will notice the blurred background on the login screen right away when you start your Windows 10 computer that’s running the v1903 and up. This kind of blurred background is known as “Acrylic Blur Effect on Sign-in Screen”. This new feature delivers a beautiful experience to users by adding more focus to the login screen. However, no matter how nice this feature is and even if it only stays for less than a minute, not all users like it and if you’re one of these users, read on as this post will guide you in disabling the blurred background login screen in your Windows 10 computer. Disabling the blurred background in the login screen can be done in two methods. The first one is via the Registry Editor and the second one is via the Group Policy Editor. Before you proceed, make sure that you are using an admin account and you must create a System Restore point first. Once you have that covered, follow the options provided below.

Option 1 – Disable the Blurred background in the login screen via Registry Editor

• First, tap the Win + R keys to open the Run dialog box and type “Regedit” in the field, and hit Enter to open the Registry Editor.
• After that, navigate to this registry path: KEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftWindowsSystem
• Next, right-click on any empty space in the right pane and create a new DWORD (32 bit) and name it as “DisableAcrylicBackgroundOnLogon”.
• Once you’ve created the DWORD, double click on it and set its value to 1 to disable it and 0 to enable it.
• After you make the necessary changes, restart your computer. You won’t now see the blurred background on the login screen.

Note: No matter what option you select to change the background, it will stay blurred when you click on the login button. At the time of writing, there is no way to disable this feature in the Personalization section so the Registry Editor will have to suffice for now.

Option 2 – Disable the Blurred background in the login screen via Group Policy Editor

• Tap the Win + R keys to open the Run utility and type “gpedit.msc” in the field and tap Enter to open the Group Policy Editor.
• After that, navigate to this policy setting: Computer ConfigurationAdministrative TemplatesSystemLogon
• From there, double click on the “Show clear logon background settings” and since its default value is “Not configured”, set it to “Disabled”. You will see the following description under this setting:
  • “This policy setting disables the acrylic blur effect on the logon background image.”
  • “If you enable this policy, the logon background image shows without blur.”

• Now click on OK and then check the login screen.

Note: If you don’t configure or if you disable this policy, the logon background image adopts the acrylic blur effect. However, if it didn’t work, you have to restart your computer and then check.

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.

If you are not able to access the Windows 10 Advanced troubleshooting options within Windows then you’ve come to the right place as this post will guide you on how you can repair or boot the Windows 10 installation without losing data using the bootable installation USB or DVD media. To repair or boot Windows 10 using the installation media, you have to download the Windows ISO, create a bootable USB or DVD drive, boot from the media and select “Repair your computer” and then select Startup Repair under Advanced troubleshooting. To get started, follow the given steps below carefully. Step 1: Frist, download the Windows ISO. Although this is not necessarily needed, it’s still better if you download the Windows ISO first so make sure that you download the same ISO version as installed on your computer. Step 2: Next, create a bootable USB or DVD drive.

• Insert your USB drive into your PC.
• Tap the Win + R keys to open the Run dialog box and type in “cmd” and tap Enter to open the Command Prompt. Alternatively, you can also search for “cmd” in the Cortana search box to open Command Prompt.
• Once you’ve opened CMD, type in this command to open the DISPART utility – diskpart
• After that, you should see a new black and white window that would say, “DISKPART>”.
• Next, type in “list disk” in the command line and tap Enter to see the list of all the Storage devices as well as your hard disk connected to your PC. Here, you have to identify your disk’s number.
• Type in this command where “X” is the disk number you have identified and then tap Enter – disk X
• Type in this command and hit Enter to clear the table records and all the visible data on the drive – clean
• Now you have to recreate a new primary partition of the drive so you’ll have to type in this command and tap Enter right after – create part pri
• A new primary partition has been created so you have to select it by typing this command and tapping Enter – select part 1
• Now you have to format it to make it visible to normal users by typing – format fs=ntfs quick

Note: If your platform supports the Unified Extensible Firmware Interface or UEFI, replace the “NTFS” with “FAT32” in the command on Step 10.

• After that, type in this command and tap Enter after – active
• Finally, type this command and hit Enter to exit the utility – exit
• After you prepare the image for the operating system, save it to the root of your USB Storage device.

Step 3: After creating a bootable drive, boot from the media and select the “Repair your computer” option. Once you boot from the USB drive, it will start the Windows 10 installation right away. So you must not keep on clicking Next as you will end up installing Windows. You need to look for the “Repair your computer” link on the first installation screen and click on it and then boot your computer into Advanced Recovery. Step 4: Select Startup Repair under the Advanced options screen

• Once you’re at the Advanced Recovery screen, select Advanced Options and select Troubleshoot.
• After that, look for the Startup Repair and click on it and then follow the next on-screen instructions. This solution will help you fix issues that do not allow you to boot into your computer.
• On the next screen, you will see the admin account with its name. Click on it and verify using the account password associated with the email.
• After verification, it will start to diagnose your computer and automatically resolve any detected issues related to boot.
• After the issue is fixed, your computer should reboot normally and you should now be able to use it. Note that your personal files are still intact since the process didn’t delete or wipe them out.

There are times when an IT admin has to set up multiple IP addresses to the same network adapter. Setting up multiple IP addresses in scenarios like hosting various SSL sites, speed up traffic exchanges can help in avoiding being blacklisted in the SPAM filters, and so on. So in this post, you will be guided on how exactly you can assign multiple IP addresses to the network adapter in your Windows 10 computer. There are several ways to assign multiple IP addresses in a network adapter. You can do it using the Network Adapter settings or using the Netsh utility, as well as the Windows PowerShell utility. To get started, refer to each one of the options provided below.

Option 1 – Assign multiple IP addresses via Network Adapter settings

• Go to Settings first and from there, select Network & Internet, and then click on the Change adapter options. This will show you a list of both the physical and virtual network adapters in your computer.
• Next, double click on the Ethernet adapter where you want to assign the multiple IP addresses and then click on the Properties button.
• After that, you should see the Ethernet properties where you have to select the “TCP/IPv4” or “TCP/IPv6”.
• Once done, click on the Properties button and then select the “Use the following IP address” option under the General tab.
• Now you have to add an IP address, subnet, and default gateway to the network adapter and then click on the Advanced button.
• This will open the Advanced TCP/IP settings where you have to click on the Add button so you can add an IP address. From here, you can keep adding multiple IP addresses to the network adapter. You also have the option to add multiple gateways or DNS IP addresses.
• Once done, if you execute the “ipconfig” command, you should see all the secondary IP addresses listed.

Option 2 – Assign multiple IP addresses using the Netsh command

Another way to assign multiple IP addresses to your network adapter is via the Netsh command.

• In the Start Search, type “command prompt” and from the search results that appear, right-click on Command Prompt and then select the “Run as administrator” to open it with admin privileges.
• If a User Account Control or UAC prompt pops up, just click on Yes.
• After that, run this command: Netsh int ipv4 add address name="Local Area Connection" 192.168.100.100 255.255.255.0 SkipAsSource=True

Note: You have the option to set “SkepAsSource” since it depends on your needs using the Netsh command. When it is configured as true, the IP address won’t be used by the OS for outbound connections.

Option 3 – Assign multiple IP addresses via Windows PowerShell

• Tap the Win + X key combination and click on the “Windows PowerShell (Admin)” option.
• After opening Windows PowerShell as admin, use the NetIPAddress command so you can add more IP addresses. Execute this command: Get-NetIPAddress | ft IPAddress, InterfaceAlias, SkipAsSource
• Next, assign an IP address to a network adapter by executing this command: New-NetIPAddress –IPAddress 192.168.100.100 –PrefixLength 24 –InterfaceAlias “vEthernet” –SkipAsSource $True
• Now to modify the “SkipAsSource” parameter, use this command: Get-NetIPAddress 192.168.100.100 | Set-NetIPAddress -SkipAsSource $False

Booting the Windows computer system includes loading it from the various boot devices such as drivers, network as well as USB drives when the computer is turned on. The instant the startup sequence is done loading the operating system the system hardware will be ready to perform some complex operations – in this process, the Boot Log in Windows 10 is a record that maintains the list of success or failure of many pieces of Windows 10 system during the booting process. In other words, the Boot Log is the one that keeps a record of all that has happened while loading from the computer storage system to the memory during the boot process. It is available for several devices like network, hardware devices, and the operating system which assist in detecting issues during the boot process and other issues with regards to troubleshooting. Through Boot Log, you’ll know which drivers were unloaded and loaded from the start of the system during the boot process. You have the option to either disable or enable this feature on your Windows 10 PC. Named as “ntbtlog.txt”, the log file lists all the successfully loaded processes and the unsuccessful ones during the boot process. It is saved to the drive C:Windowsntbtlog.txt. As mentioned, you can enable or disable this feature in two ways – the first one is by using the System Configuration or MSConfig while the second one is using the Command Prompt. In this post, we’ll show you how you can enable or disable Boot Log in Windows 10 either way.

Option 1 – Enable or Disable Boot Log using System Configuration

Enable Boot Log:

• Tap the Win + R keys to open the Run dialog box.
• Then type in “msconfig” and click OK to open System Configuration.
• After that, go to the boot tab and check the checkbox labeled “Boot Log” under the Boot options so that you can enable the Boot Log feature.
• Then click on OK to save the changes made.
• Next, click on the Restart button in the prompt window to get started with the Boot Log process.
• After restarting your PC, go to C:Windowsntbtlog.txt to open the boot log.

Note: As pointed out earlier, the log file contains a list of all the successfully loaded drivers and also the list of drivers that failed to load during the boot process and every time you restart the system, the boot log file will keep on updating and will eventually increase the list of entries. For you to locate the drivers and make your troubleshooting a lot easier, I advised disabling the boot log after troubleshooting. To disable the boot log using System Configuration, refer to the steps below. Disable Boot Log:

• Tap the Win + R keys to open the Run dialog box.
• Then type in “msconfig” and click OK to open System Configuration.
• After that, go to the boot tab and unmark or uncheck the checkbox labeled “Boot Log” under the Boot options so that you can disable the Boot Log feature.
• Then click on OK to save the changes made.

Option 2 – Enable or Disable Boot Log using Command Prompt

Enable Boot Log:

• Go to the Start Menu and then type in “command prompt” in the search bar.
• After that, right-click on the Command Prompt option and select the “Run as administrator” option.
• After opening Command Prompt, type in “bcdedit” and tap Enter.

Note: You have to find the Identifier of the current operating system first to enable the Boot log. You can find it under the Windows Boot Loader section in the “Description” field and in this case, it’s Windows 10. You can also find the operating system identifier under the Windows Boot Loader section next to the field name identifier.

• To check if the boot log entry is disabled or enabled, go check the “Bootlog” field under the Windows Boot Loader. And if it turns out that the “bootlog” entry is enabled, the entry will be “Yes”. Otherwise, the entry will be “No”.
• Next, type in the following command with the operating system identifier to enable the boot log.

bcdedit /set {identifier} bootlog Yes

Note: In the command given above, make sure that you replace the given system identifier with your computer’s system identifier. For instance: In this example, the identifier was replaced with the actual operating system identifier as current.

bcdedit /set {current} bootlog Yes

• Afterward, restart the system to start the Boot log process.
• After the restart, go to C:Windowsntbtlog.txt to open the boot log.

Note: Every time you restart your computer, the boot log file will keep on updating which will increase the size of the log eventually. So if you want seamless and easier troubleshooting, it is advised to disable the Boot log after you troubleshoot. To disable it using the Command Prompt, here’s what you have to do. Disable Boot Log:

• Go to the Start Menu and then type in “command prompt” in the search bar.
• After that, right-click on the Command Prompt option and select the “Run as administrator” option.
• Once the Command Prompt is opened, type in the following command and then tap Enter to disable the boot log feature.

bcdedit/ set {identifier} bootlog No

Note: In the command given above, you need to replace the given system identifier with your computer’s system identifier. For instance: In this example, the {identifier} was replaced with the actual operating system identifier as {current}.

bcdedit /set {current} bootlog No

• Now close the Command Prompt.

In case you don’t know, the .Net Framework is a programming infrastructure introduced by Microsoft. You will need it to run on lots of services and applications. Note that most of the applications that require the .Net Framework are packed with their installation files which is why it will be installed automatically on your computer when you install an application. However, there are instances when you’ll get an error message saying, “The .NET Framework 4.7 is not supported on this operating system” while trying to install the .NET Framework as a standalone service. The very reason why this error message appears is stated in the error message itself. Although the .Net Framework is supported on Windows 10, it is not actually compatible with some other Windows 10 versions. So it is most likely that you are seeing this error message because the .Net Framework in your computer is not compatible with the Windows 10 version you are running. Since that’s the case, you need to update Windows 10 to fix the problem. Updating your Windows 10 computer is the only solution you can try to fix this problem. Thus, it is advised that you check for Windows Updates even if you are now using the latest version of Windows 10. And since the issue is caused by an incompatible operating system version, once you install the exact version of Windows 10 required by the .Net Framework, the problem will be fixed. Simply follow the steps given below to do so.

• Step 1: Tap the Win + R keys to open the Run dialog box.
• Step 2: After that, type in “winver” in the field and tap Enter.
• Step 3: Next, your Windows 10 version should be given in the new window that appears. Take note that the number after the Version which is in the second line is your version number of Windows 10. And that the number must be 1507 or 1709. The first two digits in these numbers are the year while the second two represent the month when the update was released. So if you are running a 1709 version, this means that the Windows 10 version you are using was released in September 2017.
• Step 4: The next thing you have to do is to make sure that you have the Windows 10 version that’s compatible with the .Net Framework. To verify, you need to click here and click on the System Requirements.

After opening the link, take a look at the Supported Operating System section where it says, “Windows 10 Anniversary Update” and “Windows 10 Creators Update”. Since there are users who are not familiar with the version numbers related to both the Anniversary and Creators updates, refer to the list given below.

• November Update (1511)
• Anniversary Update (14393)
• Creators Update (1703)
• Fall Creators Update (1709)
• Spring Creators Update (1803)

As you can see, the Creators Update has version 1703 while the Anniversary Update has version number 14393 so if you are using a version lower than the 14393 version then it’s no wonder you aren’t able to install the .Net Framework 4.7 on your Windows 10 PC. Now all that’s left to do is to update your Windows 10 version and make sure that you will be updating it to the latest version available and then try installing the .Net Framework again.

Outlook PST Mailbox Errors Malfunctions

Can you use an MS-Outlook e-mail account to send and get workplace e-mails on a daily basis? Are you using the exact same Outlook e-mail account for a long time? Are you getting PST Mailbox Errors? Then you have developed awareness and knowledge about Outlook PST Errors. Ms-outlook essentially stores the email items in a PST record. This includes all attachments, contacts, calendar items, your e-mails and records. You might encounter various kinds of Outlook Inbox error messages exhibited on the display in extended formats eg. 0x80040600 0x8004060c or 0x80040116. All all these are Outlook mailbox malfunctions that stop the Outlook program from executing jobs correctly and thus restricting your capacity to gain access to your e-mail account, see attachments, contacts, and calendar items that are significant.

Error Causes

There's not a single particular trigger for Outlook email malfunctions. A few causes can trigger these, but, the most frequent are virus contamination, 2 GB limit is exceeded by PST file and broken. There are no specific signals which will help help you identify but some pointers to look at include the following:-

• You cannot access certain parts of your Outlook interface
• Obscure error messages start popping on your screen
• You can’t add new contacts or change entry data in your calendar

Further Information and Manual Repair

When you experience these signs related to PST Inbox errors, it is advisable to repair the problem immediately to ensure it does not cause inconvenience for you and hampers your communication via Outlook emails. Remember this error not only inconveniences you but also hinders proper communication between various business partners. Determining the ultimate reason for distinct Outlook email malfunctions could be tricky, time-consuming, and might need specialized knowledge to nail it down with regards to fixing the Outlook mailbox malfunctions. In case you are not a specialist, working out and fixing this problem is an uphill process. To simplify this process, obtain and install an Outlook PST Repair Tool! This is an intelligent solution to fix all kinds of Outlook errors. You do not have to go deeper into the technical details of the problem. The Outlook PST Repair tool does it for you. An inbox repair tool identifies and also repairs all sorts of MS Outlook errors in seconds. It is easy to use, highly functional, safe and efficient. By installing an Outlook repair tool, Outlook errors can be easily removed from your computer and keep the errors from happening again. It also fixes damaged PST files and damaged e-mails can help regain data. Whatever you should do is to begin:

1. Click here to download the inbox repair tool
2. Install the software on your system
3. Run it and click restore to resolve Inbox errors

In case you don’t know, Windows 10 comes with a native ability to project to another screen, be it wireless or wired. All it takes to do that is by tapping the Win + P key combination to display options to manage the extended display. However, there are times when you might encounter errors when you do that like the “Your PC can’t project to another screen” error. This kind of error stops you from projecting your computer to the other screen. Here’s the full content of the error message:

“Your PC can’t project to another screen, Try reinstalling the driver or using a different video card.”

This error could be due to loosely connected hardware or the display adapter. It is also possible that a recent Windows Update has messed up its settings. To resolve this issue, you can try several suggestions that will be given in this post. You can try to check the hardware cable connections or run the Hardware and Devices troubleshooter. You could also update or reinstall the display adapters or replace the graphics card.

Option 1 – Try checking the hardware connections

The first thing you have to do before you further troubleshoot the problem is to check the hardware connections of your computer and see if there are damaged ones, just like with the ports as it would also affect the overall connectivity of the device with the computer. You also have to make sure that no pin is missing from the ports. So if you notice some irregularities in the connecting cable physically, you might have to buy another one and replace it and then see if it fixes the problem or not.

Option 2 – Run the Hardware and Devices Troubleshooters

• The first thing you need to do is click on Start and then on the gear-like icon to pull up the window for Settings.
• After opening Settings, look for the Update and Security option and select it.
• From there, go to the Troubleshoot option located on the left-hand side of the list.
• Next, select Hardware and Devices from the list and open the Troubleshooter and run it. Once it is doing its job, wait for it to complete the process and then restart the system.
• After the system restarts, check if the problem’s now fixed. If not, refer to the next option given below.

Option 3 – Try to update or reinstall the display adapters

You might also want to update the drivers for Display adapters and Monitors or you might also have to update or reinstall your NVIDIA driver if you’re using one. To update or reinstall the display adapters, follow these steps:

• 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 Display Adapters.
• And then select the Display Driver and right-click on it.
• From the drop-down menu, select the Update Driver option and follow the on-screen instructions to install the latest version of the Display Driver.
• Restart your PC after the installation.

If you find that updating the drivers does not help, you can try to reinstall them. How? Simply follow the steps below.

• Tap the Win + X keys and select the Device Manager.
• After that, look for the affected driver in the Device Manager window. And if you see a yellow exclamation mark beside it, right-click on it and select the option “Rollback” to roll back the driver.
• And if the Rollback option is not available, just select Uninstall and then restart your PC.
• Finally, open the Devices Manager once again and select the option “Scan for hardware changes” to install the driver.

Option 4 – Consider replacing the graphics card

You might also want to consider replacing the graphics card of your computer to resolve the problem if the options provided above didn’t work.

A couple of Windows 10 users have reported an error on domain-connected systems when they tried accessing their computer systems remotely. This occurs when the network level authentication or NLA is enabled on the computer. If you are one of these users, you better keep reading as this post will guide you on how you can fix this error. To resolve this issue, there are several workarounds you can try. You can either disable this option directly via properties or you can also modify some registry entries or sub-keys and restart the system. When you encounter this problem, an error message pops up that states:

“The remote computer that you are trying to connect to requires network level authentication (NLA), but your windows domain controller cannot be contacted to perform NLA. If you are an administrator on the remote computer, you can disable NLA by using the options on the Remote tab of the System Properties dialog box.”

Or you could also see this error message instead:

“The remote computer requires Network Level Authentication, which your computer does not support. For assistance, contact your system administrator or technical support.”

Before you proceed in troubleshooting the problem using the options provided below, you need to create a backup for your data or system restore point as well as make a copy of any registry entries you are going to modify.

Option 1 – Disable Network Level Authentication via Properties

The NLA is a useful tool that provides your computer with extra security and helps network administrators in controlling who can log into the system with just a click of a single box. However, there are times when it can become a disadvantage and could prevent you from accessing your system remotely. Thus, you need to disable it using Properties.

• Tap the Win + R keys to open the Run dialog box.
• After that, type in “sysdm.cpl” and tap Enter to open System Properties.
• Next, go to the remote tab and uncheck the checkbox for the “Allow connections only from computers running Remote Desktop with Network Level Authentication (recommended)” option.
• Now click the Apply button to save the changes made and exit System Properties and then try logging into the remote computer again and see if the problem is fixed or not.

Option 2 – Disable NLA via Registry Editor

Note that you can only use this option if the first one didn’t work for you. Take note that this option will require you to restart your PC completely which could mean some downtime if your computer is running a production server. So make sure to save all your work.

• Tap the Win + R keys to open the Run dialog box and then type in “Regedit” in the field and tap Enter to open the Registry Editor.
• From there, click on File > Connect Network Registry and input the details of the remote computer and then try to connect.
• Navigate to the path below after you’re connected:

HKLM >SYSTEM > CurrentControlSet > Control >Terminal Server > WinStations > RDP-Tcp

• After that, change the values given below to “0”
  • SecurityLayer
  • UserAuthentication
• The navigate to PowerShell and execute this command – restart-computer

Option 3 – Disable NLA via PowerShell

PowerShell allows you to tap into the remote computer and once you’ve targeted the machine, you can execute the commands given below to disable NLA.

• Tap the Win + S to open Search and then type in “PowerShell” in the field. Right-click on the related result and select the “Run as administrator” option.
• After opening PowerShell, execute the command below:

2. Once in the PowerShell, execute the following command:

$TargetMachine = “Target-Machine-Name” (Get-WmiObject -class “Win32_TSGeneralSetting” -Namespace rootcimv2terminalservices -ComputerName $TargetMachine -Filter “TerminalName=’RDP-tcp'”).SetUserAuthenticationRequired(0) Note: In the command given, the “Target-Machine-Name” is the name of the machine you are targeting.

Option 4 – Use the Group Policy Editor to disable NLA

Another option you can use to disable NLA is via the Group Policy Editor. This is ideal for you if you are blanket disabling. Just take note that the Group Policy Editor is a powerful tool and that if you make some mistakes by changing values you have no clue about, you can render your computer useless so make sure that you create a backup for all the values before you proceed.

• Tap the Win + R keys to open the Run dialog box.
• Then type in “gpedit.msc” and tap Enter to open the Group Policy Editor.
• From there, go to this path – Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Security
• After that, search for “Require user authentication for remote connections by using Network Level Authentication” and set it to disabled.
• Now check if the error is fixed or not.