Skip to content
This repository has been archived by the owner on Mar 17, 2024. It is now read-only.

Duplicated client #1212

Open
brabus1000 opened this issue Sep 2, 2023 · 0 comments
Open

Duplicated client #1212

brabus1000 opened this issue Sep 2, 2023 · 0 comments
Labels

Comments

@brabus1000
Copy link

Quasar version

1.4.0

Server installed .NET version

No response

Server operating system

Windows 10/Server 2019/2016

Client installed .NET version

No response

Client operating system

Windows 10/Server 2019/2016

Build configuration

Debug

Describe the bug

On server side: seems like 2 clients are connected but they are the same computer, the only difference is that one client has admin privileges and other has user privileges.
Only one of the two are working, the admin privileges probably works only if the client has accepted the privileges for the file, however, if not, or, in some random cases, the Admin privileges client will be disconnected and only the user client will be connected, but the user client will not work at all, no commands can be run on this client but it is seem to be connected, can be seen if idle or not, but not more than that.

On client side:
the file is running twice on the task manager, i checked the files location and it is in the same location (Subdir/Client.exe)

How to reproduce

i installed the client and after the installation I clicked on the option: "Elevate Client Permissions" which asks the client for Admin privileges, I clicked "Yes" and I could see 2 clients on the same computer, one of them is user and the other is admin.
since then it is like that, no matter if you restart the computer.

Expected behavior

I expected to get admin privileges only until the computer will be restarted and then I will get user privileges again.
I did not expected to get 2 running clients on the same computer, and of of them doesn't work, not to mention that sometimes non of them are working because of this bug.

Actual behavior

I have nothing more to add

Additional context

No response

@brabus1000 brabus1000 added the bug label Sep 2, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

1 participant