I’ve just encountered an ‘Application Error’ with Scrivener that prevents the program from launching.
The error is thus: “The instruction at 0x019b0000 referenced memory at 0x019b0000. The memory could not be read.” It then prompted me to close the window.
I installed the program again (without uninstalling) and got the same message. I used Revo Uninstaller (I selected Moderate for those that know what I’m talking about) and reinstalled and received the message a third time.
Using Revo again (selecting Advanced) I uninstalled the program and searched my PC for every Scrivener folder and file to be certain it installed fresh. The programn briefly flashed on the screen and then crashed with an error same as above but now the number read 0x00320000. Try opening again and the error changed to 0x01b9000.
I’m stumped.
This looks like an error caused by Kaspersky Internet Security which we’ve worked around in the latest update. 1.7.3 will be available shortly, so try clearing your browser cache and then downloading that from here. This version should launch without needing to disable Kaspersky or adjust the settings, but if you’re still running into trouble you may need to add the Scrivener installation folder to the list of trusted locations.
Kaspersky is the only software I’ve seen recently that’s causing this, but the same error could be resulting from another memory manager or security program. I’d try downloading the latest update and installing that to see if it fixes it, and if it does not, take stock of what other software you have running that might be conflicting.
I do have Kaspersky installed so your assumption is correct. After placing Scrivener on the Trusted list within Kaspersky, it still crashed with an error. I restarted my machine and, after clicking, Scrivener never launched at all.
Hrm.
Okay so Scrivener has now been uninstalled and installed six times. So I’d wager we’re good on that front. 
But I’m willing to do it again.
The program work very well for a long time. So I’m certain it was something I did recently outside the software developers purview, but any continued assistance is very welcome.
Last night I did a memory text, but it was for a different reason, and I had no issues. The reason for the memory test though was an issue with a BSOD I got last night. I was restarting my PC to correct a desktop icon issue, when I hit a BSOD (win32k.sys issue). I was not able to start the PC in normal mode nor safe mode. One of Microsoft’s recent updates caused the issue. I solved it this morning.
In the back of my mind I had hoped this was something that caused my problems with Scrivener. Hard to believe coincidences sometimes.
I’ll continue to run more diagnostics. I assembled the PC myself and have many programs available to me to suss this out.
One thing:
I’m assuming that this link will eventually point to 1.7.3, but wasn’t meant to link to it at this moment, as it downloads 1.7.2. Not an issue. I can wait. I am patient.
None of this has me bothered. It’ll get sorted soon enough, I’m sure. When I get home I will turn Kaspersky off and try again. Currently, Scrivener doesn’t start at all. I see the process begin in my list of processes both in Windows and Kaspersky, but it disappears soon after, not providing any visual crash.
Sorry, yes, the fix is in 1.7.3 which I expected to be available for download shortly after posting, but it looks like we’re having some trouble getting it up on the usual servers. Try downloading it directly from here and replacing your 1.7.2 version with that. Ideally it will work without needing any further changes to Kaspersky’s settings. In a pinch though, you can pause Kaspersky from the task tray via right-click, launch Scrivener, and then re-enable Kaspersky.
Just got home and pausing Kaspersky frees Scrivener and I have no issues. But I shall install the update and reply shortly.
EDIT: It works. No more issues. Thanks for all the help and attention.
Great, glad to hear it’s working for you!