Windows 11 PCs suddenly stopped connecting to L2TP/IPsec VPN hosted on SonicWall firewall. The following error is displayed immediately after clicking Connect:
Can't connect to VPN
The L2TP connection attempt failed because the security layer encountered a processing error during initial negotiations with the remote computer.
Read more: L2TP/IPsec stopped working in Windows 11 / Windows 10
Blue Sherpa application cannot detect plugged in USB Yeti Nano microphone. The following message is displayed.
oh no!
It appears that you don't have any devices connected. If you do have a device connected and it's not showing up, please unplug the device, and plug it back in.
Unplugging and re-plugging the devices, restarting the PC, and re-installing the application doesn't make any difference.
Read more: Blue Sherpa application doesn't detect Yeti Nano microphone
To enable concurrent Remote Desktop (RDP) sessions in Windows 11, you need to make a small change to termsrv.dll file. This file is located in C:\Windows\System32 folder. Before modifying termsrv.dll for the first time, you need to take ownership and assign yourself full permissions. You also need to stop the Remote Desktop service (TermService), if it's running.
DLL files can be modified using any HEX Editor (for example Tiny Hexer). You can do this yourself by replacing the strings shown below, or just download patched versions from this page.
Read more: Multiple RDP (Remote Desktop) sessions in Windows 11
After moving to a different WiFi network, a user can no longer connect to L2TP/IPsec VPN using built-in Windows 10 VPN client. It looks like connection gets established, but instead of saying "Connected", the following error message is displayed:
Can't connect to VPN
A connection to the remote computer could not be established. You might need to change the network settings for this connection.
Read more: Can't connect to VPN - A connection to the remote computer could not be established