Installation
Installer requirements, Windows security prompts, dependencies and first-run guidance.
This hub is prepared for public support content as NeoWorks moves from development into testing and release.
Installer requirements, Windows security prompts, dependencies and first-run guidance.
Licence-key entry, machine activation, transfer and deactivation guidance.
Planned licensing →Stable and Preview channels, update checks and release notes.
View updates →Supported Windows versions, file formats and known limitations will be documented per release.
Public release notes will surface meaningful known problems without exposing internal debugging noise.
Release notes →A structured public bug-report route will be added before wider testing. It will collect reproducible details rather than sending users into the development repo.
As public builds arrive, support will grow around installation, activation, updates, diagnostics and compatibility.
NeoWorks already includes a diagnostics direction for checking modules, dependencies, settings and logs.
Every public build should explain what changed and what is still known to be imperfect.
A proper contact route will be published before public sales or support commitments begin.