What also would help for debugging are the following steps: A) before upgrading, change the VNC server backend to Headless VNC server - if the reboot does not happen after upgrading, the issue is related with the updated UltraVNC server component in Veyon 4.10.3 B) before upgrading, disable Veyon service autostart - login should work normally also after upgrading. What happens when starting the service manually after being logged in? C) Check the Windows event log for indications about why the system has been rebooted D) In Veyon Configurator in advanced view mode, at page "Windows" there's a setting called "Handling of interfering windows". Is it set to a value other than "None"? If so, please revert it to "None".

Starting with Veyon 4.10.3 there are dedicated packages for Fedora 44.

Hi. Just use the IntuneWinAppUtil.exe. The packaging tool converts application installation files into the .intunewin format.

I'm getting the same error only with some users in our AD domain. Technicians with elevated rights in AD are able to authenticate to the Master program, but other users, like Teachers cannot. All the LDAP setup works fine after that, but the initial authentication fails with: 2026-05-12T12:51:01.160: [ERR] AcceptSecurityContext failed with 8009030C 2026-05-12T12:51:01.161: [DEBUG] WindowsUserFunctions::authenticate(): SSPLogonUser() false 1385

I may be dealing with a similar problem on my side (version 4.10.1). I found out that access control is basically not used at all when I use authentication keys. I have an access group assigned to the authentication key, and if the user is in that group, it works even if the user is restricted through access control. At the same time, I have another issue: when I add another group (nested group) into the group assigned to the key, the user is not recognized.

@zsv08 您好！咱们编译成功了吗？

Its working now as I had to use AD-Credentials from Windows in Directory Server. DOMAIN\User solved the problem.

I also have this problem with Veyon 4.10.0.0. First time I run into this one (v4.9.7.0 and older versions did not show this problem). Btw, we are currently under Windows 11 24H2 in our organization.

Same with docs[.]veyon[.]io/es/latest/