Startup Log file for Spyder ?

[Rich Lysakowski]

Is there a log file created whenever Spyder starts up?   Or debug mode that shows everything that happens when starting up an instance of Spyder?

I have two environments (out of 10 installed) which I corrupted by interleaving conda and pip package installations.  If I could examine a log file that would help me see what startup steps are completing successfully and at what step the startup fails. 

My issue is that I corrupted my Base environment by interleaving the use of pip and conda repeatedly.   Now when I try to start Spyder, it does not finish the startup process and displays the message "#QWidget: Must construct a QApplication before a QWidget".

#############################################

I posted this to the Spyder-IDE github page too.  

#############################################

"I am still debugging this problem. My development is not dead in the water, because I have multiple environments where Spyder is still working fine. My BASE environment is one of 2 or 3 environments where Spyder won't start completely. I have projects in about 10 environments at various stages of developments, so I am reluctant to remove and reinstall Anaconda completely. I don't know how to EASILY (automatedly) preserve / reinstall or recreate all my projects and environments once Anaconda is removed. I am lazy and stubborn and want to fix my existing Anaconda installation (if possible.) But having a corrupted BASE environment bugs me because I like doing most things in BASE and only use custom environments for "riskier" projects where I anticipate package dependency problems.

If I compare the behavior of the "bad" environments where Spyder fails to start completely, I see several packages loading during the splash screen, but not all packages finish loading in the Splash screen. I also monitor the Windows Task Manager to see two new Python kernels start and stop running (two Pythonw.exe processes). The Splash screen shows messages:
0) "Initializing"

1. "Starting Code Completion Manager"...
2. "Loading Help"

For the environments where Spyder starts up fine I see
0) "Initializing"

1. "Starting Code Completion Manager"...
2. "Loading Help"
   ...
3. "Loading iPython"
4. "Loading Projects"
5. "Loading Variable Explorer"
   ... etc. (The rest of them flash by so fast I cannot read them all.

This brings me to ask if there is a "Startup Log" or Debug Mode" in Spyder that I can use to see where all the steps that happen when it starts successfully and when it fails to startup completely? "

##############################################

Is there a way to turn on some type of a "tracelog" process in Windows 10, or a "non-silent" startup process to see every scripts and every line that executes during a startup of a series of scripts like Python and Spyder inside Anaconda?