Skip to content

Upgrade to v4.5.2

uyujkk edited this page Oct 28, 2026 · 2 revisions

Install or Upgrade to v4.5.2

Historical page for 4.5.2. To install or upgrade now, see Upgrade to 4.6.0.

中文 · Home · Features and known issues · Download

New Installation

  1. Use Windows 10 1809 or later, x64, with the .NET 8 x64 runtime. The package bundles the Windows App SDK; normal use does not require the SDK or Visual Studio.
  2. Download Integrated_Mod_Manager-v4.5.2.zip and Integrated_Mod_Manager-v4.5.2.zip.sha256, then verify them below.
  3. Fully extract into a new writable folder, keep the directory structure, and run the root IntegratedModManager.exe. Do not copy only the EXE or run inside the ZIP.
  4. Create or select a repository on the Dashboard. Check the Mod storage root, the Mods directory actually read by the loader, deployment mode and optional launcher.

Moving source to src/ does not change the installed layout. Runtime files and user configuration still use the package's WinUI3 directory.

From an Older Stable Release

  1. Close the manager and back up its entire folder. For state presets, also back up the Mod library, target Mods directory and active d3dx_user.ini.
  2. Open the old stable app, check app updates in Settings, and confirm 4.5.2. The 4.5.1 → 4.5.2 updater flow has an isolated upgrade record; check other old-version environments individually.
  3. Alternatively, fully extract the new package separately. With both apps closed, copy old WinUI3/config.ini, WinUI3/beta-shell.json and any needed cache and backups to matching locations, retaining the new binaries. Do not let two managers operate on the same target.
  4. On first start, check paths, deployment mode, character multi-select, presets, parameter file and input settings. An unchanged library path does not require reinstalling the entire Mod library.

Preview and separate 4.0-beta users should use the full stable ZIP. Do not rely on disabled app self-update, or overwrite a real setup with demo repositories or test configuration.

Changes to Check After Upgrading

  • Overlay combination and single-Mod capture: select the game window and manually enable input. 4.5.2 sends F10, waits for a stable loader-file write, then captures. No write within 5 seconds means no save. If sending is unavailable, cancel or explicitly read the existing file.
  • Endfield permissions: input needs an elevated manager; follow the shortcut page's restart prompt. Use the file picker for imports after elevation, since Explorer drag-and-drop may be unavailable.
  • Single or multiple Mods in link mode: one per character by default; enable that character's multi-select before keeping several. Copy mode does not automatically remove other copies for that character.
  • Ordinary restore and hot apply: exit the game and loader for ordinary restore. Restoring slots or snapshots while running uses experimental F10 hot apply and requires an explicit choice. Review and confirm combination restores in the main window.
  • Overlay refresh: successful deployment changes refresh automatically, with a manual Refresh button as well; disabled Mods no longer keep stale bindings.

See 4.5 Combination and State Presets and the shortcut guide.

Verify the Download

In the download directory:

Get-FileHash -LiteralPath .\Integrated_Mod_Manager-v4.5.2.zip -Algorithm SHA256
Get-Content -LiteralPath .\Integrated_Mod_Manager-v4.5.2.zip.sha256

Both hash and filename must match the checksum file. Use this version's checksum, not the separately released Developer Tools checksum.

If upgrading fails, keep the old version, settings and logs, then try a full extraction in a new folder. Do not delete settings to troubleshoot. If the new app has changed configuration, keep that copy before restoring the pre-upgrade backup. Redact private paths and parameter contents before reporting problems.

Release notes · Upgrade verification · Licensing

开始 / Start

使用手册 / Guides

发布记录 / Release Notes

历史页面与实验 / Historical Pages and Experiments

项目 / Project

Clone this wiki locally