Request installation option to turn-off hardware acceleration completely

[mirillis]

repeat what reported earlier on UAC prompt screen (asking for admin right) results in blank screen in 1.33. in win 11, not related to hyper-v.

it does recover itself if wait for a minute or so and reconnect (but reconnecting before that also blank screen).

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 problem. It's a new bug in 1.33 beta version.

 

[mirillis]

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)

 

[hhspiny]

Always the same user which is the built in administrator

 

[hhspiny]

VM/GPU-P crash question -- for the 1.33 installer, are manual registry entries needed?

I have been playing with remotely inside a copy of the VM machine in last a couple of weeks, accumulating all these fixes/versions. and it does not crash with 1.33 versions.

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.

 

[hhspiny]

new version about booter process in VM. re-install (use "run as admin") and reboot, no booter. login, no booter. logout and login again, there is booter. however, I did NOT need to run remotly.exe manually with "run as admin"

Same no UI behavior in the new version

 

[mirillis]

VM/GPU-P crash question -- for the 1.33 installer, are manual registry entries needed?

I have been playing with remotely inside a copy of the VM machine in last a couple of weeks, accumulating all these fixes/versions. and it does not crash with 1.33 versions.

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.

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 "checkpoints" enabled for a VM with GPU-P? If yes, then this might be the source of these problems.

 

[hhspiny]

I had a previous copy of virtual dsk before installing remotly. Used that one and crash happened again.

 

[mirillis]

I had a previous copy of virtual dsk before installing remotly. Used that one and crash happened again.

I don't think doing so with vGPU is safe.

 

[hhspiny]

It is safe as long as hardware is the same and gpu-p status is the same

 

[mirillis]

It is safe as long as hardware is the same and gpu-p status is the same

But "checkpoints" are not allowed for VM with vGPU to work stable. Isn't it a similar case?

 

[hhspiny]

Not using checkpoint. Just copy virtual disk. Have done this for several years as way of backing up which hyper-v does not allow with Gpu-p

 

[mirillis]

Not using checkpoint. Just copy virtual disk. Have done this for several years as way of backing up which hyper-v does not allow with Gpu-p

But the latest "snapshot" works fine? The older one crashes?

 

[hhspiny]

if virtual disk is disk-0, made a copy of it before installing remotely (disk-1).
then play with all remotely settings in disk-0, (registry, new versions, update AMD driver), and eventually disk-0 works fine except for the no UI problem.
now, use disk-1 instead, upgrade AMD driver and install the latest remotely, it crashes while UI is loading.

experimenting now with different things that might have been done to disk-0 to see why.

 

[mirillis]

I still don't get it with the "no UI" problem.

Summarizing:
1. Is Remotly.exe visible and running in task manager (details)
2. If point 1 is true, what is the user/owner visible in task manager (details) for Remotly.exe
3. Is remotly_boot.exe running at this point
4. Is there a Remotly icon visible in the tray?
5. Was "start with windows (minimized)" selected?

 

[hhspiny]

what I meant by "no UI".

1. remotly.exe is visible and running in task manager, runs under administrator account. booter process runs
2. "start within windows "minimized" selected before rebooting.
3. connect via remotely client, login, remotely icon not visible in the tray (and no interruption during login)
4. connect via hyper-v terminal, remotely icon visible in the tray, clicking it can open remotely UI

 

[hhspiny]

finally figured out how to avoid VM crashing.

repeat the setup, a previous copy of VM disk, which never had remotely installed.

connect via hyper-v terminal
1. update to latest AMD driver that worked. GPU-P enabled and working, installe remotely, VM crashes while remotely UI is loading.
2. add the registry entries, reboot, still crashes.
3. shut-down VM. DISABLE GPU-P in hyper-v host for this VM. boot up VM. remotely now runs fine inside VM, login to remotly account, select "start with windows", obviously no hardware acceleration encoding (grayed out in UI).
4. shut-down VM. ENABLE GPU-P in hyper-v host for this VM. boot up VM. remotely still runs fine inside VM. in UI, turn on hardware acceleration encoding. Reboot. remotely runs fine.
5. delete registry entries, reboot, remotely runs fine
6. reboot VM

Now connect via remotely client
1. connect to windows login screen, login (admin), no remotely UI (no tray icon).
2. run 3D benchmark, confirm that hardware acceleration is on

Now connect via hyper-v terminal, login, and remotely tray icon is visible

 

[mirillis]

what I meant by "no UI".

1. remotly.exe is visible and running in task manager, runs under administrator account. booter process runs
2. "start within windows "minimized" selected before rebooting.
3. connect via remotely client, login, remotely icon not visible in the tray (and no interruption during login)
4. connect via hyper-v terminal, remotely icon visible in the tray, clicking it can open remotely UI

I still need to dig deeper into this...

"1. remotly.exe is visible and running in task manager, runs under administrator account. booter process runs".

By booter process do you mean remotly_boot_svc.exe or remotly_boot.exe. This information is very important as remotly_boot.exe hands-over to Remotly.exe when the admin account logs in (the account which is LastUser and selected "start with windows"). So you should not see remotly_boot.exe when full version starts (this is different for Remotly QuickHost which always starts remotly_boot.exe after closing full version). Of course the hand over is done after the admin account logs in. If you reboot after signing out of the admin account and log in to a standard user account and this account has "start with windows" enabled you wiil see both remotly_boot.exe and Remotly exe. But these instances are in fact different devices (have different Connectin ID codes etc.).
And in this case you can connect to both, service account and full version running for standard user at the same time.

 

[mirillis]

finally figured out how to avoid VM crashing.

repeat the setup, a previous copy of VM disk, which never had remotely installed.

connect via hyper-v terminal
1. update to latest AMD driver that worked. GPU-P enabled and working, installe remotely, VM crashes while remotely UI is loading.
2. add the registry entries, reboot, still crashes.
3. shut-down VM. DISABLE GPU-P in hyper-v host for this VM. boot up VM. remotely now runs fine inside VM, login to remotly account, select "start with windows", obviously no hardware acceleration encoding (grayed out in UI).
4. shut-down VM. ENABLE GPU-P in hyper-v host for this VM. boot up VM. remotely still runs fine inside VM. in UI, turn on hardware acceleration encoding. Reboot. remotely runs fine.
5. delete registry entries, reboot, remotely runs fine
6. reboot VM

Now connect via remotely client
1. connect to windows login screen, login (admin), no remotely UI (no tray icon).
2. run 3D benchmark, confirm that hardware acceleration is on

Now connect via hyper-v terminal, login, and remotely tray icon is visible

What do you mean by:
"Now connect via hyper-v terminal, login, and remotely tray icon is visible"

Maybe i'm missing something important.

 

[hhspiny]

In all my testing in this thread, only administrator account is used.

when "no UI" (connect via remotely and login after reboot), both remotly_boot.exe and remotly_boot_svc.exe are both in task manager.
one instance of every process related to remotly

then connect and login via hyper-v terminal, UI shows, still both remotly_boot.exe and remotly_boot_svc.exe are both in task manager.
but, there are two instances of remotly_logon.exe and remotly_svc.exe.

 

[mirillis]

I have no idea why you can have remotly_boot.exe and Remotly.exe (UI) running at the same time. remotly_boot.exe closes as soon as full version is started and hand over happens (reconnect when connected at that time).

Can you check/search registry (regedit) for "LastUser" entry and check if LastUser has the name of current admin user?