Arm64 Office

[Melvina Kryder]

HiI have extensively searched for an answer to this but cannot find a single reference to it so, LibreOffice for windows arm64. Does it exist, is it on a roadmap? Are there any obvious impediments to me compiling it myself?

If I took it on I would definitely be looking to cross compile X86 to Arm64. Even for basic web app development VS chugs on my surface pro x, it would be an exercise in frustration to emulate all those tools in 32bit.

I run Office on a Windows Arm64 PC. All of the office apps except Access run as Arm64 (x64 compatible) apps. Access runs under the x64 emulation, and suffers a performance penalty as a result. I have several Access projects with over 50,000 lines of VBA code. I request that you update Access as you did the other Office apps.

I was able to make this work end to end with STM32CubeProgrammer and IAR on Windows 11 ARM64 (running in Parallels on an Apple M1). To make that work, I have removed all references to the certificate signatures (CAT files) from INF files.

To install, you need to temporarily disable driver checks: -to-fix-the-third-party-inf-doesnt-contain-digital-signature-information/ (use the temporary solution 3 - Reset while holding Shift). After rebooting with driver signature checks, go to Device Manager, find the STLink device and manually specify the folder where you've unzipped the file attached below.

I made the modifications and because the inf changed Windows fails to install the driver (tampering). Because the driver is signed and the signature changed, I don't know of a simple way to disable the check. This means there is no viable workaround for now for all Windows ARM64 users.

The changes I've made cannot work (for security reasons as the driver package is signed). The changes are following driver documentation from Microsoft here: -us/windows-hardware/drivers/install/inf-controlflags-section

I have attached only the INF files from the STLink driver. These have been changed from NTamd64 to NTarm64. The correct fix is to add another arm64 section (i.e. wherever amd64 is used, add something similar for arm64).

A few years ago I ported Takua Renderer to build and run on arm64 systems.Porting to arm64 proved to be a major effort (see Parts 1, 2, 3, and 4) which wound up paying off in spades; I learned a lot, found and fixed various longstanding platform-specific bugs in the renderer, and wound up being perfectly timed for Apple transitioning the Mac to arm64-based Apple Silicon.As a result, for the past few years I have been routinely building and running Takua Renderer on arm64 Linux and macOS, in addition to building and runninng on x86-64 Linux/Mac/Windows.Even though I take somewhat of a Mac-first approach for personal projects since I daily drive macOS, I make a point of maintaining robust cross-platform support for Takua Renderer for reasons I wrote about in the first part of this series.

Note that everything in this post uses arm64 Windows 11 Pro 23H2 and Visual Studio 2022 17.10.x.Noting the specific versions used here is important since Microsoft is still actively fleshing out arm64 support in Windows 11 and Visual Studio 2022; later versions will likely see improvements to problems discussed in this post.

The current system for emulating x86 and x86-64 on arm64 Windows is a fairly complex system that differs greatly from Rosetta 2 in a lot of ways.First, arm64 Windows 11 supports emulating both 32-bit x86 and 64-bit x86-64, whereas macOS dropped any kind of 32-bit support long ago and only needs to support 64-bit x86-64 on 64-bit arm64.Windows actually handles 32-bit x86 and 64-bit x86-64 through two basically completely different systems.32-bit x86 is handled through an extension of the WoW64 (Windows 32-bit on Windows 64-bit) system, while 64-bit x86-64 uses a different system.The 32-bit system uses a JIT compiler called xtajit.dll [Radich et al. 2020, Beneš 2018] to translate blocks of x86 assembly to arm64 assembly and has a caching mechanism for JITed code blocks similar to Rosetta 2 to speed up execution of x86 code that has already been run through the emulation system before [Cylance Research Team 2019].In the 32-bit system, overall support for providing system calls and whatnot are handled as part of the larger WoW64 system.

Below are some numbers comparing running Takua on arm64 Windows 11 as a native arm64 application versus as an emulated x86-64 application.The tests used are the same as the ones I used in my Rosetta 2 tests, with the same settings as before.In this case though, because this was all running in a virtual machine (with 6 allocated cores) instead of directly on hardware, the absolute numbers are not as important as the relative difference between native and emulated modes:

Learn more about running Windows on PCs powered by Arm processors. Find guidance on how to build Windows apps for Arm64 devices or iteratively update your existing Windows app to take advantage of Arm64 native capabilities.

I am just guessing, since I am not an employee of Docker Inc, but I know that Docker Inc and Microsoft worked together to make Windows containers possible, so there must be a reason why they could not make Docker Desktop available for Windows with ARM CPU.

Hi, Arm lent us a Windows 10 machine a while back and I did a little testing. Docker runs fine on Arm64 WSL2 if you install it yourself (via ), which is great, once you have updated to a Windows version that supports WSL2.

Building Docker Desktop has a bunch of issues around software we use and available toolchains, and as you say lack of emulation for 32 bit x86. This situation should get better over time as the Windows arm64 ecosystem gets better and we update some dependencies. If other people are interested please let us know.

We now officially announce the availability of CODE for the ARM64 platform. Users can now benefit from the availability of the latest developments in document collaboration with a feature rich open-source application, offering great support for all major file formats. The availability for the ARM64 platform is possible thanks to the work for the recently announced Collabora Online for the Raspberry Pi.

CODE is the Collabora Online Development Edition. It contains the latest developments and is perfect for home users. It enables them to regain control of their own online documents and to host them themselves in a secure and private environment. For tech-enthusiasts, it is a low-threshold way to get involved and familiar with our online office solution. CODE will be improved continuously and our next supported and maintained Collabora Online product will be built from it. All of our code is Open Source, and a vibrant community in participating in growing Collabora Online. Would you like to be part of the story? Join the community!

Don't know if the issue is specific to the Arm processor or whether the 32-bit Office version does not play nicely with the store version of iCloud (could try downloading an older version of iCloud for Windows and try that, though)

I understand from your post that you have not been able to set up your mail client with iCloud for Windows on your Surface Pro X. According to this Microsoft document you may only be able to sync your photos, contacts, and bookmarks at this time:

iCloud works fine on my other Surface devices. From your text above one correction is that you can only sync bookmarks an Photos without the iCloud to Outlook connector service installed, not Mail, Calendar or Contacts

I've got the Surface Pro X as well and the same problem. I've factory reset and reinstalled and get the same error message on Outlook as you. That was an incredibly dumb response from Apple? They must think we are all idiots and don't search forums or help sites????

I have spent hours on the phone with Microsoft to see if it's windows, Office365 or something else related. I and Microsoft have re-installed windows and then SPX image about 4 times, manual and automated uninstalls of iCloud for Windows etc etc. They have even taken log files an analysed that. Microsoft admitted there is nothing more they can do currently as it's clear it's iCloud for windows incompatibility with the SPX and Arm processor.

It is also clear to me that some responses I got from Microsoft and even the Apple MVP's was they they did not know that you cannot just download the 64-bit iCloud from the Apple web site... it will not install.

In the interim, I have set up my iCloud account on the SPX using the in-built Microsoft mail app and it works fine (mail, calendar, contacts etc). I love the SPXZ for work related tasks (90% Microsoft products and I can work whole day until around 4PM with about 21% battery remaining. Even run 2 x 28" 4K monitors (one through Surface Dock and one via USB-C)

3. If you go to the Control Panel, Can you seethe Mail 32 bit icon and if you click on it does it open the Outlook Profiles? I know you can get to the profiles via the RUN (Outlook /Profiles) command. Microsoft are trying to resolve why the Mail32 icon under control panel is not working... It may/may not have anything to do with iCloud for Windows not working so I want to see if others have the same issue. The Mail icon not doing anything is only a problem on the Surface Pro X not my other Microsoft devices.

1) Go to Control Panel (Type Control Panel in the search box at the bottom left of your screen). Click on the MAIL (Microsoft Outlook 2016 (32 bit) icon.. Does it open the profiles or just briefly show the hourglass window and then do nothing

3a8082e126