Device Information Could Not Be Stored
Troubleshooting when device information cannot be written to the local configuration store during pre-migration (~25%).
Description
During pre-migration, the application collects device details such as hostname, serial number, join state, Intune ID, Entra device ID, Autopilot ID, and local domain.
This error occurs when one or more values cannot be written to the local configuration store.
No domain leave, Entra disconnect, provisioning package installation, or profile migration has started at this stage.
Quick Reference
| Item | Details |
|---|---|
| Stage | Pre-Migration device inventory |
| Progress | Around 25% |
| Device impact | No destructive migration changes have been made |
| Safe to retry | Yes |
| Responsibility | Customer IT administrator |
What You Will See
Application Message
Migration failed in module StoredeviceDetails
Portal Log
Migration failed in module StoredeviceDetails
Root Cause
The application is unable to write device information to the local configuration store.
Common causes:
- Endpoint security or application control blocking write operations
- Policy restrictions preventing updates to system configuration
- Local configuration store missing or inaccessible
- Registry hive locked or system inconsistency
Diagnosis
Run the following checks in PowerShell (Administrator):
Step 1 – Confirm the configuration store exists
Test-Path "HKLM:\SOFTWARE\OpsoleMigrate"
Step 2 – Test write access
Set-ItemProperty -Path "HKLM:\SOFTWARE\OpsoleMigrate" -Name "TestWrite" -Value "OK" -Type String -Force
Get-ItemProperty -Path "HKLM:\SOFTWARE\OpsoleMigrate" -Name "TestWrite"
| Result | Meaning |
|---|---|
| Step 1 returns False | Configuration store is missing |
| Step 2 fails with access denied | Security policy or endpoint protection blocking write |
| Step 2 succeeds | Retry migration after ensuring no interference |
Resolution
Write Operation Blocked
Allow write access to the configuration store:
HKLM:\SOFTWARE\OpsoleMigrate
Ensure endpoint security or application control does not block the migration process.
Configuration Store Missing
Re-run the migration to allow the application to recreate the required configuration path.
System Inconsistency
Run:
sfc /scannow
Dism /Online /Cleanup-Image /RestoreHealth
Restart the device before retrying.
Recovery Steps
- Close the Opsole Migrate application
- Re-open the application
- Start migration again
When to Contact Support
Contact support@opsole.com if:
- Manual write test succeeds but the issue persists
- Multiple devices show the same failure unexpectedly
Related Logs
- Event Viewer → Application and Services Logs → OpsoleMigrate
How is this guide?