I believe this is more or less down to Copilot’s reason #1. Scrivener loads a bunch of stuff (technical term) at first launch; subsequent launches then pull from a cache.
If nobody with actual technical specifics happens along, you can possibly figure out the difference yourself between first and subsequent launches by enabling and studying the output from File > Options > General > Startup > Warnings > Show internal log console.
I doubt it!
However – If nobody comes along with something more elegant, something to try is
- Create a very lightweight Scriv project (empty except for 1 blank doc)
- Create a script that launches the LW project, waits the 20 seconds or whatever, then closes it
- Launch the script automatically at Windows startup
- Then, once your PC is up & running, you can press the magic button (you should be able to remove the 20 second wait)
Probably not exactly what you were looking for, but maybe it’ll give you ideas for something better?
Best,
Jim