MobileRead Forums - View Single Post - Sigil won't start on new Windows 10 laptop

DiapDealer · 05-25-2021, 05:12 AM

The Python _ssl.pyd errors are almost certainly relevant. Regardless of whether the times don't match up with Sigil not working, there should be no errors in the Windows events log related to Sigil. Sounds to me like the Sigil update check is silently crashing. That could very well be early enough in the launch process to explain why no new Sigil.ini is created after renaming it.

Two possibilities come to mind: 1) a process is being blocked by a firewall application 2) another program you have installed has somehow exposed a version of openssl that is incompatible with Sigil's Qt (though I don't think the latter is likely since Sigil long ago offloaded the update check to an embedded python routine precisely to avoid crashes due to incompatible openssl libs being on the PATH on Windows systems).

Can you post the exact error message you're seeing regarding _ssl.pyd?

05-25-2021, 05:12 AM	#10
DiapDealer Grand Sorcerer Posts: 28,614 Karma: 204624552 Join Date: Jan 2010 Device: Nexus 7, Kindle Fire HD	The Python _ssl.pyd errors are almost certainly relevant. Regardless of whether the times don't match up with Sigil not working, there should be no errors in the Windows events log related to Sigil. Sounds to me like the Sigil update check is silently crashing. That could very well be early enough in the launch process to explain why no new Sigil.ini is created after renaming it. Two possibilities come to mind: 1) a process is being blocked by a firewall application 2) another program you have installed has somehow exposed a version of openssl that is incompatible with Sigil's Qt (though I don't think the latter is likely since Sigil long ago offloaded the update check to an embedded python routine precisely to avoid crashes due to incompatible openssl libs being on the PATH on Windows systems). Can you post the exact error message you're seeing regarding _ssl.pyd? Last edited by DiapDealer; 05-25-2021 at 05:19 AM.