2026-10-08, 06:58:09
Hi,
Strange. It would not expect it to be due to Windows 11 update breaking things as then it wouldn't only involve Vimalin.
Not seeing this reported by other developers using the same development environment.
Although this was working for you in the past, so it is unclear to me as to what has changed?
No need to use RunAs administrator. Vimalin should be installed using the same user that also runs VMware Workstation.
Installing as another user might even cause problems (although I think that I got that covered now).
Workstation versions should not matter and I also fail to see how the vCenter Converter would interfere with the GUI of Vimalin.
Let's proceed by email and see if we can figure this out.
Strange. It would not expect it to be due to Windows 11 update breaking things as then it wouldn't only involve Vimalin.
Not seeing this reported by other developers using the same development environment.
Although this was working for you in the past, so it is unclear to me as to what has changed?
No need to use RunAs administrator. Vimalin should be installed using the same user that also runs VMware Workstation.
Installing as another user might even cause problems (although I think that I got that covered now).
Workstation versions should not matter and I also fail to see how the vCenter Converter would interfere with the GUI of Vimalin.
Let's proceed by email and see if we can figure this out.