I opened a v19x project in Beta 39. It came over fine, and opens normally if I use the Beta to open the project. However, if I double-click on the converted .scrivx file, it calls up the v1.9x software, and obviously can’t be opened.
I tried pulling the folders into a new Beta 39 setup, but even then, the .scrivx called up the v1.9x program to open it when I double-clicked on it.
All of my Beta 39 .scrivx files now call up the v1.9x software when I double-click on the .scrivx file. Have I somehow managed to mess up my associations? I can’t seem to fix it.
Scriv v1.9 vs. beta files both share the same .scrivx extension, so Windows should recognize whichever program you installed last as the association with .scrivx.
If you reinstall the beta, that should fix the association. You don’t need to uninstall first, but be sure to specify the same target folder for the install.
Or you should be able to fix the association without reinstalling. In windows Explorer, right-click on a .scrivx file, select Properties. Click on the Change button next to Opens With, and navigate to the Scriv Beta executable in the Program Files folder (if you’re using 64 bit beta) or Program Files (x86) folder (if you’re using 32 bit beta).
I tried a couple of those methods, but they don’t work. I’ll wait until the next auto-download beta (I don’t want to lose my toolbars). If that doesn’t fix it, I’ll re-install.
I really have no idea how it happened. My other laptop is fine.
I broke down and downloaded the x64 B39, installed manually, and lo, all is well. It even kept my toolbar mods in place!
Still no idea why “it” reset the B39 .scrivx file to open via v1.9x on a double-click. No idea why I couldn’t reset the associations using all the Win10 methods, either. * shrug * Gremlins.
