Problems with Excel loading spreadsheets and add-ins

[Dazzathedrummer]

Hi,

I use a MacBook Pro for work and we use Citrix to provide a Windows environment but I have an exam coming up and I don't want to log in to the work environment to run Excel.

The Mac version of Excel doesn't have all the feature that I use so I'm experimenting with VM/Parallels in order to get a stable version of Windows Excel 365 running on my Mac.

So far VM has been great, I'm running W11 Home but I've found that Excel has trouble loading files from the Mac and it will not load VBA editor or install a ]n Add In without crashing.

I'm also finding I get black boxes appear on the spreadsheet after using it for a while - the black boxes disappear if I select over them.

It's a 2020 MacBook Pro M1 with 16GB Ram - I've got VM set to use 10GB ram and all other VM setting are default.

Any advice would be great!

Also, just as an aside, is it true that there is no Unity or multi screen support for Arm Macs?

[Technogeezer]

What version of Fusion, and what build of Windows 11 ARM, and what version of Excel are you running.

I'm running Fusion 2023 Tech Preview on a M1 Mac mini, Windows 11 ARM 22621.2283, and Excel for Microsoft 365 MSO (Version 2308 Build 16.0.16731.20182) 64-bit. I'm able to load the VBA editor without crashing. I can't say that the black boxes are appearing, but I haven't worked on a spreadsheet for any extended length of time.

As far as Unity goes, it is not available in Fusion for Windows 11 ARM, and from what I understand is likely not to appear in the next official release of Fusion later this fall.  I haven't seen anyone that's been able to get multiple monitor support to work acceptably on Fusion 13 on M1 Macs. 

[Dazzathedrummer]

Thanks for your reply. 

I did the sensible thing and uninstalled Office and re-installed it and seems to be working fine now - in fact it seems to be running a bit quicker!

[Technogeezer]

Glad you were able to get it to run.

I had a feeling you may have been running an older version of Office. If it’s running more quickly, you might have had one that was not optimized for ARM.