Home / Solara Executor / Windows 10 and 11
OS compatibility
Both 64-bit Windows 10 and 64-bit Windows 11 are documented targets, and the setup procedure is identical on each. What differs is how aggressively the operating system interferes before you get that far. This page covers the version checks worth doing first, the three separate Windows features that can block an unsigned executable, and what genuinely changes between the two releases.
Two facts about your machine determine whether anything on this site applies to you, and both take under a minute to confirm. The architecture matters because there is no 32-bit and no ARM64 package in this line, so a mismatch is a hard stop rather than a performance question.
Press Win + R, type winver and press Enter to see your Windows release and build number. For architecture, open Settings, then System, then About, and read the System type line — it needs to say a 64-bit operating system with an x64-based processor. If it reports ARM-based, this tool has no build for your machine, and no compatibility layer changes that.
| Your system reports | Supported | What it means |
|---|---|---|
| 64-bit, x64 processor, Windows 11 | Yes | Documented target. Check Smart App Control before you start |
| 64-bit, x64 processor, Windows 10 | Yes | Documented target. 22H2 is the baseline this site assumes |
| 32-bit operating system | No | No x86 package exists |
| ARM-based processor | No | No ARM64 build exists in this line |
| Windows 8.1 or older | No | Outside the documented scope entirely |
People often describe "Windows blocking it" as one problem, but there are three distinct mechanisms at work and each needs a different response. Telling them apart from the wording of the prompt saves a lot of guesswork, and the safety page covers how to decide whether you should proceed at all.
The most common one. You get a dialog saying Windows protected your PC, or that the publisher is unrecognised, usually with the real action hidden behind a "More info" link. This is a reputation check: the file is unsigned and has no established download history, so SmartScreen defaults to caution. It appears for a great deal of legitimate independent software on first launch.
Different in kind. Here the file is not merely unknown, it has matched something — either a behavioural heuristic or a named malware family. A tool that requests elevation and writes into another running process performs exactly the behaviours heuristic engines exist to catch, so a generic flag is unsurprising. A named family detection is a far stronger claim and should be taken seriously. The practical tell is that the file quietly disappears after download; check Windows Security, then Protection history, to see whether it was quarantined rather than failing to download. The verification guidance explains how to read the distinction.
This is the one that catches people out, because it does not warn — it blocks. Smart App Control is a Windows 11 feature that only permits applications it can positively evaluate as trustworthy, and unsigned software generally does not qualify. There is no "run anyway" path through it. Check its state under Windows Security, then App & browser control. Note that it has an unusual constraint: once turned off, it cannot be re-enabled without reinstalling Windows, which is worth knowing before you switch it. If it was already off or in evaluation mode, this does not affect you.
Less than the volume of discussion suggests. The application, the prerequisites, the elevation requirement and the attach procedure are the same on both. The differences are in the operating system's own posture.
On Windows 11 the main practical difference is Smart App Control, described above, plus the fact that recent builds ship with a stricter default security configuration generally. Nothing about the setup steps changes; you simply have one more feature to check before the first launch.
On Windows 10 the significant fact has nothing to do with this tool: Windows 10 reached the end of Microsoft's mainstream support on 14 October 2025. It still runs, and 22H2 remains the documented baseline here, but it no longer receives the regular security updates a currently supported release does. That is a decision about your whole machine rather than about any single application, and it is worth weighing on its own terms.
You may also see claims that one release executes Lua faster than the other. This site does not publish performance comparisons because it has no benchmark data to support them, and a machine that already struggles to run Roblox smoothly will not run better with a second process attached to it. The requirements page sets out realistic expectations.
The procedure below is the short form. Every step, and the specific failure each one prevents, is covered in the full install guide — worth reading once rather than working backwards from an error later.
winver and the System type line in Settings.On Windows specifically, three things change underneath a working setup. A Windows update can reset a security setting or re-scan a folder you had excluded. A Defender definition update can start flagging a file it previously allowed, which is normal for heuristic engines and not evidence that the file changed. And a Roblox client update can break attach entirely until the tool is rebuilt against it — that last one is the most common by a wide margin and has nothing to do with Windows at all.
The unhelpful response to any of these is to go looking for a patched build on an unfamiliar mirror, because that is exactly the window in which fake builds get the most downloads. Check the release notes for what is currently published, work through troubleshooting by symptom, and read the fake-download indicators before trusting a new source.