#TwitchyBait perms
1 messages ยท Page 1 of 1 (latest)
Yes, so make sure your backups are current from that directory
Ok
Then wipe it, and start fresh. License key verification, install a system, create a fresh world.
Don't copy any data back into it yet. Let's just get a world launched in Foundry first.
Ok wiping it all now
Reinstalling now
Ok installed PF2E, created a new world and launched it successfully
so guessing something is wrong with the backup somewhere
Maybe
Shut down Foundry, then copy just the world back in.
Windows inheritance for permissions can be really screwy... the idea here is that by making Foundry recreate the user data directory from scratch, copying the files back in should override their permissions to the new appropriate permissions and things should work.
Hmm, I copied just the world file, it showed up on launch but when hitting launch has the same EPRM permissions error
similiarly if I now try to launch the original test world it gives me the error:forbidden pop up
Blast...
Wait, it's causing a problem even on the one you were able to launch?
Yeah, oddly
And you're not running Foundry as admin or anything?
Nope just standard opened it
And you didn't copy your entire worlds directory, just the one world?
ah no I had just copied the one, I'll remove the individual then go back and do that
If you copied the entire worlds directory, yeah, let's retest by wiping out the worlds directory, relaunching, and creating a new test world.
Ok I replaced the world folder and created a new world and that worked. I'll go back and try to launch the original backupworld now
yeah so somethings screwey with the original world launching it gives the error again and then makes launching the new test one error out as well
damn
it's pointing directly to the actors.db if that means anything
alright... let's try a force update here... hold on, I need to go back in and make sure I get the steps right
also quick note it seems restarting it lets me launch the test world again
Shut down Foundry.
From within the worlds directory, right click your world and choose properties.
Choose security.
Choose Advanced.
Is the Owner set to your microsoft account (or the account you log in to your world with)?
something about trying to start the old world makes launching any world not function
Yeah that's really odd
the owner is set to my windows account
Alright, crap my laptop is windows 11 now so things are different. Let's just go straight to the source and check that actors.db file
Close out of that window, navigate to it, and same deal - just screencap that security screen this time
Yep that's set to the microsoft account as well
๐ค bloody hell.... I hate windows permissions for this. Everything looks right but it's not right.
I'll need to find my powershell script to force update the permissions... go ahead and copy your user data back over. We'll force update all of it.
yup, just restore your backup.
We've confirmed it's a permissions issue (the test world was fine), but clearly some permission behind the scenes is set wrong.
Actually, let's check one thing before I do that. Regular file permissions on actor.db (after right clicking -> properties). Make sure read-only isn't checked.
read only is checked
hmm so unchecked it and it didn't work, checked it again and it reapplied read only so I just backed out a bit to get the whole world off read only and that launched sucessfully.
Jesus thanks for your patience haha
๐
gotta fix file extensions in the world now but at least it works
Whelp, I'm glad we didn't need powershell
haha
Did I mention I hate Windows file permissions?
Ok, good, just making sure ๐
Because I hate Windows file permissions
So I'd double check your packs and everything with that world.... Just to be safe
Thanks for the hard work that'll save me weeks of remaking everything and trying to remember what everyone had haha
Welcome ๐ Glad things are going! And remember - no running Foundry as admin unless it's to update the core software!
And you can skip even doing that by uninstalling Foundry and re-installing it someplace else, even the root c drive would keep you from having to run as admin again
Definitely noted