Update: UltraVNC and UltraVNC SC viewtopic.php?t=37885
Important: Please update to latest version before to create a reply, a topic or an issue: viewtopic.php?t=37864

Join us on social networks and share our announcements:
- Website: https://uvnc.com/
- GitHub: https://github.com/ultravnc
- Mastodon: https://mastodon.social/@ultravnc
- Facebook: https://www.facebook.com/ultravnc1
- X/Twitter: https://twitter.com/ultravnc1
- Reddit community: https://www.reddit.com/r/ultravnc
- OpenHub: https://openhub.net/p/ultravnc

MSLogon problem after new Windows updates

Should you have problems with the MS logon plugin, here's the place to look for help or report issues
Post Reply
Posts: 1
Joined: 2023-09-07 11:28

MSLogon problem after new Windows updates

Post by adamcios »

Mslogon and MSlogonII stop working on 22h2 Windows 10 version after new windows Updates (
When i try to use MSLogonACL.exe and import file which i used in last years
File to import mslogon_AD_default.ini
allow 0x00000003 .\adminek
allow 0x00000003 ..\VNCEdit
allow 0x00000001 ..\VNCView

i get such info:
"C:\Program Files\uvnc bvba\UltraVNC\MSLogonACL.exe" /i /o "C:\Program Files\uvnc bvba\UltraVNC\mslogon_AD_default.ini"
Detected computername = KOMP3
account: KOMP3\adminek, mask: 3, type: allow
Detected domain = XXXXX
XXXXX\VNCEdit: SID not valid.
Detected domain = XXXXX
XXXXX\VNCView: SID not valid.
RegSetValueEx passed
deleting ACE_DATA linked lists

I try to check mslogon and mslogonII and i get such info in logs
Password authentication accepted from (Interactive) (ID:1)
MSLogon authentication refused from using XXXXX\vncadmin account (not authenticated)
Password authentication accepted from (Interactive) (ID:1)
MSLogon authentication refused from using vncadmin@xxxxx.lan account (not authenticated)

I checked everything I could and the result is still the same. Any suggestions?
oooo one more thing when i deinstall windows update
If KB5028244 is not installed, uninstall KB5028166
In some cases, if that doesn't work, you need to uninstall KB5028412 , KB5027937
But this is not a solution
Post Reply