Search results

Please remove all manually added registers as they should no longer be used. "today, I went back to earlier version of the same VM w/o remotely ever installed, updated to the same AMD driver and installed the most recent 1.33. the VM crashes during UI loading like before." Do you have...

Hi joffi, There is some problem with remote webcam access in latest version. It will be fixed in 1.33.0 tomorrow. Please note that after connecting the remote camera is not enabled (you will see remote desktop first). You need to manually enable it using RightCTRL+F12 after connecting.

And updated installer is now available: https://downloads.mirillis.com/files/beta/remotly/remotly_pc_1_33_0_setup.exe 1. Fixed booter service start 2. Fixed UAC screen in booter mode (non-VM) 3. UI changes (recent inbound connection list is now available in Settings->Security tab)

We will add an option in Settings->General "Close to tray".

Does this happen for booter or full version? Does it happen on the admin account or other/standard user? Cannot repeat this problem on my side. EDIT: i think i might have seen such problem on win 11 22h2. But after reinstalling to 24h2 problem does not seem to happen anymore. EDIT2: Replicated...

Is this the same user as admin user? There is no hand-over from booter to full version if the active user account is different from booter user (admin user that started the booter service). Maybe we are investigating something that is done so by design (at least currently).

Здравствуйте Veyran, это очень плохие новости :( Не могли бы вы попробовать пропинговать сайт remotly.com со своего ПК?

Can you confirm that setting the gpu used for remotly.exe (using display-settings-graphics) to low performance or specific 1 fixes the UI problem for you?

We will check it. Good idea. We will try to initialize 3D device used for rendering to the one which is AMD but in fact is Hyper-V. UI uses vGPU hardware for rendering itself (not hardware acceleration like for video but rather 3D part of GPU like games).

This time it's a bug in the OS itself. You will not see Hyper-V Video but instead duplicated AMD entires. The list looks like this: 1. Let Windows decide (can give random results) 2. AMD: Low power (should use hyper-v) 3. AMD: High power (should use AMD vGPU) 4. AMD: Specific 1 (should use...

My test setup: Two GPUs: Nvidia RTX4060 + AMD installed in one PC. Two VMs running at the same time, one VM using Nvidia and the other AMD. BTW. This allows big cost reduction as one PC can serve multiple users at the same time. One observation on my side. The best performance is achieved...

It's a bug. Thank you for reporting this. It's already fixed. We will upload an updated 1.33 installer soon.

It works. You can check it in task manager (performance tab). In the GPU graphs please select Decode or Decode 1 (it's a system bug, shows encoding part in decode section). If you disable hardware acceleration these graphs do not show anything. After enabling hw acceleration graphs show gpu load.

Can you try forcing Remotly.exe to be run using Hyper-V Video (using Settings-Display-Graphics). This way the UI will be rendered using Hyper-V Video adapter but other stuff will be using GPU-P.

1. reboot, and connect to VM via remotely client and login, the remotely UI does not load at all. no UI, no taskbar icon, nothing. can see remotly.exe process in task manager, and everything else works, including hardware acceleration. now, disconnect remotely client, open hyper-v terminal and...

"3. No prompt for installing without UAC (in win srv) -- from earlier, without UAC, booter process is not enabled. Even with UAC, it took me a couple of attempts and login/logout to somehow got it enabled." FIXED 4. Not related to hyper-v. In the hyper-v host itself (win 11), virtual display...

A new updated installer has just been uploaded: https://downloads.mirillis.com/files/beta/remotly/remotly_pc_1_33_0_setup.exe It fixes freeze on Hyper-V when virtual display renders using Hyper-V Video driver. "Hyper-v host win 11, up to date. Client win srv 2025 also up to date." Win 11 24H2...

Will upload one more test version today.

Ok. Got "low signal" when no virtual GPU is available and after setting Hyper-V video as source for virtual display.

I did not do this test before (always minimized Hyper-V window instead of closing it) but after closing it I got "low signa" for a moment and got signal back. But I lost virtual display and cannot switch to it (it is working when Hype-V instance window is minimized and not closed). EDIT: Go...