Directory Junctions Move 10GB of WorkBuddy Data Off a Full C Drive With History Intact
A full system drive can crash Windows and force a reinstall, so moving app data without losing history or rewriting app configs is a practical escape hatch. The same junction technique applies to any Windows app that hoards large files on C:.
WorkBuddy's data folder on Windows can quietly grow past 10GB, and on a nearly full C drive that is enough to crash the OS. Deleting it wipes the app's history, so the alternative here is a directory junction: an NTFS-level pointer that redirects every read and write from the original path to a target folder on another drive. The application never sees the change, no configuration or database path needs updating, and only one copy of the data exists.
A GUI tool built for the job steps through scanning (after the user exits WorkBuddy to prevent file locks), a dry run, export, migration with progress and logs, verification, rollback, and backup deletion. After migration, the original C drive location drops to 1.25GB while the bulk of the data lives elsewhere. The junction itself occupies only a few hundred bytes, and new logs and snapshots keep growing on the destination drive.
The whole script was generated by WorkBuddy's AI, turning an unfamiliar Windows feature into a working utility in one session. The tool is published on GitHub for anyone facing the same disk-pressure problem.
Directory junctions turn the 'delete history or keep a full drive' dilemma into a redirect that preserves both, and because the app is unaware, rollback only requires removing the junction and restoring files.
The tool's scan, dry-run, verify, rollback, and backup-deletion steps make this a repeatable filesystem migration pattern, not just a one-off fix for one app.
AI removed the need to learn NTFS junction mechanics before writing the tool; the idea and workflow mattered more than the low-level API.
I can simply choose not to install WorkBuddy.
That works. [grin]