Request installation option to turn-off hardware acceleration completely

[hhspiny]

even more interesting, with the setup from above

inside remotly session, connecting to the VM. can load the UI fine in normal user account. can also login to admin account, but UI does not show up (although remotly.exe process is active), even if kill the process and re-run it. rebooted multiple times, same.

On the other hand, on the server's consol, connect to VM via hyper-v terminal, loading UI in normal user account or admin account crashes VM.

almost there, game inside VM via remotly.

 

[mirillis]

It works OK in booter mode with hardware acceleration when there is no UI?

There is still one other option. The problem might be with remotly_x86.bin or remotly_x64.bin processes which I think are not used by the booter.

 

[mirillis]

I will prepare remotly_wincore.dll which works the same for full version and booter version (not start .bin helper processes).

 

[hhspiny]

Correct. Works fine as long as UI is not showing. Including booster with hardware encoding in VM

 

[mirillis]

Hi hhspiny,

Sorry it took so long.

Please check the file below:

Loading…

downloads.mirillis.com

Please overwrite files in Remotly installation folder with these new files (all are digitally signed)

It includes files that will be used in 1.32.1 update.
These files include the following changes:

1. Adds support for new test registry "ForceVmWorkaround" (please create just like before and set it to '1')
This registry forces Remotly not to use low-level capture engine. Please make sure to use the virtual display adapter and set it to use the GPU-P.
Additionally it is highly recommended to use Windows->Settings->Display and make Windows use only the virtual display (Show only on 2).
Moreover please go to Windows->Settings->Display and find the "Graphics" option. Please make sure Remotly is started on the GPU-P - High Performance and not Hyper-V).
To make sure ForceVmWorkaround is used you can use Task Manager to check there are no remotly_x86.bin and remotly_x64.bin running.

2. New UI design for Remotly settings
3. Fixed "Share specific monitor" not showing all displays after Remotly Virtual Display initializes virtual display
4. Critical fix for remotly_svc.exe (memory leak)

 

[mirillis]

BTW. There are also log files for these .bin files. They are also located where the previous log files were.
Can you let me know if you see a file named "action_bin_x64_log.txt" in C:\Users\<user name on your hyper-v>\AppData\Local\Mirillis folder?

 

[hhspiny]

the good news is that VM does not crash anymore. the bad news is blank screen. reproducible.
Apply the patch and other suggest setting, reboot VM,

the first problem:
1. remotely client connecting to windows login screen, login to admin fine.
at this point, remotely UI does not show up at all, and no icon in notification area. remotly.exe process is running.
2. run remotely manually, nothing happens.
at this point, can disconnect and reconnect from remotely client fine.
3. login via hyper-v terminal into admin account, the remotely UI loads automatically. close hyper-v terminal
at this point, got two remotely instances now. and remotely client gets blank screen !!!

the second problem: reboot VM again
1. run #1 and #3 above to avoid two instances
at this point, even in hyper-v terminal, no remotely UI at all
2. close hyper-v terminal
at this point, remotely client gets blank screen !!
3. connect hyper-v terminal, without login, terminal shows windows login screen
at this point remotely client gets blank screen !!
4. in hyper-v terminal, login to admin, keep terminal open
!!!remotely works again !!! but no remotely UI, no notification icon.

 

[mirillis]

Thbak you so much!

I will try to replicate these problems running the same test scenarios.

I do not undestand one thing. The new test version should work just like the booter but with UI.

"the bad news is blank screen. reproducible".
By blank do you mean the video on the Hyper-V is not refreshing looking at it locally? Or is it black after connecting remotely?

I also see a blank screen after selecting "show only on 2". But after connecting it works.

 

[mirillis]

BTW. We will prepare new remotly_x86.bin and remotly_x64.bin with more logs. This way we will be able to exactly locate the place where VM crash happens. It would be ideal to make the original version work without any workarounds.

 

[hhspiny]

When I say blank screen it means when connecting remotely client to the server, client has blank screen and after a few seconds says reconnect or disconnect.

In summary... booter works before remotly.exe loads after login. The Remotly.exe can't show UI. Once remotly.exe runs, needs hyper-v terminal connected AND login to avoid blank screen. VM has remotely virtual display driver installed.

VM setting system display does not show multiple monitor option. In fact, most options such as resolution are grayed out.

 

[mirillis]

We are working hard on making booter work with low-level capture engine in Hyper-V with GPU-P and virtual display.

We see similar problems discussed in this thread on a Hyper-V VM running with Intel UHD 630 GPU as GPU-P. Now everything works like a charm with best possible performance and hardware acceleration. We still need to add this to the full version on non-admin account.

I will upload a test version as soon as it is ready and stable.

 

[mirillis]

Sorry it took so long...

https://downloads.mirillis.com/files/beta/remotly/remotly_pc_1_33_0_setup.exe

This is a BIG update and we hope it will not introduce new problems:
1. Hyper-V now uses low-level capture engine for all user accounts when booter service is running
2. Booter service in Hyper-V does not use low-level capture engine (but can use hardware acceleration)
3. For best performance it is recommended to connect to full version (booter should be used for supervisor purposes)
4. The UI has changed and adds list "incoming connections". This allows quick monitoring if someone has tried to connect to our host machines...

IMPORTANT:
Tests were done for all GPU vendors on Windows 11 24H2! We have also tested this version on Hyper-V running on Windows 10 22H2.
Older OS versions may cause problems (for example we see problems on Hyper-V running on Windows 11 22H2).
We are not going to fix problems for Hyper-V running on Windows 11 older than 23H2 and Windows 10 older than 22H2.

 

[hhspiny]

tested the new version 1.33 in hyper-v.
installed via hyper-v terminal. crashed right after installation (with virtual display) when UI was loading, but did not crash anymore after reboot.
but, could not get UI to load. remotly.exe process runs, but no UI, no icon in taskbar. run remotely shortcut, still no UI, but two remotly.exe processes running.

still in hyper-v terminal, logout and login again, icon shows up in taskbar, and can load UI. hardware acceleration is off.

close hyper-v terminal, connect via remotely client. blank screen.

login via hyper-v terminal and keep it open, connect via remotely client, now finally works. but if hyper-v terminal is closed, blank-screen again.

 

[mirillis]

Can you please let us know what OS is running on the Hyper-V (like Windows 10 22H2 etc.). Also we need to know what AMD driver version is installed on the Hyper-V.

 

[mirillis]

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 virtual display after reconnecting (Hyper-V windows still closed, not minimized)

 

[mirillis]

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

 

[mirillis]

Will upload one more test version today.

 

[hhspiny]

Hyper-v host win 11, up to date. Client win srv 2025 also up to date.
The issue of UI not loading quite strange. Need to logout and login to get ui to load but not always. Ui can still not load after re-login. Maybe this is unique to server OS VM?

 

[mirillis]

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? Can you please insert a screenshot of the Device Manager with Display Adapters shown on the Hyper-V host? Or at least write what the Display Adapter list shows.
We have a Server OS VM so we can further investigate this. As soon as we reproduce the exact same setup.

By "win srv 2025 client" do you mean that you connect from a Windows Server 2025?
Are you sure there is no Remotly icon in the system tray?
Please remember there is no UI for booter so you need to start full version.

 

[hhspiny]

Thes new version AND upgrading to latest AMD driver seem have solved the problem. Hyper-V VM works fine now, hardware acceleration works, no crash with virtual display. also tried 1.32 with the latest AMD driver, crashed. it now almost works except for the following issues:

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 login, two remotely icons show up in taskbar and two processes are in task manager, and two identical instance in list of active devices.

2. inside the VM, hardware acceleration is by default disabled in UI option, but it is actually enabled (3D app/benchmark gets native speed). toggling this option on/off does not affect anything.

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.

4. Not related to hyper-v. In the hyper-v host itself (win 11), virtual display driver causes crash in 1.33. not in 1.32. (possible 1.32 did not crash because of using old AMD driver). the crash happens during remotely session, and seems to be random, but once 3D intensive application runs for example 3D benchmark, always crashes.