| Previous | Next |
| VDS_E_DUP_EMPTY_PACK_GUID | VDS_E_BAD_PNP_MESSAGE |
VDS_E_DRIVER_NO_PACK_NAME
VDS_E_DRIVER_NO_PACK_NAME indicates a broken contract between VDS, its software provider and the volume-management driver. Dynamic disks are grouped into packs, and the provider needs the pack identity to build stable pack, disk and volume objects.
Diagnose the provider-driver boundary
- Capture the VDS and storage-driver event logs before refreshing the service.
- Query existing pack objects and compare their IDs, names and online status.
- Avoid creating or importing dynamic volumes while pack identity is incomplete.
This is not fixed by renaming a user-visible volume or drive letter. The missing value originates below those objects. A service refresh may rebuild cached objects after a transient notification problem, but persistent recurrence points to driver/provider corruption or incompatibility. Because dynamic disks are legacy, migration planning is preferable to repeated cache repair.
IVdsPack · Pack properties · MS-VDS error codes
Looking for a different code? Search another status or error code.