|
no declined updates.
i think , attempting a summary of the thread, that all of these are eliminated:
usb devices, usb port scans, networked drives, DLLs, AV interference... and I'm pretty sure we can add folder locations to that list.
some initial interaction between python and windows seems prime suspect still, partially fixed via the windows update cleanups...
re-reading the entire thread, it seems that several respected contributors have said, " I also see that , occasionally", which suggests program code , not PEBCAK
also that it has been around for a long time, at an almost annoying enough to need it fixed, but not quite, level.
e.g. I think I only get it after a cold start, which is rare, and knowing that its can happen there I tent to launch calibre before it's needed ,& just walk away until any freeze is over.
so yesterday it was because I'd shut down to swap out a case fan, not something I need to do daily!
because it's rare, I'd like to see to see a togglable progress log/debug option added to calibre, so that it reports OK so far to screen or to a timestamped log file at each step of launch, in order to help determine exactly where it stalls.
|