btw, in my GPU-P, hardware decoding and encoding works fine. handbrake runs fine with hardware de/encoding. but getting it work was tricky. however, before I was able to get it work, handbrake simply did not detect GPU and turned off hardware encoding, it never crashed the VM. in fact, never...
still have problem with booter process after server is up and running for a while (can be days, and during which use computer console too). therefore, difficult to replicate. however, eventually it happens.
The direct phenomenon is blank screen after connection, and have to reboot to get it...
Attempted to run in hyper-v VM with GPU-P enabled. after installation, when GUI was loading, VM crashed, and VM always crashed during booting. in previous conversation, I was told that this is not supported at least for some GPU.
without GPU-P, installed and ran fine. but all hardware...
In windows 11, when login with admin account to do the installation, booter process is enabled -- i.e. access to windows login-screen without user login
in Windows Server 2019, when login with admin account to do the installation, the booter process is not enabled. need to right click the...
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...
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...
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.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.