earlier update for the topic is from over 1 ago... any updated thoughts and plans to add windows clients to support ARM architecture?
https://learn.microsoft.com/en-us/windows/arm/add-arm-support
Rgs,
-Teemu
earlier update for the topic is from over 1 ago... any updated thoughts and plans to add windows clients to support ARM architecture?
https://learn.microsoft.com/en-us/windows/arm/add-arm-support
Rgs,
-Teemu
If I understand correctly there will be a new Desktop Client in 2025.. I think the current Client won't get arm64 Support, but I could imagine it for the new one..
We've not announced anything on this, but rest assured that your comments have been passed on internally.
Now that Windows 11 has added the support to run unmodified x64 Windows apps on Arm-powered devices (at least according to the Microsoft documentation), I assume that the technical blocker is the kernel-mode driver that M-Files Desktop includes. That would result in exactly the kind of behavior that's seen in the screenshot above, i.e., failing to start the MFClient service because a dependency service (the driver) failed to start.
If you have the opportunity, you could try verifying this assumption by trying to install only the "M-Files Server" and "M-Files Server Tools" components. If the installation of those components succeeds and the M-Files Server service starts without issues, it seems clear that then only the kernel mode driver in M-Files Desktop would be the technical issue.
I can't promise that we would product an Arm-compatible version of the kernel-mode driver any time soon, but we'd be a step closer if we knew that it is likely the only remaining missing part.
Hello, so yes it is possible to install "M-Files Server" and "M-Files Server Tools" (I just tried with the last version of Windows 11 insider preview) but it doesn't work
© 2024 M-Files, All Rights Reserved.