Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Vimalin for Fusion 2.5.487 update
Vimalin for Fusion 2.5.487 update
(or use the Vimalin -> "Check for Updates" menu option)

Please note that the update recommendation is to first uninstall your existing Vimalin application by dragging it to the Trash (or for our English users, drag it to the Bin).
Only after the old Vimalin is uninstalled run the installer to update to Vimalin 2.5.487.

Here's the list of changes since version 2.5.481:

  • VMware Fusion 12.1 support

Added new guest OS support for:
  • Windows Server 2019

General changes
  • For Fusion 12 and 11.5.6 there's a new feature called a sandbox renderer. This creates a new log file for each VM, the mkssandbox.log. The mkssandbox.log should not have its md5 hash calculated on the source when a VM is running as it can still change. As a result the backup will falsely get flagged as not correctly backup. We now calculate the hash on the copy. (Thanks Matt for reporting)
  • On startup Vimalin used to do a "are there any VMs configured" check and stop if no VMs had been detected. This is not helpful if you are configuring Vimalin on a new host where you want to restore VMs as you then have to create a dummy VM first in order to start restoring your VM's. The check has been removed.

Backup Archive
  • Tweaked backup thread to less often trigger a waiting cursor.

Backup Targets
  • On Big Sur the share "/System/Volumes/Update/mnt1" sometimes was offered as a valid backup target. This is a private Big Sur folder, so no longer offering this share.

More information about Vimalin is available at the main website:

Forum Jump:

Users browsing this thread: 1 Guest(s)