<![CDATA[Antwise community forums - Vimalin for VMware Fusion]]>

<![CDATA[Antwise community forums - Vimalin for VMware Fusion]]> https://forums.antwise.com/ Sat, 09 May 2026 12:45:23 +0000 MyBB <![CDATA[SSL email settings crash Vimalin]]> https://forums.antwise.com/showthread.php?tid=215 Wed, 05 Mar 2025 16:21:17 +0100 gmartine]]> https://forums.antwise.com/showthread.php?tid=215

Code:
-------------------------------------

Translated Report (Full Report Below)

-------------------------------------

Process:               Vimalin [42243]

Path:                  /Applications/Vimalin.app/Contents/MacOS/Vimalin

Identifier:            Vimalin

Version:               2.6.599 (2.6.599)

Code Type:             X86-64 (Translated)

Parent Process:        launchd [1]

User ID:               501

Date/Time:             2025-03-05 10:13:06.5037 -0500

OS Version:            macOS 15.3.1 (24D70)

Report Version:        12

Anonymous UUID:        AE6C59D7-33D3-2366-D3C6-56779B183124

Time Awake Since Boot: 1200000 seconds

System Integrity Protection: enabled

Notes:

PC register does not match crashing frame (0x0 vs 0x7FF89599AA84)

Crashed Thread:        0  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_CRASH (SIGABRT)

Exception Codes:       0x0000000000000000, 0x0000000000000000

Termination Reason:    Namespace SIGNAL, Code 6 Abort trap: 6

Terminating Process:   Vimalin [42243]

Application Specific Information:

abort() called

Invalid dylib load. Clients should not load the unversioned libcrypto dylib as it does not have a stable ABI.

]]>

Code:
-------------------------------------

Translated Report (Full Report Below)

-------------------------------------

Process:               Vimalin [42243]

Path:                  /Applications/Vimalin.app/Contents/MacOS/Vimalin

Identifier:            Vimalin

Version:               2.6.599 (2.6.599)

Code Type:             X86-64 (Translated)

Parent Process:        launchd [1]

User ID:               501

Date/Time:             2025-03-05 10:13:06.5037 -0500

OS Version:            macOS 15.3.1 (24D70)

Report Version:        12

Anonymous UUID:        AE6C59D7-33D3-2366-D3C6-56779B183124

Time Awake Since Boot: 1200000 seconds

System Integrity Protection: enabled

Notes:

PC register does not match crashing frame (0x0 vs 0x7FF89599AA84)

Crashed Thread:        0  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_CRASH (SIGABRT)

Exception Codes:       0x0000000000000000, 0x0000000000000000

Termination Reason:    Namespace SIGNAL, Code 6 Abort trap: 6

Terminating Process:   Vimalin [42243]

Application Specific Information:

abort() called

Invalid dylib load. Clients should not load the unversioned libcrypto dylib as it does not have a stable ABI.

]]> <![CDATA[Crashing when testing email server]]> https://forums.antwise.com/showthread.php?tid=214 Tue, 25 Feb 2025 15:50:49 +0100 nickh1011]]> https://forums.antwise.com/showthread.php?tid=214
Mac Studio is running Sonoma 14.7.4, MacBook pro is running Sonoma 14.4.1

On both machines when I configure and try to test the email settings the application crashes and quits.

From what I can see the backup jobs are running correctly, but I receive no email notification of job success and can't test my email server settings are correct due to the repeatable crash.

VMWare Fusion is v13.6.2 in both cases.

Apple crash report states:

PC register does not match crashing frame (0x0 vs 0x7FF8A2602A78)

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000

Termination Reason: Namespace SIGNAL, Code 6 Abort trap: 6
Terminating Process: Vimalin [2861]

Application Specific Information:
Invalid dylib load. Clients should not load the unversioned libcrypto dylib as it does not have a stable ABI.
abort() called

Error Formulating Crash Report:
PC register does not match crashing frame (0x0 vs 0x7FF8A2602A78)

Any thoughts?

Thanks]]>
Mac Studio is running Sonoma 14.7.4, MacBook pro is running Sonoma 14.4.1

On both machines when I configure and try to test the email settings the application crashes and quits.

From what I can see the backup jobs are running correctly, but I receive no email notification of job success and can't test my email server settings are correct due to the repeatable crash.

VMWare Fusion is v13.6.2 in both cases.

Apple crash report states:

PC register does not match crashing frame (0x0 vs 0x7FF8A2602A78)

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000

Termination Reason: Namespace SIGNAL, Code 6 Abort trap: 6
Terminating Process: Vimalin [2861]

Application Specific Information:
Invalid dylib load. Clients should not load the unversioned libcrypto dylib as it does not have a stable ABI.
abort() called

Error Formulating Crash Report:
PC register does not match crashing frame (0x0 vs 0x7FF8A2602A78)

Any thoughts?

Thanks]]> <![CDATA[Vimalin stopped working after upgrading to Sonoma]]> https://forums.antwise.com/showthread.php?tid=173 Thu, 02 Nov 2023 22:02:33 +0100 wila]]> https://forums.antwise.com/showthread.php?tid=173 He upgraded and somewhere along the way Vimalin stopped working and taking backups.

One of those things that changed is that apple shows you details about processes running in the background.
By default processes that ran in the background on earlier macOS versions, continue to do so, but when apple asks you if you want to continue running processes in the background, it doesn't mention the application, instead it mentions whatever is on the certificate that the application was signed with.
This is a bit confusing as macOS asks you somewhere if you want to allow a guy named “Wil van Antwerpen” to run things in the background.
Not weird to say “No thanks” as who knows what that fellow is up to...

It would have been much better if macOS would have said can “Vimalin” run in the background, as that’s much more clear. Sadly there is no way for me to change that (it is the choice of apple to use the name of the developer instead of product name, only big companies can get it for their product name, not a small shop)

To verify that the vimalinWorker process can run in the background please follow these steps:

In the apple menu go to -> System Settings -> General -> Login Items
see screenshot:

.png

Sonoma-login-items.png (Size: 74.7 KB / Downloads: 5)

It should have the item "Wil van Antwerpen" enabled or else Vimalin will not work.

Hope this helps
--
Wil]]> He upgraded and somewhere along the way Vimalin stopped working and taking backups.

One of those things that changed is that apple shows you details about processes running in the background.
By default processes that ran in the background on earlier macOS versions, continue to do so, but when apple asks you if you want to continue running processes in the background, it doesn't mention the application, instead it mentions whatever is on the certificate that the application was signed with.
This is a bit confusing as macOS asks you somewhere if you want to allow a guy named “Wil van Antwerpen” to run things in the background.
Not weird to say “No thanks” as who knows what that fellow is up to...

It would have been much better if macOS would have said can “Vimalin” run in the background, as that’s much more clear. Sadly there is no way for me to change that (it is the choice of apple to use the name of the developer instead of product name, only big companies can get it for their product name, not a small shop)

To verify that the vimalinWorker process can run in the background please follow these steps:

In the apple menu go to -> System Settings -> General -> Login Items
see screenshot:

.png

Sonoma-login-items.png (Size: 74.7 KB / Downloads: 5)

It should have the item "Wil van Antwerpen" enabled or else Vimalin will not work.

Hope this helps
--
Wil]]> <![CDATA[Vimalin and macOS Sonoma [Fixed]]]> https://forums.antwise.com/showthread.php?tid=166 Wed, 27 Sep 2023 21:48:06 +0200 wila]]> https://forums.antwise.com/showthread.php?tid=166
If you upgrade to macOS Sonoma then Vimalin currently does not work.

The screen layout is .. weird. This appears to be due to a bug in our development framework, but .. who knows.
It's pretty much unexpected.

We are trying to track down what's happening. As far as I can see there are more problems, so for now I would suggest to hold off upgrading to Sonoma for a bit.

I'm looking into this and hope to have better news soon(ish).
--
Wil]]>
If you upgrade to macOS Sonoma then Vimalin currently does not work.

The screen layout is .. weird. This appears to be due to a bug in our development framework, but .. who knows.
It's pretty much unexpected.

We are trying to track down what's happening. As far as I can see there are more problems, so for now I would suggest to hold off upgrading to Sonoma for a bit.

I'm looking into this and hope to have better news soon(ish).
--
Wil]]> <![CDATA[Disk outside current bundle, any work around?]]> https://forums.antwise.com/showthread.php?tid=132 Mon, 22 Aug 2022 14:35:18 +0200 Jupeman]]> https://forums.antwise.com/showthread.php?tid=132
Over the weekend I had to add disk capacity to one of my VMs. I added a second disk on a separate drive. Now my backups for this VM fail with "VM has a disk outside of the current bundle, unable to backup." What are my options to fix this, if any? I'd actually be happy if Vimalin kept backing up what is on "disk 1" because that contains the OS and apps, etc. The disk I added was for storage, primarily. Is there a way to "stick to bundle"? Out of curiosity, what's the limitation with having virtual disks across several physical disks? Is there a way I should have done this that would work with Vimalin?

Thanks!]]>
Over the weekend I had to add disk capacity to one of my VMs. I added a second disk on a separate drive. Now my backups for this VM fail with "VM has a disk outside of the current bundle, unable to backup." What are my options to fix this, if any? I'd actually be happy if Vimalin kept backing up what is on "disk 1" because that contains the OS and apps, etc. The disk I added was for storage, primarily. Is there a way to "stick to bundle"? Out of curiosity, what's the limitation with having virtual disks across several physical disks? Is there a way I should have done this that would work with Vimalin?

Thanks!]]> <![CDATA[restore permissions]]> https://forums.antwise.com/showthread.php?tid=131 Thu, 18 Aug 2022 03:18:04 +0200 kgp06]]> https://forums.antwise.com/showthread.php?tid=131
When Fusion tries to start the virtual machine, it says it cannot find "Virtual Disk.vmdk", but when I hit the Browse button, that file is in the list of displayed file names. Choosing it there, the next thing is "Error while replacing a missing file: Insufficient permission to access the file."

I'm not sure if the renaming is the source of this problem or if there are some missing macOS permissions? I did give "full Disk Access" to the Vimalin app and the VimalinWorker process. The backup and restore operations in Vimalin do not show any error in the logs. But the net effect is the restored virtual guest will not start. Thanks in advance for any suggestion.

Vimalin ver 2.6.560
Fusion ver 12.2.4
macOS ver 12.5]]>
When Fusion tries to start the virtual machine, it says it cannot find "Virtual Disk.vmdk", but when I hit the Browse button, that file is in the list of displayed file names. Choosing it there, the next thing is "Error while replacing a missing file: Insufficient permission to access the file."

I'm not sure if the renaming is the source of this problem or if there are some missing macOS permissions? I did give "full Disk Access" to the Vimalin app and the VimalinWorker process. The backup and restore operations in Vimalin do not show any error in the logs. But the net effect is the restored virtual guest will not start. Thanks in advance for any suggestion.

Vimalin ver 2.6.560
Fusion ver 12.2.4
macOS ver 12.5]]> <![CDATA[Vimalin stuck on "Started"]]> https://forums.antwise.com/showthread.php?tid=86 Fri, 19 Nov 2021 13:18:24 +0100 wila]]> https://forums.antwise.com/showthread.php?tid=86
It seems that on some updates, the vimalinWorker process gets unchecked in the security preferences pane.

In order to verify that and fix it, the following steps might help:
- macOS apple icon
- select System Preferences
- Security & Privacy
- Go to the Privacy tab
- On the left hand locate "Full Disk Access" and select it
- Make sure that vimalinWorker is checked

Normally that's it.
However if vimalinWorker was already checked then you should select vimalinWorker and then click on “-“ button to remove it from the list.

As you just removed vimalinWorker from the list.. it’s a bit harder to add it back.
There are two ways:
- (the difficult way) either via drag & drop on Finder (but then you have to navigate into the Vimalin / Contents / Library bundle) or
- (the more easy way) by going back to Vimalin and launch another fruitless backup.. this then puts vimalinWorker back in the privacy tab and now you can select it and enable Full Disk Access for vimalinWorker.

Note that if vimalin doesn’t show a new line when you try to add another backup that the process might be hung and then you need to kill vimalinWorker in the activity monitor and try the steps above again.

Hope this helps and really sorry for all the trouble.

--
Wil]]>
It seems that on some updates, the vimalinWorker process gets unchecked in the security preferences pane.

In order to verify that and fix it, the following steps might help:
- macOS apple icon
- select System Preferences
- Security & Privacy
- Go to the Privacy tab
- On the left hand locate "Full Disk Access" and select it
- Make sure that vimalinWorker is checked

Normally that's it.
However if vimalinWorker was already checked then you should select vimalinWorker and then click on “-“ button to remove it from the list.

As you just removed vimalinWorker from the list.. it’s a bit harder to add it back.
There are two ways:
- (the difficult way) either via drag & drop on Finder (but then you have to navigate into the Vimalin / Contents / Library bundle) or
- (the more easy way) by going back to Vimalin and launch another fruitless backup.. this then puts vimalinWorker back in the privacy tab and now you can select it and enable Full Disk Access for vimalinWorker.

Note that if vimalin doesn’t show a new line when you try to add another backup that the process might be hung and then you need to kill vimalinWorker in the activity monitor and try the steps above again.

Hope this helps and really sorry for all the trouble.

--
Wil]]> <![CDATA[Experimental vTPM feature and Vimalin for Fusion]]> https://forums.antwise.com/showthread.php?tid=81 Thu, 28 Oct 2021 14:36:27 +0200 wila]]> https://forums.antwise.com/showthread.php?tid=81 It is called the Experimental vTPM feature (I wrote a more indepth article about it here)

Sadly this feature is not compatible with Vimalin.
If you added this to a VM then you can no longer make backups of that specific VM with Vimalin while the VM is running.
You can still make backups of that virtual machine with the VM shut down.

The reason for this is that the VMware automation programming interface that Vimalin uses thinks the VM is encrypted, but there is no password.
As such the automation interface cannot make or remove any snapshots while the VM is active.
I have contacted VMware about this.
Last night they informed me that "it currently works as designed" and that we will have to wait for this to be resolved at their end.]]> It is called the Experimental vTPM feature (I wrote a more indepth article about it here)

Sadly this feature is not compatible with Vimalin.
If you added this to a VM then you can no longer make backups of that specific VM with Vimalin while the VM is running.
You can still make backups of that virtual machine with the VM shut down.

The reason for this is that the VMware automation programming interface that Vimalin uses thinks the VM is encrypted, but there is no password.
As such the automation interface cannot make or remove any snapshots while the VM is active.
I have contacted VMware about this.
Last night they informed me that "it currently works as designed" and that we will have to wait for this to be resolved at their end.]]> <![CDATA[Important: macOS security update breaks Vimalin functionality]]> https://forums.antwise.com/showthread.php?tid=68 Tue, 25 May 2021 23:08:54 +0200 wila]]> https://forums.antwise.com/showthread.php?tid=68
We're still investigating this, but so far we have been able to work with a customer and have determined the following:
- No longer able to make backups, errors such as "cannot create the new files and/or directories on the target external drive"
- No longer able to delete existing backups, the delete fails on the first file it tries to delete.

Probably more issues besides this..

What so far appears to have happened is that apple has tightened some security rules.

Vimalin exists of a few parts, there's a foreground application that lets you configure the backups and lets you manage those.
Another important part is the "worker" process that runs in the background and actually takes care of everything you tell Vimalin to do.

Before the macOS update it was sufficient to just allow "Full Disk Access" to the foreground application.
Because the worker process is part of the bundle, it used to also get Full Disk Access as well.
Now you also have to explicitly assign "Full Disk Access" to the worker process for it to be able to read/write to an external disk.

Eg. go to Apple menu -> System Preferences -> Security & Privacy -> Scroll down to "Full Disk Access" in the left bar and add "vimalinWorker" to the applications allowed there as well. Make sure that the checkbox there is set.

After doing that you should be able to use Vimalin again as normal.

More details will follow later.

edit: fixed a typo where I said it was VMware changing the rules, no it is not, it is apple.

edit 2: This also happens on Catalina as well as on Monterey

--
Wil]]>
We're still investigating this, but so far we have been able to work with a customer and have determined the following:
- No longer able to make backups, errors such as "cannot create the new files and/or directories on the target external drive"
- No longer able to delete existing backups, the delete fails on the first file it tries to delete.

Probably more issues besides this..

What so far appears to have happened is that apple has tightened some security rules.

Vimalin exists of a few parts, there's a foreground application that lets you configure the backups and lets you manage those.
Another important part is the "worker" process that runs in the background and actually takes care of everything you tell Vimalin to do.

Before the macOS update it was sufficient to just allow "Full Disk Access" to the foreground application.
Because the worker process is part of the bundle, it used to also get Full Disk Access as well.
Now you also have to explicitly assign "Full Disk Access" to the worker process for it to be able to read/write to an external disk.

Eg. go to Apple menu -> System Preferences -> Security & Privacy -> Scroll down to "Full Disk Access" in the left bar and add "vimalinWorker" to the applications allowed there as well. Make sure that the checkbox there is set.

After doing that you should be able to use Vimalin again as normal.

More details will follow later.

edit: fixed a typo where I said it was VMware changing the rules, no it is not, it is apple.

edit 2: This also happens on Catalina as well as on Monterey

--
Wil]]> <![CDATA[The service to manage your backup has not been installed]]> https://forums.antwise.com/showthread.php?tid=63 Thu, 04 Feb 2021 18:55:35 +0100 nickr54]]> https://forums.antwise.com/showthread.php?tid=63 <![CDATA[Backups often fail]]> https://forums.antwise.com/showthread.php?tid=57 Tue, 19 Jan 2021 01:40:45 +0100 AKLima]]> https://forums.antwise.com/showthread.php?tid=57
Looking for suggestions. Out of the last 15 backup attempts, 11 failed. Setup is Macbook running OS X 10.15.7 Catalina. Backing up to a QNAP NAS through a gigabit ethernet switch. One possibility: my lovely wife's iMac backs up to the QNAP using TimeMachine. No, I didn't point Vimalin at the TimeMachine partition. Is it possible that there are collisions between Vimalin and TimeMachine?

Please be gentle with me. I love this product but am still something of a rookie with Fusion and its intricacies.

Best,
Tony Lima

[Image: test.png]

]]>
Looking for suggestions. Out of the last 15 backup attempts, 11 failed. Setup is Macbook running OS X 10.15.7 Catalina. Backing up to a QNAP NAS through a gigabit ethernet switch. One possibility: my lovely wife's iMac backs up to the QNAP using TimeMachine. No, I didn't point Vimalin at the TimeMachine partition. Is it possible that there are collisions between Vimalin and TimeMachine?

Please be gentle with me. I love this product but am still something of a rookie with Fusion and its intricacies.

Best,
Tony Lima

[Image: test.png]

]]> <![CDATA[Cannot restore backups to new installation of Vimalin]]> https://forums.antwise.com/showthread.php?tid=43 Mon, 03 Aug 2020 05:55:57 +0200 Jupeman]]> https://forums.antwise.com/showthread.php?tid=43 <![CDATA[Backup of Linked Clone]]> https://forums.antwise.com/showthread.php?tid=42 Fri, 10 Jul 2020 11:11:17 +0200 crazypush]]> https://forums.antwise.com/showthread.php?tid=42 I'd like to know if backup of running Linked Clone is also supported ?
I can easily understand that the main VM also need to be backup for restore process to work correctly.
Main VM is always off, just Linked Clone are running.
Thanks
BR
CrazyPush]]> I'd like to know if backup of running Linked Clone is also supported ?
I can easily understand that the main VM also need to be backup for restore process to work correctly.
Main VM is always off, just Linked Clone are running.
Thanks
BR
CrazyPush]]> <![CDATA[Error on restore]]> https://forums.antwise.com/showthread.php?tid=37 Mon, 24 Feb 2020 19:24:23 +0100 mikemccloskey]]> https://forums.antwise.com/showthread.php?tid=37
VMWare Fusion 10.1.6
VM Size is 365GB (i know it is big)

TIA]]>
VMWare Fusion 10.1.6
VM Size is 365GB (i know it is big)

TIA]]> <![CDATA[Can't get backups to run]]> https://forums.antwise.com/showthread.php?tid=34 Mon, 23 Dec 2019 13:31:00 +0100 jcbeckman]]> https://forums.antwise.com/showthread.php?tid=34
Just installed Vimalin on Mac OS 10.15.2 for the firs time. Set everything up, but the backups would not run because I had auto snapshots enabled. Turned off snapshots and let it clean them all up. Now when I try a manual backup, it takes me to the the Archives screen and shows me the two failed attempts, but I never see any sort of evidence that any backup I attempt is started. I also tried VMs that had never had snapshots and all it does is take me to the Archive screen. Log only shows the two failed attempts, nothing else. I have tried sending Vimalin away a couple of times as well. Do I need to do something else to get this started?]]>
Just installed Vimalin on Mac OS 10.15.2 for the firs time. Set everything up, but the backups would not run because I had auto snapshots enabled. Turned off snapshots and let it clean them all up. Now when I try a manual backup, it takes me to the the Archives screen and shows me the two failed attempts, but I never see any sort of evidence that any backup I attempt is started. I also tried VMs that had never had snapshots and all it does is take me to the Archive screen. Log only shows the two failed attempts, nothing else. I have tried sending Vimalin away a couple of times as well. Do I need to do something else to get this started?]]>