You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have ensured my environment (operating system, app launcher, etc) is up to date
Operating System and Version
Mint 22.2
Launcher
Lutris (Recommended)
Launcher Installation
Flatpak (Recommended)
Other Install
No response
Wine Version
ElementalWarrior (Recommended)
Affinity Version
Latest on website
Desktop Environment
Cinnamon
Description
I have used both the old and new version to attempt to install Affinity and i always encounter the same error as above. Even when i actually install .NET V4.8 i still get the same error
I also had this problem when trying to install Affinity Canva. I clicked Yes a few times and ended up giving up because I thought it was a bug, but then I tried with Affinity Designer 2 and the same message appeared, but I accepted all the dialog boxes and the installation was successful.
I haven't tested this on Affinity Canva again yet.
I have this same problem using the V2 guide for Lutris, Lutris Flatpak (0.5.20), on Bluefin (43.20260217.1). I get the same error message as the OP. My logs are attached.
Clicking "Yes" to the dialog just opens the download link in the browser, before showing the dialog again. Clicking "No" does nothing, but the dialog shows again. Either way it's an endless loop at this point. Only way to abort is to kill Lutris.
I'm happy to help try and debug this, if there are any suggestions on things to try.
I managed to install Affinity Canva this time. The Xalia installation prompt appeared four times, but I just accepted it each time it appeared and the installation continued.
After that, it may seem like nothing is happening, but you should check that there are no Wine-related processes running in your task manager.
The system used was CachyOS, installation method Lutris flatpak + ElementalWarriorWine.
@johninside Thank you. I gave it another shot and had the same error messages as you. I just closed the messages each time they popped up (four times each) and it eventually finished installing and I was able to start the application.
I suppose a temporary fix for now would be just to note this in the installation guide?
Also currently trying to reinmstall it, cause the installation i had stopped working with some error i wasnt able top fix or understand and also running in those errors, im on cachyos und tried with the ew script, though for me im also running in another error the the uninstaller cant be fund and then some fancy registry ids. and sadly it stops then and doesnt finish.
If it loops indefinitely instead of eventually finishing (rather than stopping after a handful of clicks), cancel and retry the install rather than leaving it running, that usually means something else went wrong upstream of this step.
Activity
kroltan commentedon Mar 2, 2026
I see the same issue, CachyOS (Arch) latest, Lutris from package manager. On both EW and TKG install scripts.
johninside commentedon Mar 7, 2026
I also had this problem when trying to install Affinity Canva. I clicked Yes a few times and ended up giving up because I thought it was a bug, but then I tried with Affinity Designer 2 and the same message appeared, but I accepted all the dialog boxes and the installation was successful.
I haven't tested this on Affinity Canva again yet.
chanceymathews commentedon Mar 10, 2026
I have this same problem using the V2 guide for Lutris, Lutris Flatpak (0.5.20), on Bluefin (43.20260217.1). I get the same error message as the OP. My logs are attached.
Clicking "Yes" to the dialog just opens the download link in the browser, before showing the dialog again. Clicking "No" does nothing, but the dialog shows again. Either way it's an endless loop at this point. Only way to abort is to kill Lutris.
I'm happy to help try and debug this, if there are any suggestions on things to try.
lutris-affinity.log
johninside commentedon Mar 10, 2026
I managed to install Affinity Canva this time. The Xalia installation prompt appeared four times, but I just accepted it each time it appeared and the installation continued.
After that, it may seem like nothing is happening, but you should check that there are no Wine-related processes running in your task manager.
The system used was CachyOS, installation method Lutris flatpak + ElementalWarriorWine.
chanceymathews commentedon Mar 12, 2026
@johninside Thank you. I gave it another shot and had the same error messages as you. I just closed the messages each time they popped up (four times each) and it eventually finished installing and I was able to start the application.
I suppose a temporary fix for now would be just to note this in the installation guide?
AlphaCraft9658 commentedon Mar 23, 2026
The setup worked just fine for me, but it fails for my friend and the xalia initialization just fails. Several times. Then the script halts.
achhandrian commentedon Apr 25, 2026
Also currently trying to reinmstall it, cause the installation i had stopped working with some error i wasnt able top fix or understand and also running in those errors, im on cachyos und tried with the ew script, though for me im also running in another error the the uninstaller cant be fund and then some fancy registry ids. and sadly it stops then and doesnt finish.
install log ew script.txt
Gamedirection commentedon Aug 22, 2026
This prompt is a known, cosmetic .NET initialization quirk during the dependency-install step, it's not fatal. As johninside and chanceymathews both confirmed, clicking through it each time it reappears (usually 3 to 4 times) lets the installer continue and finish normally. We've documented this here: https://github.com/seapear/AffinityOnLinux/wiki/Install-Guide-Lutris#repeated-xaliaexe-net-framework-initialization-error-prompt-during-install
If it loops indefinitely instead of eventually finishing (rather than stopping after a handful of clicks), cancel and retry the install rather than leaving it running, that usually means something else went wrong upstream of this step.