| Previous | Next |
| IMAPI_S_IMAGE_FEATURE_NOT_SUPPORTED | RTC_S_ROAMING_NOT_SUPPORTED |
ERROR_SPACES_POOL_WAS_DELETED
The cached object no longer represents a live storage pool
ERROR_SPACES_POOL_WAS_DELETED is a synchronization result, not evidence that the pool deletion itself has just failed. The Storage Management provider has learned that the driver removed the pool, while the caller is still holding a CIM object, ObjectId, or PowerShell object created by an earlier enumeration.
Continuing with that stale instance can target an identity that no longer exists. The correct recovery is to refresh the storage model and decide whether a replacement pool with a different identity should be used. Recreating a pool with the same friendly name does not make an old object reference valid.
Checks that preserve the actual object identity
- Run a fresh
Get-StoragePoolenumeration instead of reusing a serialized object. - Compare
ObjectIdandUniqueId, not onlyFriendlyName. - Refresh any application-side cache after pool removal or storage-service restart.
- Confirm whether the pool was intentionally deleted by another management session.
- Inspect Storage Spaces operational events before attempting disk reset or pool recreation.
- Do not retry the original method indefinitely against the obsolete CIM instance.
References
- Microsoft: New-StoragePool
- Microsoft: Storage Spaces health and operational states
- Microsoft: troubleshoot Storage Spaces
Looking for a different code? Search another status or error code.