Jump to content

Affinity Suite v2.5.0 run issues


Recommended Posts

Hi All,

I decided to reset my PC yesterday because I felt it was running slower than I liked and wanted to speed it up and just do some spring cleaning.

Upon logging back in to a clean version of Windows I reinstalled several programs I use and when it came to Affinity things got weird. I started up Designer and updated it (I was using the v2.1 installer at first, so it prompted me to upgrade to v2.5). Once done and it started I logged in, but then I closed it as I was not going to use it, I did the same for both Photo and Publisher. A few hours later I was going to work on a document so started up Publisher, the splash screen loads and gets as far as loading Fonts and then disappears. I sit waiting for it to load up but it never does, so I tried running it again and the same thing happens.

Checking Event Viewer I see the below error:

Application: Designer.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Runtime.InteropServices.SEHException
   at <Module>.PersonaController.LoadFontsAndPropertyCollections(PersonaController*)
   at Serif.Interop.Persona.Services.InteropService.LoadFontsAndPropertyCollections()
   at Serif.Affinity.Application+<>c__DisplayClass100_0.<OnServicesInitialised>b__1()
   at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
   at System.Threading.ThreadHelper.ThreadStart()

Source: .NET Runtime

Event ID: 1026

Level: Error

The first thing I do is go to Windows Update and check nothing is pending an install or failed, but its all fine. I check Programs and Features and no sign of .NET being installed, however Add Windows Features shows that v3.5 and v4 have components installed. The registry also shows entries and matches my laptop which still has the software installed on working fine.

I tried downloading .NET v4.8 but it said .NET was already installed. Running the Repair Tool also said it made 2 changes but still I have an issue. I reinstalled Windows all over again and the problem persists. I can find no solution online and all my other programs work fine, so unsure if this is a Windows/.NET issue or an issue with my Affinity software.

 

Kevin,
 

Link to comment
Share on other sites

Hi @KBerry and welcome to the forums. I believe this is a known issue with 2.5.0. Three suggestions.

Take a look at where your fonts are installed. Please see this new FAQ.

Or try the 2.5.2 beta and if that solves your problem use it until 2.5.2 is released:

Or uninstall 2.5.0 and install 2.4.2 until the final version of 2.5.2 is released:

 

Link to comment
Share on other sites

You legend, yes that's fixed the issue. That's very odd as having installed a fresh copy of Windows and installed a fresh copy of the Affinity programs, I'm lost as to how it would know there would be additional fonts. Either way I can access the software now so not that concerned.

Thanks

Kevin,

Link to comment
Share on other sites

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.