about ndis im driver installation

I have a ndis6 IM driver. When I install it in WIN7, the function of “DriverEntry” is called once. But I find In WIN10, the function of “DriverEntry” is called three times. The first time no adapters are bound. The second time adapters are boung and unbound . The last time it seems to be a normal installation. some adapters are bound and no adapter are unbound. Why is this happening? Is it normal ? Thanks.

Windows 10 may start, stop, and start again an NDIS miniport driver. This only happens the first time that the device is seen on the system, and after some types of driver updates. Windows does this to make sure that the driver sees any registry keys that were changed while installing the device.

In the upcoming “Fall Creators Update” release, we no longer need to do this. (Instead we’ve integrated with a new feature from the kernel PNP stack to allow the networking stack to delay the first start of the device until networking is finished setting up the network interface.)

In any case, it’s normal to see 2 DriverEntry calls the first time you install something. It maybe be normal to see other DriverEntry calls later, depending on what’s going on. Is this causing some problem?

Oh, No problem. Just that’s a bit odd. Thanks