Request for helping test updater/installer changes

[Moon Wizard]

I'm working on a couple different versions of the installer to help resolve many of the installation and permission issues we've seen sporadically over time, and more noticeable recently with the failed write notifications showing up in the console log. I've got a new updater in the Dev channel, and available here as a stand alone installer. (https://www.fantasygrounds.com/filelibrary/FGWebInstall_316.exe)

If you have a non Windows 10 machine (i.e. Mac, Linux, Windows XP/7/8) and some time, please try uninstalling and reinstalling FG to see if you can create and modify campaigns after installation. If so, please post which system you tried and what your results were.


[UPDATER] Reverted default data folder location to user appdata directory, instead of common appdata directory (which has stricter permissions).
[UPDATER] If a vault package is identified and the vault can't be initialized (permissions or missing license key), the updater/installer will simply skip and continue installation instead of failing.
[UPDATER] When restarting the FG client after changing Settings or updating, the desktop user credentials will be used, instead of the admin credentials supplied during update/install.


Also, I'll be continuing to work on another iteration to investigate whether I can/should explicitly set the permissions for the Everyone group to have full control over the FG data folder, and retroactively make those changes for people affected.

Thanks in advance,
JPG

[damned]

Im just guessing on some of these changes but if you do Uninstall and Reinistall and you cant see your campaigns you would need to go to:

C:\ProgramData\Fantasy Grounds and copy \campaigns to the new data location. The new data location can be found by clicking the Explorer Icon on the top RHS of the FG Splash Screen.

[Moon Wizard]

I believe that the registry settings are not removed on uninstall, so that probably won't change unless you are installing as a different user. But, it's good information, just in case.

Also, make sure to backup your data directory before uninstalling, if you are doing it on a machine you use for your actual game.

JPG

[damned]

I think I know how to reproduce now...

Close FG. Delete 4E.pak, run FG and then run the Updater. This will Invoke the installers permissions.
Create a new campaign and create a story entry.
Close FG.
Run FG and try and save some changes into the new campaign.

If that is right the reason it hasnt been seen a LOT is that it would only affect campaigns that were created on the same session as you ran the updater and even then some people with elevated User permissions wouldnt be affected either.

[Moon Wizard]

Are you reproducing on the new installer/updater, or on the current live one?

If live, then that is what I was seeing too.

Thanks,
JPG

[damned]

live.

[Minty23185Fresh]

My setup: Currently on vacation in Mexico. Because of router port forwarding issues I remote in to a PC in the US using TeamView. The PC here in Mexico is a Windows 7 Dell desktop. The PC in the US is also a Windows 7 Dell desktop.

Using damed’s instructions: removed the 4E.pak, updated FG with production installer, created campaign and performed edits, save was successful, on close. Restarted FG, loaded campaign, performed edits, save failed. So confirmed defective operation.

Used production FantasyGroundsUpdater.exe –u to uninstall FG. Deleted FG Data and App folders. Downloaded beta installer and ran it. (BTW, registry entries do seem to remain intact, license key, user name and purchased packages all show up in Settings dialog.) After install created campaign and performed edits, save was successful, on close. Restarted FG, loaded campaign, performed edits, save was successful. So confirmed desired operation. Closed, restarted, reloaded, edited and closed three more times just to be sure. Each time the edits were saved successfully.

I will repeat this entire scenario with my local PC here in Mexico (with incredibly slow internet).

[Minty23185Fresh]

In my posting above (#7 at 20:40) I failed to mention that I had remotely logged into the PC in the US using TeamView.

In this confirmation, I logged into the PC here in Mexico (locally).

I followed the same steps as in the previous posting, with exactly the same results (Windows 7 Dell Desktop).

[damned]

Thanks Minty23185Fresh! That is helpful.