This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(99.2, 7.000000000000001%, 19%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJI%3C/text%3E%3C/svg%3E)
Windows 11 Home, Version 10.0.26200, Build 26200
Microsoft 365 paid subscription, Version 2603, Build 19822.20104, Click-to-Run
Publisher crashes every time I try to insert a Drop Cap - Custom into a paragraph. All other Drop Caps options have gradually disappeared and Custom is the only option left. This issue persists after Repair, Reinstallation and GPU changes. Does anyone have any workarounds or suggestions?
A desktop publishing application from Microsoft that focuses on page layout and graphic design.
Does the Drop Cap look good after Repair in new publications?
It seems that problems have been observed before, for example:
To revive the file, perhaps it is possible to start the second instance of Publisher and copy and paste the items. Keep backup and intermediate files.
Hi Viorel,
I am unable to add a Drop Cap at all in the current situation. Repair made no difference, neither did reinstallation of Microsoft 365. The problem has indeed been observed before, going back at least four years according to closed comments in Microsoft Support. It does seem to be a problem with the document (a monthly newsletter) rather than the software; Drop Caps worked fine on a new document and new text when I just tried it in Safe Mode, but crashed as soon as I tried it on the document I'm working on, even in Safe Mode. It may be compounded by my constantly Saving it As the next month's issue before editing, as others have reported, but I was hoping for some guidance on how to correct the problem rather than recreate the entire newsletter as a fresh document.
I think the crash comes from a broken style‑graph hook tied deep in the old master chain… Custom is the only callpath that still touches that stale node. just move the text into a fresh blank box once — Publisher rewires the chain cleanly, and that’s the only fix I’ve ever seen hold.