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 firstname.lastname@example.org 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 email@example.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!