Skip to content

WuMgr v1.2.0

Choose a tag to compare

@github-actions github-actions released this 26 May 20:37
· 48 commits to master since this release

WuMgr v1.2.0

This is the first maintenance release from the public Darkaxt/wumgr fork of DavidXanatos/wumgr.

Changes

  • Added maintained-fork docs, SECURITY.md, build docs, option docs, and release packaging.
  • Added GitHub Actions workflows for Windows build/test, CodeQL, and release packaging.
  • Applied the PR DavidXanatos#114 Unicode INI fix consistently to read and write calls.
  • Added a clean Visual Studio .gitignore and removed the tracked .csproj.user file from PR #48 scope.
  • Cherry-picked safe typo cleanups from PR DavidXanatos#75 without importing its compile error.
  • Reimplemented the PR #20 notification improvement by including pending update titles in the tray balloon text.
  • Added focused regression tests for manual download planning.

Fixes

  • Fixes issue DavidXanatos#145 class behavior: selected updates without usable download URLs now fail instead of reporting success.
  • Manual install no longer starts when any selected update was skipped or any manual download failed.
  • Cached update entries can re-resolve their live Windows Update object by UUID before install/hide operations, addressing stale-list behavior around issue DavidXanatos#117.
  • Log output now has a copy context menu for issue DavidXanatos#146.
  • Window size/position and update-list column widths are saved and restored for issues #5 and DavidXanatos#142.
  • Translation.ini is now tracked and included in the portable zip for translation/release packaging issues DavidXanatos#90 and DavidXanatos#135.

Assets

  • WuMgr_v1.2.0.zip: portable release zip.
  • SHA256SUMS.txt: SHA256 checksums for the zip and packaged files.

Known limitations

  • Binaries are unsigned in this release.
  • Skip UAC remains a powerful local-administrator convenience feature; disable it if not needed.
  • Tools.ini command hooks intentionally execute local user-configured commands from the application directory.
  • Code/security scanning workflows are present; repository-level security scanning settings still need to be enabled in GitHub settings.