RayCFrog

Nope. Nobody had pointed it out to me before. I can't be bothered to try uninstalling and going through the post's suggestions; I'll see what happens next time. The move option was useful, though - I didn't know that existed. Thanks. A couple of things: The link in that FAQ that matches my issue ("App didn't start") says that this can happen if App Installer is not installed, and gives no other reason. App Installer was installed on my system (and up-to-date) but I still got the problem. Workarounds are fine, but solutions are better, so I repeat my earlier question, is anyone actually looking for a solution for this? Thanks.

I guess no-one's looking at this thread, so I guess no-one's looking at the problem. Not very good, Affinity.

Has this issue been fixed yet? I need options such as installing to a different folder, which I don't get with a Microsoft Store install.

The apps downloaded from the Microsoft Store seem to work fine. Would still like the .msix fixed though.

Hi Lee, As it says in my original post, I'm using Windows 11 22H2. That's later than "Windows 11 or Windows 10 May 2020 Update (2004, 20H1, build 19041)", I believe. The link you supplied for the App Installer gives me "Invalid Product ID". I haven't tried the Microsoft Store versions. I shall do so now. Thank-you.

When I try and execute the .msix installer for any of the V2 products, I get an error message saying "The app didn't start". Tried rebooting, no difference. sfc /scannow found no issues. The event log has the following info: Faulting application name: AppInstaller.exe, version: 1.18.2209.26001, time stamp: 0x6332366c Faulting module name: ucrtbase.dll, version: 10.0.22621.1, time stamp: 0xf5fc15a3 Exception code: 0xc0000409 Fault offset: 0x000000000007f61e Faulting process ID: 0x0x6C0 Faulting application start time: 0x0x1D8F4FCB1AB3F5D Faulting application path: C:\Program Files\WindowsApps\Microsoft.DesktopAppInstaller_1.18.2691.0_x64__8wekyb3d8bbwe\AppInstaller.exe Faulting module path: C:\WINDOWS\System32\ucrtbase.dll Report ID: 68b3039a-76ba-4fb9-9e64-825e09583cd5 Faulting package full name: Microsoft.DesktopAppInstaller_1.18.2691.0_x64__8wekyb3d8bbwe Faulting package-relative application ID: App Edition Windows 11 Pro Version 22H2 Installed on ‎08/‎10/‎2022 OS build 22621.525 Experience Windows Feature Experience Pack 1000.22634.1000.0

Faulting application name: Photo.exe, version: 1.10.5.1342, time stamp: 0x62227da7 Faulting module name: ucrtbase.dll, version: 10.0.22000.1, time stamp: 0x00e78ce9 Exception code: 0xc0000409 Fault offset: 0x000000000007c648 Faulting process ID: 0x2f38 Faulting application start time: 0x01d8a1aaf125107f Faulting application path: D:\Program Files\Affinity\Affinity Photo\Photo.exe Faulting module path: C:\WINDOWS\System32\ucrtbase.dll Report ID: 22850ce5-5994-4808-8f25-56073a6e47c6 Faulting package full name: Faulting package-relative application ID:

Upload finished.

On its way. Gonna take about 4 hours with my broadband. I'll let you know.

You've certainly got a lot further than I did, so I don't see the value in struggling through the remainder - it's obviously not a simple capacity issue. The files are stored locally. In terms of drives, if that makes a difference, AF is installed on my "D:" drive, not my "C:"; the .cube files are stored on my "J:" drive. All of these are local, and physically inside the PC. If the LUTs are stored in the adjustments.propcol file, is it worth me uploading that to you to see if there's something strange happened to that?

Hi @Callum. I've uploaded all my .cube files to the link you supplied. In case it makes a difference, I have AP's RAM limit set at 32GB.

How about I upload the adjustments.propcol file? Would that give you the same info?

Hi Callum, there is no individual LUT file that causes the problem. As I said, after it crashes, I can successfully import the file(s) it crashed on before. Have you tried it after importing circa 4000 LUTs into around 150 categories? 'Coz that's my current situation. I think it's size-related, so just importing the same 20 or 30 LUTs into a couple of hundred different categories should do the same thing. I'm not sure there that much value in me sending you the 4000+ LUTs I currently have imported, and I'm not sure that would be within the terms of my licence anyway.

3.55 GB (3,818,082,668 bytes)

Unfortunately no. Although I told VS to break on just about any exception, it doesn't catch it, so no stack trace. It does seem that, when it's about to crash, it takes longer to import the LUTs than when it doesn't crash, and I'm thinking a loop at this point (which would fit with a stack overflow). I tried to get VS to pause the process when I thought it was about to crash, to get a stack trace at that point, but either I got to it too late or VS just couldn't do it. I might try a couple more times and see if I can get any useful info.

It doesn't produce a dump, unfortunately. If I run it under Visual Studio debugger, the crash appears to be an 0xc0000409 exception (which I think is STATUS_STACK_BUFFER_OVERRUN).

I have around 30,000 LUTs arranged in some 500 categories, and am trying to import them into Affinity Photo (I won't go into just how painful AP is making this process - other posts have described the issues around LUTs and their import and use in AP). I've imported around 5 or 6 thousand in about 100 categories ok, but now AP is crashing when I try to import. It doesn't crash every time, but when I go through the rigmarole of "Create new category", "Rename category", "Import", it will crash maybe every third time. I restart it and reimport the same file(s) it crashed on, and it works ok, and then crashes on a later import, which works ok the second time, only to crash on a later import,... This is very painful. Affinity Photo 1.10.5.1342. Windows 11 x64. 64GB memory. Intel i9-9900K. Nvidia GTX 1080ti.