Font issue with MS Office 16.77.1 (365)

I use Bauhaus93 for my company logo in MS Word header & MS Excel text boxes (invoices/ statement of works/ timesheet/ etc).

I noticed that when I created recent invoices at the end of Sept, the font was not displaying correctly.

Weirdly the font displays correctly in MS Excel cells but not the text box.


I've had a read of some existing posts, understand that it's part of the Office install and not a native Mac font and have tried the following:

1)cleared font cache using "sudo atsutil databases -remove" & rebooted

2)removed MS Word/ MS Powerpoint app and re-installed - no change. I didn't do the full uninstall of clearing Library etc (yet)

3)started in safe mode - same issue

4)tried downloading a new font package and importing into FontBooks but made no difference so removed it. Minor validation issue with kern table structure

5)expanded the MS Word app package contents : \contents\resources\dfonts - font is there and can be opened in FontBook. Minor validation issue with kern table structure

6)copied that font out of DFonts into \Library\Fonts and Users\[user]\Library\Fonts


None of which seemed to made any difference and I'm not sure what to do next other than the complete uninstall of Office.

Anyone got any ideas?

Posted on Oct 9, 2023 9:37 AM

Reply
Question marked as Top-ranking reply

Posted on Oct 11, 2023 4:22 AM

I had an ancient Bauhaus 93 Type 1 font suitcase, some Type 1 Bauhaus 93 display fonts, and an OpenType Truetype Bauhaus 93 font — all in my ~/Library/Fonts folder. That was the "detritus" that I spoke of and subsequently removed from that location. There was no longer a Bauhaus 93 entry in Font Book. The font location inside the Microsoft application bundle is not seen by Font Book that location is not among the three primary font search locations used by the operating system.


Once I achieved the first paragraph, the Bauhaus 93 font internal to Word 16.77.1 appeared on the font menu and was applied to the selected text.

Similar questions

22 replies
Question marked as Top-ranking reply

Oct 11, 2023 4:22 AM in response to RecordNotFadeAway

I had an ancient Bauhaus 93 Type 1 font suitcase, some Type 1 Bauhaus 93 display fonts, and an OpenType Truetype Bauhaus 93 font — all in my ~/Library/Fonts folder. That was the "detritus" that I spoke of and subsequently removed from that location. There was no longer a Bauhaus 93 entry in Font Book. The font location inside the Microsoft application bundle is not seen by Font Book that location is not among the three primary font search locations used by the operating system.


Once I achieved the first paragraph, the Bauhaus 93 font internal to Word 16.77.1 appeared on the font menu and was applied to the selected text.

Oct 19, 2023 4:21 AM in response to Kurt Lang

Wow.

Well this has been incredibly frustrating so I'm going to give up and just create my invoices on a Windows VM where it works and maybe look at replacing that font as my company logo font. Just putting this here for completeness


I went back through a number of versions as suggested above, downloading the full Office suite with Teams and following the full uninstall instructions (so removing the /Container and /Group Containers folders) at each point.


On a clean install of the 16.76 and newer packages the font wasn't available straightaway so those are 'broken'.

On a clean install of the 16.75 package (I also tried the 16.27/ 16.73/16.74 packages) the font was displayed so looks like latest package to use was the 16.75.


I then tried updating all the other apps except Word. After those updates, font now not displaying correctly.

I then uninstalled completely, re-installed the package and went through updating individual apps. Tried a couple of updates (excel/ teams) but font now not displaying correctly so I thought it might be the updates.


So back to a full uninstall and re-install at which point I discovered that on closing and re-opening word without any updates, font does not display correctly so the simple action of opening word then closing it after 1st use seems to stop the font displaying correctly & nothing to do with any updates.


The only thing I can think of is that it's something to do with the /container or /group container files.


In /Group Containers, on install, two folders are initially created:

  • UBF8T346G9.ms
  • UBF8T346G9.Office

then on opening word, another is created:

  • UBF8T346G9.OfficeOsfWebHost

and all folders are modified as they now have the same modify date


Word needs to then be activated using my M365 account. This doesn't appear to impact any of those folders modified date


in /Containers, when word is opened for the 1st time, a folder called Microsoft Word is created


Once all this has happened I can use the font.


I then close Word.


UBF8T346G9.Office modified date changes and on re-opening Word the font doesn't display correctly


So it looks like something in that folder is causing the problem.


Next step was to take a copy of a freshly installed UBF8T346G9.Office folder, which contains a structure and no files other than an alias: UBF8T346G9.Office/Library/Application Scripts/UBF8T346G9.Office


If I then subsequently overwrite this folder after each use of Word, I have to reactivate Word and the font displays currently - until I close Word


I tried keeping just some of the registration& license files in the folder and deleting the rest but that doesn't seem to work. It's only on the first activation and use that I can use the font.


So that's me done on this lol.





Oct 12, 2023 7:14 AM in response to RecordNotFadeAway

To add further clarification, the font was working in the app but stopped working sometime in Sept. It could be tied to an update I imagine and I'm the only one using that font so

Yes, that is helpful insight. That essentially proves something changed in either the OS or Office to cause Bauhaus to disappear.


Since the font appears in all other apps when a copy is activated, I'd have to say reinstalling the OS will change nothing.


You can go back to 16.77 on Microsoft's download page, and is the one just before the version you noted at the beginning of this topic. I'd try installing that version just to see if the font comes back in Office.


Or do multiple tests, like the 16.76 version, or, update it to the latest 16.78 version to see if MS fixed it.

Oct 11, 2023 9:18 AM in response to RecordNotFadeAway

5) run atsutil databases -removeUser and restarted - no change

That only removes the font cache data for the current logged in user account. It can't fix a coding issue for an app.


The purpose of the new account test was to see if Bauhaus93 would work there. We already know the root Library's Fonts folder is empty, as you noted the only thing there was the alias for Arial Unicode. And a new account will have no fonts in the user account Fonts folder.


That all means the only fonts the new account had any access to were those in the System folder, and those within the Office application packages. Since Bauhaus93 still didn't appear can mean a few things.


  1. The code for Office 2021 and 365 is slightly different. Mostly in the means of activating the software. But, it's still a difference and somewhere in there may be a bug that causes the 365 version to misbehave.
  2. The OS itself may be the problem which only an OS reinstall could fix. Make sure to have a full backup on hand, first. Then reinstall Ventura. Don't erase the drive, just reinstall the OS over itself so all of your third party apps, user account and other personal data are still there.

Oct 10, 2023 5:44 AM in response to RecordNotFadeAway

That last part actually isn't strange at all. The Office apps have the same set of fonts within each application package, and only each app knows they exist when looking within their own package.


Because they're not in any normal Fonts folder, nothing else on your system knows about those fonts unless you copy them out and activate whichever ones you want with Font Book, or any other font manager. Then they're just a font like any other font the system and other apps can see.


The main question though is, why can't Office see its own font? Not that Office has ever been great at handling fonts. It's been a while since I've checked, but it never sees the OS installed font, Zapf Dingbats. If you want Office to use that font, you have to copy it into each Office application package DFonts folder.

Oct 10, 2023 1:32 PM in response to RecordNotFadeAway

Yes. I was wondering if since all other apps can see Bauhaus93 when activated separately, if it would then show up in Office. But, no. It still ignores the font.


I stopped using Office a couple of years ago (now using the SoftMaker Office suite) and can't test MS Office without a license. It will only operate in read-only mode and won't even let me select the font drop-down menu to see if Bauhaus93 is there.


I can't imagine why Office won't list one of its own fonts, and you've done pretty much all basic troubleshooting steps. Then only one I can think of otherwise is to create a new user account, login to that and see how Office behaves.

Oct 10, 2023 2:13 AM in response to Kurt Lang

Hi Kurt, thanks for the help. I've tried that but no change. I've then completely removed Office using this process https://support.microsoft.com/en-us/office/uninstall-office-for-mac-eefa1199-5b58-43af-8a3d-b73dc1a8cae3

and then re-installed office. No change.

Very strange and annoying as since I've now added the font to my fonts, I can use it in the Apple apps like Pages!

Oct 11, 2023 1:40 AM in response to VikingOSX

Hi, thank you for the tip, can I check what you mean by removing detritus from you local Fonts folder?

In addition to my original troubleshooting steps above, I have now:

1) created a new user - same issue 

2) removed the font from /Library/Fonts - the only file in there is an alias for Arial Unicode.tff

3) removed the font from /Users/myuser/Library/Fonts

4) checked Font Book - all clear

5) run atsutil databases -removeUser and restarted - no change


I have crossposted on the MS forum and a contributor has been able to reproduce the issue and requested to log the call so we will see how that progresses I guess. Link below if interested.

https://answers.microsoft.com/en-us/msoffice/forum/all/font-issue-with-ms-word-for-mac-16771-365/bb4fa3b1-e4e4-4edc-87d4-b29d35db9e61


Least I can run a windows vm and still create my invoices with my logo :)

Oct 12, 2023 7:03 AM in response to Kurt Lang

Kurt Lang wrote:
That only removes the font cache data for the current logged in user account. It can't fix a coding issue for an app.

Thanks, yes I understand that :) I should have been more explicit:

I created the new account, logged on and verified the problem occurred for a new user, then logged off and back in as myself and ran through steps 2-5 as I had copied in the bauhas93.ttf into my user accounts font libraries as per my post Oct 10, 2023 1:03 PM in response to Kurt Lang


I'll see if I get anywhere with the MS feedback but if not then I guess I'll have to go with an OS reinstall.

Thanks for your assistance :)

To add further clarification, the font was working in the app but stopped working sometime in Sept. It could be tied to an update I imagine and I'm the only one using that font so

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Font issue with MS Office 16.77.1 (365)

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.