Migration & access
Updates, configuration backups and uninstalling
Protect farm configuration through updates and understand what an uninstall should and should not remove.
Before an update#
- Stop new schedules and let active work reach an idle state.
- Use the released backup/export control for VRA configuration if available in your version.
- Back up valuable LDPlayer profiles through LDPlayer’s documented tools separately.
- Record the current application version and read the destination release notes.
Know what is being backed up#
VRA configuration includes customer-created farm names, profile mappings, routines, schedules and supported preferences. It is not a backup of Android, Viking Rise accounts or game progress.
Do not edit generated configuration files by hand unless a released support article explicitly instructs you to do so. Use in-app import and restore controls where available.
Before uninstalling#
- 1
Stop schedules
Prevent a background run from starting during removal.
- 2
Export configuration
Keep the supported backup if you may reinstall later.
- 3
Review evidence retention
Delete diagnostic captures separately if that is your intention.
- 4
Leave LDPlayer deliberate
Removing VRA should not be treated as permission to delete emulator profiles.
A workflow update, app restart and emulator update are not the same#
Follow the release notes for the actual update being installed. Do not assume every change hot-reloads, or that installing a new desktop build can never interrupt work. A workflow refresh may have a different activation boundary from a service, native dependency or emulator change.
Record the running and target versions and prevent overlapping inputs during a required restart. Keep unresolved action evidence. An update is not permission to reset a checkpoint or repeat an uncertain resource spend, claim or march.
Change one emulator profile before the whole fleet#
- 1
Record the known setup
Keep the emulator/game versions, renderer, resolution, DPI, language and farm mapping in your notes.
- 2
Back up separately
Use the emulator vendor’s documented backup process. VRA configuration is not Android data or account recovery. LDPlayer’s multi-instance guide requires the relevant instance to be stopped for backup/restore.
- 3
Preserve the original
Keep the source profile and backup until the replacement is checked. Restore operations can replace data; select the intended destination deliberately.
- 4
Verify identity and playability
After a change, open the profile manually and confirm the game and intended character still work. Recheck the VRA mapping.
- 5
Retest a small routine
Inspect current controls and observed results before applying the same change to the rest of the fleet. Do not assume cross-version restore or downgrade compatibility.
Still stuck?
Complete the evidence checklist before contacting support. Never send passwords, recovery codes, payment details or private licence material.