Noticed that in Windows 11 the Windows Security icon in the notification tray indicated there were some action to be addressed. The icon was a yellow triangle. However opening up the dashboard there are no action to take.
There is a good chance that the action is coming from the App & browser control section which may not be visible on the Dashboard. To open those settings open up the Windows start menu and search for "App" and select the App & browser control. The action needed should be listed in these settings.
Recently I noticed that the service vmmem had high memory usage at the same time I was not running any containers in Docker Desktop, the memory usage was actually around 96%, the CPU usage was higher than normal as well. The key was to create a .wslconfig file (windows) in your %USERPROFILE% folder with the config options from the Microsoft Site. Below is what I am currently using.
[wsl2]
memory=6GB # limits VM memory in WSL to 6 GB only
processors=4 # limits the WSL2 to use 4 virtual processors only
Once you create the file and add the options you can restart the LX subsystem using the following Powershell command (must be at an elevated prompt)
Restart-Service LxssManager
You may get some errors in Docker Desktop about communication but you can just restart Docker Desktop to get rid of them.
Not sure why R# is complaining about this, never did before but hey I just updated to the latest version. Found this issue entry in the R# issue tracker. If you don't want or care about smart rule detection you can turn this feature off and all will be right in your IDE world again.
Recently while setting up a new Ubuntu 20.04 VM (from the Quick Create in Hyper-V) I found that I could not RDP into the machine once it was setup, however it was sitting on my network configured with my NAT Switch.
Turns out that the xrdp daemon was not starting and had a cryptic error about VSOCK. Doing a bit of research found that I needed to edit the /etc/xrdp/xrdp.ini file and set the option use_vsock from true to false
#/etc/xrdp/xrdp.ini
use_vsock=false
After that change I restarted the xrdp daemon and was able to connect to it.
Randomly would get this error and dialog when loading and running a new or existing Visual Studio Web project on a machine that never had run it before. The problem seems to have various solutions to it with varying results. Below is the solution that ultimately worked in my situation with the Event Log error I was getting.
First open up the Event Viewer in "Windows Administrative Tools" under the start menu. If you find the following error:
Unable to bind to the underlying transport for [::]:XXXXX. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine. The data field contains the error number.
Where XXXX is a port number for the website that is failing to run in Visual Studio.
If this is the case you can run the following command in an elevated PowerShell / command prompt
netsh http add iplisten ipaddress=::
Then reboot the machine and try again