ArtisL Posted October 20, 2022 Posted October 20, 2022 Publisher keeps crashing when I try to update images through resource manager. I tried also to replace images but it still crashes. And it started happening suddenly, before it worked just fine, and now I can't do anything with my existing file. Maybe anyone knows how to fix it? I even tried to reinstall the newest version. Quote
LeiNi Posted November 4, 2022 Posted November 4, 2022 I have the same problem. I just installed all windows and driver updates and it still keeps crashing as soon as I'm trying to update the resources. Pleasel, Affinity-Team do something about it, I cannot work like that on my project. And if anyone has a solution for it, I'd appreciate your comment. Quote
Komatös Posted November 4, 2022 Posted November 4, 2022 @LeiNi the posting from N.P.M. has linked to the known bugs and it's solutions. LeiNi 1 Quote MAC mini M4 | MacOS Sequoia 15.5 | 16 GB RAM | 256 GB SSD AMD Ryzen 7 5700X | Sapphire Nitro+ RX 9060 XT 16 GB | 32 GB DDR4 3200MHz | Windows 11 Pro 24H2 (26100.4351) Windows 11 Pro on VMWare Virtual Machine (on Mac) Affinity Suite V 2.6.3 & Beta 2.6 (latest) Interested in a free (selfhosted) PDF Solution? Have a look at Stirling PDF No backup, no pity.
LeiNi Posted November 4, 2022 Posted November 4, 2022 (edited) I could solve the issue for now by myself, by following the instruction of @N.P.M. thx a lot. It was shared I think above, but the sharing style hides too many information, so here again with full a quote: Quote Posted October 19 Install all pending updates. Restart pc afterwards. Goto update history>uninstall updates section Search for: Windows 11:KB5017264 Windows 10:KB5017262 Uninstall Run the tool provided in the faq. There should be only 1 .net(kb) update present(if you did all things above) It will have a new kb number but it is the one you need to hide for the windows updating it again @Komatösthx, you were just replying when I was writing.^^ Edited November 4, 2022 by LeiNi Quote
Komatös Posted November 4, 2022 Posted November 4, 2022 @LeiNi However, I recommend another solution, as the cumulative .NET updates also close security gaps in the .NET components, which are then reopened by the uninstallation. My preferred solution: Open the directory in which the Affinity programmes are installed. As a rule, C:\Programme\Affinity\(Desinger ...Photo ...Publisher) Search and open the .exe.config file (for example Designer.exe.config) with a text editor. Search for "<add key="IsVirtualizingStackPanel_45Compatible" value="true"/>" Replace the value true with the value false. Save the file (administrative rights are required to overwrite!) saladknown 1 Quote MAC mini M4 | MacOS Sequoia 15.5 | 16 GB RAM | 256 GB SSD AMD Ryzen 7 5700X | Sapphire Nitro+ RX 9060 XT 16 GB | 32 GB DDR4 3200MHz | Windows 11 Pro 24H2 (26100.4351) Windows 11 Pro on VMWare Virtual Machine (on Mac) Affinity Suite V 2.6.3 & Beta 2.6 (latest) Interested in a free (selfhosted) PDF Solution? Have a look at Stirling PDF No backup, no pity.
Blueart Posted November 4, 2022 Posted November 4, 2022 On 10/20/2022 at 11:16 AM, N.P.M. said: Hello, I have the same crash but do not have the Windows 10:KB5017262 update. Instead I have the KB5017500 update and the uninstall option does not appear on the update screen. https://ibb.co/FYPX87V https://ibb.co/FwKth8B Fabio Quote
LeiNi Posted November 4, 2022 Posted November 4, 2022 @Bluearft the Windows 10:KB5017262 should be a bit further down in the list. I had to manually look for it, too. Quote
Blueart Posted November 5, 2022 Posted November 5, 2022 LeiNi I cannot find the update windows10:KB5017262 update even in the list belowhttps://ibb.co/bKVYfj1 Quote
LeiNi Posted November 7, 2022 Posted November 7, 2022 @BluearftI now have the same problem as you, I don't have anymore the windows10:KB5017262, but Affinity starts crashing again. So I guess, I'll take @Komatössuggestion and edit the Affinity file. As it makes no sense to me to uninstall one culprit update after another. Hopefully, there will be an bug fix soon, as this is not really good advertisment. Quote
saladknown Posted November 16, 2022 Posted November 16, 2022 On 11/4/2022 at 1:35 PM, Komatös said: @LeiNi However, I recommend another solution, as the cumulative .NET updates also close security gaps in the .NET components, which are then reopened by the uninstallation. My preferred solution: Open the directory in which the Affinity programmes are installed. As a rule, C:\Programme\Affinity\(Desinger ...Photo ...Publisher) Search and open the .exe.config file (for example Designer.exe.config) with a text editor. Search for "<add key="IsVirtualizingStackPanel_45Compatible" value="true"/>" Replace the value true with the value false. Save the file (administrative rights are required to overwrite!) Thank you so much for this answer! I also could not find that update in my update history, and very much dislike the idea to just uninstall a bunch of updates. This fix worked flawlessly. Quote
rjav Posted April 7 Posted April 7 I have a 108 page image-heavy document. When I open it in Publisher 2.6.2, running on Windows 11, I am alerted to two linked files which need to be updated. When I open Resource Manager, the entire computer hangs and all I can do is switch off the power and start again. I decided to ignore the outdated files and proceeded to export a print quality PDF. It got about two-thirds of the way through and then crashed. After this happened twice, I just exported the first 54 pages but, doing the second 54, it crashed again. I then exported the next 27 and the final 27 and stitched the three PDFs back together in my PDF program (Kofax). I then tried to fix the linked images by splitting the afpub into two documents but Resource Manager still caused the app to hang. The Publisher file for the complete book is 9.184 megabytes and the complete PDF is 498.422 megabytes. The split files are about 4 and 5 megabytes. Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.