I probably should have limited this reply to one paragraph and will likely regret it, but here we go. Hope it is of some assistance.
I would suggest that you each, individually, report the problem you are experiencing to Literature & Latte’s technical support, via email, as discussed here:
They may be swamped, what with NaNoWriMo and holidays, but I’m sure they’ll get to you.
If you haven’t already done so, you might consider seeing if compatability settings will help…
scrivener.tenderapp.com/help/kb … y-settings
If you are using a cloud backup/sync service, you should review the Cloud Syncing articles here…
That said, a few comments from a cranky old burned out retired technical support person with a couple of decades experience in Windows PC/network deployment and support…
Plain and simple, the fact that one experiences a problem with a given application, such as Scrivener, does not prove or guarantee the problem is in the given application. It is as much or more likely that the problem is in the environment on the PC that that the app is running on.
As far as the app itself, one can uninstall it, then download a fresh copy and reinstall from it, which may help. A previous download or install might have gotten corrupted or something on the PC may have corrupted the installed version later.
As far as the environment on the PC, that gets trickier.
There are legitimate packages (antivirus, …) that can interfere, unless tweaked. And there are illegitimate and/or poorly implemented apps and updates that can interfere. Changes happen on PCs for a variety of reasons, often without the user’s intent or knowledge.
Trying to sort through possible causes gets complicated. If you know or can afford a knowledgeable PC tech with a good track record, consider getting them involved.
A review of Windows event logs may turn up something. Responsible well written apps report problems and details there.
A review of the installed programs list may turn up something. What are they? Are they needed? Simplify the environment as much as possible.
A review of programs being launched behind the scenes at Windows startup may turn up something. Read up on using the msconfig utility, regarding checking its Startup tab to see what all is being started, and temporarily disabling such, in order to rule them in or out as likely suspects. Likewise, read up on rebooting/restarting Windows in safe mode or diagnostic mode (in which all that extra stuff is not started) so as to see how Scrivener works without all the extra/optional stuff running.
Words/phrases worth searching for, both on the Literature & Latte forums and the Internet in general, to see what causes and fixes have proven to be, include freeze, antivirus, keylogger, not responding, msconfig, safe mode, etc.
The issue of an app that is experiencing problems not being killable via Task Manager’s End Task command is generic, not specific to Scrivener. A Google search on “end task not working” turns up discussions of this happening with a variety of apps. Two examples, with relevant quotes follow. You’ll also find discussions of techniques and utilities that can probably succeed in killing such tasks that End Task can’t handle.
stackoverflow.com/questions/4998 … in-windows
“If it doesn’t go away, it’s currently locked waiting on some kernel resource (probably a buggy driver)”
blogs.msdn.com/b/oldnewthing/arc … 83787.aspx
“A process only goes away when all I/O requests it issued are completed or canceled. A buggy driver can hold an I/O request indefinitely and not support CLEANUP. This will prevent the process’ address space from being destroyed.”
Leaping to conclusions and getting self righteous is easy. Getting results, not so much.
Six reports in this thread of this sort of a problem does not constitute “everyone” and does not necessarily reflect on Scrivener.
In my case, I’m running Scrivener 220.127.116.11 on Windows 10 Pro (64 bit), currently without any issues. A few weeks back, I had a couple of days during which I had to try to launch Scrivener multiple times before it would finally start successfully and present the project I’ve been working on for several months. The problem went away, so I didn’t get around to digging into what was going on. It could be Scrivener, but it’s more likely one the numerous other apps or utiities present, their interaction, malware, intermittent hardware issue (RAM, hard drive), general build up of crud, … was at fault.
If you follow Mac forums, you’ll find the same issues exist in the Mac world, too.