If your users are having issues logging in to your OpenSSH Server for Windows Server after the latest October 2024 Windows Updates, this might help you:

Firstly, configure logging so that you can see what is happening:

Change the config file:

C:\ProgramData\ssh\sshd_config

SyslogFacility LOCAL0

Restart OpenSSH Service

In my environment i saw this error:

userauth_pubkey: signature algorithm ssh-rsa not in PubkeyAcceptedAlgorithms [preauth]

The solution is pretty straight forward. Add this line at the top of your OpenSSH config file:

C:\ProgramData\ssh\sshd_config

PubkeyAcceptedAlgorithms +ssh-rsa

When a file is moved to a different folder on the same NTFS volume, its permissions don’t automatically update to match the destination folder’s settings. Instead, the file keeps its original permissions, which can lead to unexpected access issues if the destination has different security settings

To ensure files inherit the permissions of their new location when moved within the same NTFS volume, you can adjust the Windows Registry to change this behavior. Set the following registry key on the file server:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer
MoveSecurityAttributes
REG_DWORD 0

EDIT:

This key does not work on newer Windows Server Operating Systems. It worked on Windows XP/Server 2003.

Having issue Azure AD joining a Windows 10 or 11 computer and getting error 8018000a? This script might help you. It deletes all keys except Context under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Enrollments

$EnrollmentsPath = “HKLM:\SOFTWARE\Microsoft\Enrollments\”
$Enrollments = Get-ChildItem -Path $EnrollmentsPath
$DiscoveryServerFullUrls = @(“https://wip.mam.manage.microsoft.com/Enroll”)
Foreach ($Enrollment in $Enrollments) {
$EnrollmentObject = Get-ItemProperty Registry::$Enrollment
if ($EnrollmentObject.”DiscoveryServiceFullURL” -in $DiscoveryServerFullUrls ) {
$EnrollmentPath = $EnrollmentsPath + $EnrollmentObject.”PSChildName”
Remove-Item -Path $EnrollmentPath -Recurse
& “C:\Windows\System32\deviceenroller.exe /c /AutoEnrollMDM”
}
}

References:

https://jocha.se/blog/tech/azure-ad-mdm-intune-error-8018000a

If you are having issues with some users having freeze issues and high response time in Citrix Director, this registry key might help you. It happens in conjunction with dedicated GPUs on notebooks. The key disabled GPU acceleration for Citrix Workspace App.

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Citrix\ICA Client\Graphics Engine] “HWacceleration”=dword:00000000

References:

https://support.citrix.com/s/article/CTX297140-screen-freezes-and-takes-a-few-seconds-to-return-to-normal-apps-also-flicker-when-open?language=en_US

If you need to perform a packet capture under Windows without having to install Wireshark, here are some netsh commands:

netsh trace start capture=yes tracefile=c:\net.etl persistent=yes maxsize=4096 filemode=circular overwrite=yes report=no

When you are done with your capture do:

netsh trace stop

This will take some time.

You will see the files under C:\net.etl and net.cab