| Previous | Next |
| ERROR_INSTALL_FIREWALL_SERVICE_NOT_RUNNING | ERROR_INSTALL_VOLUME_NOT_EMPTY |
ERROR_PACKAGE_MOVE_FAILED
Package relocation failed between managed deployment volumes
ERROR_PACKAGE_MOVE_FAILED is returned by the package-volume relocation path, not by a normal file move. Windows must transfer package content, preserve registration and integrity, update deployment metadata, and ensure the target PackageVolume is online and suitable.
Record the package full name, source and target volume identities, free space, volume state, and extended deployment error. Check whether the package is in use, partially staged, or dependent on streaming content. Do not move the protected package directory with Explorer or a file utility; only PackageManager can update the corresponding package-volume records safely.
What to inspect
- Verify the target is a registered online PackageVolume.
- Check free space, package use, and pending servicing.
- Use MovePackageToVolumeAsync and retain its extended result.
References
- Microsoft: moving a package to another volume
- Microsoft: PackageVolume management
- Microsoft: deployment extended-error diagnostics
Looking for a different code? Search another status or error code.