Bug 427883 - Fatal Error 126 - Unable to launch Krita - Windows 10
Summary: Fatal Error 126 - Unable to launch Krita - Windows 10
Status: RESOLVED NOT A BUG
Alias: None
Product: krita
Classification: Applications
Component: General (show other bugs)
Version: 4.4.0
Platform: Microsoft Windows Microsoft Windows
: NOR critical
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-10-17 17:29 UTC by aeweiker
Modified: 2020-10-17 19:10 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Error 126 After Attempting To Start Krita (103.58 KB, image/png)
2020-10-17 17:29 UTC, aeweiker
Details

Note You need to log in before you can comment on or make changes to this bug.
Description aeweiker 2020-10-17 17:29:56 UTC
Created attachment 132493 [details]
Error 126 After Attempting To Start Krita

SUMMARY

When I try to start Krita, I get this error message: "LoadLibrary failed with error 126: the specified module could not be found." 

It popped up a couple of days ago. I had to do a system rollback to a previous save point from a couple of days before that. I can't keep doing a system rollback every time this happens. No idea what is causing it. Really need a solution, if anyone knows what's going on. Can't start Krita at all. Already contacted Windows tech support. Went through all of their troubleshooting steps. The only thing that worked was the system rollback. Can't do a rollback every time this happens. Can anyone help me find a viable solution? Otherwise I'm going to have to scrap Krita altogether.

STEPS TO REPRODUCE
1. Click on Krita icon
2. Krita fails to initialize
3. Error message pops up

OBSERVED RESULT
Krita doesn't start. Error message pops up instead.

EXPECTED RESULT
Expect Krita to start running like normal.

SOFTWARE/OS VERSIONS
Windows: Windows 10 Version 2004
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
I attempted to change brushes for the first time a couple of days ago. That's the only thing that I did differently that day. Closed Krita. Tried to open it again a few minutes later and the error 126 popped up for the first time.
Comment 1 Halla Rempt 2020-10-17 18:05:58 UTC
I'm sorry, but this really isn't something we can fix for you. Your Windows installation is broken in one way or another. We could perhaps get a hint of what's wrong if you attach the %LOCALAPPDATA%\krita-crash.log file to this bug report, but I fear you'll have to reinstall Windows completely.
Comment 2 aeweiker 2020-10-17 18:21:00 UTC
(In reply to Boudewijn Rempt from comment #1)
> I'm sorry, but this really isn't something we can fix for you. Your Windows
> installation is broken in one way or another. We could perhaps get a hint of
> what's wrong if you attach the %LOCALAPPDATA%\krita-crash.log file to this
> bug report, but I fear you'll have to reinstall Windows completely.

How do I go about finding the crash log? It's not showing up in the search bar. I'm new to this kind of thing. Microsoft already had me update the Windows version. I take it that's not the same as a complete reinstallation.
Comment 3 aeweiker 2020-10-17 18:51:34 UTC
(In reply to Boudewijn Rempt from comment #1)
> I'm sorry, but this really isn't something we can fix for you. Your Windows
> installation is broken in one way or another. We could perhaps get a hint of
> what's wrong if you attach the %LOCALAPPDATA%\krita-crash.log file to this
> bug report, but I fear you'll have to reinstall Windows completely.

This is turning into a cascade effect. I now have SEVERAL programs that are failing to open. Most are giving me the error 126. This is also my first SSD computer, so I have no idea if that might have something to do with it. It looks more and more like it might be a hardware issue. Doing a factory reset to see if it fixes the problem.
Comment 4 Halla Rempt 2020-10-17 19:10:35 UTC
To find that file, press WINDOWS-r and type %LOCALAPPDATA% in the dialog that appears; press enter and Windows File Explorer will take you to the right place.

But yes, this really sounds like a problem with your computer. I'm going to close this report, but I do hope a reinstall fixes things. You might also want to check the SMART status of the SSD or run a memory checker application.