Legacy File system filters on windows server 2016

NTFSD
1

Will my legacy File system filter drivers run on Windows Server 2016 if I:

  1. Turn on the registry setting (IoBlockLegacyFsFilters) to allow legacy FS filters &
  2. EV sign said legacy FS drivers?

Is there something else that will need to be done?

Will legacy file system filters need to go through HLK tests in order to run on windows server 2016?
When I ran the HLK tests on my legacy FS filters (controller running and client running Windows 10 enterprise) it only selected the “DF-Hypervisor code integrity readiness test” to run, and that passed successfully. It sounds too easy and too good to be true, which lead me to believe I may be missing something.
I could not find clear documentation/help when it comes to Legacy FS filters & HLK. Any pointers appreciated.

Thx,
-Salil.

P.S.: I know we should move to the mini-filter model, and hopefully we’ll get to it sooner more than later.

2

That should be all that is needed but you know the registry setting to
allow for the loading of legacy fs filters will be going away very soon
and all legacy fs filters will be blocked from loading. As for HLK
testing for a legacy fs filter, I highly doubt that they (MSFT) will
logo certify them.

Pete

–
Kernel Drivers
Windows File System and Device Driver Consulting
www.KernelDrivers.com http:</http:>
866.263.9295

------ Original Message ------
From: xxxxx@yahoo.com
To: “Windows File Systems Devs Interest List”
Sent: 6/7/2016 7:39:26 PM
Subject: [ntfsd] Legacy File system filters on windows server 2016

>Will my legacy File system filter drivers run on Windows Server 2016 if
>I:
>1. Turn on the registry setting (IoBlockLegacyFsFilters) to allow
>legacy FS filters &
>2. EV sign said legacy FS drivers?
>
>Is there something else that will need to be done?
>
>Will legacy file system filters need to go through HLK tests in order
>to run on windows server 2016?
>When I ran the HLK tests on my legacy FS filters (controller running
>and client running Windows 10 enterprise) it only selected the
>“DF-Hypervisor code integrity readiness test” to run, and that passed
>successfully. It sounds too easy and too good to be true, which lead me
>to believe I may be missing something.
>I could not find clear documentation/help when it comes to Legacy FS
>filters & HLK. Any pointers appreciated.
>
>Thx,
>-Salil.
>
>P.S.: I know we should move to the mini-filter model, and hopefully
>we’ll get to it sooner more than later.
>
>—
>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:>

3

Thanks, Pete.

fs filters will be going away very soon
I assume that by ‘very soon’ you are implying post-Server 2016. That’s the impression I got from another post on OSR. As long as MS does not yank legacy FS filters support in Windows Server 2016, I am good.

doubt that they (MSFT) will logo certify them
And that is fine by me. All I am looking for is the bare-minimum things I *must* do in order to get my legacy FS filters to do their job on Windows Server 2016.