| Previous | Next |
| STATUS_VOLMGR_INTERLEAVE_LENGTH_INVALID | STATUS_VOLMGR_MEMBER_IN_SYNC |
STATUS_VOLMGR_MAXIMUM_REGISTERED_USERS
A new notification client cannot be registered
STATUS_VOLMGR_MAXIMUM_REGISTERED_USERS belongs to the notification side of the volume-management interface. The registration table is already at its supported limit, so another client cannot join it.
This status is about management clients, not about users signed in to Windows and not about the number of volumes. The Disk Management remote protocol has an explicit initialization and notification interface; Microsoft notes that clients cannot receive notifications until initialization has established that callback relationship.
Look for leaked or duplicated registrations in the component using Volume Manager. A service that reconnects without unregistering its previous notification identity can exhaust a bounded table even though storage topology is unchanged.
What to inspect
- Identify the process or service performing registration and count its reconnect or restart attempts.
- Verify that shutdown and error paths unregister notification users instead of leaving stale registrations.
- Do not alter disk layouts to fix this code; the failing resource is the notification-registration capacity.
References
- Microsoft VOLMGR table for STATUS_VOLMGR_MAXIMUM_REGISTERED_USERS.
- MS-DMRP initialization and notification callback behavior.
- MS-DMRP terminology for the volume manager protocol.
Looking for a different code? Search another status or error code.