Search results

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...

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...

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

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

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

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

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...

Always the same user which is the built in administrator

as title. many times, hit the close by habit and asked if I really want to exit remotely. then have to go back to click the minimize.

On the problem of no UI in VM. probably not a video device problem alone. set remotly.exe to either of the two GPU list in graphic result in the same, no UI. (remotely session to VM) notice that when login to admin account within remotely session, there is no interruption has it should...

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).

Can the installer/program set it automatically? I would think UI does not need hardware acceleration.

what I meant by this is for remotely host inside VM. setting hardware encoding disabled or GPU-P, produce the same 3D benchmark score and hyper-v host's physical GPU is fully occupied in both cases. .

not sure if it is related. for the 1.33, in win 11, UAC promote results in blank screen if it is the first time like happened in previous version. but it seems to recover either after a while or reconnection. after that, 2nd time UAC promote works fine

I thought so too, but hyper-v video is not in the list.

end of day, it is super cool to remote to hyper-v host AND VM at the same time and run hardware accelerated 3D apps in both. congrs. have not tried to have multiple VM up at the same time, and if it runs, a vGPU host machine in your normal laptop !!

A separate observation on booter process in VM/Win Server and v1.33. all in administrator account and hyper-v terminal. install with "run as admin", select "start with windows", no booter process, after reboot, no booter process. close remotely UI and re-run with "run as admin", still no...

A separate observation on hardware acceleration (encoding) in VM (w/o virtual display). this option in UI does not have effect. hardware acceleration is used with it disabled or not. confirmed with the same 3D benchmark score. however, I do feel heavy 3D session (benchmark) runs smoother and...

In my case, only admin account was used in the VM. the remotly.exe process (w/o UI) runs under admin account via remotely client connection, logout/login still not loading UI. Re-install without the virtual display driver, the same outcome. Remotely in VM runs fine without the virtual...

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...