| Passing the WLKs is, absolutely, a best practice. But, with all due respect, Mr. cpgxiii, you seem to not understand the vast extent of systems that use Windows. It is simply NOT POSSIBLE to run the HLKs on certain hardware systems. Let me give you a few examples: We write a driver for an unmanned aircraft. The driver runs on a custom processor box, with custom, on-board hardware, that's inside the aircraft. This custom system will not support the HLK client. Ever. The hardware for which we've written the driver cannot be separated from the custom system. This customer is now screwed. We write a driver for a device that lives in a piece of industrial equipment. Even if we could pull the boards for which the driver was written, and stick them into a system that was capable of serving as an HLK client, the hardware is designed in such as a way that is designed to be never powered off. This device, therefore, does not support ANY non D0 power states. While it might be possible to get his device to pass the HLKs with a LOT of work, it's unlikely. There are a lot of drivers/devices in the world that fall into similar categories to those above. And, there is the case of File System Isolation Minifilters. Any such driver will never pass all 80,000 WLK tests (that's a real number, by the way) due to the way these tests are written. We have worked with MSFT for YEARS to try to get the Minifilter tests to treat Isolation Minifilters specially. MSFT simply does not have sufficient motivation to make this happen. So, yeah, easy to say "just pass the HLKs" -- I wish it were that easy. |
What kind of equipment is like this? Or is it common for factory equipment or something? And what would be the consequence of a total power outage (including generators failing, I guess)?
This isn't something I've heard of before, it's interesting.