Hi there. I’ve been using Windows 10 for just over a week and haven’t experienced any compatibility problems with Scrivener. However, my PC installed some updates last night and is now telling me that Scrivener is ‘non-compatible’. I can’t open any of my projects. Can anyone help, please? Any advice will be greatly appreciated.
I’m having the same trouble. When I run Scrivener I first get a window that the project isn’t found followed by the Scrivener start screen. If I try to create a new project, or open an old one Scrivner hangs. I assume I’m getting the “project not found” because I’ve archived the last project that I had opened, but mention it to be complete.
I ran through the compatibility settings suggestions found here, but that didn’t solve my problem. W10 upgraded for me last night too so I assume the problem is related. Help!
Jeff
Okay, I did two things and was able to make Scrivener run:
- I uninstalled the W10 update that came yesterday. For me, that was KB3081444
- I opened a new project in Documents. I had been trying in Desktop because that’s where I put temporary junk.
- After verifying that it ran, I turned off all the compatibility options I’d experimented with and returned to the default.
Ideally I would have only changed one variable, but I’d suggest rolling back your last update. Go to Settings then search for “view installed updates” and you’ll find it. Left click should bring up the uninstall option. Obviously, this update is going to get reinstalled at some point, but hopefully the good folks at L&L and MS will get a handle on it.
Hope that helps.
Jeff
You could also try reinstalling Scrivener after the update. I’ve just booted up a fresh virtual machine with Windows 10 and all the latest updates, then installed Scrivener, and it’s running just fine. It’s possible the update messed something up with the existing settings, but there’s nothing incompatible between Scrivener and the update itself.
Thanks for the advice, Jeff. I finally got the chance to roll back the Windows update yesterday and it worked a treat. Full access restored!
Thanks for the tip, Jennifer. I’m sure this is a better long-term solution - I’ll have to see if I can still find my licence permissions.