Search results

Hi Raffien, This must be a false-positive. Just scanned the same file using virustotal and it does not show anything using Bitdefender with latest database. https://www.virustotal.com/gui/file/aacb6ef78c17382dda4b26c1a4d794e712e64a39d82f7d52329ec44b90ad125d?nocache=1 There are 2 others that...

I have double checked remote camera and it works. The only problem I see is that the camera is only refreshed when the desktop is refreshed.

Hi jofii, First about the camera. The connection is always done to the desktop (even if your last connection ended showing remote camera video). You always need to send Ctrl + F12 after reconnecting.

Dear Users, Today we bring you a big update that fixes existing problems and introduces new features! 1. Major fixes and improvements for Hyper-V with GPU-P (GPU Paravirtualization aka vGPU) 2. Added recent inbound connection log which allows checking who connected, or was trying to connect to...

During start, Remotly.exe gives a signal to remotly_boot.exe to close so a hand-over can be done. For some, yet unknown reason, this does not work in this case.

Actually this sentence: remotly_boot.exe still sticks around preventing remotly.exe from starting and it is consuming decent CPU time. may finally help us in locating this problem. In tje previous post there was a typo: "Remotly PC v1.33.0 is not available from the official download page"...

I will try to contact the person responsible for this tomorrow. Please find more details in a private message.

One more idea regarding GPU-P problem. Can you please download DebugView (https://learn.microsoft.com/en-us/sysinternals/downloads/debugview) and run it on the problematic VM before starting Remotly and check if there are any errors from AMD driver? BTW. Remotly PC v1.33.0 is now available from...

Hi Qsab, Sorry for the late response. Someone from our team will contact you on Monday.

We would already fix it if it had happened at least once in our labs :( Our six VM setups with GPU-P (all vendors) are working OK.

Booter service has nothing to do with GPU-P. It would also have happened our side if it did. We are testing on 6 VMs with GPU-P at the moment and do not see this problem on v1.33. EDIT: It must be related with this crash so partially it might by related with GPU-P.

99% this because of mouse disconnection.

We will check this again. We have already changed this for the mobile app after our last conversation. You can always switch between game/desktop mode even when a game was detected.

Forgot one thing regarding booter service. It will not start when "Keep me logged in" is not enabled.

I have changed LastUser value by hand to make it case sensitive. Remotly.exe starts anyway. The difference is that I see two different devices as "ready to connect" one is the booter and the other being full version. But it does not prevent Remotly.exe from starting. Something else is preventing...

We will remove case sensitivity for user name anyway. Your last post is good news (at least partially) but we still need to make all this rock solid before moving to v2.0. For example this problem with remotly_boot_svc.exe not starting should not happen anymore. A new (and probably final) v1.33...

I will try to replicate this on win srv VM. Yes, not case sensitive for the system but not for Remotly... But if LastUser is in fact "administrator" and Remotly.exe user/owner also "administrator" in task manager it should work properly.

Here everything works OK.

Is LastUser also "administrator" and not "Administrator"? Remotly.exe is not starting as it is waiting for a hand-over. Full version will not start properly as it waits for booter to close (it is the same device - same Connection ID).

Something is seriously wrong. Your current logged in user is also Administrator? Because it looks like Remotly.exe is not running under Administrator user. Can you check in task manager what is the user/owner for remotly_boot.exe and Remotly.exe? Are these the same users/accounts/owners?