The problem is that this should be done after the executable is loaded (mapped + relocated if necessary + all the import table entries are prepared), but before the driver's entry point is invoked. The key to the victory is probably replacing the DxgkInitialize within the driver executable import section with the address of my function. My goal is to intercept this call.Ĭan anyone suggest me any useful source I can find information about how to achieve this? In its DriverEntry it's expected to call a DxgkInitialize system routine (exported by win32k.sys I guess). It's a Vista/7 display miniport driver to be exact.ĭisplay driver is loaded as a standard WDM driver. Theoretically in such cases it's recommended to create a filter driver, however in my case the driver doesn't expose a filter-compatible interface. I need to intercept system calls to a driver. Let me know if this helps you in the comments below.My question is regarding driver development for Windows 7. If you still have problems try running the Aero Troubleshooting utility by clicking on the Start Button and typing in Find an fix problems with transparency and then hit Enter.Īs a last resort you can try the old Windows Vista registry hack to enable Aero glass on low end systems. Click on the Start Button and type in check the windows experience index and hit Enter. This will run the Windows Experience performance tool to benchmark your computer and identify what features should be turned on and off. If no WDDM compatible drivers are found for your video adapter on Windows update try looking on the manufacturers Web site.Īfter you have, or your system has automatically updated your video adpater drivers to compatible WDDM drivers it is best to refresh the Windows Experience Index. To make Windows search for new drivers manually just click on the Start Button and type in Windows Update. In this scenario Windows will search on Windows Update for compatible drivers once an internet connection is established. When Windows 7 was installed compatible drivers were not found on the installation media.

The most common issue I have seen is a lack of compatible WDDM drivers. In most cases when you install Windows 7 Aero will be enabled but on some configurations various issues prevent the feature from starting. According to Microsoft the bare minimum requirements for Aero is a graphics card that supports DirectX 9.0 or newer and a native WDDM (Windows Display Driver Model) driver.

Without the slick glass interface a number of key features will be disabled such as taskbar thumbnails and Aero Peek. If you want the full Windows 7 experience the Aero glass interface is a must.

Wddm driver for windows 7 aero