I thought I had a minor issue as described in this thread
Unfortunately, the issue is project specific. CORRECTION There is an old project that is unaffected, but the current project and all backups and NEW blank projects are affected. (It’s surely (??) the app or some corruption in the registry, AppData…???) I tried importing into a new blank project, dragging and dropping into new Novel project, creating a new document in a new project – all suffer the same.
I was about to compile and send to beta readers, but can’t control formatting. I am screwed.
ALL suggestions welcome.
UPDATE: Is it possible that the 3.1.50 install, uninstall, 3.1.4.1 reinstallation left things in a mess? The issue is now present even in a NEW project, so maybe the fact that all backups seemed affected is simply because the app is affected?
Maybe a complete clean install is required, but I don’t know how to do that.
Things I have tried: import novel into new project (no change); create new project (issue present). Reinstall 3.1.4.1 without uninstalling – no change.
Follow up Info & Question
I installed Scrivener 3.1.4.1 on my laptop and copied the existing project over IT LOOKS FINE
PANIC Cancelled, but I still need to get things sorted on the desktop PC.
This does however confirm there’s nothing wrong with the project, but it’s the app, the AppData or registry that has got, what’s the technical term?, completed f*cked 
Since a fresh install on the laptop is fine, is there a way of eradicating the current install on the desktop and starting from scratch again?
NB I just had to do a Windows update on the laptop, but afterwards Scrivener and Project are still OK, so there’s that I suppose.
Hi.
Save your options to a file, in a dedicated folder that you’ll easily find later on.
Go to the application support folder File / Show application support folder and copy paste the “compile formats” folder to the folder you had just created where you saved your options.
After that, uninstall both versions of Scrivener through Windows settings/Apps.
You can also after that delete the folders Scrivener versions were installed to (if the uninstall left bits behind). Same for the support folder. (So take note of where it is when securing your compile formats.)
Reboot your computer.
Reinstall.
That should, I believe, give you a fresh install.
Note that unless you specifically do the same copy/paste for it, you’ll lose stuff like your personal words list, custom script formats and whatever else I didn’t think of. (I’d first take time to think and make a list of what I don’t want to lose.)
Good luck.
3 Likes
I will tackle that and report results tomorrow - thanks.
1 Like
I see no “compile formats folder” and a search shows up nothing at the folder opened by File... Show Application Support Folder
(I’d show an image but when I try to paste/upload image I am currently getting
undefined method `video_thumbnails_enabled’ for #Class:0x00007fb99aa247d8
despite Ctrl-F5; will update again later)
Apart from that I have saved out the Wordlists (.ini and .txt); exported my compile formats ( ), saved my theme options… I think I’m good to go.
TL;DR RESOLVED I saved files as described, uninstalled, rebooted, installed 3.1.5.0 (I previously reported a search-crashing bug in 3.1.5 and reverted (or did I 
?) to 3.1.4.1 only to find the bug is there too, so why not use the latest this time?) and rebooted
Everything looks in order - I even got prefs and substitutions and compile formats back without reimporting the prefs etc. files…! I think I recall a release note about some things having moved to the registry?
Anyway, toolbar space is still wrong, but exactly the same wrongness as before; other than that, style, font, etc. seem to be normal again.
Thank you all for the heart-saving assistance. 
Takeaways?:
- Possible interaction between 3.1.5 settings and 3.1.4.1 such that uninstalling 3.1.5 does not facilitate correct 3.1.4.1 installation
- Too many “support” files scattered in too many places - ideally there would be as 1-click “save my setup” and 1-click “restore my setup”
- Uninstall should offer options to remove the app or the app and all its support folders/ files (?+ reg entries?) (after giving the user a chance to take backups if they want to)
- I don’t think, given the apparent incompatibility of 3.1.4. and 3.1.5 re prefs etc. it should have been a minor dot release. I would have been more cautious about accepting it as soon as it was offered if I had better appreciated the potential impact. Should have been 3.2.0 I think
NB I used a tool that allows me to save or discard changes to a system, so I tried it all first and when I found it was working, I committed the changes. Of course, the paranoia dilemma* was: what if the uninstall etc. makes things worse vs what if the temp disk management screws up on commit? (With a side order of, I haven’t tested my recovery strategy in far too long… 
) Only marginally complicated by the temp disk management software giving a false warning half way through that I had run out of temporary storage. Technology giveth, and technology taketh away, and it moves in ways usually incompatible with fleshly reasoning.