Having tried the method described above and finding it did not work for me, I started searching for a possible solution on winehq.org. I ended up coming up with a simple process that was successful and repeatable when used again on a freshly set up laptop. In order to avoid the potential for interfering with other software I had installed under Wine, I did all this in a new Wine prefix.
I tried to create a script for this but discovered that it was executing steps before prior steps had completed. I therefore suggest each command is run separately once the preceding step has fully finished. Those steps are:
env WINEARCH=win64
env WINEPREFIX=$HOME/wine_scrivener wineboot --init
env WINEPREFIX=$HOME/wine_scrivener winetricks dotnet40 corefonts
env WINEPREFIX=$HOME/wine_scrivener winetricks win7
env WINEPREFIX=$HOME/wine_scrivener winetricks dotnet462
env WINEPREFIX=$HOME/wine_scrivener wine Scrivener-1.9.15.exe
The same process also worked for the latest V3 beta.