Quote:
Originally Posted by KevinH
That is good to hear. At least we know what is going on. BetterRed is much better at understanding how to manually enable or disable extensions on your Windows system.
BetterRed, what is the best way or tracking down the extension or program that is giving Sigil such trouble?
|
Here you go
Getting into and out of so called Windows Safe Mode can be a PITA, and you don't have any selective control over what 3rd party programs are excluded from automatic startup, and sometimes programs are not excluded.
If you have a problem with Program A (e.g. Sigil) in Normal Mode but its OK in Safe Mode, a possible cause is that some third party software is interfering with Program A. So how to find out which one(s)? The first thing of course is to shut down any other 'regular' programs you previously started - browsers, editors, spreadsheets etc - i.e. the things you start from the desktop, what ever.
You've probably already done that, so we come to the programs that get started automatically when you boot. CCleaner is the only tool I know of that gives you control over 3rd party (i.e. non-MS) tasks that are started automatically - and is easy to use.
Latest version is here ==>>
Download CCleaner 5.54.7088 for PC Windows - FileHippo.com
Select the Tools icon on the far right, then the Startup tool and you'll see three tabs - Windows, Scheduled Tasks, and Context Menu. My experience is that the culprit is most likely to be found in the Windows or Context Menu tabs. So select everything from those lists whose absence won't kill your system (the Publisher and File columns are the best guide) and press the Disable button (over on the right)
Now restart - and try running Sigil for as much time as you see fit, hopefully it will run fine. The goal now is to narrow the candidate culprits down to a manageable number (IMO 7 or less)
I would re-enable the top half of the Windows list, restart and test again, if Sigil does NOT run OK then the culprit is in the top half of the Windows list - now you can stop and start them manually to determine which task is causing the trouble. If Sigil ran OK, re-enable the bottom half (leave the top half enabled), restart and test again.
If Sigil runs OK with all the Windows tasks started then repeat the process on Context menu tasks.
Once you narrow it down to a manageable number (7 or less) you will probably be able to hazard a guess which program is creating the problem. But sometimes when diagnosing these sort of problems the least expected candidate can fall out as the rogue program.
BR