Beta program
Utly Remote 0.2 is ready for everyday use. The beta helps us find problems on computers, networks and versions of Windows that we don’t have ourselves. This page explains how to join, what to test, how to report problems, what a crash report contains, and how each version is tested before it reaches you.
Joining
You don’t need to sign up. Install Utly Remote from remote.utly.dev, using the installer, the portable version or the Windows 7 version, and turn on Settings › About › Beta channel. New versions come to the beta channel first, and they become the stable version once they’ve run without problems for two weeks. The program checks for updates 30 seconds after it starts and then every six hours, and asks before it restarts.
If you’re helping us test, please tell us which computers you use it on: the Windows version, whether you used the installer or the portable version, whether you share your screen or connect to others, and what kind of network you’re on. This tells us which setups still need testing on a real computer.
What to test
Use it as you’d use any remote desktop program, and then go through this list once. We’ve tested each item on our own computers, but not yet on yours.
- Install it both ways: the installer on one computer (which includes the background service) and the portable version on another. Sign out and back in. The installed version should start in the system tray when you sign in, and you should be able to connect to it before anyone signs in.
- Connect in both directions. Check that the four words on the request window match on both screens.
- During a session, turn each permission off and on again (keyboard and mouse, clipboard, sound and files), and check that the other side loses and regains it straight away.
- Unattended access: set a password and connect with it from the other computer. Then turn on Ask on screen even when the password matches and connect again. Type the password wrong five times, and find the lockout in the session log.
- With the background service: connect to a computer that’s showing the sign-in screen, send Ctrl+Alt+Del, approve an administrator prompt, then restart the computer from the session and wait for it to come back.
- Monitors: connect to a computer with two or more screens, try View all, and unplug or plug in a monitor during the session.
- Files: send a large file each way using the files panel, drag a file onto the session window, and cancel a transfer halfway through.
- Copy text in both directions, and listen to a video playing on the shared computer.
- Chat in both directions, and make a voice call and a video call.
- Unplug the network cable on one side for ten seconds. The session should reconnect by itself.
- Accounts: sign up, sign in on a second computer and approve it from the first, sign it out from the second, then sign in again with a recovery code. Rename a computer in the address book on one computer and check that the new name appears on the other.
- Updates: leave the beta channel on and let the next version arrive. With the portable version, the previous file should stay next to it as
.previousuntil the new version has started once. - Windows 7, 8 or 8.1 with
remote-win7.exe, with and without update KB4474419.
Reporting problems
Bugs: write to mail@lohit.me. Please include the version (from Settings › About), your Windows version, whether you used the installer or the portable version, which side you were on, and the log file from Settings › About. The log doesn’t contain passwords or anything from your sessions. If there was a crash report, send that too. Short steps to make the problem happen again are more useful than a long description.
Security problems: write to mail@lohit.me, and don’t post them anywhere public. We’ll reply within three days, tell you what we think within seven, and fix anything serious within thirty days or explain our plan. We’ll credit you in the release notes, unless you’d rather we didn’t.
If someone told you to install this, whether on a phone call, in a message or in a pop-up, end the conversation and use Report an ID in Settings › Security. Our safety page explains why.
Some things aren’t bugs: the limits listed in our threat model under Not covered before 1.0; a server showing its sign-in screen instead of someone’s Remote Desktop session; and Windows Server Core, which has no desktop to share.
Crash reports
When the program crashes, it saves a text file in the crashes folder inside the data folder shown in Settings › About. The report includes the version, which part of the program crashed (the main program, the screen sharing helper, the background service or the Windows 7 version), your Windows edition and version, the time, and the error with the file and line where it happened. Your Windows user name is replaced with ~. The newest twenty reports are kept. A report never contains anything from your screen, clipboard or file transfers, because the part of the program that writes it can’t see them.
Nothing is sent until you choose to send it. Settings › About › Crash reports shows how many are waiting, with buttons to send or delete them. If you turn on Send crash reports automatically, they’re sent straight away and then every time the program starts, including reports from the background service. The Windows 7 version only has the switch. When a report reaches our server, we store it with your internet address and the time. A person reads it, and we delete it once the problem is fixed. Our privacy page says the same.
Reports from the background service are saved in %ProgramData%\Utly Remote\crashes, which only administrators can open, so they aren’t included in the count in the program. They’re sent when the automatic switch is on, or you can attach them to an email yourself.
Some crashes can’t be captured, such as a fault inside a video codec or a display driver. Windows records those in Event Viewer, under Windows Logs › Application, as an application error that names the faulting module. Including that entry in a bug report is the next best thing.
How each version is tested
Before a version reaches the beta channel:
- All our automated checks pass: code formatting, the strictest code checks on both versions, the tests, the release build, the Windows 7 build, the interface build, and a licence check of everything the program uses.
- Ten minutes of fuzz testing on the four parts that read incoming messages finds no problems. A longer run, six hours for each part, happens during the beta on a spare computer.
- A test session on Windows 7, Windows 10, Windows 11 and Server 2022 virtual machines, plus a server without a monitor whenever screen capture or the background service has changed. Any version of Windows affected by the changes is tested in full.
- The portable version, the installer, the Windows 7 version and the update files are built, signed, and published to the beta channel with a signed update document.
Before a beta version becomes the stable version:
- Network tests: a session on the same local network, one between two home routers (a direct connection), and one from a mobile or hotel network (through the relay). In each case, the viewer’s status bar confirms P2P direct or via relay.
- An update from the previous stable version on an installed computer with the background service running (the service stops, the program is replaced, the service starts again, and the session log carries on), and on the portable version (the previous file is kept, then removed after the new version starts properly). We also rehearse, on a copy, what happens when a portable version starts but doesn’t finish starting: it should go back to the previous file the next time it’s opened.
- Someone other than the developer installs it from scratch, from the download page to a first session, with no help except the help page.
- Two weeks in a row on the beta channel with no serious bugs and no unresolved problems with saved keys or signing in, while we read the crash and abuse reports every day.
- The stable version goes to ten percent of computers, then fifty percent, then everyone, over the following days, and we check the same reports after each step.