Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Vimalin for Windows 2.5.481 update, adding support for VMware Player!!
Vimalin for Windows 2.5.481 update

You can download the update for Vimalin from:
(or use the Vimalin -> "Check for Updates" menu option)

How-to update
First uninstall the old version from the Add/Remove programs or in Windows 10 the Settings -> Apps & Features screen. If you keep defaults you are fine and nothing changes.
Only after the old Vimalin is uninstalled run the installer to update to Vimalin 2.5

Here's the list of changes since version 2.5.474:

  • Vimalin now also supports VMware Player 16.0 and newer. This wasn't possible with earlier versions. Thanks to changes made by VMware this is now also possible. A huge thanks to the VMware Workstation team for making this easy to support.
  • VMware Workstation 16.0 support

General changes
  • Trying to use Vimalin immediately after install was problematic as the worker process could end up hanged waiting for the database to get installed. As such it would not work until after a reboot. The worker process now properly respawns itself after a missing database initialisation as was designed.
  • The new resize logic caused the application to start in the top left of the screen instead of in the middle. This has been fixed.
  • If the backup process gets interrupted, for example by a reboot of the host, then a backup snapshot might not be removed. When trying to run a new backup this would then result in a slightly confusing error 'Failed it already has a backup snapshot'. If this problem happens now then Vimalin will first try to automatically remove that old backup snapshot and continue with the backup if that was successful.
  • If the worker could not connect to a network drive then it would not register the backup. This is now properly saved and handled in the backup archive.

Backup Archive:
  • When a job gets scheduled it now changes the status for that archive immediately to "queued". That way the user knows that their action was registered by Vimalin.
  • There was a timing issue with jobs that completed before the screen was updated and as a result some jobs would never display on the backup archive as being busy processing. The timing logic has been tweaked a bit so that it would be much harder for this to happen.

More information about Vimalin is available at the main website:

Forum Jump:

Users browsing this thread: 1 Guest(s)