Fatal Error Message When Opening PI

[llpastro]

I just installed the new version of PI on a new computer (Win 10).  When I try to open PI it starts to open but after about 10 sec. I get the attached error message.  Can anyone direct me on what to do about this?  It installed fine on another Win 10 computer.  Thanks.

Larry Phillips

[Jan Porter]

I am having this issue as well - immediately following a Windows update on 10/12/17.

[Jan Porter]

Rebooted the PC and all came up fine.

[llpastro]

I tried that and it made no difference.  I hope someone with a lot of computer knowledge will be able to help me.

Larry

[wimvb]

I have that on my windows 8.1 computer as well. When I restart PixInsight after a first crash, it opens fine. I think it may be related to windows multitasking, as it happens more frequently when I just booted my computer, and some background processes may still be starting up.
For me it's just annoying.

[llpastro]

After having problems yesterday, I took your advice and waited a while before opening PI and it worked.  However, when I tried to download the updates I got another error message.  I then tried going to Resources/Updates and got the first attached error message.  I tried again and got the second error message.  I tried a third time and it allowed me to download and install the updates.  If anyone has an answer to this I would love to hear it.  But for right now, everything is working.

Larry

[llpastro]

Things still seem to be very fragile.  I installed a new script (LocalFuzzyHistogramHyperbolization) and decided to see if the error message would come back.  After closing and reopening PI the Fatal Error message came back.  I closed and restarted PI with the same error.  I restarted the computer and still got the same error.  I did a separate shut down and then a restart of the computer and after waiting 5 minutes, PI opened error free.  Frustrating to say the least.

Larry

[Terry Danks]

I had this problem on my Win 10 machine as well.
My 1TB HDD was about 78% full. When I reduced it to about 73%, the problem disappeared.
No idea why . . . but it worked in my case.

[llpastro]

Thanks for the feedback.  Unfortunately, my machine is only 38% full.

Larry