1. CoreX release files
The CoreX project builds Windows x64 packages. Its release configuration defines an NSIS setup installer and a portable build target. Which files are actually available depends on the release; only download files attached to an official release and described by its notes.
| Package | What it is | Best for |
|---|---|---|
| Windows setup installer | Standard interactive installer configured to create Start menu and desktop shortcuts and allow an install-folder choice. | Most users. |
| Portable build | A separately built executable target, only if attached to the release. | Users who specifically need a portable executable. It may still write settings and logs to the user profile. |
| Source code | Project source and dependency manifests, including package.json and the pnpm lockfile. | Developers building or reviewing CoreX. |
For user installation steps, see the Installation Guide. The installer is configured not to delete app data automatically when uninstalling, so local settings or logs can remain.
2. Package managers inside CoreX
The CoreX Apps feature can use Windows Package Manager (Winget) or Chocolatey to install selected third-party applications. This is different from installing CoreX itself: the package manager downloads and installs other software you choose.
- Check the selected app's name and source before installing.
- Review package-manager and Windows prompts; an individual installer may request administrator approval.
- Third-party apps and their package sources have separate licenses, privacy practices, and update policies.
- Chocolatey may be detected or installed by the app as its README describes. Review the in-app prompt and current project documentation before allowing installation.
3. Developer dependencies and build outputs
The project manifest currently identifies pnpm 10.29.3 as the package manager, Electron 44, and React 19. The lockfile should be used to keep dependency versions consistent. Do not mix package managers or remove the lockfile in a routine change.
pnpm install
pnpm start
pnpm build
pnpm build:portablepnpm installinstalls project dependencies.pnpm startlaunches the desktop app from the project directory.pnpm buildcreates the configured Windows NSIS installer.pnpm build:portableinvokes the configured portable Windows build target.
Signing hooks and signing credentials are maintainer-controlled. Do not publish unsigned or locally signed artifacts as official releases. See the repository's code-signing documentation.
4. Verify before installing
- Open the official Noveriks/CoreX repository and release page, not an advertisement or mirror.
- Compare the attached file's version and name with the release notes.
- Use a publisher-provided checksum or signature if one is included. Do not trust a missing, placeholder, or unrelated checksum.
- Cancel if Windows reports an unexpected publisher or the downloaded file does not match the release information. Ask maintainers through an official channel.
5. Package-feed status
The public repository includes a package-bucket manifest, but the manifest currently contains a placeholder hash and inconsistent version/download fields. It is not reliable installation metadata as written. Until maintainers publish and verify a corrected package definition, prefer the official GitHub release installer rather than installing CoreX through that bucket. Do not use or distribute the placeholder hash.
This note may become outdated when the repository is fixed; check the manifest and release version at the time you install.
6. Package troubleshooting
- Checksum missing or placeholder: stop; do not install from that package feed. Download from the official release or ask maintainers for a verified checksum.
- Package version differs from release: check release notes and package metadata. Do not assume the package manager points to the newest version.
- Install failed: read the package manager output and avoid repeatedly retrying elevated commands. Report the exact package version and sanitized error.
- CoreX app installation tools: report the third-party package name, manager (Winget/Chocolatey), and error to the relevant service or CoreX issue tracker.
For help, use GitHub Issues or email help.mahinulislam@gmail.com.