FortiClient on Mac ARM with Windows 11 in parallels VM

Same issue

When is this coming out?!

Problem Solved for Windows 11, download the client, from the microsoft store.  After the install, navigate to Network/VPN -> Add VPN -> choose Fortinet, enter your config settings.  worked perfectly on my side.  Lenovo Thinkpad 13s

Still not working. The install stops about 75% of the way, then rolls back and says the install was stopped "prematurely". The work-around, if that's what you want to call it, is to install the VPN for Mac. Once connected, the Windows VM can connect through the VPN running on the Mac side.

Unfortunately, the Microsoft Store app does not work properly when some details are used as a different port.

So, It is still not working.

I have a W11 ARM VM on VMware Fusion w/ FortiClient installed on a Mac Air M1, works just fine.

I am using FortiClient v1.0.1041 in a Virtual PC (via Parallels Desktop) on a Mac with M1 processor.

The structure of the M1 processor means that Windows 11 can only be used as an ARM version. In this Windows, the FortiClient can only be loaded from Windows Store.

It must be said that the Virtual PC is considered subordinate in the network (due to technical reasons) and therefore FortiClient cannot be accessed from MacOS in Windows active.

Some applications go more elegantly on Windows (SAP for example) and for some applications it does not matter. Therefore, for such cases I have installed FortClient 7.0.7.0245 for Mac OS. If this is active, both OS (Mac OS and Windows OS) can access the VPN.

The disadvantage of the Mac version is that since version 7 the config is encrypted and therefore you can not set that the password can be saved.

The disadvantage of the Windows ARM version is, it deactivates itself in sleep mode, select params in the advanced settings make sense, and it must be selected whether the VPN is used in private / public networks.

For the Windows ARM version, the traditional client is not available in the console, but the Windows system settings can be used, where you can let off steam.

See screenshots

.App in Windows StoreApp GUI

Add a ConnectionSettings of a ConnectionExt. Settings of a ConnectionEdit of a ConnectionMac Fortinet Console

Good morning,

My dear, do you know any Solutions for this issue, I just have the same problem.
I appreciate any help or comment.

Thank you!

2023 and still no Arm64 Windows Zero Trust FortiClient.   If you landed here, like me and are frustrated that these solutions don't quite fit your use case.  I might have another solution for you. 

First - the Microsoft Store version of Forticlient can work but it can also be pretty finicky. It often put me in a reboot loop on startup trying to apply new drivers. The other problem is that the Windows Store version of the headless Forticlient driver-thing doesn't support ipsec -or- SSO-enforced SSL vpn connections. So, if your employer forces SSO on the VPN (which seems reasonable, especially to get MFA) then you can't connect anymore b/c that version doesn't have support for that feature.

Another workaround is this:

Install the VPN Client on your Host Mac.  (FortiClient for Mac does work on M-series processors) Swich parallels to shared network.

When you Establish your VPN connection Parallels will share the vpn routes to your Windows VM.

"But Shared networking in parallels isolates my Windows instance from the rest of the network", you might say.     Yes, straw man, yes it does.  But, if you need to access resources from the Windows Parallels VM, enable port forwarding for those services in the advanced networking features of the network config in parallels for that virtual NIC.

In my case, for instance, I RDP into the parallels VM routinely from a nicer machine because my employer provides terrible / cheap hardware that makes me die a little inside everytime I turn it on.  Enable port forwarding from host port 3389 to Your-Windows-VM port 3389 and then RDP into your Mac's IP address and it gets forwarded to the VM.  VOILA - you can almost forget about the employers' crappy hardware and Fortinet's insanely slow roll out of Arm64 Windows support.

Same issue, after more than 2 years, are there any updates on this issue?