Changed
- Use tools4devs for the Windows application identity, publisher, installer registry keys, installation directory, component store and saved preference keys.
- Migrate existing profiles, settings, history and downloaded tools automatically. Keep the original profile and component directories as recovery copies; never overwrite an existing tools4devs profile.
- Retarget existing shortcuts to the new installation and remove the previous app registration after the replacement installer has completed.
- Keep the legacy update channel pinned to the signed 3.4.0 bridge. The tools4devs channel advertises 4.0.0 and future releases.
Fixed
- Stop migration before opening the new profile if data cannot be copied safely. Existing data remains intact, and migration can be retried.
- Preserve the original updater signing key and MSI upgrade family across the identity change.
Downloads
| File | What it is |
|---|---|
tools4devs_4.0.0_x64-setup.exe |
Installer (recommended) |
tools4devs_4.0.0_x64_en-US.msi |
MSI, for managed deployment |
tools4devs_4.0.0_x64-portable.zip |
Portable, unzip and run |
tools4devs.json, latest.json, *.sig |
Needed for automatic updates |
Windows x64 only. SHA-256 checksums are in checksums.txt. The portable build doesn't update itself. SmartScreen warns on first run because the installer isn't code-signed.
If you are on ToolHaven 2.1.0 or later, open the app and use the Restart button after the signed update has downloaded. The update keeps your preferences, history and installed tools.
Older clients first install the signed 3.4.0 bridge, then check the tools4devs channel for this version. latest.json intentionally stays at 3.4.0; tools4devs.json advertises this release. Keep every v3.4.0 asset available and upload both manifests here.