Home / How to install Solara Executor on Windows
Install guideHow to install Solara Executor on Windows
Five steps, in this order. Most failed sessions are the same three mistakes: running from ZIP preview, attaching on a loading screen, or launching without elevation.
Before you extract
You need 64-bit Windows 10 or 11 and the x64 .NET Desktop Runtime. A missing runtime looks like a dead download: the process starts and never draws a window. Confirm you can already join a place in the official Roblox Player. Solara is not a launcher and does not install Roblox for you.
Smart App Control on recent Windows 11 can refuse an unsigned executable outright. If the file never starts and there is no useful dialog, read that setting on the requirements page before you redownload.
1 — Extract to a real folder
Unpack Solara_v3.zip to a directory under your user profile. Documents\Solara is enough. Explorer can show an EXE inside a ZIP and still not give you a stable folder. ZIP preview unpacks to a temporary location. Windows may clean that location while the process is running. Errors then look random: missing files, a flash of a window, or a silent exit.
Do not unpack into Program Files or other protected paths. Those locations add permission failures that get reported as attach bugs. Do not keep the EXE on the desktop as a copy dragged out of the preview — extract the whole archive.
2 — Start official Roblox yourself
Launch Roblox Player from the desktop installer you already use. Join a place and wait until you can move the camera or the character. A black frame, a loading bar, or the join fade is not a loaded place.
Store-only or mixed installs can point attach at the wrong process. Use the same player binary you actually click to play. Mobile, console, and cloud PCs have nothing useful to attach to.
3 — Run Solara as administrator
Right-click the extracted executable, choose Run as administrator, accept User Account Control. Administrator here means Windows elevation for this PC. It is not your Roblox password and it is not a Microsoft login form in the browser.
Attach has to reach another process. Without elevation the call has nowhere to go. A web page cannot show a real UAC dialog. If a site asks you to type a Microsoft password into HTML, close it.
4 — Attach once
Use attach after the place accepts input. Wait for the UI to confirm. Repeat clicks stack work the process did not ask for and are a common crash after a teleport.
Until attach confirms, do not dump a hub into the editor. An empty editor on first run is normal. ScriptHub is search, not auto-run.
5 — Then load Lua
After confirmation, run a one-line print if you want proof the session is live. Then load the script you actually want. Closing Roblox ends the injected state. There is no patch left in the place files.
If a window never appears, install the x64 .NET Desktop Runtime and check Windows Security protection history before you download a second archive. If attach fails, close both apps, join a place fully, elevate, attach once — that sequence is on the attach chapter.
What a first good session looks like
You should see a Solara window, a UAC yes, then an editor after attach — not a browser tab. Output and errors belong to that session only. A place change drops the session; rejoin, wait, attach again. That is expected for session attach, not a corrupt ZIP.
Typical mistakes that look like a bad ZIP
- Double-clicking the EXE inside Explorer’s ZIP overlay, then wondering why files vanish
- Unpacking into Program Files and treating access-denied as an attach bug
- Attaching during the join fade because the window already exists
- Clicking attach five times because the first click felt slow
- Skipping .NET, then downloading six other archives named Solara
- Turning Defender off instead of reading Protection history
If you hit two of those in one evening, stop and walk the five steps from the top. The install order is the product. The ZIP is just the file.
When to download again
Download again from this host when the changelog says the package moved, or when you cannot confirm the file you have is Solara_v3.zip from getsolara.live. Do not download again because a hub threw a missing-function error — that is coverage, and a new mirror will not add the API.
Continue
Attach · Requirements · Troubleshooting
Updated 2026-10-31 · Canonical host getsolara.live · Package Solara_v3.zip 3.221