Problems after februari windows updates

[Jack Konings]

Hi all,
Does anybody have any problems with D2H after the windows updates of this week? Looks like the word documents in the D2H projects keep repaginating and constantly have a high CPU usage.

Best regards
Jack Konings

[Chainware]

Hi Jack

I have the same problems after Word update...

Sjouke

[Chainware]

Hi all,

Another related problem: it takes ages to generate a PDF from NetHelp Manual target

Sjouke

[Jack Konings]

Hi Sjouke,

Yes, the problem only seems to occur in print layout view. Other views to not have the problem. I guess the PDF problem is directly linked to this issue.
But what to do now? We have automatic updates in our company, so I cannot revert that easily. And I am afraid Madcap and Microsoft will be looking at each other, because it only seems to occur with Word documents related to Doc-to-Help.
Any way, I will create a bug report and see what will be the answer.

Best regards
Jack

[Chainware]

Hi Jack,

I will create a bug report as well. Madcap certainly has to fix this annoying issue!

gr Sjouke

[Jack Konings]

Hi all,

I have figured out what the problem is with the bad performance in my doc-to-help source documents.
It turns out to be a MS Word problem, not a D2H. In my headers I have used styleref fields; one for heading 1 and one for heading 2. If I delete the stylreref field for heading 2, then the problem is resolved.
This also happens in a clean Word document, without using a D2H template.
So, for me the issue is not solved yet, because I want to use this styleref field, but it does not turn out to be a D2H problem.

@Sjouke. Maybe you could check is this is also the case at your end.

Best regards
Jack

[Chainware]

Hi all,

It seems Jack is right! I removed the footer's STYLEREF "heading1" from a source file, and the paginating went OK. In fact there is no need to have footers and headers in a source file, as it is all skipped when generating online (html) outputs. It comes from the Word Source template. From the source file I modified, I also generated manual output (with a different Target template). As I expected, this went wrong again because of a header STYLEREF "heading1" (coming from Target template). After removing that styleref as well, paginating was OK!
So at least we have a workaround to continue work, but the problem still needs to be fixed.

@Jack
Thanks Jack for sorting out so far!!

Gr Sjouke

[Jack Konings]

Hi all,

I just upgraded to Microsoft 365 Version 2101 (Build 13628.20528 Click-to-Run -- Word Version 16.0.13628.20318) and I can confirm that the issue with the performance related to the styleref fields is solved in this version. This version is now available in the Monthly Enterprise Channel.

Best regards
Jack

[Chainware]

Yes, upgrading to the version Jack mentioned resolved the issue for me as well.

Gr Sjouke