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

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

More Info on Driver Writing and Debugging


The free OSR Learning Library has more than 50 articles on a wide variety of topics about writing and debugging device drivers and Minifilters. From introductory level to advanced. All the articles have been recently reviewed and updated, and are written using the clear and definitive style you've come to expect from OSR over the years.


Check out The OSR Learning Library at: https://www.osr.com/osr-learning-library/


UMDF 1.9 for Windows XP

shaguftasyedshaguftasyed Member Posts: 3

Hello,
We have a UMDF driver written for Vista in UMDF 1.11 and we want to run it on Windows XP. As XP supported latest up to UMDF 1.9, we are not able to install 1.11. The errors are like supporting wudfcoinstaller was not found or WUDFRd.sys not found. We need to have supporting files for UMDF 1.9 in order to make it work. Also, we found that these header files are a part of this KB "KB970159"(https://support.microsoft.com/en-in/help/970159/user-mode-driver-framework-version-1-9-update-for-windows-xp-for-windo). We are not able to find this update for Windows XP. Where can we find this? or is there any alternate way to make 1.11 run on XP?

Note all of the above is to compare a KMDF driver that works fine to UMDF which is partially written and we are trying to complete missing part. This is intended for Win 10 but KMDF driver we have works only on XP so we're trying to make UMDF work on XP too in order to complete the missing part and then we will make it compatible to Win 10. Please share your thoughts.

Comments

  • Tim_RobertsTim_Roberts Member - All Emails Posts: 13,771

    or is there any alternate way to make 1.11 run on XP?

    No. If you require features that aren't in 1.9, then your driver will not run on XP. You know the coinstallers for UMDF 1.9 are all in the WDK, yes?

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

  • shaguftasyedshaguftasyed Member Posts: 3

    @Tim_Roberts Thanks for replying. You mean 1.11 is a superset of 1.9? While installing 1.11 on XP, it says one of the coinstallers WudfUpdate_01011.dll is not a valid win32 app and the other error is like "#E339 Add Service: Binary "C:\WINDOWS\system32\DRIVERS\WUDFRd.sys" for service "WUDFRd" is not present." Since this is not the driver code itself, I've a difficulty understanding but does it look like features missing in 1.9?

  • Tim_RobertsTim_Roberts Member - All Emails Posts: 13,771

    Each version of KMDF and UMDF is a proper superset of all prior versions (well, within the major versions; UMDF 2 is entirely different from UMDF 1).

    ... WudfUpdate_01011.dll is not a valid win32 app ...

    That almost always means you tried to install a 64-bit DLL on a 32-bit system. Remember that XP is strictly 32-bit. You have to use the matching co-installers. However, in this specific case, 01011 is never going to work in XP. You've been told that. Don't try it. Go get 01009.

    ... for service "WUDFRd" is not present ...

    That is the UMDF redirector. It is the kernel component that sits in the driver stack and acts as a proxy for your user-mode driver. It would have been installed by the co-installer, if you had included the proper one.

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

  • shaguftasyedshaguftasyed Member Posts: 3

    Thanks @Tim_Roberts. I would need to re-compile to update 01009 in .inx. Do we need a copyfiles section for coinstallers? If I have this section, I land up into 22.9.1, co-installers missing or cannot be decompressed from source media.

  • Tim_RobertsTim_Roberts Member - All Emails Posts: 13,771

    Yes, since XP did not include KMDF or UMDF in any form, you have to copy them into place, you have to include the files in your driver package, and you have to include the INF sections that call them: https://docs.microsoft.com/en-us/windows-hardware/drivers/wdf/using-the-umdf-co-installer

    If you didn't use any 1.11 APIs in your driver, then you probably don't have to recompile.

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

  • Doron_HolanDoron_Holan Member - All Emails Posts: 10,553
    edited January 15

    If you didn't use any 1.11 APIs in your driver, then you probably don't have to recompile.

    When you compile a UMDF or KMDF driver, the min required framework version is baked into the binary and checked at load time. This means that if you compile your UMDF driver for v1.11, v1.11 or greater of the framework must be installed, regardless of the actual framework APIs called by the driver. To keep your life simple, consider recompiling and targeting v1.9

    d
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!

Upcoming OSR Seminars
OSR has suspended in-person seminars due to the Covid-19 outbreak. But, don't miss your training! Attend via the internet instead!
Writing WDF Drivers 7 Dec 2020 LIVE ONLINE
Internals & Software Drivers 25 Jan 2021 LIVE ONLINE
Developing Minifilters 8 March 2021 LIVE ONLINE