Message 2 of 2
12 Jan 17 10:19
Join Date: 17 Feb 2012
Posts To This List: 596
Support for Legacy File System Filter Drivers
I think we are in the 'in between' state right now. They could pull the=20
registry value which allows them to load at any point. Maybe they are=20
delaying it because they realize how many systems would break out there?=
Similar to when they implemented WFP to remove all tcpip filter drivers.
Windows File System and Device Driver Consulting
------ Original Message ------
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" ( firstname.lastname@example.org )=20
>posted that after windows "vNext" Legacy File System Filter drivers=20
>would not load ( see=20
>To quote ....
>"Post Windows vNext, the reg key will be removed and the legacy file=20
>filter will be blocked by default. There won't be any option to unblock=
>file system filter."
>At that time, Windows vNext turned out to be Redstone 1 (Win 10 1607)=20
>so Post Windows vNext would be post Redstone 1, ie Redstone 2. I have=20
>found that on Redstone 2 my legacy file system filter driver (which is=20
>Microsoft 'signature only' certified) still loads and runs okay.
>Can i take it that Microsoft has pulled back from the stated plan=20
>regarding Legacy File System Filter drivers post Windows vNext or is it=
>that "Post Windows vNext" should be interpreted as "in one of the=20
>windows releases post vNext (but not sure which one)".
>We are planning to rewrite the legacy driver as a mini-filter driver=20
>but would still like to know what Microsoft's plans are in this area.
<...excess quoted lines suppressed...>