Search results

We have found a critical bug that prevented login to account on PC app when the user has registered more than 40 devices in the admin panel. Please do check version 1.16.0 that will be available tomorrow.

In version 1.16.0 we are going to force "~ HIGHDPIAWARE" for Remotly.exe, RemotlyLauncher.exe, remotly_launcher_x64.exe and (not public yet) Quick Support (RemotlyQS.exe) and Quick Support with branding (RemotlyQS_<company_code>.exe)

OK we have something: 1. Please open Local Group Policy editor. To do this please Press Win + R to open the Run dialog box. Type Control Panel in the text box and press Enter. Type edit group policy in the search box in the top-right corner of the Control Panel window. Under Windows Tools...

Thank you for letting us know. We are preparing 1.16.0 and will upload it soon. I will let you know. "when it is NOT freezing, can't move to another screen, always comes back to original screen after mouse release." This is a bug (regress since it was working in the past :/ ). We have also...

I will send a link to per-release v1.16.0. It might help.

Do you still have one of the older installers? Can you please check if this happens with v1.14.x? Thank you.

Please let me know if the crash is captured in the crash folder when crashlog.txt is present. Thanks!

I forgot about one thing that might help us. Please create a crashlog.txt file (empty file but with this name). This will enable crash report generation. After the crash please check the "crash" folder (it will be located in the folder where Remotly.exe is) and let me know if you see 3 files...

"found out that if moving the window to other screen, the GUI crashes -- remotly.exe is gone" Do these screens have same DPI? Can you also check if this happens when only one screen is available/connected? There must be a specific thing that is causing these problems. Another user reported a...

Can you create an exclude.txt file in Remotly installation folder and after checking ASUS software executable names(s) add them to this file (each line of this text file should include one exe name just like they appear in task manager).

We do our best to understand how this can happen and fix it before 1.16.0 update.

Both P2P and cloud (Connect Anywhere) connections fail and you see "connection failed" (from outside)?

Does not make any sense why the watchdog process could cause any trouble though :/

One more question. Are you sure remotly_launcher_x64.exe has to be removed/disabled? This process has no impact on Remotly.exe at startup. Since RemotlyLauncher.exe starts/creates Remotly.exe process it might have an impact on it. But the watchdog launcher_x64 process is started by Remotly.exe...

Please note that remotly_launcher_x64.exe is a watchdog for Remotly.exe process. If you delete it from the installation folder Remotly.exe will not start this watchdog process at startup and if Remotly.exe crashes during execution it will not restart automatically. This can be a serious problem...

In some situations we see a crash when the network adapter is enabled/disabled. But this does not happen often. It is on todo list. But for example if I have 2 network adapters installed and working in the same server i can switch them in real time in General-Settings (i'm switching between...

Are you connecting in local network or outside?

No changes where made in this area between 1.15.1 and 1.15.2. "the solution is to kill not only remotly.exe but also remotlyLauncher.exe and remotly_launcher_x64.exe. then start remotly.exe manually. becomes usable again." This is very useful information! Can you please make such test: -...

Is the connection ID field grayed out after running Remotly on the problematic PC? Or is it white? This is a very important thing to know since even when not logged in it should be white and you should be able to click the "eye" button to shot the connection ID assigned to this PC (you can...

Hi Fu2chN, You are not able to login to your account on this PC or not able to connect to this PC/connect from this PC? I see that KB5035942 is something brand new (released 26th March). We will install it and check it. Does the other PC also have KB5035942 installed (the one which works fine)?