Cherrytree

For managed CherryTree updates, close CherryTree before running the Windows installer. The EXE-x64 package can return Exit Code 5 when the application is open during update, so treat that as a conflicting-process condition and use a pre-close step in ConfigMgr, Intune, RMM, or PSADT instead of retrying while user sessions still have CherryTree running.

Use the official giuspen/cherrytree GitHub releases page as the Windows package source when the project home page is unavailable or redirects; it is the upstream repository linked by the CherryTree README.

Use the CherryTree project site as the source of record for current Windows packages, and close CherryTree before updates so Exit Code 5 is handled as a running-process conflict.

Official source: CherryTree official download/source page.

Official source: CherryTree official site.

For managed CherryTree deployments, pre-stage the Microsoft Visual C++ v14 Redistributable x64 runtime before installing or updating. Keep the VC++ runtime in deployment detection so fresh Windows images satisfy the note-taking app setup requirements.

Sources: CherryTree official download/source, Microsoft Visual C++ Redistributable.

For managed CherryTree updates, close CherryTree before launching setup. The EXE x64 package can return Exit Code 5 when the application is open during update, so treat cherrytree.exe as a conflicting process and verify the installed version afterward. Official source: Cherrytree Windows/download documentation.