| Previous | Next |
| ERROR_VOLMGR_STRUCTURE_SIZE_INVALID | ERROR_VOLMGR_TRANSACTION_IN_PROGRESS |
ERROR_VOLMGR_TOO_MANY_NOTIFICATION_REQUESTS
Why this is narrower than a generic disk error: volmgr too many notification requests
ERROR_VOLMGR_TOO_MANY_NOTIFICATION_REQUESTS has unsigned value 0xC0380042. In the volmgr layer, it rejects a specific contract because a notification wait is already pending for the registration and another asynchronous wait would duplicate it. Diagnosis of this result should follow volume-manager notification registration and pending wait request through one controlled state transition.
Dynamic volumes are represented as packs containing disks and volumes; each volume has one or more plexes, and each plex is assembled from members and extents. Indices and counts are relative to the submitted layout generation, while configuration logs are replicated across participating dynamic disks. This object model determines which identifiers, counts and ownership state are meaningful for this HRESULT.
Diagnosis of this result should begin with the object model and generation current at the failure. A later successful enumeration may describe a replacement object and cannot retroactively validate the rejected request.
Storage facts that change the diagnosis
| Storage diagnostic field | Value |
|---|---|
| Closest comparison | ERROR_VOLMGR_MAXIMUM_REGISTERED_USERS |
| Owning object | volume-manager notification registration and pending wait request |
| Rejected invariant | a notification wait is already pending for the registration and another asynchronous wait would duplicate it |
| Identity and generation | registration ID, task number, pending IRP count, process lifetime, pack ID and the notification generation returned before the failure |
| Narrow experiment | register one consumer, issue exactly one asynchronous wait, complete or cancel it, and compare registration/task identifiers at each step |
When it is followed by a secondary cleanup failure, store both codes with timestamps and retain this one as the initiating result.
A/B test for this HRESULT
- serialize the failing request and the enumeration from which its identifiers came while diagnosing this result.
- Preserve registration ID, task number, pending IRP count, process lifetime, pack ID and the notification generation returned before the failure while every handle is still valid for this HRESULT.
- Repeat the operation using this controlled change: register one consumer, issue exactly one asynchronous wait, complete or cancel it, and compare registration/task identifiers at each step.
- Close and reacquire the relevant objects, then run once more to test lifecycle correctness after this result.
The distinction from ERROR_VOLMGR_MAXIMUM_REGISTERED_USERS is operational. The decisive condition is a notification wait is already pending for the registration and another asynchronous wait would duplicate it; log the neighboring code separately so capability, identity and state are not conflated.
Mechanism-specific note
Notification registrations have two lifetimes: the registration itself and any outstanding asynchronous wait. Log both identifiers and the cancellation path. A service restart, handle close or notification reset can invalidate the old generation even when the numeric task value is later reused, so never match completion by task number alone.
Corrective action and regression check
Repair notification ownership and sequencing: cancel stale waits, unregister only live IDs, then create one replacement registration after the previous generation is closed. After correcting it, reopen the pack, volume, tier, snapshot or virtual disk so no cached generation participates in the validation run.
- The original request now reaches success or a documented later status with the intended layout and access mode.
- A new enumeration reports internally consistent IDs, counts, geometry and ownership for the object corrected after it.
- The passing state survives the lifecycle transition relevant to it, such as reopen, remount, owner change or detach/attach.
- The application still distinguishes it from
ERROR_VOLMGR_MAXIMUM_REGISTERED_USERSand has no unbounded retry loop.
Before responding to it with destructive cleanup, prove which object owns the failure. Changing every disk or provider at once prevents a meaningful regression test.
Technical references
- Microsoft: COM error codes for VOLMGR, VHD and SDIAG — documents the supported management path relevant to it.
- Microsoft: Virtual Disk Service object model — defines the volmgr objects used to interpret it.
- Microsoft: Pack object — primary API or object-model reference for the boundary.
- Microsoft: Virtual Disk Service common return codes — use this source to verify volmgr state and parameters for this HRESULT.
Looking for a different code? Search another status or error code.