Bug 383297

Summary: Krita 3.1.4 installer for Windows crashes
Product: [Applications] krita Reporter: hopland <THORHOP>
Component: GeneralAssignee: Krita Bugs <krita-bugs-null>
Status: RESOLVED WORKSFORME    
Severity: crash CC: alvin
Priority: NOR    
Version: 3.1.4   
Target Milestone: ---   
Platform: Microsoft Windows   
OS: Microsoft Windows   
Latest Commit: Version Fixed In:
Attachments: Windows 10 Event log ID 1000 0x57956397

Description hopland 2017-08-08 22:40:06 UTC
Created attachment 107166 [details]
Windows 10 Event log ID 1000 0x57956397

The installer for Windows crashes when reaching the license agreement stage, giving the exception 0xc000041d, which I Googled and found that it translates to STATUS_FATAL_USER_CALLBACK_EXCEPTION (supposedly it's due to early threat created by the app).

I'm running Windows 10 build 15063. The install was attempted before and after  having run sfc.exe /scannow and Dism.exe /Online /Cleanup-Image /CheckHealth.

This is an issue with the installer, as Krita portable runs just fine.

NOTE: Eventlog provided is in Norwegian. The information is there, though.
Comment 1 Alvin Wong 2017-08-09 07:41:54 UTC
I am inclined to believe this is caused by some external process hooking the installer with bad code or injecting some bad DLLs, or that some application installs messed up (e.g. ms office).

The installer we use is a fairly standard NSIS-based installer (not so standard compared to MSI installers, but NSIS is still widely being used), mostly unchanged since Krita 3.0 (which is more than a year ago), and there hasn't been any reports of similar errors in the past. There also isn't any search results related to NSIS regarding the error, so I wouldn't think the installer is to be blamed.

The error happens in RichEd20 which is the rich-text editor control that NSIS uses to show RTF license texts. You might not get the same error with other NSIS-based installers that uses only plain-text license texts, but I bet you'll get the same crash for other NSIS-based installers that _do_ use RTF license texts. Perhaps you can try running the standalone Krita shell extension installer.

Anyway, I don't think much can be done on our side about this other than trying to update the version of NSIS used to make the installer, which is probably not going to change anything according to their changelog.