None of the Apps are starting

[BacMan12]

Tried to reinstall all the apps and reinstall any .net/Visual C++/DX Redistributables. Nothing seems to work. Can't find any list of what prerequisites Affinity apps are dependant on. When i launch them, the crash reports are blank

[v_kyr]

36 minutes ago, BacMan12 said:

Can't find any list of what prerequisites Affinity apps are dependant on.

On the Affinity website look under the "TECH SPECS" and there for Windows!

• Photo - Tech specs (look under Windows there)
• Designer -Tech specs (look under Windows there)
• Publisher - Tech specs (look under Windows there)

[BacMan12]

39 minutes ago, v_kyr said:

On the Affinity website look under the "TECH SPECS" and there for Windows!

• Photo - Tech specs (look under Windows there)
• Designer -Tech specs (look under Windows there)
• Publisher - Tech specs (look under Windows there)

Oh, okay so it needs nothing except hardware specs

It worked two days ago

[v_kyr]

22 minutes ago, BacMan12 said:

Oh, okay so it needs nothing except hardware specs

A critical factor on Win here, is very often the ...

Quote

 

Hardware GPU acceleration*

Requires:

- Windows 10 April 2020 update (or later)

- Direct3D level 12.0-capable card

 

... since not all GPU drivers work correctly here together with the Affinity apps in terms of OpenCL hardware acceleration. That has been often a cause for problems and app cores. Disabling an as default in Affinity apps enabled OpenCL hardware acceleration setting (under it's prefs) often helped here.

22 minutes ago, BacMan12 said:

It worked two days ago

Well then some app settings or Win updates might be the cause. Usually the Win systems or Affinity's crash reports would tell and give an indication/some hints here. But if none are generated it's hard to tell what the cause of all evil is.

[walt.farrell]

25 minutes ago, BacMan12 said:

It worked two days ago

What happened since then, that caused you to want to reinstall all of the applications?

Have there been any updates to Windows? What Windows version do you have (output from the winver command run in a command prompt might be useful)?

[BacMan12]

1 hour ago, walt.farrell said:

What happened since then, that caused you to want to reinstall all of the applications?

Have there been any updates to Windows? What Windows version do you have (output from the winver command run in a command prompt might be useful)?

I tried to reinstall because they aren't opening. Winver Windows 11 Home N version 21h2 (22000.318)
I've updated my GPU driver since last time

[walt.farrell]

What is version N of Windows 11, and how long have you been running it? Have the apps ever worked on it?

[BacMan12]

2 minutes ago, walt.farrell said:

What is version N of Windows 11, and how long have you been running it? Have the apps ever worked on it?

Version N is just without the media functions prepackaged, selected it by accident, but it works just like normal. The apps har worked just fine, except some problems with the sonic audio drivers(that is uninstalled now)

[mikeseese]

I'm on Windows 11 Pro Insider Preview (Build `22494.rs_prerelease.211029-1421`), with Affinity Designer `1.10.4.11998` and Affinity Photo `1.10.4.11998` and both applications open fine if I just run the application from the start menu. However, both of them will exit whenever I use `File -> Open` a afdesign/afphoto file or open the application via double clicking on an existing afdesign/afphoto file. When double clicking on an existing file (with the application closed), I do see the splash screen for the expected amount of time, but the full GUI never loads (and the exe finishes).

Just tried another thing, `File -> New` also closes the application (in both applications) after I push the Create button in the new wizard.

This bug was introduced in `1.10.4` as I know I had it working in `1.10.3` (because I only download updates when prompted after loading the application).

I've attached two Affinity Photo crash dumps (located in `%APPDATA%\Affinity\Photo\1.0\CrashReports\reports` if you see any as well @BacMan12 to see if you're having the same issue). One has a `-open` suffix in the file name where I double clicked on an aphoto file, and the other has a `-new` suffix where I did `File -> New` in Photo.

97b9b417-2594-4a4e-aab5-40ac64f79c1b-new.dmp3194e2c6-c3d3-4b7b-b8a2-968277f5555d-open.dmp

Any way we can download old versions of the applications? Edit: I found old installers in my downloads folder; seems that I have to uninstall the apps first to be able to backtrack, but I believe that should be fine.

Edited November 17, 2021 by seesemichaelj

[mikeseese]

Uninstalling both versions of `1.10.4` and installing `1.10.3` does not resolve the issue, which would indicate it may be a Windows 11 issue. I have a pending update that I will try to see if it fixes it.

[BacMan12]

14 minutes ago, seesemichaelj said:

Uninstalling both versions of `1.10.4` and installing `1.10.3` does not resolve the issue, which would indicate it may be a Windows 11 issue. I have a pending update that I will try to see if it fixes it.

Might be a Windows 11 issue, I've had some updates since last time i opened any Affinity app. But It's only Affinity apps that ain't working

[walt.farrell]

17 minutes ago, BacMan12 said:

But It's only Affinity apps that ain't working

Doesn't mean it's not a Windows issue, or a Driver issue.

Are you getting crash reports? Or is anything showing up in the Windows Event Log?

[BacMan12]

21 minutes ago, walt.farrell said:

Doesn't mean it's not a Windows issue, or a Driver issue.

Are you getting crash reports? Or is anything showing up in the Windows Event Log?

I'm getting dump files

a005d72c-a4b7-420f-a076-8a15c8647c99.dmp

[mikeseese]

Upgrading Windows 11 to the latest Insider Preview build (now `22499.rs_prerelease.211105-1550`) still has crashes happening for `1.10.3` and `1.10.4`. I'm not seeing any information in the Windows Event Viewer when the crashes happen.

Below is my `Log.txt` which show that OpenCL had issues creating a context. This just sounds like a compatibility issue with something new that got introduced in some Windows 11 (or accompanying driver) update.
 

[DXCore] Found 2 adapters
NVIDIA GeForce RTX 2070 SUPER
	Version: 30.0.15.1031
	IsHardware: Yes
	Supports D3D12 Feature Level 12.0: Yes
	HardwareID: PCI\VEN_10DE&DEV_1E84&SUBSYS_317338420000&REV_A1
	LUID: 0xE0DF
Microsoft Basic Render Driver
	Version: 10.0.22499.1000
	IsHardware: No
	Supports D3D12 Feature Level 12.0: Yes
	HardwareID: PCI\VEN_1414&DEV_008C&SUBSYS_00000000&REV_00
	LUID: 0xEE6F
[DXGI] Enumerating adapters
NVIDIA GeForce RTX 2070 SUPER
	HardwareID: PCI\VEN_10DE&DEV_1E84&SUBSYS_317338420000&REV_A1
	LUID: 0xE0DF
Microsoft Basic Render Driver
	HardwareID: PCI\VEN_1414&DEV_008C&SUBSYS_00000000&REV_00
	LUID: 0xEE6F
[OpenCL] Found 1 platforms:
Name: NVIDIA CUDA
	Vendor: NVIDIA Corporation
	Version: OpenCL 3.0 CUDA 11.6.0
[OpenCL] Found 1 devices for platform NVIDIA CUDA:
NVIDIA GeForce RTX 2070 SUPER
	Vendor: NVIDIA Corporation
	Version: OpenCL 3.0 CUDA
	Integrated: false
	Detachable: false
[OpenCL] Error 222 (810): Could not create context!
	Installed
TabletContext::Create: original queue size is 50
TabletContext::Create: new queue size is 128
Exit

Let me know if there's anything else I can try to help solve this issue since I can't use the applications. Thanks!

[walt.farrell]

1 minute ago, seesemichaelj said:

Let me know if there's anything else I can try to help solve this issue since I can't use the applications.

You could try disabling OpenCL, which can be done from Preferences, Performance if the application is getting that far.

If it's not getting that far, then either of these might help:

or

 

[v_kyr]

4 hours ago, BacMan12 said:

I've updated my GPU driver since last time

Well that highly indicated even without looking into the dump file, where the evil comes suddenly from. - Namely as mostly from that newer/updated GPU driver version, which seems to produce OpenCL issues for the Affinity apps now!

[mikeseese]

30 minutes ago, walt.farrell said:

You could try disabling OpenCL, which can be done from Preferences, Performance if the application is getting that far.

I was able to get to the preferences when opening the application via the Start Menu (aka without opening a file), and disabling OpenCL did work for both applications on `1.10.4`.

10 minutes ago, v_kyr said:

Well that highly indicated even without looking into the dump file, where the evil comes suddenly from. - Namely as mostly from that newer/updated GPU driver version, which seems to produce OpenCL issues for the Affinity apps now!

Agreed that an OpenCL issue would be related to a GPU driver. While I didn't explicitly update the driver, when I went back to check to just make sure, lo and behold, someone (NVIDIA or Windows) automatically updated my driver at some point to some 510 driver (which I'm guessing is a special Windows 11 build because Geforce Experience doesn't list anything over 500 as the latest versions).

Downgrading my NVIDIA graphics driver  (some unknown 510+ version shown in Geforce Experience) to the latest Geforce Studio Driver fixed my issues (after reenabling OpenCL in Affinity products).

 

Thanks @walt.farrell and @v_kyr for the help!

[BacMan12]

48 minutes ago, v_kyr said:

Well that highly indicated even without looking into the dump file, where the evil comes suddenly from. - Namely as mostly from that newer/updated GPU driver version, which seems to produce OpenCL issues for the Affinity apps now!

Okay, so I'll just have to wait for updates. Nothing seems to work

[walt.farrell]

2 minutes ago, BacMan12 said:

Okay, so I'll just have to wait for updates. Nothing seems to work

Have you tried disabling OpenCL?

[v_kyr]

3 minutes ago, BacMan12 said:

Okay, so I'll just have to wait for updates. Nothing seems to work

Did you tried disabling OpenCL as @walt.farrell told and pointed to above?

[BacMan12]

1 minute ago, walt.farrell said:

Have you tried disabling OpenCL?

 

Just now, v_kyr said:

Did you tried disabling OpenCL as @walt.farrell told and pointed to above?

Yes, didn't make any difference

[v_kyr]

I'm not on Windows, so can only partly look at what your dump file shows here via MacOS.  But AFAI recall on Win a crash 0xE0434352 can be anything .NET related here, mostly in the context of...

Quote

 

Issue:

.Net application code aborts before it starts its execution [Console application or Windows application]

Error received: Aborted with Error code "E0434352"

Exception: Unknown exception

Scenario 1:

When an application is already executed, which have used some of the dependent resources and those resources are still in use with the application executed, when another application or the same exe is triggered from some other source then one of the app throws the error

Scenario 2:

When an application is triggered by scheduler or automatic jobs, it may be in execution state at background, meanwhile when you try to trigger the same application again, the error may be triggered.

One would have to load your dump file via the VS Debugger or WinDbg in order to get more precise indication here. - Your Photo.exe related dump looks like this:

Quote

Operating system: Windows NT
                  6.2.22000 318
CPU: amd64
     family 25 model 33 stepping 0
     32 CPUs

GPU: UNKNOWN

Crash reason:  0xe0434352 / 0x00000081
Crash address: 0x7ff88808466c
Process uptime: 0 seconds

Thread 0 (crashed)
 0  KERNELBASE.dll + 0x4466c
    rax = 0x00007ff88807890a   rdx = 0x000000ae00020019
    rcx = 0x0000000000000000   rbx = 0x00000000e0434352
    rsi = 0x0000000000000001   rdi = 0x0000000000000005
    rbp = 0x000000ae711fec80   rsp = 0x000000ae711fe7d0
     r8 = 0x0000000000000428    r9 = 0xfffffffffffffffe
    r10 = 0x0000000000000524   r11 = 0x0000000000000000
    r12 = 0x0000000000004000   r13 = 0x0000024e8039be08
    r14 = 0x000000ae711fe968   r15 = 0x0000024e8039bd48
    rip = 0x00007ff88808466c
    Found by: given as instruction pointer in context
 1  KERNELBASE.dll + 0x4466c
    rbp = 0x000000ae711fec80   rsp = 0x000000ae711fe808
    rip = 0x00007ff88808466c
    Found by: stack scanning
 2  mscorlib.ni.dll + 0x1600000
    rbp = 0x000000ae711fec80   rsp = 0x000000ae711fe838
    rip = 0x00007ff853eb0000
    Found by: stack scanning
 3  clr.dll + 0xc5be4
    rbp = 0x000000ae711fec80   rsp = 0x000000ae711fe870
    rip = 0x00007ff853f75be4
    Found by: stack scanning
 4  System.ni.dll + 0x44552b
    rbp = 0x000000ae711fec80   rsp = 0x000000ae711fe878
    rip = 0x00007ff84fe0552b
    Found by: stack scanning
 5  clr.dll + 0xb4988
    rbp = 0x000000ae711fec80   rsp = 0x000000ae711fe880
    rip = 0x00007ff853f64988
    Found by: stack scanning
 6  clr.dll + 0xb4961
    rbp = 0x000000ae711fec80   rsp = 0x000000ae711fe8b0
    rip = 0x00007ff853f64961
    Found by: stack scanning
 7  System.ni.dll + 0x83bc0
    rbp = 0x000000ae711fec80   rsp = 0x000000ae711fe8e0
    rip = 0x00007ff84fa43bc0
    Found by: stack scanning
 8  System.ni.dll + 0xca60
    rbp = 0x000000ae711fec80   rsp = 0x000000ae711fe8e8
    rip = 0x00007ff84f9cca60
    Found by: stack scanning
 9  System.ni.dll + 0xca60
    rbp = 0x000000ae711fec80   rsp = 0x000000ae711fe938
    rip = 0x00007ff84f9cca60
    Found by: stack scanning
10  mscorlib.ni.dll + 0x1600000
    rbp = 0x000000ae711fec80   rsp = 0x000000ae711fe990
    rip = 0x00007ff853eb0000
    Found by: stack scanning
11  clr.dll + 0xb5e44
    rbp = 0x000000ae711fec80   rsp = 0x000000ae711fe9d0
    rip = 0x00007ff853f65e44
    Found by: stack scanning
12  System.ni.dll + 0x8ba8
    rbp = 0x000000ae711fec80   rsp = 0x000000ae711fe9d8
    rip = 0x00007ff84f9c8ba8
    Found by: stack scanning
13  clr.dll + 0x7e7740
    rbp = 0x000000ae711fec80   rsp = 0x000000ae711fe9e8
    rip = 0x00007ff854697740
    Found by: stack scanning
14  System.ni.dll + 0x8ba8
    rbp = 0x000000ae711fec80   rsp = 0x000000ae711fea00
    rip = 0x00007ff84f9c8ba8
    Found by: stack scanning
15  System.ni.dll + 0x8ba8
    rbp = 0x000000ae711fec80   rsp = 0x000000ae711fea08
    rip = 0x00007ff84f9c8ba8
    Found by: stack scanning
16  System.Configuration.ni.dll + 0x64b0
    rbp = 0x000000ae711fec80   rsp = 0x000000ae711fea40
    rip = 0x00007ff84e4964b0
    Found by: stack scanning
17  mscorlib.ni.dll + 0x63804a
    rbp = 0x000000ae711fec80   rsp = 0x000000ae711fea80
    rip = 0x00007ff852ee804a
    Found by: stack scanning
18  clr.dll + 0x7caab0
    rbp = 0x000000ae711fec80   rsp = 0x000000ae711feaa0
    rip = 0x00007ff85467aab0
    Found by: stack scanning
19  System.Configuration.ni.dll + 0x10fe1a
    rbp = 0x000000ae711fec80   rsp = 0x000000ae711fead0
    rip = 0x00007ff84e59fe1a
    Found by: stack scanning
20  clr.dll + 0xb5d75
    rbp = 0x000000ae711fec80   rsp = 0x000000ae711feb68
    rip = 0x00007ff853f65d75
    Found by: stack scanning
21  System.Configuration.ni.dll + 0x10fe1a
    rbp = 0x000000ae711fec80   rsp = 0x000000ae711feb80
    rip = 0x00007ff84e59fe1a
    Found by: stack scanning
22  System.Configuration.ni.dll + 0x53197
    rbp = 0x000000ae711fec80   rsp = 0x000000ae711febb0
    rip = 0x00007ff84e4e3197
    Found by: stack scanning
23  clr.dll + 0x5735
    rbp = 0x000000ae711fec80   rsp = 0x000000ae711febc0
    rip = 0x00007ff853eb5735
    Found by: stack scanning
24  System.ni.dll + 0x8ba8
    rbp = 0x000000ae711fec80   rsp = 0x000000ae711febc8
    rip = 0x00007ff84f9c8ba8
    Found by: stack scanning
25  System.ni.dll + 0x3365da
    rbp = 0x000000ae711fec80   rsp = 0x000000ae711febf0
    rip = 0x00007ff84fcf65da
    Found by: stack scanning
...
...

You can post it into the "Report a Bug in Affinity Photo" forum section, the devs can then take a look at it and tell you the cause of evil!

[BacMan12]

11 minutes ago, v_kyr said:

can be anything .NET related

There was a .Net update 5 days ago for windows 11. So might have to contact Microsoft...

[BacMan12]

51 minutes ago, v_kyr said:

You can post it into the "Report a Bug in Affinity Photo" forum section, the devs can then take a look at it and tell you the cause of evil!

Did this now

[RichardMH]

Are you running a tablet like a Wacom?