Windows System Software -- Consulting, Training, Development -- Unique Expertise, Guaranteed Results

Before Posting... Please check out the Community Guidelines in the
Announcements and Administration Category.

WDF coInstaller problem

I am working on a WDF Filter driver using the Windows 10 WDK.



While building the driver $KMDFVERSION$ expands to 1.15 as expected.



I am modeling my install after the NONPNP example in the WDK. I need the version 1.15 compatible version of
the coInstaller DLL



The Windows 10 WDK redistributables directory has WdfCoInstaller01007.dll, WdfCoInstaller01009.dll, and
WdfCoInstaller01011.dll. These seem to correspond with WDF versions 1.07, 1.09 and 1.11.



Where do I find the CoInstaller DLL for WDF 1.15?



Ed

Comments

  • Doron_HolanDoron_Holan Posts: 10,360
    1.11 was the last version that used a coinstaller and went down level. Every version afterward is only available on the os that released that version.

    Sent from my Windows 10 phone

    From: xxxxx@eclectic-eng.com
    Sent: Tuesday, May 10, 2016 8:14 AM
    To: Windows System Software Devs Interest List
    Subject: [ntdev] WDF coInstaller problem

    I am working on a WDF Filter driver using the Windows 10 WDK.

    While building the driver $KMDFVERSION$ expands to 1.15 as expected.

    I am modeling my install after the NONPNP example in the WDK. I need the version 1.15 compatible version of the coInstaller DLL

    The Windows 10 WDK redistributables directory has WdfCoInstaller01007.dll, WdfCoInstaller01009.dll, and WdfCoInstaller01011.dll. These seem to correspond with WDF versions 1.07, 1.09 and 1.11.

    Where do I find the CoInstaller DLL for WDF 1.15?

    Ed

    ---
    NTDEV is sponsored by OSR

    Visit the list online at:

    MONTHLY seminars on crash dump analysis, WDF, Windows internals and software drivers!
    Details at

    To unsubscribe, visit the List Server section of OSR Online at
  • Doron,



    How does this change the installation procedure for a WDF filter driver?



    Are the wdf pre and post install and remove calls still needed?

    Does this mean that a WDF driver built with the Windows 10 WDK can only run on Windows 10?

    How do I write a WDF driver which will run on multiple versions of Windows ?



    Ed



    From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Doron Holan
    Sent: Tuesday, May 10, 2016 11:30 AM
    To: Windows System Software Devs Interest List
    Subject: RE: [ntdev] WDF coInstaller problem



    1.11 was the last version that used a coinstaller and went down level. Every version afterward is only
    available on the os that released that version.



    Sent from my Windows 10 phone



    From: xxxxx@eclectic-eng.com
    Sent: Tuesday, May 10, 2016 8:14 AM
    To: Windows System Software Devs Interest List
    Subject: [ntdev] WDF coInstaller problem



    I am working on a WDF Filter driver using the Windows 10 WDK.



    While building the driver $KMDFVERSION$ expands to 1.15 as expected.



    I am modeling my install after the NONPNP example in the WDK. I need the version 1.15 compatible version of
    the coInstaller DLL



    The Windows 10 WDK redistributables directory has WdfCoInstaller01007.dll, WdfCoInstaller01009.dll, and
    WdfCoInstaller01011.dll. These seem to correspond with WDF versions 1.07, 1.09 and 1.11.



    Where do I find the CoInstaller DLL for WDF 1.15?



    Ed


    ---
    NTDEV is sponsored by OSR

    Visit the list online at:

    MONTHLY seminars on crash dump analysis, WDF, Windows internals and software drivers!
    Details at

    To unsubscribe, visit the List Server section of OSR Online at



    ---
    NTDEV is sponsored by OSR

    Visit the list online at:

    MONTHLY seminars on crash dump analysis, WDF, Windows internals and software drivers!
    Details at

    To unsubscribe, visit the List Server section of OSR Online at
  • Tim_RobertsTim_Roberts Posts: 12,622
    xxxxx@eclectic-eng.com wrote:
    >
    >
    > How does this change the installation procedure for a WDF filter driver?
    >

    If your driver is built to use KMDF 1.15, then you don't need to use a
    co-installer. You can assume that KMDF is already present. That does
    mean your driver will only work on Windows 10 or higher.


    > Are the wdf pre and post install and remove calls still needed?
    >

    No.


    > Does this mean that a WDF driver built with the Windows 10 WDK can
    > only run on Windows 10?
    >

    No, but it means that a driver built for KMDF 1.15 can only run on
    Windows 10. You can choose earlier KMDF versions.


    > How do I write a WDF driver which will run on multiple
    > versions of Windows ?
    >

    Use KMDF 1.11 if you need to go back to Vista. Use KMDF 1.9 if you need
    to go back to XP.

    --
    Tim Roberts, xxxxx@probo.com
    Providenza & Boekelheide, Inc.

    Tim Roberts, [email protected]
    Providenza & Boekelheide, Inc.

  • <quote>
    1.11 was the last version that used a coinstaller and went down level. Every
    version afterward is only available on the os that released that version.
    </quote>

    I'm embarrassed to say that somehow I managed to miss this fact (perhaps I didn't get the memo?)... But this is a pretty big change from the V1.11 days and before, right?

    For the benefit for those of us watching at home, can you clarify a bit please? This definitively means that if I write a driver using 1.15, I can't run that driver on a down-level box? Can I WU V1.15 onto an older OS version, say... Windows 7?

    In practice, this hasn't been a problem (obviously, because I haven't noticed it in all this time) because stuff we've written that supports down-level versions of Windows (say, Windows XP and later) is written to the older version of the Framework, and stuff that's targeted exclusively to Win 10 or later (for example) requires Win 10 and thus uses the newest version of the Framework.

    Still... a surprise.

    Peter
    OSR
    @OSRDrivers

    Peter Viscarola
    OSR
    @OSRDrivers

  • Tim_RobertsTim_Roberts Posts: 12,622
    xxxxx@osr.com wrote:
    > <quote>
    > 1.11 was the last version that used a coinstaller and went down level. Every
    > version afterward is only available on the os that released that version.
    > </quote>
    >
    > I'm embarrassed to say that somehow I managed to miss this fact (perhaps I didn't get the memo?)... But this is a pretty big change from the V1.11 days and before, right?
    >
    > For the benefit for those of us watching at home, can you clarify a bit please? This definitively means that if I write a driver using 1.15, I can't run that driver on a down-level box? Can I WU V1.15 onto an older OS version, say... Windows 7?

    No, it can't, and this is actually documented:


    https://msdn.microsoft.com/en-us/windows/hardware/drivers/wdf/kmdf-version-history

    1.13 will not run on anything before 8.1. 1.15 will not run on anything
    before 10. 1.17 will not run on anything before the 1511 update. Put
    simply, starting with 1.13, KMDF will not run on any system unless it is
    in the box.


    > In practice, this hasn't been a problem (obviously, because I haven't noticed it in all this time) because stuff we've written that supports down-level versions of Windows (say, Windows XP and later) is written to the older version of the Framework, and stuff that's targeted exclusively to Win 10 or later (for example) requires Win 10 and thus uses the newest version of the Framework.

    Yes. Maybe I also missed a memo, but I haven't seen anything in KMDF
    beyond 1.11 that compels me to switch.

    --
    Tim Roberts, xxxxx@probo.com
    Providenza & Boekelheide, Inc.

    Tim Roberts, [email protected]
    Providenza & Boekelheide, Inc.

  • <quote>
    No, it can't, and this is actually documented:

    https://msdn.microsoft.com/en-us/windows/hardware/drivers/wdf/kmdf-version-histor
    y
    </quote>

    Thank you, Tim.

    Imagine that. I missed an entry in a table on one of an endless set of MSDN doc pages.

    This is kind of a big deal. It changes the long-established policy of the latest Framework supporting down-level versions of the OS.

    A blog post from the WDF Team calling attention to this would have been appreciated. Well, now we know. I've missed this change for about two years. Sigh.

    Peter
    OSR
    @OSRDrivers

    Peter Viscarola
    OSR
    @OSRDrivers

  • Doron_HolanDoron_Holan Posts: 10,360
    This change happened in the win8 timeframe and well before win8 RTM, I think the first beta release had this policy in place.

    d

    -----Original Message-----
    From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@osr.com
    Sent: Wednesday, May 11, 2016 10:37 AM
    To: Windows System Software Devs Interest List <xxxxx@lists.osr.com>
    Subject: RE:[ntdev] WDF coInstaller problem

    <quote>
    No, it can't, and this is actually documented:

    https://msdn.microsoft.com/en-us/windows/hardware/drivers/wdf/kmdf-version-histor
    y
    </quote>

    Thank you, Tim.

    Imagine that. I missed an entry in a table on one of an endless set of MSDN doc pages.

    This is kind of a big deal. It changes the long-established policy of the latest Framework supporting down-level versions of the OS.

    A blog post from the WDF Team calling attention to this would have been appreciated. Well, now we know. I've missed this change for about two years. Sigh.

    Peter
    OSR
    @OSRDrivers


    ---
    NTDEV is sponsored by OSR

    Visit the list online at: <http://www.osronline.com/showlists.cfm?list=ntdev>;

    MONTHLY seminars on crash dump analysis, WDF, Windows internals and software drivers!
    Details at <http://www.osr.com/seminars>;

    To unsubscribe, visit the List Server section of OSR Online at <http://www.osronline.com/page.cfm?name=ListServer>;
  • <quote>
    This change happened in the win8 timeframe and well before win8 RTM
    </quote>

    There was just too much happening in that timeframe for me to notice.

    Now that I've had more time to think about this, I'm really not sure it matters that much. Yes, it's a dramatic departure from the past policy. But, at the end of the day, I'm not sure it much matters from a practical point of view.

    Peter
    OSR
    @OSRDrivers

    Peter Viscarola
    OSR
    @OSRDrivers

Sign In or Register to comment.

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!