Fix Instance Name Editing That Does Not Save in LDMultiplayer

## Overview In LDMultiplayer, changes to an instance name or settings may not save. The likely cause is that your Windows user account lacks Write permission on the configuration folder that LDPlayer uses. This guide shows how to grant that permission to your account.

## Why this works LDMultiplayer stores instance names and settings in configuration files. If your account cannot write to the config folder, the change does not stick. Granting Write permission to your own account lets LDMultiplayer save its changes.

## What to expect Windows may show a permission or User Account Control prompt. Approve it only if you started this change. After you click Apply, the Security tab shows Write as allowed for your account.

## Verify Rename an instance in LDMultiplayer. Close LDMultiplayer, open it again, and check that the new name stays. If the name reverts, check that you applied the change to the config folder for the correct account.

## Common mistakes

• Changing permissions on the whole LDPlayer folder instead of the config folder.
• Selecting a different user account than the one that runs LDPlayer.
• Clicking Edit and checking Write, but forgetting to click Apply.

## Security note Granting Write access lets your account change the instance configuration files. Any program that runs under your account can also change them. Keep the change limited to your own account and the config folder.

To revert, right-click the config folder, open Properties, go to the Security tab, select your account, click Edit, clear Allow next to Write, and click Apply. Only clear Write if you added it in this guide. Leave other permissions as they were.

## If the change still does not save

1. Confirm that you changed the config folder inside the vms folder, not a copy elsewhere.
2. Confirm that the account you selected is the one you use to sign in to Windows.
3. Open the folder’s Properties and check whether it is marked read-only on the General tab. Clear that mark if it is set, then apply the change.
4. Close LDMultiplayer, open it again, and rename the instance again.

## Notes and Troubleshooting

• Select the account you use to run LDPlayer. If you are not sure which account that is, check which user is signed in to Windows.
• Change permissions only on the config folder, and only for your own account.

## Related

• Managing Multiple LDPlayer Instances With LDMultiplayer
• Running More LDPlayer Instances at Once by Tuning Hardware and Emulator Settings
• Fix Multiple Instances Stuck at Engine Starting 94 Percent
• Using Synchronizer to Control Multiple LDPlayer Instances