Hi bodyzitz, and thank you for the logs (this is how a useful report should always look like 🤗)
The last checkpoint is missing in the second log (there should be CP24 but it only got to CP23)
We will get back to you soon.
It works OK in booter mode with hardware acceleration when there is no UI?
There is still one other option. The problem might be with remotly_x86.bin or remotly_x64.bin processes which I think are not used by the booter.
BTW. Can you also try to start Remotly without administrator rights on the Hyper-V. Please let me know if this will make any difference (Run Remotly.exe from installation folder).
Thank you!
Good news is that the UI starts properly. The core crashes.
I have uploaded one more remotly_wincore.dll (also digitally signed):
https://downloads.mirillis.com/files/beta/remotly/remotly_wincore.dll
1. Does not initialize D3D9 (legacy stuff for old Windows operating systems)
2...
The UI is using CEF for UI rendering (yes, it might initialize something that causes problems).
Could you be so kind and past the content of these two files:
C:\Users\<user name on your hyper-v>\AppData\Local\Mirillis\remotly_exe_log.txt
C:\Users\<user name on your...
File uploaded (digitally signed):
https://downloads.mirillis.com/files/beta/remotly/remotly_wincore.dll
To disable video decoding hardware acceleration (for all possible GPU vendors) please add a new registry value:
DisableHwDec (REG_DWORD) and set it to "1"
in the following registry key...
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.
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.