RadioBOSS Complete Configuration Loss Following Windows Crash — Successfully Recovered Using Previous Versions
Date: 9 November 2026
Operating system: Windows
Application: RadioBOSS
Status: Configuration successfully recovered
1. What happened
On 9 November 2026, my Windows computer suffered a serious system disruption while I was speaking with a technical engineer.
During the incident:
- My Focusrite Scarlett audio interface stopped producing sound.
- Several Windows services and applications recorded errors.
- RadioBOSS lost its broadcasting configuration and associated settings.
- My RadioBOSS registration information also had to be re-entered.
- My normal RadioBOSS settings and backup archives could no longer be located.
RadioBOSS had previously been configured to save its profile automatically. I had also been using dated backup archives.
When I reopened RadioBOSS following the incident, its previous broadcasting configuration was no longer available.
2. Searching for missing backups
I initially searched for the expected ZIP backup archives, including files named similarly to:
- Radio Boss Settings Backup Archive.zip
- 2026-11-09.zip
I also carried out a recursive PowerShell search of the C: drive for ZIP files with names containing RadioBOSS, Settings, Backup or November 2026.
The search did not locate the expected RadioBOSS backup archives.
This search alone could not prove whether the files had been deleted, moved or stored elsewhere.
3. Windows errors recorded
During the investigation, Windows Event Viewer showed several errors, including:
OpenAI Codex Sandbox Service
- Source: CodexSandboxService.OpenAI.Codex
- Event ID: 1003
- Time: 5:58:58 PM
- Message: Cannot complete this function.
An Event ID 1000 entry was also recorded for the same service at that time.
PRI-Driver
- Event ID: 7000
- Time: 6:03:09 PM
- Error: The system cannot find the file specified.
Corsair Link 4
- Application: CorsairLink4.Service.exe
- Version: 4.9.9.3
- Exception: 0xc0000005 (access violation).
Windows SysMain
- Windows reported that it could not load the performance-counter DLL sysmain.dll.
These events were recorded during the investigation. Their causal relationship to the RadioBOSS configuration loss has not been established.
4. Locating the RadioBOSS configuration directory
Using PowerShell, I checked the RadioBOSS application-data location:
%APPDATA%\djsoft.net
The directory contained:
RadioBOSS_626329039
The full path was:
C:\Users\bigburtha\AppData\Roaming\djsoft.net\RadioBOSS_626329039
The associated radioboss_key file still existed but had been modified at 6:39:01 PM, when I re-entered my registration information.
The active RadioBOSS settings folder did not appear to contain the previous working configuration.
5. Finding the previous configuration using Windows Previous Versions
The breakthrough came from Windows' built-in
Previous Versions facility.
I right-clicked the RadioBOSS settings folder, opened
Properties → Previous Versions, and discovered three earlier snapshots:
| Date | Time |
|---|
| 8 November 2026 | 2:34 PM |
| 8 November 2026 | 8:11 AM |
| 7 November 2026 | 4:08 PM |
I opened the 8 November snapshots and found that they contained RadioBOSS configuration files and folders, including:
- Profile
- Presets
- base.ini
- base.ini.bak
- adscheduler.ini
- EncoderStats.db
- Database
- Log
- M3U playlist files
- Additional configuration INI files
This demonstrated that copies of the pre-incident RadioBOSS configuration were still accessible through Windows' snapshot mechanism.
6. Recovery procedure
The recovery was carried out as follows:
- Located the RadioBOSS configuration directory under %APPDATA%\djsoft.net.
- Opened its Windows Previous Versions property page.
- Located two snapshots dated 8 November 2026.
- Copied both snapshot directories to the D: drive for safekeeping.
- Confirmed that the recovered directories contained the RadioBOSS configuration and encoder INI files.
- Ensured RadioBOSS was completely closed.
- Preserved a backup before making changes.
- Copied the recovered configuration files into the existing active RadioBOSS_626329039 directory, replacing matching files.
- Reopened RadioBOSS.
Result: The RadioBOSS configuration returned successfully.
It was not necessary to reinstall RadioBOSS or reconstruct the broadcasting configuration manually.
7. What this demonstrates
This recovery highlights the importance of the RadioBOSS configuration directory as a separate recovery source from any ZIP backup archives.
Although the expected backup archives could not be located, Windows Previous Versions retained usable copies of the application settings.
For other RadioBOSS users experiencing a sudden loss of configuration:
- Avoid reinstalling or resetting the application immediately.
- Locate the active RadioBOSS configuration directory.
- Check Windows Previous Versions.
- Copy recoverable snapshots to another drive before attempting restoration.
- Close RadioBOSS before restoring files.
- Restore the previous configuration only after preserving the existing files.
Previous Versions will only help where suitable snapshots or backups exist.
8. Questions for DJSoft / RadioBOSS support
I would appreciate clarification on the following:
- Under what circumstances can RadioBOSS start with its previous configuration missing or reset?
- Does RadioBOSS maintain any internal emergency copy of its last working profile?
- Can an unexpected Windows crash cause the application to overwrite or recreate its settings directory?
- What is the relationship between Save profile automatically and the separate settings backup archives?
- Is there a recommended way to protect the complete configuration against unexpected corruption or loss?
The recovery was successful, but the original cause of the configuration loss remains undetermined.
I hope this record helps other RadioBOSS users who encounter a similar situation.