MYOB Won't Print After the August 2026 Windows Update
What Broke — and the Fix That Lasts

1. What's Broken — and What Isn't

MYOB AccountRight is built on a Microsoft technology called Windows Presentation Foundation, or WPF. When AccountRight prints, it doesn't send text straight to your printer. It first builds a print-ready document, and part of building that document is subsetting the fonts — cutting each font file down to just the characters the page actually needs, so the file stays small.

The August 2026 security update tightened how strictly that subsetting code checks a font file before using it. The check is now strict enough that fifteen ordinary Windows fonts fail it. When a font fails, the code doesn't skip the font or fall back to another one — it abandons the whole document.

Sometimes you get that error. Just as often you get nothing at all — the "Please wait…" bar simply hangs, because the failure happens quietly inside the render and the progress dialog never gets told to close.

Here's the important part: nothing is wrong with your printer, your driver, your print queue, your print server, your network, or your MYOB data file. The fonts themselves aren't damaged either — they're the same files they always were, they display perfectly on screen, and every other program on the machine can still use them. Only the code that prepares them for printing changed.

If you want the technical detail: the affected fonts carry a legacy kern table — an old spacing table — larger than 65,535 bytes. The field that records that table's length can only count to 65,535, so it wraps around and reports a nonsense figure. The old code never looked. The new code does, sees a length that can't be right, and refuses the font. Microsoft has confirmed this as a regression and it's tracked publicly as issue #11834 in the dotnet/wpf repository.

2. The Thirty-Second Test

Before you touch anything, run this one test. It separates this problem from a genuine printer fault faster than anything else, and it costs you nothing.

1. Open Word, or Notepad

   Type anything. A single line is plenty.

2. Print it to the same printer MYOB is failing on

   Not a different printer. The same one, from the same computer, logged in as the same person.

3. Read the result

   If Word prints and MYOB doesn't, you have this problem. If Word also fails, you have a genuine printer or driver problem and this guide isn't the one you want.

One more signal worth checking: when did it start? If printing worked on Friday and stopped the following week, and the machine installed updates in between, the timing lines up. This update went out on 11 August 2026 and most machines picked it up between the 11th and the 13th.

3. Confirm It Properly — One Command

The test above is strong evidence. This is proof. There's a single Windows file whose version number tells you definitively whether a machine is affected — PresentationCore.dll.

Open PowerShell as administrator (right-click the Start button › Terminal (Admin) or Windows PowerShell (Admin)) and paste this in:

You'll get one or more version numbers back. Compare them to this:

* If you get several results back, that's normal — Windows keeps more than one copy. Any single result showing 4.8.9344.0 means the machine is affected.

4. Which Programs Are Affected

Any program built on .NET and WPF that prints, or exports to PDF or XPS, can hit this. In Australian small business the ones we're seeing are:

If you run an accounting or bookkeeping practice, assume you're exposed until you've checked. The pattern we'd expect is that staff report it as a printer fault, because that's genuinely what it looks like from the desk.

5. Which Fonts Break, and Which Are Safe

Fifteen faces fail. Note that Cambria Regular is fine while its bold and italic versions are not — which is exactly the kind of detail that makes this maddening to diagnose, because a template can print until someone bolds a heading.

Calibri Light is the swap you want. It's from the same family, it's very slightly lighter in weight, and on a printed invoice nobody notices the difference. Every other option changes the look of your paperwork enough that clients may comment.

6. The Fix That Lasts — Change the Fonts

Change every affected font in your templates to Calibri Light. That's it. It keeps your security update in place, it needs no registry edits or policy changes, and — the part that matters most — it survives every future Windows update. A template that doesn't use a broken font can't be broken by this again.

Here's the procedure for MYOB AccountRight.

1. Find out which forms you actually use

   There's no point re-fonting forty templates when you print three. Check a customer card › Selling Details › Printed Form, and check Print/Email Invoices › Advanced Filters. Between them you'll see which forms are really in play.

2. Open the form for editing

   Setup › Customise Forms › choose the form type › highlight the form › Customise.

3. Save a backup copy first — then edit the original

   Use Save Form As to keep a copy, then make your changes to the original form. Editing the original in place matters: your customer cards point at it by name, and a renamed form quietly stops being used.

4. Select all on the canvas and set the font

   Then do it again for each band. The header, body and footer sections don't select together, so "select all" only ever catches the band you're in.

5. Double-click into the data table separately

   This is the step nearly everyone misses. The table holding your line items has its own font settings — and the column headings have different settings again from the column contents. Both need changing.

6. Check every remaining object one at a time

   The ABN block, the amount-in-words line, the tax summary, payment terms, free-text boxes and page numbers are all separate objects with their own fonts. Click each one and confirm.

7. Do your reports too

   Display the report › Insert & Modify tab › font options. Reports are separate from forms and are easy to forget until someone tries to print a month-end pack.

8. Repeat for every company file

   Forms are stored inside the company file, not centrally. Two company files means doing it twice.

Always finish by printing a real invoice — not a preview. Preview never touches the code that's broken, so a clean preview proves nothing at all.

7. What Doesn't Work (Don't Waste the Afternoon)

These are the things people try first, and none of them will help. We're listing them so you can skip them.

• Reinstalling the printer driver. The document never reaches the driver. A brand-new driver receives exactly nothing, same as the old one.
• Clearing the print queue or restarting the spooler. The queue is empty because nothing was ever sent to it. Restarting the spooler restarts something that isn't broken.
• Deleting and re-adding the printer, or rebuilding the print server. Same reason. This one costs the most time and helps the least.
• Printing to a different printer, or to PDF. Also fails — emailing a PDF from the app uses the identical rendering path. If anything this is useful confirmation rather than a fix.
• Reinstalling MYOB. The fault is in a Windows component, not in AccountRight. A reinstall lands you back in the same place with an afternoon gone.
• Repairing or reinstalling the fonts. The font files are not damaged and never were.

8. Where This Is Up To

Microsoft has confirmed the fault is a regression — code that used to work and now doesn't — and it's been given the highest internal priority. As at 21 August 2026 no corrected build has shipped.

When one does, it will arrive as a normal Windows update and printing will start working again on its own. If you've changed your templates to Calibri Light, you won't notice, because nothing on your side depended on the fault being fixed. That's precisely why it's the recommendation.

We'll update this page when a corrected build is released.

9. When to Call a Tech

Plenty of businesses will get through section 6 on their own, and if that's you, good — you don't need us. It's worth handing over when:

• You have a lot of templates. Several form types across multiple company files turns a twenty-minute job into a long afternoon, and the all-or-nothing failure mode punishes rushing.
• You've changed everything and it still won't print. There's an object you haven't found. Someone who knows where AccountRight hides them will find it faster.
• You've got more than a handful of machines. Checking the DLL version across an office and sorting the templates once is a single job rather than a recurring interruption.
• Your forms were built by someone else and nobody left is confident editing them.
• You need it printing today — end of month, payroll, a client waiting on an invoice — and you'd rather it just be handled.

This is a remote support job almost every time — we connect to the machine, you watch the whole thing, and there's no waiting for a visit. Remote support is $125/hr and onsite is $205/hr. A single machine with two or three templates is usually well inside an hour; a practice with several company files takes longer, and we'll tell you what we're looking at before the time adds up rather than after.

We look after homes and small businesses across Perth — Fremantle, Joondalup, Rockingham, Scarborough and Stirling included — and for this particular problem almost nobody needs us at the door. If MYOB sits inside a bigger office setup, our business IT support team handles Windows updates, servers and Microsoft 365 across whole practices. If the email side is misbehaving as well, there's a separate guide to email setup and troubleshooting, and you can always just get in touch and describe what you're seeing.