Your applications. One place.

The catalog is the heart of it.

Corex ships with a hand-picked catalog of 431 Windows applications, organised into categories like Browsers, Security & Privacy, Messaging, Media, Development, Gaming and Utilities. Each entry is a tiny record that names the application, who publishes it, where to get it from, and the switches to install it silently. The catalog is plain data — not code — and lives next to the executable, which means it can be refreshed on its own without a new build of Corex.

You open Corex, browse, filter, search by name or tag. When you pick an application, Corex already knows whether it is installed on this machine, whether an update is pending, and which source it will pull from.

Four sources, one experience.

Every application in the catalog is tagged with one of four sources, and Corex speaks all of them. You never have to think about which one applies to what you are installing.

• Windows Package Manager — Corex drives WinGet for anything available there, including the Microsoft Store.
• Microsoft Store — Store-signed packages come through the same path, verified by Windows itself.
• GitHub releases — for projects that ship on GitHub, Corex grabs the latest release asset directly from the repository.
• Direct publisher downloads — HTTPS endpoints on the vendor's own site, with signature and checksum checks against the expected signer.

HTTPS is non-negotiable. Even after a redirect, Corex refuses to continue if a hop drops to plain HTTP. Every transfer is encrypted end to end.

Download and verify, before anything runs.

When you confirm an install, Corex plans the session. Dependencies get pulled in automatically and installed first. Then the downloads begin — in parallel, with real byte-level progress (no made-up percentages) and resume support so an interrupted transfer picks up where it left off instead of starting over.

A downloaded file does not get to run until it has been checked. Every package is validated against the signals Windows itself trusts. If any of those signals fail, the file stays on disk and the task is marked failed with a human-readable reason — the installer is never invoked.

Install, one at a time, silent where possible.

Downloads happen in parallel, but installers run strictly one after the other. This is on purpose: Windows Installer gets confused when two MSI-based setups fight for the same lock, and silent flags behave less predictably when runners stack up. Running them sequentially is the boring, reliable path.

Corex uses only documented silent switches — the ones published by WinGet manifests or named in the catalog entry. Applications whose installer insists on user interaction are flagged up front, so you know which ones will pop a window instead of finishing in the background. Nothing is monkey-patched or injected to make an installer go silent that was not designed to.

Updates offered on open.

When you open Corex, it reads the installed-applications list from Windows itself and compares it against the catalog. If anything has an update available, a dialog appears — "7 applications have updates. Update all?" — and a single click runs the whole update batch through the same verified pipeline as a fresh install.

A toast notification mirrors the prompt in Windows' own notification centre, so you do not miss it if Corex is minimised or in the system tray.

Session log on disk, every time.

Every installation session writes a dedicated log file. For each application it records the source URL, download start and end timestamps, verification result, exact installation command, process exit code, duration, and final status. If something ever fails, the log tells you where in the pipeline it broke and why.

Logs go through a redactor before they touch disk — anything that looks like a URL credential, token, API key, password or authorization header is replaced with a mask. Nothing sensitive is written. Nothing is uploaded. The logs stay on your machine, like everything else Corex remembers about you.