Re[2]: Solution if IRP_MN_MOUNT_VOLUME is not called

I am unsure what this comment refers to.

That said, you do understand that mount requests are NOT sent to a file
system’s volume device object? They are sent to the device object which
you registered using IoRegisterFileSystem(). And, again, the order in
which the system invokes the mount request for each registered file
system is the order in which they registered, IIRC.

Pete


Kernel Drivers
Windows File System and Device Driver Consulting
www.KernelDrivers.com
866.263.9295

------ Original Message ------
From: xxxxx@gmail.com
To: “Windows File Systems Devs Interest List”
Sent: 8/17/2017 1:20:20 PM
Subject: RE:[ntfsd] Solution if IRP_MN_MOUNT_VOLUME is not called

>I forgot says about filespy in “show minifilter” , i don’t view my
>volume.
>
>—
>NTFSD is sponsored by OSR
>
>
>MONTHLY seminars on crash dump analysis, WDF, Windows internals and
>software drivers!
>Details at http:
>
>To unsubscribe, visit the List Server section of OSR Online at
>http:</http:></http:>

Nothing to do I did not find anything,
I followed the documentation:
https://docs.microsoft.com/en-us/windows-hardware/drivers/ifs/mounting-a-volume
Unsuccess problem not solved.

I do not know if I hallucinate:
So I try to mount the VPB and associate it in DeviceObject-> VPB and
It seems to work good with out BSOD (SANS BSOD).
Problem solved partially.

Now i force mount and the disk filesystem work good.

Otherwise, if a Windows update makes this method incompatible,
Can we send me the executable link (KBXXXX) of this windows update?

I want to be in compliance if we given solutions

However later I will test it on another machine.

Thanks anyways.

The link you provided covers mount processing from a high level, mostly
outside of how a file system would actually implement mount processing.
That said, are you calling IoRegisterFileSystem() in your code?

Pete


Kernel Drivers
Windows File System and Device Driver Consulting
www.KernelDrivers.com
866.263.9295

------ Original Message ------
From: xxxxx@gmail.com
To: “Windows File Systems Devs Interest List”
Sent: 8/18/2017 11:53:21 AM
Subject: RE:[ntfsd] Solution if IRP_MN_MOUNT_VOLUME is not called

>Nothing to do I did not find anything,
>I followed the documentation:
>https://docs.microsoft.com/en-us/windows-hardware/drivers/ifs/mounting-a-volume
>Unsuccess problem not solved.
>
>I do not know if I hallucinate:
>So I try to mount the VPB and associate it in DeviceObject-> VPB and
>It seems to work good with out BSOD (SANS BSOD).
>Problem solved partially.
>
>Now i force mount and the disk filesystem work good.
>
>
>Otherwise, if a Windows update makes this method incompatible,
>Can we send me the executable link (KBXXXX) of this windows update?
>
>I want to be in compliance if we given solutions
>
>However later I will test it on another machine.
>
>Thanks anyways.
>
>—
>NTFSD is sponsored by OSR
>
>
>MONTHLY seminars on crash dump analysis, WDF, Windows internals and
>software drivers!
>Details at http:
>
>To unsubscribe, visit the List Server section of OSR Online at
>http:</http:></http:>