Windows x64.exe installer
The published Windows x64 installer for this release candidate.
- Version
- 1.2.0-rc.2
- Size
- 32,746,152 bytes · 32.75 MB
- Stable release
- Not yet
This guide includes only steps supported by available artifacts and testing. The current release is Void Scriptor Studio 1.2.0-rc.2, a release candidate for Windows x64, not a stable release.
Download only from the canonical domain voidscriptor.com. The SHA-256 checksum detects changed or corrupted files; the checksum alone does not prove provenance or a publisher signature.
Windows x64The published Windows x64 installer for this release candidate.
LOCAL VERIFICATIONf53402cc84ab3e1e15d7870d4c408cb4f4eef7ebdb0487b79f56e56cddfe5ae6
Text fallback readable without JavaScript:
Open checksum manifestPowerShell: run this from the folder where the installer is stored.
Get-FileHash .\VoidScriptor-1.2.0-rc.2-windows-x64-setup.exe -Algorithm SHA256The Hash value must exactly match the manifest. If it differs, do not run the installer; preserve the evidence and use the bug report form.
Maintainer verification: the repository provides checksum and Authenticode checks in one step.
pwsh -File tools/verify-release.ps1 -InstallerPath ./VoidScriptor-1.2.0-rc.2-windows-x64-setup.exe -ManifestPath ./release-manifests/VoidScriptor-1.2.0-rc.2-windows-x64.sha256A result of SignatureStatus: Valid only means the signature can be verified. RC.2 still uses a self-issued certificate, so the publisher is not trusted by SmartScreen.
Open VoidScriptor-1.2.0-rc.2-windows-x64-setup.exe after the checksum matches. The installer uses the default Windows location and offers an optional shortcut.
RC.2 has a timestamped Authenticode signature that passed a local audit, but its certificate is self-issued and is not yet a publisher identity trusted by SmartScreen. SmartScreen may still show a warning. Verify the source and checksum before deciding in the Windows dialog.
Open Settings → Apps → Installed apps → Void Scriptor → Uninstall, or run Uninstall Void Scriptor from the Start Menu. Project documents and user data should not be removed without a manual check.
The last audited portable artifact was marked RC.1: 34,496,233 bytes, SHA-256 1a13bbeaf1e2af1401690004cc4a34ad8f4a9e3e2b8377a0587fe79805ac071f, 497 members (494 matching payloads in CHECKSUMS.txt, plus BACA-SAYA.txt, CHECKSUMS.txt, and codesign.pub). Its public download has not been republished, so this page no longer offers a ZIP download button.
The RC.1 archive fingerprint can still be checked through the ZIP checksum manifest.
If you have an RC.1 portable archive from a trusted copy, verify its sibling .zip.sha256 hash, extract the entire folder, then run Release\void_scriptor.exe. Do not run the executable from inside the ZIP or separate the DLL/data files. Portable documentation is separate from installer documentation because the distribution flows differ.
The following configuration is a real test configuration measured for local evidence; it is not an official minimum requirement and does not promise compatibility with every device.
Sign-in status and error reports are stored in the Windows application support folder (the technical component is named path_provider), inside VoidScriptor\state and VoidScriptor\diagnostics\crash. The folder location may vary according to Windows configuration.
If you do not choose a location yourself, the main project folder is in Documents, inside VoidScriptor\Projects. Your chosen location is the primary reference; if the drive is unavailable, the application tells you that a fallback location is being used.
The website uses GitHub or Google for sign-in. The session cookie only helps keep you signed in and does not contain a password. The optional Byte connection runs only on your computer at 127.0.0.1:8766 and accepts requests from permitted origins. Do not copy tokens, cookies, or secrets into a report.
Check the status and release limits, read the release notes, or send a structured bug report. For security issues, use security.txt.