Version 1.9.8 loads slowly for me also on Windows 7 Home Premium. Ctrl-left does not work as expected - even after resetting and re-assigning in options, which may indicate some problem with a library or a component,
Running a Windows 8.1 (i3 core) with Scrivener, made the update last night and switched off. Next morning I’ve had the Unresponsive freeze for about 5 minutes and shut it down out of frustration. It might work after a longer wait, but I’ve downgraded as per the suggestions to run with Scrivener 1.7 and now that I’ve installed it, it loads straight away.
I’ll roll with whatever works, but I wouldn’t have updated after reading the message boards! 
I’m having the same problem today on Win7 Pro. I updated yesterday and today Scrivener won’t open. At first the software would try to open and then hang at about 79% complete and after several minutes, if I hovered over the header bar, windows would tell me the software isn’t responding. Now it’s gotten to the point that when I try to open Scrivener, I get an error message talking about a font not loading. Windows Task Manager shows Scrivener is actually running and using about 800k of memory but there is nothing on either monitor, nor does the icon in the tray light up to indicate the software is running. The memory usage starts at about 1600k and then dwindles after 30 seconds or so to 800k and hangs there. I just downloaded and reinstalled v1.9.7 and it opens right up, so I’ll use that until the problem with the newer version gets figured out.
I have the same trouble: newest Scriv just doesn’t open and worse, makes everything slow in my PC. Things like connect to FFox to report the issue.
Ooops, Chrono: 10 minutes to open, finally. Anyway, I’ll try to get back the older version from release notes.
I’m operating a Windows 7 and, sorry to say, that’s the last call to use Scriv for my works.
And another one. 1.9.8 does not open on either Win 7 Pro or Win 10 Pro. The process starts and then just hangs with no UI appearing. Left them both for over an hour but nothing happened. Have gone back to 1.9.7 which still works perfectly.
You need to pull this update until it is fixed or you will have an army of very unhappy customers!
I tried installing the previous version but getting the same error. I changed the file where the saves are made too and it works ok now, but I am not sure which version is the one that is working.
After the update wouldn’t took forever to start and seemed sluggish, It gave me a font missing error on start up, which was strange as it said that the font that missing was Calibri.
I wondered if that was supposed to be a joke?
Anyway, I d/l 'd the one from the release notes page, but performance was just as bad.
Finally, I re-installed 1.9.7 and it’s again running without any issues and loads normally.
-B
update totally broke scrivener on my win7 ultimate machine. downgrade works except i have to disable the update prompts.
also, to anyone coming here and thinking that they’ll just register for the forums to helpfully chime in “me too” so that maybe literature & latte will actually address this problem – the process took me 36 hours and i get the feeling scrivener doesn’t want people to be able to register and complain about broken updates like this.
This most recent update blew me out of the water, too. I’m on a Windows 7 Ultimate platform. I’ll not try updating the Windows 10 system until this is resolved.
When I ran the update, Scrivener wouldn’t launch. Instead, it showed up in the background processes. At one point it did make an attempt to function normally when I clicked on a project in my save folder, but I got a message that there was a problem with a font – oddly one not on my system – said it was ignoring the font, then . . . nothing.
I took the advice of reinstalling the last version and it’s now working. I hope the problem can be found and sorted. There are a couple features that were previously working that aren’t now.
Windows 10 Home 1709
The 1.9.8.0 version takes much longer to open. A project that use to open instantaneously, now takes precisely 45 seconds. Another one that used to open in 2-3 seconds now takes a minute and a half. Otherwise, I don’t experience any other issues.
Something is definitely wrong.
The main difference between the 1.9.7 and 1.9.8 builds is that a few libraries were updated internally for a third-party converter we use, so at the moment I’m guessing that’s what’s causing the problem on some people’s systems. We’ve seen before some cases where antivirus or other security software will flag Scrivener or components of it following a new release because the new version is not “trusted” by enough users yet, with the result that Scrivener will hang on startup or chug along a lot more slowly. If any of you are running security software, please try whitelisting Scrivener and its files, or temporarily disable the software to see if Scrivener will run more smoothly. Particularly if you notice that any files have been quarantined, you may need to reboot and reinstall Scrivener after whitelisting it.
If that doesn’t seem to help at all, we’d appreciate if some folks could go through the following steps to get us more information on what’s happening on the system when trying to launch Scrivener. You’ll need to have administrator privileges for installing the Windows debugging tool (you should be able to just enter the admin password when prompted, if you’re running as a standard user, or you can right-click the installer and choose “Run as administrator” when you start the process), but the rest can be done as a standard user. This is applicable for Windows 7 thru 10.
- Download the Windows 10 SDK from here: https://developer.microsoft.com/en-us/windows/downloads/windows-10-sdk
- Run the installer and choose to install the kit “to this computer”, using the default location (C:\Program Files (x86)\Windows Kits\10).
- During installation, select the Debugging Tools for Windows box and clear all the other boxes.
- Navigate in File Explorer to
C:\Program Files (x86)\Windows Kits\10\Debuggers\x86\and double-click the windbg.exe to run the WinDbg tool. - In the WinDbg window that opens, select File > Open Executable and navigate to the Scrivener executable, typically at
C:\Program Files (x86)\Scrivener\Scrivener.exe; select the Scrivener application file and choose Open. - In the main WinDbg window, select Edit > Write Window Text To File to save all the contents of that second window to a .txt file in a convenient location of your choice.
- Once you’ve confirmed the file is created, you can close WinDbg, which will also close the second window.
Please then either attach the file from step 6 to a post here (you will need to change the extension for the forum to accept it) or email it to windows.support@literatureandlatte.com so we can take a look. Please also include your Windows OS version number and whether you installed via the auto-update or by downloading the full installer from the website.
Finally, a few other less-involved things to try. Each of these is an individual test, not something that needs to be done in order.
- Please navigate in File Explorer to the Scrivener installation folder and remove the “rtfi.exe” file (you can just drag it to the Desktop temporarily) then try again to launch Scrivener. If there’s no change, go ahead and restore the rtfi.exe to its original location.
- Hold Ctrl+Shift while launching Scrivener. This prevents font parsing on startup (needed for compatibility with iOS) and may show a difference in Scrivener’s behaviour if there’s a problem with accessing the system files needed for this process.
- Launch Scrivener by right-clicking the “ScrivenerLog.bat” file within the installation folder and choosing “Run as administrator.” (If Scrivener is installed to a non-privileged location like your Documents folder, you can run this as a standard user instead.) After Scrivener launches and you’ve experienced the hang or slowdown, quit Scrivener, then reload the installation folder in File Explorer and check for a “log” folder. Please attach the log file inside to a reply here (change the extension) or email it to windows.support@literatureandlatte.com.
- If any crash files are created within the “minidump” folder in Scrivener’s installation folder, please zip the most recent one or two by right-clicking the selected files and choosing “Send to > Compressed (zipped) folder”, then attach or email that.
Thank you for your help in tracking down the problem!
Hope this helps in debugging.
Because the actual update wouldn’t even run for me (I had moved the Scriv executable to Program Folders but it was originally installed in my personal folder so that was my fault) I decided to uninstall Scriv so I could then reinstall it in the Program Folders where I wanted it. Because of that decision, I had to download the new version from the website and did a complete install instead of an update.
So far everything is fine.
Maybe the problem is in the update versus a new install?
I had a a few bad minutes while the updated Scrivener searched for my file(s). Eventually it came up. After reading the postings on the Scrivener Users FB group, I brought up Scriv (second time since the update). It takes a long time to come up, a most unusual thing. When it comes up, all the correct files seem to be as they should.
I had exactly the same problem. Wrote to L&L support twice but no reply. The suggestion to reinstall the previous version 1.9.7 worked for me. But many hours of panic and frustration.
- Windows SDK debugging tool
Your link was for the Windows 10 SDK, but I’m on Windows 7. If anybody else wants to try, the earlier SDK packages are all available from https://developer.microsoft.com/en-us/windows/downloads/sdk-archive. I tried the Windows 7 kit, but the installation kept failing for an “unknown reason” .(Very useful, thank you Microsoft!) - Remove the “rtfi.exe” file
Starting Scrivener threw up an error message “Failed loading font file “C:\Windows\Fonts\lucon_0.ttf”. The font file will be ignored.”. But thereafter the process still hung with no UI. - Hold Ctrl+Shift while launching Scrivener.
Scrivener started normally and very fast. (Is this a clue?) - Launch Scrivener by right-clicking the “ScrivenerLog.bat” file within the installation folder and choosing “Run as administrator.”
Log file echoed to the console window showed Scrivener writing at about one line per second. After 11 minutes the UI finally opened normally. There’s about 1300 lines in the log file, so I’ve emailed it - If any crash files are created within the “minidump” folder in Scrivener’s installation folder…
No crash files were produced.
Same for me on Win 7 Pro.
Documents > Move > Left seems permenantly grayed out, will not work.
Hi all,
We’ve put up a new version of 1.9.8 which should fix the slowdown and freezing that some people are experiencing. Please clear your browser cache (or use a second browser), then download the new installer. You can install this over your existing installation or do a completely fresh install by uninstalling the previous version first.
The date for this version of 1.9.8 and the installer is 15 June (you’ll see this in Help > About Scrivener, or if you check properties on the Scrivener.exe or the installer and view Details).
This version also fixes the the menu/shortcut for promoting items (moving left) in the binder.
Please note that if the font parser in Scrivener encounters a corrupt font on the system, it can crash Scrivener during the startup process. If you experience this–Scrivener seems to start launching, then stops (the 'wait" icon disappears, Scrivener vanishes from Task Manager), just launch Scrivener again. You should this time see a message indicating that the font which caused it to crash will be ignored for subsequent launches, and Scrivener will continue opening as normal. (You’ll only see that message about the font the first time.)
Please install the new version and let us know if that gets Scrivener running more swiftly again! Thanks to everyone who reported and helped us track down the trouble, and to all of you for your patience as we’ve worked to resolve it.
The Windows 10 SDK should work for Windows 7 and 8,1 as well as 10, at least for the WinDbg tool that we’re after. Sorry you had trouble getting the SDK to install, but thank you for trying!
Yes, holding Ctrl+Shift causes Scrivener to open without the font parsing process. The process under normal circumstances won’t cause the startup to take much longer (it’ll depend on the size of the font library on Windows, but even with a large one we’re just talking a few seconds, give or take based on the machine specs) but here with problems encountered, it would make a significant difference. This is good news, and I’m hopeful the updated 1.9.8 build linked above will resolve the problem for you!
That did the trick for me, MM! Scrivener now launches quickly and normally on Windows 7 Professional, yayyy! Thank you!
:mrgreen:
The new 1.9.8 update works for me on Windows 7 Home Premium. Loads quickly and the issue with Ctrl-left is resolved. Thank you!