Updates fail when the next file comes from a different door than day one. Write MSI, .deb, rpm, or source on the ticket and return to that class of asset.
Windows
Take a newer pychess-*-mingw_x86_64_msvcrt_gnu.msi from Releases. Uninstall from Windows settings if you need a clean removal. The exact wizard text is UNVERIFIED here.
Linux
Take a newer python3-pychess_*.deb or the matching rpm. Distro packages may lag. Pick one owner per user.
Source
If you built from the tarball, follow INSTALL for the next tag. That path remains UNVERIFIED. Source guide: source.
Related doors
Releases: releases. Safe download: download safe. First hour: installed.
Rank Timber maps the update door so labs do not invent a mirror during SmartScreen. Upstream remains at pychess.github.io. Keep website boards as a fallback; they are not the updater.
After uninstall, the PGN folder still belongs to you. Copy it before you wipe a profile. Club nights go faster when the next image already has the filename on the ticket. Machine chooser: for this computer.
Why doors matter
An MSI, a .deb, an rpm, and a source prefix uninstall in different ways. If the ticket is blank, the next volunteer guesses and installs a second copy. That is how labs collect three Start-menu entries.
What to keep
Keep the PGN folder. Keep the engine policy. Keep the Releases URL. You can throw away the old installer after the new one works.
What not to do
Do not run a “cleaner” from a search ad. Do not download a helper toolbar to fix a blocked MSI. Do not mix distro pychess with the GitHub .deb on one user without a note.
After a clean uninstall, prove a fresh install with the named asset before you restore custom board themes. First hour: installed.
Rank Timber maps the update door. Upstream remains at pychess.github.io. Related: releases, Windows, Linux .deb.
Shared-machine rhythm
Write the installer class on the ticket beside the OS version. After every reimage, take that same class from GitHub Releases, launch the GTK window, and replay one saved PGN. That three-step loop catches vanished packages and portal shortcuts that reappear from old bookmarks.
Keep engine binaries on a documented path. Keep the PGN folder off the package tree so uninstalls do not wipe club history. Keep website bookmarks if rated pools still matter, and keep them labelled as a different job.
Rank Timber publishes the install map. Upstream remains at pychess.github.io. Related doors stay under guides, releases, and installed.
Frequently asked questions
How do I update this chess client?
Return to GitHub Releases for pychess/pychess and take the same class of asset you installed: Windows mingw MSI, Linux .deb, or Fedora rpm. No winget id was found. Mixing a distro package with the GitHub file on one user without notes causes confused uninstalls.
How do I uninstall this chess client?
Use the Windows installer uninstall entry for the MSI, or your package tool for the .deb or rpm. Source prefixes need a manual delete of the install location you chose. Commands remain UNVERIFIED here and are not described as observed prompts.
Where should I download a chess update?
Prefer GitHub Releases for pychess/pychess when you want named chess assets. Take pychess-*-mingw_x86_64_msvcrt_gnu.msi on Windows or python3-pychess_*.deb on Linux. Keep Softonic-style mirrors out of the loop. Document the update door on the machine ticket so the next bump stays honest for shared desks.