Windows 11 printing from Win32 application error 0x80040154
You will find that Windows 11 isn’t always error-free, especially after an update. Today we fixed Windows 11 printing from Win32 application error 0x80040154 with a script using cmd.
The script simply modifies the Windows registry and reverts the new printing UI back to the old printing UI. You can either follow the instructions below to fix this issue automatically or manually edit the registry to resolve the problem on your computer.
This issue affects all printers in Windows 11 and is not limited to Brother, HP, Fuji Xerox, Canon or Epson printers. This bug even affects printing to software printers such as Adobe PDF or Microsoft Print to PDF.
Tip: You will need administrator rights to run the repair in CMD. If you don’t have admin rights contact your IT support for assistance or give us a call.
CMD Fix for Printing From Win32 application error 0x80040154
We found that all native Windows 11 apps had the same error in our testing as we will as some custom applications. Although this issue affected Windows 11 Microsoft 365 applications were not affected as they used the original UI, not the new UI.
Here’s the cmd fix for printing from Win32 application error 0x80040154:
- Close whatever program that is having the issue
- Click Start
- Type in CMD
- Run as administrator (important)
- Type the following command and press enter
reg add HKCU\Software\Microsoft\Print\UnifiedPrintDialog" /v "PreferLegacyPrintDialog" /d 1 /t REG_DWORD /f
Printer repairs & Installation
Did you know we also offer printer repair services? Our trained experts have been repairing printers, setting up wireless connections and configuring scanners for over 20 years.
Don’t waste your time trying to work out if you’re issue is driver, printer or software related it. Let us work it out for you, saving you time and hassel. Remember we are available for same-day repairs throughout Melbourne.
We can setup your new HP, Cannon or Epson printer on your Windows 11 computer or your MacBook.
Resources
Thanks to the Microsoft community for assisting us in resolving this issue. Here are the resources we used to find the answer:
