Thank you for the suggestion!
This is the log it created:
Code:
calibre Debug log
calibre 4.11.2 [64bit] embedded-python: True is64bit: True
Windows-10-10.0.18362-SP0 Windows ('64bit', 'WindowsPE')
('Windows', '10', '10.0.18362')
Python 2.7.16+
Windows: ('10', '10.0.18362', 'SP0', u'Multiprocessor Free')
Interface language: None
Successfully initialized third party plugins:
calibre 4.11.2 [64bit] embedded-python: True is64bit: True
Windows-10-10.0.18362-SP0 Windows ('64bit', 'WindowsPE')
('Windows', '10', '10.0.18362')
Python 2.7.16+
Windows: ('10', '10.0.18362', 'SP0', u'Multiprocessor Free')
Interface language: None
Successfully initialized third party plugins:
Turning on automatic hidpi scaling
devicePixelRatio: 1.0
logicalDpi: 96.0 x 96.0
physicalDpi: 92.0150943396 x 91.44
Using calibre Qt style: False
[0.00] Starting up...
[0.00] Initializing db...
[0.01] db initialized
[0.01] Constructing main UI...
[1.95] main UI initialized...
[1.95] Started up in 1.95 seconds with 117 books
calibre 4.11.2 [64bit] embedded-python: True is64bit: True
Windows-10-10.0.18362-SP0 Windows ('64bit', 'WindowsPE')
('Windows', '10', '10.0.18362')
Python 2.7.16+
Windows: ('10', '10.0.18362', 'SP0', u'Multiprocessor Free')
Interface language: None
Successfully initialized third party plugins:
Traceback (most recent call last):
File "boot_com_servers.py", line 44, in <module>
File "os_integration\windows\shell_extension.pyc", line 33, in <module>
ImportError: No module named propsys
It crashed as expected and did show the same blank window as before.
Also, I somehow managed to recreate the 2nd error message, and although I couldn't take a screenshot or copy it, it indeed matched the log (it read
ImportError: No module named propsys, like the error at the end of the log).