Thanks for a fast response Tiho.
I've wasted a morning on this in an attempt to assist. These are my findings...
1. That Scricener 3 RC1 for Windows crashes within 30 seconds whilst it continues loading
2. This occured on my Windows 7 PC running in both nomal mode and safe mode with networking, but worked okay in safe mode with command prompt (no networking)
3. That others have reported the foregoing critical problem
4. Scriv 3 RC1 works on my Lenovo Legion laptop (64GB memory) with Win 10 OS
5. This issue cannot be my PC, I've just arrived back from two months in the Middle East and China attending conferences (like https://10times.com/tase-guilin
), meeting my development teams out there, and writing a book. All I've done, apart from that mentioned this morning, is update Scrivener
Possible: Given that I've just updated to RC1 and it works in Win safe mode without networking, there's a network related issue been introduced recently.
With 50 years in systems development and running companies it comes hard to receive an "it's the customer" response. I had recommended Scrivener with free ads across our systems until now, and generally elsewhere. I've instructed my colleagues to remove recommendations until at least three months working operation after release. I'm now concerned about the development mindset here, a pity given L&L are a fellow British organisation. One reason why I recommended Scriv is because we have an automatic book production system, for ordinary folk to publish full or part books and other documents, with subscriptions so authors can increase income from their hard work. Our system requires Latex files, which Scrivener is wonderful at, especially with Markdown. I've instructed a development team to look at a Markdown editor that can be modified to included inline Latex commands (like Scrivener does with HTML comment tags) and produce Latex output so that we don't have to wait for a Scrivener fix.
Scrivener is a good product. I do not want to unfairly criticise. Crash "bugs", though, are serious. I'll see what else I can do when I have time, but not today.
For anyone else experiencing this issue, try starting your OS in safe mode with command prompt mode, change directory to your Scrivener installation folder, and run Scriv from there, If it works, restart your machine in normal mode, turn off your firewall/anti-virus software, and run Scriv again. If it works, look for the problem within your firewall/anti-virus software --- and don't forget to turn it back on. In my case, that wasn't the issue, Scriv still fails. Good luck!
I'll still buy Scriver when V3 is released, to regain confidence.