AppGeek 1.0.2

A packaging fix. AppGeek itself is unchanged from 1.0.1 - no new features, no behaviour changes.

What was wrong

The binaries published with 1.0.1 were stamped with the wrong version number. Right-clicking AppGeekSetup.exe and looking at Properties > Details showed 1.0.0, even though the release was 1.0.1.

The build never received the version. Both the project file and the installer script carried a hardcoded 1.0.0, and nothing passed the tag's version in, so every build produced files labelled 1.0.0 regardless of what was being released.

What changed

The release build now takes its version from the tag and writes it into all three executables. A check step reads the version back out of each finished file and fails the build rather than publishing if any of them disagrees - so a mislabelled download cannot ship again without someone noticing.

Which file do I want?

File	Who it is for
AppGeekSetup.exe	Most people. Installs to Program Files, Start menu entry, proper uninstall entry
AppGeek.exe	Portable. Self-contained, nothing to install first
AppGeek-light.exe	Portable, and you already have the .NET 8 Desktop Runtime

Verifying your download

SHA256SUMS.txt is published below.

Get-FileHash .\AppGeekSetup.exe -Algorithm SHA256

The binaries are not code signed, so Windows SmartScreen warns on first run - click More info, then Run anyway.

You can also now confirm the version yourself before installing: right-click the file, Properties > Details. It should read 1.0.2.

What's Changed

• Cover winget version parsing with tests (APP-03) by @techygeekshome in #1
• README: document the one network call (APP-09) by @techygeekshome in #2
• Stamp the release version into the built binaries by @techygeekshome in #3
• Bump to 1.0.2 so the next release ships correctly stamped binaries by @techygeekshome in #4

New Contributors

• @techygeekshome made their first contribution in #1

Full Changelog: v1.0.1...v1.0.2

AppGeek 1.0.1

AppGeek now ships with an installer.

AppGeekSetup.exe installs AppGeek into Program Files, adds a Start menu entry and an optional desktop shortcut, and registers a proper uninstall entry. The two portable builds are unchanged and still published alongside it.

Also in this release: publisher and version strings read from the registry are now cleaned of stray quotes before they are displayed, and an application winget does not track no longer claims "winget" as its source in the Installed list.

Verify any download against SHA256SUMS.txt. The binaries are not code signed, so Windows will warn on first run - click More info, then Run anyway.

Full Changelog: v1.0.0...v1.0.1

AppGeek 1.0.0

First public release.

AppGeek reads everything installed on your PC, works out what has a newer version available, shows you exactly what would change, and updates the ones you tick. It also carries a catalogue of 67 common Windows applications, so setting up a machine is a case of ticking a list and walking away.

Free for everyone, including at work. No bundled offers, no telemetry, no account, no Pro tier.

Which file do I want?

File	Who it is for
AppGeek.exe	Most people. Self-contained, nothing to install first
AppGeek-light.exe	You already have the .NET 8 Desktop Runtime and want the small download

Neither one installs itself. Download and run.

Windows will warn you

AppGeek is not code signed, so SmartScreen shows "Windows protected your PC" on first run. Click More info, then Run anyway.

SHA256SUMS.txt is published below so you can check what you downloaded:

Get-FileHash .\AppGeek.exe -Algorithm SHA256

Both binaries are built by GitHub Actions from the source in this repository rather than on a developer's machine, so the build is auditable.

What it needs

• Windows 10 version 1809 (build 17763) or later, or Windows 11
• Administrator rights
• An internet connection while installing or updating

Nothing third-party. AppGeek shells out only to winget.exe, powershell.exe and cmd.exe, all of which ship with Windows. If winget is missing, AppGeek offers to repair it rather than failing with a cryptic error.

Worth knowing

• Upgrades are pinned to the scope an application is already installed at, so AppGeek cannot relocate a per-user install to machine-wide and leave your shortcuts pointing at nothing.
• An installer is never killed part-way through. Stopping a run prevents the next package from starting; it cannot interrupt the one in flight.
• A package is left alone rather than matched on a guess. An app AppGeek cannot identify with confidence is simply not offered.
• All 67 catalogue entries are verified against Microsoft's live winget index.
• Network and domain features — discovering other machines, remote inventory, pushing installs — are deliberately not in this release.

Found a problem? Open an issue.

Full Changelog: https://github.com/techygeekshome/AppGeek/commits/v1.0.0