Affinity Publisher v1 and v2 crashing on "save" on one System but not the other (Windows 10 identical configuration looking for difference)

[Dobicki]

Hi there. 

I just noticed Problem on one of my two workstations. I keep booth PCs with the same configuration and rather identical apart form slightly differend hardware. (Newer graphics card, both nvidia)

- Both PC Windwos 10

- Both with Publisher v1 latest Version

My Problem is that Publisher crashes reproducibly and consistenty as soon as I save an existing file. 

On the second PC everything is stable. 

 

I tried to no effect: 

- uninstalling and reinstalling. 

- updating graphics card driver

- uninstalling all third party fonts from the system

- changing the performance settings to more or less ram

- activating and deactivating openGL

- Step by step importing pages from and old document to a new one. 

- tried loading the file without the embedded resource documents 

- tried several different files

 

Publisher keeps crashing when click save. 

- tried publisher v2 same ting. 

- went back to v1.92 "save" still produces crash "save as" works and saves new file. however publisher still crashes when doing other stuff like moving an image. 

also it is not doable to create a new file after any kind of change. :( 

  

Would you have any I dear what parameter, property of the system might be responsible for the crash?

Looking forward to your feedback. 

 

Cheers

 

Roman

[Dobicki]

So I have been looking into the issue further since yesterday. 

 

This seems to be the solution! I uninstalled Windows Update KB5017262 and now things seem to work.

 

Additional Info for other issues here: 

 

 

Good riddance you guys. This cost me some nerves and made me some more grey hair -.-* 

Looking back on it it also made sense that the problem did not occur on the second PC since it had not had the latest Windows Updates yet. 

After working on it yesterday the update in question may have been installed so today when I checked things out again the problem happend on this second system as well.

Anyway. Hope this helps somebody else. Also hope you can soon fix the issue. Especially given that all fresh v2 seems to deal with the same thing still.

Cheers

 

Roman