Build 0.10.1 is not signed with an Authenticode certificate yet. The browser stops the download, SmartScreen stops the first run, and User Account Control asks for elevation. None of them means the file is broken. Below is every screen in order and the button that moves it along.
An Authenticode certificate is issued to a verified legal entity and renewed yearly. Talyh does not have one, so every build ships unsigned — this one included.
SmartScreen scores an executable by how many machines have already run it. A build published today starts at zero — signing shortens that climb, it does not skip it.
Each release publishes the SHA-256 of the installer next to the file. Get-FileHash in PowerShell compares it with what landed in your Downloads folder — the one check these dialogs cannot make for you.
step by step
Scroll, or use the arrows under the screen. Each step shows the window you will actually see and marks the control to press.
01download
Press the download button on the download page. The file is The-0.10.1-setup.exe. The browser fetches it, then refuses to hand it over: instead of a finished file the downloads tray shows a warning row.
“This file isn’t commonly downloaded and it may be dangerous.”
02keep the file
Open the downloads tray, click the warning row and read the panel. The button that keeps the file is deliberately the plain one: Download suspicious file in Chrome.
Nothing is fetched a second time — the file is already on disk. The browser is waiting for permission to release it.
03smartscreen
Double-click the installer. A blue window appears with one visible button, Don’t run. The one you need is hidden until you click the More info link.
“Windows protected your PC. Microsoft Defender SmartScreen prevented an unrecognized app from starting.”
After the click, two lines appear — the app name and the publisher — and next to them Run anyway.
04user account control
The installer writes into Program Files and registers file associations, so Windows asks for administrator rights. The publisher line reads Unknown — that is the missing certificate again, not a different program.
Check that the file name is the one you downloaded, then press Yes. If a name you do not recognise appears here, press No: this prompt is exactly where a substituted file would show itself.
05install
Choose a folder, wait for the progress bar, launch The. The editor opens without further prompts.
The warnings do not come back on every launch — they are attached to the downloaded file, not to the installed application. The next unsigned update repeats steps 01 to 04 once.
still stuck
The warnings describe a missing signature and a missing download history, not the contents of the file. That is also why they are worth a check rather than a shrug: hash the installer against the published SHA-256, and you have verified the thing the dialogs cannot.
An Authenticode certificate is planned before the 1.0 release. Until it is in place every build stays unsigned, and this page stays accurate. SmartScreen reputation then accumulates on top of the signature over the following weeks.
It appears only after More info. If the link is missing entirely, a policy on the machine blocks unsigned installers — on a work computer this is set by an administrator and cannot be worked around from the user side.
Some engines flag unsigned installers heuristically. Check the SHA-256 first. If it matches the published value, add an exception or report the detection to your vendor as a false positive.
Yes, once per downloaded build, until a certificate is in place. The installed application launches without prompts in between.
ready
Windows 10 version 1809 or newer, 64-bit. macOS builds and the checksums are on the same page.