Author Topic: Pixinsight.exe - Bad Image Message  (Read 2525 times)

Offline niteman1946

  • PixInsight Addict
  • ***
  • Posts: 234
Pixinsight.exe - Bad Image Message
« on: 2017 October 23 09:04:24 »
Hi Group,
I suspect this issue has been discussed before, my apologies if so.

I tried to start PI this morning for processing.  I received the "Pixinsight.exe - Bad Image" warning (see the Dropbox attachment).  Each time I try to open PI, this message comes up twice.  And PI does not start.

My computer was installed and commissioned in December 2016.  Below version of PixInsight installed at that time.
1.  Computer
   a)  Desktop:  Dell XPS8910 Desktop, Intel (R) Core i7-6700 CPU @ 3.40ghz, 16 gb ram
   b) Graphics:  AMD Radeon RX480 w/ 8gb GDDR5 memory
   c)  OS:  Win 10 Home, 64bit, v1607, build 14393.1770

2.  PixInsight v1.8.4.1195

I find that Microsoft did an update to the computer last night (see Dropbox image, attached).

Here are the options I'm aware of to get things back up and running.
1.  Uninstall and then re-install PixInsight v1.8.4.1195 as per the text on the warning, or if that doen't work .....
2.  Roll back the latest upgrade of Windows, or if that doesn't work ..... ?

Any suggestions and guidance would be appreciated.
Thanks,
Mark

https://www.dropbox.com/sh/7l2f9df243l0v43/AACrRyy_6dBaj4xdngoiV5JCa?dl=0


Offline niteman1946

  • PixInsight Addict
  • ***
  • Posts: 234
Re: Pixinsight.exe - Bad Image Message
« Reply #1 on: 2017 October 23 11:47:02 »
As I look a bit closer, I see that the error message(s) are referring to three (3) separate files.  These are:
1.  Qt5PrintSupport.dll
2.  QT5WebKit.dll
3.  Qt5WebKitWidgets.dll

And all three of these show to have "zero" file size on my home desktop installation. (i.e. the one used for processing).

I do have the same version of PI installed on my observatory desktop, and there PI is still functional.  Those three files on the OBS computer show various file sizes (not zero).

What would be the advice on swapping out the functional files for those with "zero" size?

Thanks,

Mark


Offline niteman1946

  • PixInsight Addict
  • ***
  • Posts: 234
Re: Pixinsight.exe - Bad Image Message
« Reply #2 on: 2017 October 24 04:18:21 »
Any thoughts on this before I start stumbling through it?

Thanks,
Mark

Offline Juan Conejero

  • PTeam Member
  • PixInsight Jedi Grand Master
  • ********
  • Posts: 7111
    • http://pixinsight.com/
Re: Pixinsight.exe - Bad Image Message
« Reply #3 on: 2017 October 24 04:50:20 »
Hi Mark,

Quote
What would be the advice on swapping out the functional files for those with "zero" size?

Run the installer package again and select the repair option. However, most likely the same problem will happen again if you don't change anything else. This has already been reported. Quoting myself from the linked bug report thread:

Sorry, but these problems are completely out of my control. All executable files in the PixInsight distribution, including all .dll files, are digitally signed with our EV code signing certificates on Windows and macOS. They are guaranteed to be valid when the application is installed. If they become damaged (because other applications and/or your operating system alter them), that's something I cannot change or control in any way.

It looks like these problems are happening after recent Windows updates. As I've said, there's nothing I can do to help with this.


Juan Conejero
PixInsight Development Team
http://pixinsight.com/

Offline niteman1946

  • PixInsight Addict
  • ***
  • Posts: 234
Re: Pixinsight.exe - Bad Image Message
« Reply #4 on: 2017 October 24 14:25:51 »
Thanks Juan, appreciate your response.  I know you are busy.

I ran the v1.8.4.1195 installer and did not remove the existing version, expecting to encounter a "repair" option. 
No repair option, but '1195 installed and PI ran fine for about 3 shutdowns and computer reboots.  Then the same problem occurred.

Rather than doing another install, I then replaced the three dll files mentioned in my earlier post with those from my other computer.  Again PI ran for a few shutdown cycles before the problem re-occurred.  That is as long as it was up and running, all was fine.

I have no doubt that what you say is true, and the problem is in the MS updates.  My workaround until something better comes along is to continue to replace the three dll files.

If anyone has a less cobby workaround, I would appreciate hearing it.

Mark