Why can I log out of my account when connecting via RDP to Windows 10?

Question

Windows

I connect to a server on Windows 10 via RDP and work with it.
Sometimes (1-2 times a day) there is an exit from the account,
with the closure of all open programs, of course, you do not have time to save anything.

At first I thought - restarting the computer, but other accounts on the same server - work in parallel without reboots.
Means there is an exit from an uchetka with closing of all processes.

What could be the problem?

Answer 1

Means there is an exit from an uchetka with closing of all processes.

guess the bad way. it is better to look in the Windows logs for security events - session entry / exit

Connecting to a server on Windows 10 via RDP

Windows 10 is not a server . according to the license requirements of the MS, only one active session is allowed . but usually other sessions (under other accounts) do not end, but go into the background upd if the connection is remote - the session on the physical console is blocked. if the same account is intercepted (but the console is still blocked. and other remote sessions are broken)
ps if you have a build , crack activation , or something like that - any side effects are possible
pps according to your description of the situation it is difficult to give advice. for a system in good condition, when using the same account, if there is already a disabled, but not completedsession - there is a re-entry. if it is not so, it is necessary to inspect on the spot.

Answer 2

Anyone logged in locally?
Not enough licenses for rdp

Answer 3

Windows 10 is not a server, only one connection is possible - either locally or via RDP. If several users connect, then the system is broken to organize such work. The most competent option is to install a server system and set up work in it, if there is a desire to understand the situation - carefully look at the logs and draw conclusions - what happens at the time of throwing out.

Answer 4

What could be the problem?

The fact that win10 is a desktop designed for the work of one person - either at the console or via RDP. When connecting via RDP, the local session is closed, and a warning is issued about this.
Not issued?
"All and so worked"?
You have a cracked system in which pseudo-server RDP is made. No one guarantees anything in this case from the word at all :)