Search results

It's still a driver error though. We need to figure out what exactly hurts the AMD driver as Remotly does a lot of complex stuff on GPU. I will upload another version of remotly_wincore.dll with another registry key "DisableHwDec" that work just like "DisableHwEnc" but for all hardware decoding...

I will do more tests with booter process only today and upload a new remotly_wincore.dll (also with new registry value DisableHwDec to disable all hardware related decode stuff).

Thats's good news and bad news. "The dxgkrnl. sys BSOD error is a common problem for Windows 10 users. The most effective solution to fix the error is reinstalling the graphics driver. Some other working solutions are disabling SLI, turning off NVIDIA Surround, running SFC/DISM scan, and...

We have uploaded a test version of remotly core for windows (digitally signed): https://downloads.mirillis.com/files/beta/remotly/remotly_wincore.dll To disable video encoding hardware acceleration (for all possible GPU vendors) please add a new registry value: DisableHwEnc (REG_DWORD) and set...

This is more tricky than it looks. On Windows Server 2025 there is a similar problem. We will add a popup message when something goes wrong after enabling "Start with Windows" ( which also starts the booter service). This might be useful as sometimes (very rarely and for unknown reasons) even...

Hi hhspiny, Thank you for a detailed explanation. "Then enabled GPU-P again, it ran fine during booting, could connect to windows login screen and login. but VM still crashed as remotly GUI was loading." This is a very useful hint. I think the problem is not with the encoding part but rather...

If you are still using old school screen saver, like this: and cannot remotely control your PC (turn the screen saver off) , please use "Send CTRL+ALT+DEL" option which is available both in mobile and desktop Remotly client apps.

We will make more tests on AMD. It is not happening on Intel and Nvidia.

"maybe it confused remotly -- for example, the login process itself was interrupted" This could have happened. In fact if there was a non-standard error the auto login process would not start and instead enter unlogged state. In the new res.bin file I have uploaded it should be fixed.

No info here which driver caused the crash :(

Please try overwriting the res.bin file located in the installation folder with this one: https://downloads.mirillis.com/files/beta/remotly/res.bin Please let me know if these is any improvement with the internet drop/recovery.

I have just done a 1 hour test: - Disable network - Start Remotly host - Remotly stays in "Trying to log in..." state - Enable network after 1h - Remotly logs in Pressin "CANCEL" on this "Trying to log in..." dialog deletes your encrypted login credentials and will switch to Remotly login screen.

There will also be an information in the System Event Monitor. Can you check what it says?

I will check when does the auto logout occur. If I remember well there were such cases in past versions but after introducing auto reconnect Remotly should eventually login to you account again when internet returns. You can check this after starting Remotly host. There will be a "Trying to log...

Is there any chance you can see in which driver the crash occured? the name is visible on the BSOD screen.

Hi Everyone, We hope you are all doing well! Today we have released a big and important update for Remotly PC Host app. Please find the changelog for this update below: - Switching between monitors, including the ability to control all monitors at once (to switch to all display view please use...

One question. Do you have more than one GPU in this system? If yes, which GPU is selected as the renderer for virtual diaplay.

No luck. No blue screens/crashes on two different test PCs.

We are checking this too.

I think you have reported it some time ago. We will check again.