https://bugs.winehq.org/show_bug.cgi?id=50804
--- Comment #20 from Chris Caudle winehq@chriscaudle.org --- (In reply to Zebediah Figura from comment #18)
My guess is that it was broken by wine-staging commit 811467bf6a4, and my further guess is that it won't run on Windows unless you explicitly run it with elevated privileges.
We'll need some way of explicitly elevating privileges in wine, to accompany that patch.
How does wine handle requests to write to what would be Windows system directories? One possibility for why this program does not always trigger the problem, or trigger with the exact same symptoms, is that in most cases it only needs access to the (Windows) user directories, but when it checks for updates it needs to write to \Program Files\LTC\LTspiceXVII which would need admin privelege to write to on a Windows machine. The equivalent on my linux machine would be ~/.wine/drive_c/Program\ Files/LTC/LTspiceXVII/ which any process running under my user account should have access to. Everything under .wine/drive_c appears to have rwxrwxr-x permissions, so perhaps that is not related. Just something that came to mind regarding why the application may not behave identically on ever start.