Hi.
I am in the process of modifying an installer that installs a file system filter driver. Currently this is done via the rundll32 call…
rundll32.exe setupapi,InstallHinfSection DefaultInstall 132 %AppFolder%\FileSystemFilterDriver\FileSystemFilterDriver.inf
I want this action to install the driver and NOT promot a reboot but whenever I change the reboot mode to 0 or 128 it still prompts for a reboot.
Does anyone have any suggestions ?
Does installing a file system filter driver always force a prompt for reboot regardless ?
Regards
Steve Williams
Is this a minifilter or full file system filter?
I never get a reboot when I install a file system minifilter using the
method that you are using.
Bill Wandel
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@baesystems.com
Sent: Friday, August 28, 2009 5:00 AM
To: Windows File Systems Devs Interest List
Subject: [ntfsd] NeverReboot on install of FileSystemFilterDriver
Hi.
I am in the process of modifying an installer that installs a file system
filter driver. Currently this is done via the rundll32 call…
rundll32.exe setupapi,InstallHinfSection DefaultInstall 132
%AppFolder%\FileSystemFilterDriver\FileSystemFilterDriver.inf
I want this action to install the driver and NOT promot a reboot but
whenever I change the reboot mode to 0 or 128 it still prompts for a reboot.
Does anyone have any suggestions ?
Does installing a file system filter driver always force a prompt for reboot
regardless ?
Regards
Steve Williams
NTFSD is sponsored by OSR
For our schedule of debugging and file system seminars (including our new fs
mini-filter seminar) visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
Thanks for the reply…
As far as I am aware it is a just a mini-filter…
I didn’t write it originally but have been lumbered with supporting it.
It must be something else in the instalation process then that is causing this reboot.
Regards.
What is the value of StartType in the inf file?
wrote in message news:xxxxx@ntfsd…
> Thanks for the reply…
>
> As far as I am aware it is a just a mini-filter…
> I didn’t write it originally but have been lumbered with supporting it.
>
> It must be something else in the instalation process then that is causing
> this reboot.
>
> Regards.
>
Steve,
my recommendation is to use Setup API’s like SetupInstallFilesFromInfSection
along with File queue. this will user a very nice installation experience.
you can also try driver installation package , I am not sure if it works
for a file system filter driver though.
regards,
Vijay
From:
Sent: Friday, August 28, 2009 2:30 PM
To: “Windows File Systems Devs Interest List”
Subject: [ntfsd] NeverReboot on install of FileSystemFilterDriver
> Hi.
>
>
> I am in the process of modifying an installer that installs a file system
> filter driver. Currently this is done via the rundll32 call…
> rundll32.exe setupapi,InstallHinfSection DefaultInstall 132
> %AppFolder%\FileSystemFilterDriver\FileSystemFilterDriver.inf
>
> I want this action to install the driver and NOT promot a reboot but
> whenever I change the reboot mode to 0 or 128 it still prompts for a
> reboot.
>
> Does anyone have any suggestions ?
>
> Does installing a file system filter driver always force a prompt for
> reboot regardless ?
>
> Regards
> Steve Williams
>
> —
> NTFSD is sponsored by OSR
>
> For our schedule of debugging and file system seminars
> (including our new fs mini-filter seminar) visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
The value of StartType in the inf file is 0.
And I’m assuming that changing that to (say) 3 changes the behavior.
I have never been able to work around that, although I haven’t tried too
hard since I usually need the reboot for other reasons and I just ignore the
warnings when I am developing.
Rod
Hi there…
I was thinking along the same lines so changed it (StartType) to 3 and it stopped the Reboot prompt…
I had to reset this to 0 later in the installation process to ensure that the filter driver stated correctly on a reboot but that sorted it out…
Many thanks for all that commented.
Steve.