CNdisApi::IsDriverLoaded wrong output

Home Forums Discussions Support Portal CNdisApi::IsDriverLoaded wrong output

This topic contains 3 replies, has 2 voices, and was last updated by  Vadim Smirnov 3 weeks, 2 days ago.

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #10303

    deepannegi
    Participant

    I recently encountered a case with a customer where CNdisApi::IsDriverLoaded() returned true but the driver was not installed. There was no entry for the driver when I tried netcfg -q command. Any steps to debug this or solution to this? Need Help.

    #10304

    Vadim Smirnov
    Moderator

    Source code for latest version of ndisapi with a couple of new samples is now available on Github. I’ve just tested dnstracer with and and without WinpkFilter driver installed and availability of the driver was reported properly (so the calls to CNdisApi::IsDriverLoaded worked correct).

    What was the Windows version you have tested? I’m not sure, but if you use NCF_HIDDEN attribute for your driver build then it may also affect netcfg output.

    #10305

    deepannegi
    Participant

    OS is Windows 7 Professional
    Driver version returned by CNdisApi::GetVersion() is: 34025472

    We do use NCF_HIDDEN but I don’t think NCF_HIDDEN not affects netcfg output (works fine on my system).

    Is there any change in the latest releases that fix a similar issue?

    #10315

    Vadim Smirnov
    Moderator

    Driver version returned by CNdisApi::GetVersion() is: 34025472

    In hex this is 0x02073000 or version 3.2.7.

    And if NDISAPI returns this value then it definitely means that driver is loaded!

Viewing 4 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic.