-
Posts
173 -
Joined
-
Last visited
Posts posted by spidermurph
-
-
3 minutes ago, Pauls said:
yes - you'll find them in the windows event viewer
I have the event viewer open could you please advise where I should be looking for you?
-
1 minute ago, Pauls said:
do you have an windows event log of a failed run up attempt we can investigate.
Is that different from the crash log?
-
18 minutes ago, Pauls said:
did you do a complete new install of windows?
Yes I did, No change I'm afraid.
-
I just tried downloading the Beta to see if that would work. But it does the same startup crash.
-
Does anyone know of any software that conflicts with Affinity?
I am trying to see if this is causing my issues.
-
17 hours ago, mopperle said:
Try the following:
- uninstall all Afinity apps
- reboot your PC
- create a new Windows Acoount (with administrative rights)
- install the Affinity Apps un der this new account.
I gave this a try and got the same results.
I also re-installed Windows in case something was missing or currupt. Still no luck.
-
Hi Otto
Thank you for your reply.
I hve checked my Microsoft Visual C++
I seem to have 28 versions of it the latest being Version 14.32.31326
Thank you
Murph -
I have taken time to check to see if any other programs will not load or have any trouble.
The answer is no. This laptop has many programs installed.
Adobe Creative Cloud with all apps
Corel Graphic Suite
Davinci Resolve
Topaz Gigapixel
Serif Plus Suite
And many more.
All of these programs work perfectly.
Which makes me wonder. Is there anything that Affinity 2.0 needs to run that could be missing from my laptop.
If anyone have any ideas I would love the help.
-
Was there any useful info in my crash report?
-
Here is the crash report if it helps.
-
Just tried the MS store version.
Same issue I'm affraid. Gets to the splash screen and quits.
-
Hi Lee
Thank you for helping.
The Spec of the laptop is:
CPU: Intel i7
GPU: GTX960
RAM: 16GB
1TB SSD (500GB Free Space)
OS: Windows 10 (all up-to-date)
Sure I'll give the MS App Store versions a try.
-
Sadly, this fix only lasted for about a day.
Now it's back to how it was. Every program works except Affinity.
If anyone has any advice it would love the help.
-
-
22 minutes ago, mopperle said:
So you tried the installation with the .exe installers?
Yes I did.
-
11 hours ago, v_kyr said:
Sounds like some Affinity apps persona interoperation problem, which then affects all apps here then, as far as all three are installed.
In my latest install attempt Publisher would not even load on it's own before I added the Designer and Photo.
-
I got a lttle excited today when I saw there was a 2.3.1 update.
Unfortunately they do not work for me. Tried the MSI and MSIX.
-
2 hours ago, v_kyr said:
Did you already tried with disabled OpenCL hardware acceleration as indicated above by Lee_T?
I did, Both the CTL launch and the --no-ocl
-
Hi Lee
Thank you for your reply.
I have gone between the two installers MSI and MSIX a couple of times already.
They don't seem to make a difference.
When I just install Publisher is seems to work. But as I add Designer and Photo, They all stop loading.
-
My issue is the same.
-
Did my Crash Report reveal any insight?
-
Hi Ron
Yes I'm running 2.3. From the 2.3 MSI/EXE.
Definitely Running the correct EXE.
-
-
Affinity v2 Apps Won't Launch in Windows 10
in Affinity on Desktop Questions (macOS and Windows)
Posted
Application: Publisher.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Runtime.InteropServices.SEHException
at <Module>.Serif.Interop.Persona.ColourProfileManager.LoadProfiles(Serif.Interop.Persona.ColourProfileManager*)
at Serif.Interop.Persona.Services.InteropService.Initialise()
at Serif.Interop.Persona.Application.OnServicesInitialised(Serif.Interop.Persona.Services.IServiceProvider)
at Serif.Affinity.Application+<OnServicesInitialised>d__100.MoveNext()
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
at System.Windows.Threading.DispatcherOperation.InvokeImpl()
at MS.Internal.CulturePreservingExecutionContext.CallbackWrapper(System.Object)
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 MS.Internal.CulturePreservingExecutionContext.Run(MS.Internal.CulturePreservingExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Windows.Threading.DispatcherOperation.Invoke()
at System.Windows.Threading.Dispatcher.ProcessQueue()
at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef)
at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame)
at System.Windows.Application.RunDispatcher(System.Object)
at System.Windows.Application.RunInternal(System.Windows.Window)
at Publisher.Application.Main(System.String[])
Is this the part you need?