Windows Update from October 1st Crashing Publisher

[natecombsmedia]

Hello there friends,

Just thought I'd inform you that trying to click on "Start New Section" in any Affinity Publisher project immediately crashes the project as of the latest Windows Update (KB5017024). I uninstalled—or so I think since it still shows my computer as up to date and I can see the update in the history—and the problem went away.

[Lee_T]

Hi natecombsmedia,

This doesn't seem to be a general issue, if you get the issue again in the future please reply with your crash report:

Lee

 

[Ervin Hajdú]

Hi Friends,

I have the same issue after Windows update: Affinity Publisher crashes.

I want to work with an old Publisher doc, but after few operations the software chrashes. I think it is related to text actions.

The error is permanent. 😞

Ervin

[MandyYeo]

I have the same problem - Affinity Publisher crashed after image change, image move, image link, font change etc.  on both new and older documents. I have now resorted to uninstalling Windows 11 update, testing, uninstalling the next update, testing until Publisher started working again.

Rather tedious and now I daren't update Windows as working in Publisher is my main source of income and I need it to work. I also don't like falling behind on my Windows updates either..... bit of a problem.

[natecombsmedia]

Thank you @LeeThorpe. Windows updated again yesterday, and the same problem came back. I will file the report.

Didn't realize I wasn't following the topic. Thought I was 😅

[natecombsmedia]

Here they are. 3 from the first time. 3 from today...looks like one encounters an error and cannot upload.

82187b85-3b4e-48a0-99be-1314ea8681a7.dmp a98d03ec-2df9-4918-bbfd-f461e63d41c9.dmp cb5494cf-55c8-46fb-ba44-080a9934f85e.dmp cf99783c-1325-40b0-aef1-794bea71e4df.dmp f5f19c37-5db5-4c65-afb2-95bcc4a95ebf.dmp

[OzNate]

On 10/3/2022 at 9:01 PM, N.P.M. said:

 

Thank you, this was the issue that brought me here to the forums. Typing in font selection box causes immediate crash.

[Ervin Hajdú]

I removed that file for the 3rd time, after the 3rd Windows update. 😔 Any updates expected from Affinity? What is the long-term solution?

[carl123]

54 minutes ago, Ervin Hajdú said:

I removed that file for the 3rd time,

Why?

Did you not follow the instructions to "prevent it being installed with future updates"?

 

[walt.farrell]

4 hours ago, Ervin Hajdú said:

What is the long-term solution?

The ideal long-term solution is that Microsoft ships a proper version of this update; one which does not break all the applications that use the Microsoft WPF framework for generating their user interfaces.

[carl123]

45 minutes ago, N.P.M. said:

There were at least 2 cumulative updates for the .net update cycle this month which installs the culprit version again.
Had to run the procedure myself 3 times too.

Did you have to run the procedure 3 times to exclude one specific KB number from reinstalling again or did you ultimately have to exclude 3 different KB numbers after the cumulative updates.

[carl123]

26 minutes ago, N.P.M. said:

The cumulative updates are with a different kb number but installs the KB5017262(win10) version again.
When done updating>restart pc>go to update history and it does show the KB5017262 again>uninstall this one (again)
Run winhideupdatetool again to find the newest kb number is the only one present>hide this one to have the .net issue go away(again).
(but yes 3 times it reinstalled already by a cumulative .net update)

Well, that is what I would expect if Microsoft are "constantly" including a problematic KB update in future cumulative updates.

You just have to hide them as they are released/detected

The only other option is to pause all updates for a while until Microsoft releases an update that does not cause the problem or Serif releases a patch/update for its 1.10.5 apps.  (Which is what I did as I'm too busy at the moment to deal with unexpected crashes during my work)

 

 

 

 

[vbwyrde]

I'm having the same issue after MS forced an update to my machine as per it's usual habit.  Now I can not work with my Affinity Publisher program as it crashes incessantly as soon as I start working.  Is this something that Affinity can deal with, or do we have to wait for MS to figure out that they are causing problems with their update and fix it? Are there any steps I can take to mitigate this for the time being?  I'm trying to finish a document and i can't get more than five steps before Affinity Publisher crashes again.  I tried rebooting, but to no avail.  Thanks.

[carl123]

28 minutes ago, vbwyrde said:

Are there any steps I can take to mitigate this for the time being? 

If your problem is due to Windows update(s) then instructions are below as to how to remove those updates and prevent those specific updates from reinstalling again.

Once you have done that you can temporarily pause all updates to prevent new ones reintroducing the problem, as has been the case so far

Also, if hardware acceleration is on, switch it off in Edit > Preferences > Performance to eliminate it as a possible cause, as that can also cause crashes on some systems

 

 

[vbwyrde]

Thank you for your advice.  That did fix the issue, however, Windows Update almost immediately popped up a window saying "Your advice will restart to update outside of active hours" and I'm pretty sure it is going to re-install the update.  I can pause updates but only for 7 days (Windows 10).  I tried the wushowhide cab, but it did not find the update and only showed two hardware driver updates instead, so I seem to have no way to block it.
 

[Arun Sarkar]

On 10/16/2022 at 6:07 PM, carl123 said:

Serif releases a patch/update for its 1.10.5 apps.  (Which is what I did as I'm too busy at the moment to deal with unexpected crashes during my work)

 

 

 

 

Dear Serif, please patch or update for to this .net issue if possible.

Best Regards