Search results

had some time in the weekend, and attempted to replicate the problem. but could not. both client and server were able to reconnect without needing re-login after cutting off internet for more than half-hour. tried to cut off at computer, or cut off at router, same. even when starting...

after crashes, it reboots. was not able to see BSOD screen. this is from minidump (from whocrashed)

Looks like the problem is not limited to booter process. had long internet outage today, both server's booter process and client became off-line after internet was resumed. the client machine needed to retype username and password. The server needed to log into admin account, but no need to...

Ryzen 8945HS iGPU only. No discrete GPU.

I think it was for running in user account and it has been fixed. might not have been fixed for the booter process?

It appears that remotly would not reconnect or re-login after losing internet connection for a while, when running booter process only. does not seem to be the case when running in user account.

it might be that the virtual display driver has conflict with something in my computer. but the crash was surely resulted from the presence of virtual display driver.

spoke too early. the virtual display driver causes crashing about 15 minutes after booting. the error was. version 1.32 The computer has rebooted from a bugcheck. The bugcheck was: 0x00000001 (0x00007ffd9cc04cb4, 0x0000000000000000, 0x0000000000000001, 0xffffc989c1b5f4e0). Uninstall and...

seems to be working now, but the virtual display and file transfer with booter process only. thanks for the update. will test more and report back. in previous versions, sometimes it worked right after rebooting, but after a while, got blank screen.

Use booter process only (i.e. remotly does not run in user's account) and remotely virtual display driver installed. when the monitor is turned off, get blank screen and failed to connect msg, most of the time. sometimes, for a short period after rebooting, can connect. works fine with a...

this has happened multiple times. connect only to the booter instance to login to normal user account. remotly not running in the user's account. all work fine. after losing internet for a while and internet is restored, can't connect to the booter instance anymore. it still shows ready to...

Since the booter mode (i.e. administrator instance) can use GPU now, I only use it and do not have remotly run in user's account. however, file transfer is not possible in this setup. also, would highly recommend to add a dedicated file transfer GUI.

love the continued improvements to address users feedback.

For my own purpose, the ability to recover from crash is enough. ability to use hardware encoding inside VM is secondary, nice to have. obviously, hardware decoding is not relevant for VM, if that is what has caused problem.

I have had success running hyper-v vGPU with remotly in VM and utilizes hardware encoding, with Nvidia 4060 card. changed to AMD 9845HS and only use the iGPU. now remotly crashes the VM (not the host) upon starting remotly . tried to turn off hardware encoding, still crashes. if disable...

tried quite a few combinations. here is how to re-produce the problem. the issue is with remote desktop session. reboot computer from within remote desktop session. the "admin" instance shows as gray and offline. login via remote desktop to admin account, then logout. now can connect to...

continue from above. login into admin account, "remotly_boot_svc.exe" is active. turn "start with windows" off, "remotly_boot_svc.exe" is gone. turn on "start with windows (minimized)", "remotly_boot_svc.exe" does not return. reboot, before login, the admin shows both gray and offline...

this is after reboot, no user is logged in yet. after login with "administrator" account, it becomes green for connection. then, logout from "administrator" account, it remains green.

v1.26 Uninstall previous remotly, reboot, install remotly in administrator account, login to remotly account, set "start with windows" off then turn on again, reboot. Without any user login, "Computer/Administrator" appears offline. requires login to administrator account on server first...

I did a clean installation -- i.e. uninstall -- reboot - install. then de-select "start with windows" and re-select again. it is back to normal. I am guessing the reboot made difference and I remember tried de-select/re-select before without success.