MRCBT is surprised... Events 7 then 6 on VHD Dismount


Author
Message
RayG
RayG
Advanced Member
Advanced Member (554 reputation)Advanced Member (554 reputation)Advanced Member (554 reputation)Advanced Member (554 reputation)Advanced Member (554 reputation)Advanced Member (554 reputation)Advanced Member (554 reputation)Advanced Member (554 reputation)Advanced Member (554 reputation)
Group: Forum Members
Posts: 277, Visits: 1.3K
When I dismount a VHD I see these two errors from MRCBT:

Device \Device\HarddiskVolume22 has been surprise removed (IRP_MN_SURPRISE_REMOVAL) - event 7
Device \Device\HarddiskVolume22 has been removed (IRP_MN_REMOVE_DEVICE) - event 6

Using the syntax:

Dismount-VHD -Path ('{0}' -f $VHDFile)

Why does MRCBT get "surprised" at it's removal?

The VHD is mounted on a directory and not a drive letter.


Regards
RayG
Windows10 Pro X64 V1809 B17763.194 MR v7.2.3906

JamieW
JamieW
Macrium Representative
Macrium Representative (210 reputation)Macrium Representative (210 reputation)Macrium Representative (210 reputation)Macrium Representative (210 reputation)Macrium Representative (210 reputation)Macrium Representative (210 reputation)Macrium Representative (210 reputation)Macrium Representative (210 reputation)Macrium Representative (210 reputation)
Group: Moderators
Posts: 135, Visits: 1.5K
RayG - 19 November 2018 11:50 AM
When I dismount a VHD I see these two errors from MRCBT:

Device \Device\HarddiskVolume22 has been surprise removed (IRP_MN_SURPRISE_REMOVAL) - event 7
Device \Device\HarddiskVolume22 has been removed (IRP_MN_REMOVE_DEVICE) - event 6

Using the syntax:

Dismount-VHD -Path ('{0}' -f $VHDFile)

Why does MRCBT get "surprised" at it's removal?

The VHD is mounted on a directory and not a drive letter.

​Hi RayG,

Thank you for your post.​​

The surprised removal​ event is issued to CBT by the Windows Plug&Play Manager to tell it that a device has been removed.

​Unfortunately, the name is slightly misleading for VHD(X) devices and the use of this event by the Microsoft VHD(X) driver is outside of our control, however; this is completely normal behaviour for this device type.

Kind Regards,
Macrium Support​​​
​​



RayG
RayG
Advanced Member
Advanced Member (554 reputation)Advanced Member (554 reputation)Advanced Member (554 reputation)Advanced Member (554 reputation)Advanced Member (554 reputation)Advanced Member (554 reputation)Advanced Member (554 reputation)Advanced Member (554 reputation)Advanced Member (554 reputation)
Group: Forum Members
Posts: 277, Visits: 1.3K
JamieW - 19 November 2018 1:46 PM

Hi RayG,

Thank you for your post.

The surprised removal event is issued to CBT by the Windows Plug&Play Manager to tell it that a device has been removed.

Unfortunately, the name is slightly misleading for VHD(X) devices and the use of this event by the Microsoft VHD(X) driver is outside of our control, however; this is completely normal behaviour for this device type.

Kind Regards,
Macrium Support

Thanks for the confirmation all is well Jamie.

Regards
RayG
Windows10 Pro X64 V1809 B17763.194 MR v7.2.3906

GO

Merge Selected

Merge into selected topic...



Merge into merge target...



Merge into a specific topic ID...




Similar Topics

Reading This Topic

Login

Explore
Messages
Mentions
Search