Hidden text being hidden suddenly causing formatting issues in subsequent (not hidden) paragraph

Question

Hidden text being hidden suddenly causing formatting issues in subsequent (not hidden) paragraph

Curtis Kasefang 20

We have been using the hidden text feature in our specifications for decades. We rely on it. Suddenly, today in Word 365 it is broken. This is happening in multiple documents, on multiple machines, on different networks, in different cities. The only commonality is Word 365 and the use of hidden text.

What is happening is that when the hidden text is not displayed the hidden text is impacting the border and numbering formats of the subsequent paragraph, where the border and numbering format of the hidden paragraph is substituted for the border and numbering format of the following paragraph when the document is previewed or printed. Everything is correct when the hidden text is displayed.

Hidden text displayed - everything formats correctly
User's image

Hidden text hidden - formatting is messed up.

User's image

Charles Kenyon 166.5K Reputation points Volunteer Moderator

2026-02-18T19:01:38.7266667+00:00

Can you save a sample document with the problem on OneDrive or DropBox and post a share link to it here so we can examine the precise structure?
https://addbalance.com/articles/Why%20a%20sample%20file%20is%20important%20for%20troubleshooting.%20How%20to%20do%20it.htm

Are there any Style Separator's being used?
Chris Hammett 0 Reputation points

2026-02-24T00:23:40.5633333+00:00

My company is having the same issue. Our use case is the same, architectural and engineering (A/E) specifications. I had to roll back to build 2507 to find a version of Word that did not produce this bug.

I can confirm that saving the document as a .doc works. However I tried just changing the extension first and that doesn't work. I had to save-as from Word as a .doc to get it to fix the formatting.

For our specific application of editing A/E specs I found that removing the hidden text resolves the formatting of the numbering. This isn't acceptable for working documents but we often send out "clean" final word docs to our clients. In those cases I would delete all hidden text and make a PDF as well. Deleting the hidden text is a bear without the use of a macro, such as Masterworks plugin, to do it on a bunch of word docs all at once. Changing to .doc is a lot simpler.

I'm not sure this is the exact same thing as the Style Separator bug but it feels the same. I don't know enough about word to comment much further and have never used the style separator.

Answer recommended by moderator

8 additional answers

Your answer

Charles Kenyon 166.5K Reputation points Volunteer Moderator

2026-02-18T19:01:38.7266667+00:00

Can you save a sample document with the problem on OneDrive or DropBox and post a share link to it here so we can examine the precise structure?
https://addbalance.com/articles/Why%20a%20sample%20file%20is%20important%20for%20troubleshooting.%20How%20to%20do%20it.htm

Are there any Style Separator's being used?
Chris Hammett 0 Reputation points

2026-02-24T00:23:40.5633333+00:00

My company is having the same issue. Our use case is the same, architectural and engineering (A/E) specifications. I had to roll back to build 2507 to find a version of Word that did not produce this bug.

I can confirm that saving the document as a .doc works. However I tried just changing the extension first and that doesn't work. I had to save-as from Word as a .doc to get it to fix the formatting.

For our specific application of editing A/E specs I found that removing the hidden text resolves the formatting of the numbering. This isn't acceptable for working documents but we often send out "clean" final word docs to our clients. In those cases I would delete all hidden text and make a PDF as well. Deleting the hidden text is a bear without the use of a macro, such as Masterworks plugin, to do it on a bunch of word docs all at once. Changing to .doc is a lot simpler.

I'm not sure this is the exact same thing as the Style Separator bug but it feels the same. I don't know enough about word to comment much further and have never used the style separator.

Answer 1

Charles Kenyon 166.5K Volunteer Moderator

It appears that this has been fixed in update 2602.

Chris Hammett 0 Reputation points

2026-02-25T19:28:57.49+00:00

Same here. Update 2602 appears to have fixed the issue.
Curtis Kasefang | TCC 5 Reputation points

2026-03-04T15:38:11.3+00:00

This is good news. It would have been even better had MS followed through on the support call that their level 2 guy was off researching ... instead of ghosting me.

Answer 2

Charles Kenyon 166.5K Volunteer Moderator

Workaround:

Try the method given in Stacy Brown's January 29 response in this thread:
https://learn.microsoft.com/en-us/answers/questions/5720470/using-style-separator-is-causing-the-numbering-to

I have been following this issue here and on other vendor and legal technology boards. A new work-around was posted from one of our vendors, DocStyle. They say to try:

Work in Draft Layout view while editing

Turn on Track Changes to print or PDF

Turn off Track Changes then save or send the file. So, it seems that turning on Track Changes makes the numbers of the affected Outline Numbering levels reappear.

There have been three workarounds that have worked with the style separator problem. I agree with Stefan that your problem is likely part of the same bug because saving to .doc format works. Those workarounds are:

Roll back to version 2511 (I have not tried this but others have)
Save in .doc format (works here but you lose newer features)
The method described by Stacy Brown. (works here)

When using your sample document, I displayed non-printing formatting, including hidden text. If I turn on track changes (which is in my status bar) and then turn off display of non-printing formatting, the problem does not show up. I have not needed to work in Draft view. Simply turning track changes on gets you the correct formatting. Here are two screenshots from your sample document.

P.S. Congrats on your use of styles!
https://www.addbalance.com/usersguide/stylesImportance.htm

With Track Changes off:

User's image

**With Track Changes on:
** User's image

Remember to turn Track Changes back off once you have printed or observed what you want with hidden text hidden.

I suspect that the Style Separator problem is because the Style Separator is a paragraph mark formatted as hidden.

Stefan Blom 338.6K Reputation points MVP Volunteer Moderator

2026-02-20T18:52:18.05+00:00

If you save to .doc format first and then save back to .docx and check the box to "Maintain compatibility with previous versions of Word," that seems to keep the numbering intact. You can then review the compatibility options via File > Options > Advanced.

Compatibility mode imposes certain limitations on the document (although the file format is .docx).
Clinton Merrell 0 Reputation points

2026-02-20T19:27:23.3166667+00:00

Saving to a .doc does not work for us at all because it removes content controls. In our specifications we often use these for dropdown choices for spec writers to chose among multiple standard choices.
Stefan Blom 338.6K Reputation points MVP Volunteer Moderator

2026-02-20T19:34:26.7666667+00:00

@Clinton Merrell, that is a good point. For you, the best option may be to revert to an older release, until this is resolved by Microsoft. I believe that version 2511 did not have the bug.
Curtis Kasefang 20 Reputation points

2026-02-20T19:42:12.68+00:00

I have a separate interaction going with MS Tech Support - now at level 2. They seem to be unaware of this bug.
Clinton Merrell 0 Reputation points

2026-02-20T20:09:07.1466667+00:00

We did revert to 2511, but that lasted a day before the software was automatically updated to a newer build. I'll keep watching here to see if this bug gets escalated to a formal recognition from MS support.
Stefan Blom 338.6K Reputation points MVP Volunteer Moderator

2026-02-20T20:14:43.6766667+00:00

You will have to turn off automatic updates as well. See https://support.microsoft.com/en-au/topic/how-to-revert-to-an-earlier-version-of-office-2bd5c457-a917-d57e-35a1-f709e3dda841 .

Or are you saying you followed those steps and it didn't help?
Chris Hammett 0 Reputation points

2026-02-24T00:35:55.7533333+00:00

Having track changes on does indeed work to display the numbering properly but sometimes you need to turn track changes off ultimately. Also if you print the document and don't want track changes to print the number formatting is bugged.

I managed to get the bug to go away by going back to build 2507. Not sure why it doesn't seem to show up for others in later builds. I actually went up to building 2508 after finding that 2507 worked and the bug was present in 2508. Once I found that .doc doesn't have the bug in any build I updated back to the latest.

Ultimately I settled on saving the document as a .doc. It's not a permanent solution but it works if you're aware of the issue and don't rely on newer Word features enabled by .docx.
Curtis Kasefang | TCC 5 Reputation points

2026-02-25T20:14:58.59+00:00

I just discovered that this formatting problem does not happen with .docm files.

It only happens with docx files that aren't saved in compatibility mode.

Answer 3

Stefan Blom 338.6K MVP Volunteer Moderator

@Curtis Kasefang

Saving in the older .doc format seems to work around the bug, no matter if you used a style separator or the "hidden paragraph mark" trick. See the screen shot below.

Note that this .doc workaround has been mentioned in other threads which specifically discuss the style separator bug. See https://learn.microsoft.com/en-us/answers/questions/5720470/ .

User's image

0 comments

Answer 4

Curtis Kasefang 20

I heavily use styles.

This is part of a specification system we have been using since the 90's. It allows us to rapidly reformat specifications (and reliably number paragraphs). I work in a group of independent contractors who work out of our homes in the US and Canada. This problem suddenly started happening on most documents, at multiple locations (each one of us provides own PC), every machine configuration is unique, each has a different ISP.

My guess is the problem is coming from a combination of Word 365 code update (bug) and perhaps some vestigial code crud in the document style. It appears that when a hidden piece of text is hidden for display or print, the paragraph numbering format and the paragraph border format is carried into the next paragraph.

Here is a link to the problem child https://www.dropbox.com/scl/fi/dnu4konp9seb1e1b57ddj/116161-40-Data-Control-Network-with-bug.docx?rlkey=hkg5ea185gnijyeh3hxaio6vn&dl=0

Red and Blue text is formatted as hidden.

I am currently working with MS support on this. There is no known bug. The Case has been escalated at MS. We have a call scheduled tomorrow, 2/18/2026, in the afternoon.

Anna Crowder 30 Reputation points

2026-02-24T18:39:39.9033333+00:00

@Curtis Kasefang did you have the call with MS? We've been fighting this for over a month now. It affects our document assembly program - making it really difficult for our customers to work efficiently (attorneys who draft complex legal documents).
Curtis Kasefang 20 Reputation points

2026-02-24T19:37:38.0033333+00:00

Yes, they went away to "Research," and we haven't heard back in 4 days.
If you aren't using choice fields, saving the docs in doc compatibility mode is a viable workaround until they get around to fixing it.

Answer 5

Scott T 5

I am experiencing same issue, with the last 2601 Build 16.0.19628.20166 update. Steps to reproduce:

Type in a paragraph using Normal style, without any applied formatting - call it Para 01. Then I type in a second paragraph, and apply an auto-numbered format, call it Para 02. Next, I apply hidden font to the entire paragraph, including the CR mark, to Para 01. When I toggle the show/hide button on and off (Ribbon Menu, Home tab, Paragraph group) the numbered Para 02 loses its number, and inherits the paragraph format of the hidden paragraph before it. This happens with applied formats as well as for paragraphs that have a previous paragraph having any kind of hidden style.

I haven't noticed the problem until the latest Word update (shown above). It does NOT happen on another machine with an earlier version: Version 2508 Build 16.0.19127.20532 (no bug)

[Edited to add:] No, there are no Style Separator characters in the affected documents. ALSO - this issue appears only in .DOCX (not "compatible") files, and not in .DOC files. We also use building specifications software, so have been looking into possible interactions those add-ins and templates.

Stefan Blom 338.6K Reputation points MVP Volunteer Moderator

2026-02-19T21:35:47.7766667+00:00

This is likely related to the style separator issue which is documented at https://support.microsoft.com/en-us/office/heading-numbering-disappears-after-applying-style-separator-in-word-535fed39-64eb-4ac1-a2c6-48f15dfd5ed5 .
Curtis Kasefang 20 Reputation points

2026-02-19T21:53:01.3266667+00:00

Thank you for this - this is an excellent insight!
Is your work-around to save the documents in a DOC format?
Scott T 5 Reputation points

2026-02-19T22:15:02.8533333+00:00

As I mentioned earlier - I am NOT using style separators. See steps to reproduce, above.
Stefan Blom 338.6K Reputation points MVP Volunteer Moderator

2026-02-19T22:18:47.9433333+00:00

@Scott T, the screen shot in my Answer is not using style separators either, only a hidden paragraph mark. The symptoms are identical.
Scott T 5 Reputation points

2026-02-19T22:29:24.5533333+00:00

Yes, converting to .DOC format (old Word 97-2003) doesn't display the bug. The other workaround is to revert to an older version (not sure which one) - before sometime in Jan 2026. I have a machine still using the semi-annual update channel that uses Version 2508 (Build 16.0.19127.20532) and it works fine [although I'm not sure why - that was Feb 10].

To revert, you have to disable automatic updating off and use the rollback command...
Scott T 5 Reputation points

2026-02-19T23:11:51.5966667+00:00

Here's another way to test for the bug on a plain, non-styled blank DOCX file: Start with a blank document based on a fresh Normal template. Type in two single-line paragraphs, then apply some paragraph-level formatting to the second paragraph, like numbering, then apply only hidden text-formatting to the first paragraph, including the CR at the end of the line. The second line's paragraph-level formatting (whatever you applied, in this case an autonumber) should disappear when toggling the show-hide button, and be replaced with no formatting (since the first line has only hidden text format, not paragraph-level formatting). Next, if you draw a box around the first (hidden text format) line, then toggle again, the second line should show up with the box, and also without a number.
Curtis Kasefang 20 Reputation points

2026-02-20T00:26:19.2233333+00:00

Scott,
Have you tried saving as a .doc.

Then saving the .doc as a .docx?

If no, would you be willing to try it?

I did this and found that once I did that, the .docx performed properly.
Scott T 5 Reputation points

2026-02-20T15:59:33.54+00:00

[Updated] - YES, the document converted to .DOC then back to .DOCX no longer displays the bug - BUT it gets saved as a .DOCX with compatibility mode turned on. When you turn it back off (File, Info, Compatibility Mode-Convert), the bug immediately reappears.
Curtis Kasefang 20 Reputation points

2026-02-20T16:05:55.9333333+00:00

I am with you. I will create a VBA routine to automate this experience. I need to run a routine to normalize our file naming format anyhow. I am testing to see if the docx>doc>docx is sticky or if it degrades.
Scott T 5 Reputation points

2026-02-20T16:17:17.7166667+00:00

See note above about compatibility mode. Temp fix only.
Curtis Kasefang 20 Reputation points

2026-02-20T20:16:19.2766667+00:00

I dug a little further.
Compatibility mode is the key to the docx working.
If the docx file is not in compatibility mode, the problem persists.
The problem is therefore an interaction between the new file format and the relatively recent Word version.
With compatibility mode, you lose the embedded fields, like dropdown lists, that the new file format gives you. If you are heavily reliant on fields, this is not a solution for you. I was lucky: I have 1 field that feeds the start of a formatting routine that works on many documents at once, so I was able to embed a pop-up prompt in the VBA routine and gather the data that way.

Share via

Hidden text being hidden suddenly causing formatting issues in subsequent (not hidden) paragraph

8 additional answers

Your answer