| Previous | Next |
| STATUS_VOLMGR_NO_SUCH_USER | STATUS_VOLMGR_NUMBER_OF_MEMBERS_INVALID |
STATUS_VOLMGR_NOTIFICATION_RESET
The client must discard its old notification registration
STATUS_VOLMGR_NOTIFICATION_RESET explicitly tells the current notification user to unregister and register again. Any task or registration identity tied to the old notification state should be treated as invalid.
This is a protocol-state event, not a disk-health diagnosis. The Disk Management remote protocol maintains a callback relationship for notifications, and Microsoft documents that initialization controls whether a client can receive those callbacks. A reset breaks the assumptions of a long-lived listener even though storage objects may still be valid.
On receipt, rebuild notification state deliberately. Stop matching new events to old task numbers, tear down the stale registration, establish a new notification user, and then refresh the current disk/volume topology so no change is missed across the reset window.
What to inspect
- Invalidate cached notification-user and task identifiers associated with the previous registration.
- Unregister and re-register the listener as directed by the status text, then confirm callbacks resume.
- Re-enumerate storage objects after registration so the client has a current baseline rather than relying only on later events.
References
- Microsoft VOLMGR definition of STATUS_VOLMGR_NOTIFICATION_RESET.
- MS-DMRP client initialization and notification behavior.
- MS-DMRP volume-manager protocol terminology.
Looking for a different code? Search another status or error code.