Hello,
from a time to now we are getting this message error when trying to open Pix4DMapper.
The application could not start correctly (0xc0000142).
Click OK to close it.
We reinstalled the nvidia drivers and Pix4DMapper and the application started fine, but when we turned off the computer and turned it on again the same error appeared.
Can anyone give us a clue as to what is going on and how we can fix it?
Greetings and thanks.
Hello @serpam , The error usually mean corrupted files or outdated software. Some of our user had the same issue previously, I recommend going through the below support article to fix it.
You can also try reinstalling the PIX4Dmapper software again following the steps explained in the below support article, if that doesn’t resolve your issue, try the steps explained in the above link.
How to completely uninstall PIX4Dmapper - PIX4Dmapper
We’re having this same issue, but with bafflingly inconsistent symptoms.
I have about 90 HP Z4’s with identical hardware and Win11 software loadsets. We’ve run Pix4Dmapper on these workstations for several years. Now, under Win11, it is a crapshoot whether Pix4Dmapper will start successfully on them, and equally unpredictable whether it will start again on the same PC after success on the 1st try and closing it. I tried 12 machines today, and the software started successfully on 9 of them, but only would start again after closing on 6 of those. The ones that would start twice could continue 4-6 times, at which point I stopped testing. Of the ones that only started once, or did not start on the first try, sometimes a restart would allow them to successfully open Pix4Dmapper.
I know the stock answer to this question is to make sure the NVIDIA drivers are updated and to try uninstall/reinstall, I’ve tried the former and it made no difference. And neither would seem to explain the intermittent nature of the problem. If the software needs to be reinstalled, or the drivers are out of date, it should just consistently not run. I can’t see why it would open sometimes and not others, on different or the same workstations.
Can someone there shed any light on this?
Thanks,
-pat