Back in March 2016 “ntfsd member 158467” ( xxxxx@microsoft.com ) posted that after windows “vNext” Legacy File System Filter drivers would not load ( see http://www.osronline.com/showThread.cfm?link=275309 ).
To quote …
“Post Windows vNext, the reg key will be removed and the legacy file system
filter will be blocked by default. There won’t be any option to unblock legacy
file system filter.”
At that time, Windows vNext turned out to be Redstone 1 (Win 10 1607) so Post Windows vNext would be post Redstone 1, ie Redstone 2. I have found that on Redstone 2 my legacy file system filter driver (which is Microsoft ‘signature only’ certified) still loads and runs okay.
Can i take it that Microsoft has pulled back from the stated plan regarding Legacy File System Filter drivers post Windows vNext or is it that “Post Windows vNext” should be interpreted as “in one of the windows releases post vNext (but not sure which one)”.
We are planning to rewrite the legacy driver as a mini-filter driver but would still like to know what Microsoft’s plans are in this area.
Thanks,
Paolo
I think we are in the ‘in between’ state right now. They could pull the
registry value which allows them to load at any point. Maybe they are
delaying it because they realize how many systems would break out there?
Similar to when they implemented WFP to remove all tcpip filter drivers.
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: 1/10/2017 9:10:17 AM
Subject: [ntfsd] Support for Legacy File System Filter Drivers
>Back in March 2016 “ntfsd member 158467” ( xxxxx@microsoft.com )
>posted that after windows “vNext” Legacy File System Filter drivers
>would not load ( see
>http://www.osronline.com/showThread.cfm?link=275309 ).
>
>To quote …
>
>“Post Windows vNext, the reg key will be removed and the legacy file
>system
>filter will be blocked by default. There won’t be any option to unblock
>legacy
>file system filter.”
>
>At that time, Windows vNext turned out to be Redstone 1 (Win 10 1607)
>so Post Windows vNext would be post Redstone 1, ie Redstone 2. I have
>found that on Redstone 2 my legacy file system filter driver (which is
>Microsoft ‘signature only’ certified) still loads and runs okay.
>
>Can i take it that Microsoft has pulled back from the stated plan
>regarding Legacy File System Filter drivers post Windows vNext or is it
>that “Post Windows vNext” should be interpreted as “in one of the
>windows releases post vNext (but not sure which one)”.
>
>We are planning to rewrite the legacy driver as a mini-filter driver
>but would still like to know what Microsoft’s plans are in this area.
>
>Thanks,
>
>Paolo
>
>
>
>
>
>—
>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:>