bodyslide error Bodyslide adjustments not saving

[ddssfu]

Haven't been playing for some months after the updates ( I have downgraded). Tried to return to playing and saw body physics weren't working so I tried to edit this in bodyslide to be greeted by these two images. I had been fiddling with security a few months ago and the game itself we being blocked from editing files for some reason. I also tried changing outfits on mass to no avail, with a similar .nif file issue. Does anyone know how I can identify what is causing this mess?
 (not sure if relevant but the app manifest to prevent updates was changed to read only)

 

 

[judge007]

2 hours ago, ddssfu said:

Haven't been playing for some months after the updates ( I have downgraded). Tried to return to playing and saw body physics weren't working so I tried to edit this in bodyslide to be greeted by these two images. I had been fiddling with security a few months ago and the game itself we being blocked from editing files for some reason. I also tried changing outfits on mass to no avail, with a similar .nif file issue. Does anyone know how I can identify what is causing this mess?
 (not sure if relevant but the app manifest to prevent updates was changed to read only)

 

 

Your Fallout 4 installation folder is in a Windows protected folder.

Most guides for modding (The Midnight Ride guide on Nexus for example), warn you to install the game and your Mod Manager outside of those folders.

Try following either The Midnight Ride, or @Aylis's guide here on Loverslab for a more stable installation.

[ddssfu]

2 hours ago, judge007 said:

Your Fallout 4 installation folder is in a Windows protected folder.

Most guides for modding (The Midnight Ride guide on Nexus for example), warn you to install the game and your Mod Manager outside of those folders.

Try following either The Midnight Ride, or @Aylis's guide here on Loverslab for a more stable installation.

 

I'll admit I never did put the files outside those folders, as its never caused issues until now. Seems I need to do some reading.

 

Thank you

[PippinTom]

1 minute ago, ddssfu said:

 

I'll admit I never did put the files outside those folders, as its never caused issues until now. Seems I need to do some reading.

 

It causes issues ever since NT times (95/98 didn't actually care about own, user-stupidity protection that much), you just didn't notice or does not really use your computer much for anything special.

Installing "own" shit (things which user plans to edit/change frequently - and to keep due to own time investment) not only outside of OS protected directories but also away from entire OS partition is generally a best option for anyone who wish to avoid loosing fruits of own work due to some automated "purge/restore/reset" that often is triggered by MS updates or any other event that MS sets up for their own purposes or even something like "emergency recovery" (or whatever that shit is called now - last resort for many).

So take an advice when given, even if you hear it for the first time in your life - rethink structure of your data, if you care about it, of course.

[judge007]

1 hour ago, ddssfu said:

 

I'll admit I never did put the files outside those folders, as its never caused issues until now. Seems I need to do some reading.

 

Thank you

 

53 minutes ago, PippinTom said:

 

It causes issues ever since NT times (95/98 didn't actually care about own, user-stupidity protection that much), you just didn't notice or does not really use your computer much for anything special.

Installing "own" shit (things which user plans to edit/change frequently - and to keep due to own time investment) not only outside of OS protected directories but also away from entire OS partition is generally a best option for anyone who wish to avoid loosing fruits of own work due to some automated "purge/restore/reset" that often is triggered by MS updates or any other event that MS sets up for their own purposes or even something like "emergency recovery" (or whatever that shit is called now - last resort for many).

So take an advice when given, even if you hear it for the first time in your life - rethink structure of your data, if you care about it, of course.

Just think of Microsoft as the Bethesda Game Studios of the OS world . . .

[subaverage]

Your installation path is ok. It's the default one and there is no need to change it in my eyes. I use it for FO 4 since the beginning. The protection means that you need a trusted installer or admin rights when you want to install an app in this location. Thats's it and it's made to protect you from installing questionable programs. What you could try is to right click on the Fallout 4 game folder and disable write protection or you could check whether the a.m. files are write protected. Maybe even your antivirus is blocking you. Can you build outfits in Bodyslide?

Edited May 31 by subaverage

[ddssfu]

2 hours ago, subaverage said:

Your installation path is ok. It's the default one and there is no need to change it in my eyes. I use it for FO 4 since the beginning. The protection means that you need a trusted installer or admin rights when you want to install an app in this location. Thats's it and it's made to protect you from installing questionable programs. What you could try is to right click on the Fallout 4 game folder and disable write protection or you could check whether the a.m. files are write protected. Maybe even your antivirus is blocking you. Can you build outfits in Bodyslide?

 

Well I did try to batch build clothes and it was not working. I've had another try, and it seems the vanilla and DLC clothes are ok. the issues appears to be modded clothing from nexus and cbbe body for some reason. I did install 3bbb some months ago and I do not believe I was getting these issues, however useful that is.

[subaverage]

Did you disable the write protection of the Fallout 4 game folder? And you could try not to use 3BBB and see what happens.

[ddssfu]

29 minutes ago, subaverage said:

Did you disable the write protection of the Fallout 4 game folder? And you could try not to use 3BBB and see what happens.

 

Apologies for sounding like an idiot, but when you say write protection are you referring to the "read only" on properties?. I'll have a go at disabling 3BBB now to see if that will solve anything.

[subaverage]

Yes, uncheck read only for the whole game folder. Sometimes there are wrong settings and this can be a possible reason when you say you can't save your changes on certain files and others are working. You only need to do it for the game folder. The setting will be inherited to every file within. It's not persistent. So maybe you need to do it again (if this was the reason). If this doesn't help you could reinstall Bodyslide, the outfits and perhaps CBBE.

Edited May 31 by subaverage

[judge007]

21 hours ago, subaverage said:

Your installation path is ok. It's the default one and there is no need to change it in my eyes. I use it for FO 4 since the beginning. The protection means that you need a trusted installer or admin rights when you want to install an app in this location. Thats's it and it's made to protect you from installing questionable programs. What you could try is to right click on the Fallout 4 game folder and disable write protection or you could check whether the a.m. files are write protected. Maybe even your antivirus is blocking you. Can you build outfits in Bodyslide?

That is some very bad advice . . .

 

If that has worked for you, it's a matter of luck only.

 

You would also have to list exclusions for the game, Steam, the Mod Manager, every utility you require (Bodyslide, FO4Edit, Wrye Bash, CM-Toolkit, Loot, etc),

with no guarantee that the OS would respect all that. That includes each individual .dll, .exe, or folder involved in the modded game.

 

Just follow an appropriate guide such as The Midnight Ride, Aylis's FO4 guide here on LL, or others out there.

 

Please don't dispense such harmful advice to noobies

[subaverage]

1 hour ago, judge007 said:

That is some very bad advice . . .

 

If that has worked for you, it's a matter of luck only.

 

You would also have to list exclusions for the game, Steam, the Mod Manager, every utility you require (Bodyslide, FO4Edit, Wrye Bash, CM-Toolkit, Loot, etc),

with no guarantee that the OS would respect all that. That includes each individual .dll, .exe, or folder involved in the modded game.

 

Just follow an appropriate guide such as The Midnight Ride, Aylis's FO4 guide here on LL, or others out there.

 

Please don't dispense such harmful advice to noobies

I am not of your opinion (and not only because it might only be me being lucky), but I don't want to argue. An exclusion in an antivirus for FO 4 might be necessary anyways. And perhaps start the f4se_launcher as admin. I still will not recommend to change the installation paths, but might mention that others would do.

Edited June 1 by subaverage

[judge007]

1 hour ago, subaverage said:

I am not of your opinion (and not only because it might only be me being lucky), but I don't want to argue. An exclusion in an antivirus for FO 4 might be necessary anyways. And perhaps start the f4se_launcher as admin. I still will not recommend to change the installation paths, but might mention that others would do.

Many people in the modding world do not hold your opinion.

Do not cause harm with your poor advice.

[subaverage]

33 minutes ago, judge007 said:

Many people in the modding world do not hold your opinion.

Do not cause harm with your poor advice.

You say it's a poor advise and I would harm players. That goes very far. I find it more dangerous to work around Windows security than perhaps to deal a bit with your OS. And I am definetely not alone.

[judge007]

26 minutes ago, subaverage said:

You say it's a poor advise and I would harm players. That goes very far. I find it more dangerous to work around Windows security than perhaps to deal a bit with your OS. And I am definetely not alone.

Read this and then keep your misguided opinion to yourself.

 

The Midnight Ride:

Choosing a Location

A clean installation is not only required to get rid of any potential leftover mod files, but also to make sure the game is installed in a safe location. Here is what you need to know when choosing where to install your game:

• Avoid any default Windows folders: This includes but is not limited to C:\Program Files, C:\Program Files x86, your Desktop and your Documents folders.
  This is because users lack write access to Program Files, while Desktop and Documents are often managed by OneDrive. This can cause many issues with the game and any modding tools.
  
  An example of a safe location is C:\Games
• Install on an SSD if possible: Having the game on an SSD will drastically improve loading times and decrease stuttering.

S.T.E.P.  Modification Guide:

 

Modding Folders

Create modding-related folders (aka, directory locations or 'paths'). Before doing so, consider the space requirements. A good rule of thumb for drive space requirements is ~100GB per game; however, this will vary from game to game. This space accounts for the game (e.g., Skyrim LE requires ~13GB, Fallout 4 requires ~30GB), installed mods, temporary files, modding tools, etc. Also remember that no PC drive should be filled to more than 90% of its capacity.

To avoid potential Windows Security / User Account Control (UAC) pemissions issues, avoid installing moddable games and modding resources under existing paths created by Windows or third-party programs. Install locations to avoid include but are not limited to...

• C:\Program Files\
• C:\Program Files (x86)\
• C:\Users\
• C:\Windows\

Instead, create the following folders on any drive root (e.g., C:\, D:\, E:\, etc.) to keep paths shallow. Installing games and modding tools onto a large, fast drive is beneficial:

C:\Modding
C:\Modding\Tools
C:\Games

In creating these directories, the 'Owner' is the Windows user who created them and who has full permissions under these locations by default, thus avoiding any potential Windows Security issues in the future.

 

[subaverage]

I know about these guides and it's totally ok if you follow them. I will not and I will also not keep my opinion to myself. But now I am tired of this discussion and in my eyes it does not help the topic author.

[PippinTom]

5 hours ago, subaverage said:

(...) And perhaps start the f4se_launcher as admin (...)

 

Dumbest and potentially most harmful advice one could give anyone - and in contradiction to all your security "concerns" so far.

You somehow figured out how to damage your own OS installation with the wrench called NTFS permissions but fact that you know how to operate a wrench does not make you s car mechanic nor even a plummer. Changing permissions require dropping of inheritance and steal of ownership from system services (oh! divine security - where are you?!) , and at the end turns out futile (in medium-to-long run) because ACLs are (should be even if aren't always) first to be reset when security update is rolled out by M$ and before it's installed - so congrats on another "great" advice.

Let's go further - having steam games inside Program Files makes it impossible to effectively block/prevent Steam enforced auto-update crap mechanism (for starters because of ownership that will be reverted despite effort put in changing it and fact that no matter what you do, and disregarding NTFS, which is NOT the only mean that OS has to enforce it's dominance over a stupid user), so next time when mod-breaking-shitstorm happens when Bethesda decides to enforce some tiny-shitty update which noone actually needs but which will break all kinds of mods - all the end user can do is to join huge group of clueless morons that beg here and there for mod updates (while many of them never will be) or are forced to use downgrader to restore their game to playable state. Which is unnecessary hassle and another waste of time - which all can be easily and "legally" avoided, by just better planning of data locations. Moving Steam, as well as moving it's libraries away from OS partition has official tutorials on Steam itself, for a reason - obviously demand was high enough.

 

Let's face it - you are just plain ignorant, that has no valid arguments (best one so far was "sniffing glue is healthy for you - I do it for years and am fine!", whose story does not hold up - but still thinks that can advice others, right?  

[subaverage]

3 hours ago, PippinTom said:

You somehow figured out how to damage your own OS installation with the wrench called NTFS permissions but fact that you know how to operate a wrench does not make you s car mechanic nor even a plummer. Changing permissions require dropping of inheritance and steal of ownership from system services (oh! divine security - where are you?!) , and at the end turns out futile (in medium-to-long run) because ACLs are (should be even if aren't always) first to be reset when security update is rolled out by M$ and before it's installed - so congrats on another "great" advice.

 

I didn't do anything the like, but of course the permissions on this folder have to be sufficient. For me it's the case by default. Regarding F4SE the question for me is whether it's better to run it from an unprotected folder without admin rights or from a protected folder with. This sounds very much like a matter of trust to me. Especially when you exclude your game folder from virus protection. Maybe you are bit safer from Micrsoft updates. I did not experience gaming problems by these, yet, but who know what the future brings. In any case I backup my entire game from time to time.

My game version is still 163 and the game is protected from updates by the normal means.

But to be more precise: I don't say don't change the paths. I only don't recommend it. Especially when someone already has an existing installation as it seems to be the case with the topic author.

Edited June 1 by subaverage

[judge007]

9 hours ago, subaverage said:

I didn't do anything the like, but of course the permissions on this folder have to be sufficient. For me it's the case by default. Regarding F4SE the question for me is whether it's better to run it from an unprotected folder without admin rights or from a protected folder with. This sounds very much like a matter of trust to me. Especially when you exclude your game folder from virus protection. Maybe you are bit safer from Micrsoft updates. I did not experience gaming problems by these, yet, but who know what the future brings. In any case I backup my entire game from time to time.

My game version is still 163 and the game is protected from updates by the normal means.

But to be more precise: I don't say don't change the paths. I only don't recommend it. Especially when someone already has an existing installation as it seems to be the case with the topic author.

An already noted malfunctioning installation, as the user request for help showed.

People give valid advice, and you step in the God Almighty Troll you are, and indicate that the previous advice was no good.

 

Go away.

STFU

and GO AWAY

[subaverage]

It seems that that my post looks for you that I meant your advise would be wrong or invalid in some way. That wasn't my intention and I am sorry if I gave you that impression. Moving the existing installation incl. Steam and all games within to a new location can be a lot of work and I would have prefered trying to find a solution for the existing one. Especially when the topic author states that vanilla and dlc outfits work I can't imagine that the installation location is the cause for the trouble in this case.

Edited June 2 by subaverage

[ddssfu]

Right, Considering current hardware complications on my end, I am postponing the moving of the game files until I have the time to move the files properly. I am aware that I should not have left the install path on x86 but had never caused an issue until now. I did not mean to start a confrontation in the comments. 

[ddssfu]

On 6/3/2026 at 8:41 PM, ddssfu said:

Right, Considering current hardware complications on my end, I am postponing the moving of the game files until I have the time to move the files properly. I am aware that I should not have left the install path on x86 but had never caused an issue until now. I did not mean to start a confrontation in the comments. 

 

Small update: I have successfully moved the game out of the x86 file and tried that, still no success. I had reinstalled cbbe to check it wasn't an issue on that end, same result. I assume now that the vortex file also has to come out of the file as well.

Edited Saturday at 10:48 AM by ddssfu

[ddssfu]

2 hours ago, ddssfu said:

 

Small update: I have successfully moved the game out of the x86 file and tried that, still no success. I had reinstalled cbbe to check it wasn't an issue on that end, same result. I assume now that the vortex file also has to come out of the file as well.

 

On 6/1/2026 at 11:35 AM, judge007 said:

Read this and then keep your misguided opinion to yourself.

 

The Midnight Ride:

Choosing a Location

A clean installation is not only required to get rid of any potential leftover mod files, but also to make sure the game is installed in a safe location. Here is what you need to know when choosing where to install your game:

• Avoid any default Windows folders: This includes but is not limited to C:\Program Files, C:\Program Files x86, your Desktop and your Documents folders.
  This is because users lack write access to Program Files, while Desktop and Documents are often managed by OneDrive. This can cause many issues with the game and any modding tools.
  
  An example of a safe location is C:\Games
• Install on an SSD if possible: Having the game on an SSD will drastically improve loading times and decrease stuttering.

S.T.E.P.  Modification Guide:

 

Modding Folders

Create modding-related folders (aka, directory locations or 'paths'). Before doing so, consider the space requirements. A good rule of thumb for drive space requirements is ~100GB per game; however, this will vary from game to game. This space accounts for the game (e.g., Skyrim LE requires ~13GB, Fallout 4 requires ~30GB), installed mods, temporary files, modding tools, etc. Also remember that no PC drive should be filled to more than 90% of its capacity.

To avoid potential Windows Security / User Account Control (UAC) pemissions issues, avoid installing moddable games and modding resources under existing paths created by Windows or third-party programs. Install locations to avoid include but are not limited to...

• C:\Program Files\
• C:\Program Files (x86)\
• C:\Users\
• C:\Windows\

Instead, create the following folders on any drive root (e.g., C:\, D:\, E:\, etc.) to keep paths shallow. Installing games and modding tools onto a large, fast drive is beneficial:

C:\Modding
C:\Modding\Tools
C:\Games

In creating these directories, the 'Owner' is the Windows user who created them and who has full permissions under these locations by default, thus avoiding any potential Windows Security issues in the future.

 

To add to the previous post, I have tried reinstalling cbbe and twb with still no change. If I have to move vortex out of x86, can I just move the file or will that brick the mods? (I have already moved the staging folders outside of x86)

[judge007]

2 hours ago, ddssfu said:

 

To add to the previous post, I have tried reinstalling cbbe and twb with still no change. If I have to move vortex out of x86, can I just move the file or will that brick the mods? (I have already moved the staging folders outside of x86)

I have limited experience with Vortex, so I Googled it!

 

To move your Fallout 4 mods to a non-Windows or non-default folder, the Mod Staging Folder must be moved correctly within the Vortex UI so it remains on the same drive as your game files. Do not copy and paste the folder manually in Windows. [1, 2, 3]

For tips on visualizing this folder migration process and the correct pathing:

Follow these steps to safely move your staging and download directories:

1. Purge and Exit

1. Open Vortex and go to the Mods tab.
2. Click Purge Mods (this temporarily removes the hard links from your Fallout 4 directory).
3. Close the Vortex application. [1, 2, 3]

2. Move your Mod Staging Folder

1. Re-open Vortex and go to Settings > Mods.
2. Under the Mod Staging Folder path, click the folder icon.
3. Create and select a new empty folder on the same drive as your Fallout 4 installation (e.g., D:\Games\Vortex\Fallout4Mods).

[ddssfu]

2 hours ago, judge007 said:

I have limited experience with Vortex, so I Googled it!

 

To move your Fallout 4 mods to a non-Windows or non-default folder, the Mod Staging Folder must be moved correctly within the Vortex UI so it remains on the same drive as your game files. Do not copy and paste the folder manually in Windows. [1, 2, 3]

For tips on visualizing this folder migration process and the correct pathing:

Follow these steps to safely move your staging and download directories:

 

1. Purge and Exit

1. Open Vortex and go to the Mods tab.
2. Click Purge Mods (this temporarily removes the hard links from your Fallout 4 directory).
3. Close the Vortex application. [1, 2, 3]

 

2. Move your Mod Staging Folder

1. Re-open Vortex and go to Settings > Mods.
2. Under the Mod Staging Folder path, click the folder icon.
3. Create and select a new empty folder on the same drive as your Fallout 4 installation (e.g., D:\Games\Vortex\Fallout4Mods).

 

The mod staging folder is already moved out of x86. Unfortunately I'm still getting the same result.