Scrivener don't open before one hour long

[Easily Distracted]

Oh my !
SpringfieldMH, THANK YOU.
I didn't think to force the compatibility to my own system... Feeling a little silly now. (It 's king of strange to force the soft to open with a window 7 compatibility on a windows 7 but well, it works !).

I'm so glad this soft works great again. Very very thank you all !

Wait. So SpringfieldMH's solution did it? If so, I hope there is a way to get it in the FAQ/Troubleshooting...

Good news!

[KingYami]

Wait. So SpringfieldMH's solution did it? If so, I hope there is a way to get it in the FAQ/Troubleshooting...
Good news!

Yay... Don't really know why you have to force the compatibility but well... It's working great right now. Don't have any lag or a not responding error again.

[Easily Distracted]

Awesome.

With these smart people, I knew you'd be back in business sooner or later!

[CASD57]

I go to TASK manager and it says it's running normal... but I don't see it ????

[dremalt]

Hello,
I'm having a very similar problem. It doesn't take an hour to load Scrivener on Windows 10, but it does take quite a while, and it is totally unpredictable.

The process is running in the background even when it doesn't appear to have started, and when I analyze the wait chain I always find that it is waiting on splwow64.exe. For me running Scrivener in compatibility mode doesn't help. I've tried reinstalling, reinstalling as an administrator and it hasn't changed the situation at all. Sometime running the program as an admin seems to make it load quickly, but I'm not sure if this is legitimate since it doesn't *always* hang when starting up.

However, another issue is the Scrivener will also hang when I search my document. It comes back eventually with my search results, but the bigger my docs get, the more I need to search, and waiting a minute each time isn't viable.

I should probably add that this only has been happening only on my new laptop, my old laptop (which is also Win 10) never had this problem, and hasn't since the few times I've used it.

Anyway, it has been a while since there have been any updates on this thread, but the issue is still happening. Does anyone have suggestions? Or could there be a known work around by now?