As I write this, HLK is out for Windows 10 build 1803. Supposing I need a driver that runs on platforms that include Windows 8.1 Server 2016, and all Windows 10 flavors, does this mean I need to test with all of HCK, HLK 1607, HLK 1703, HLK 1709, and HLK 1803? Is there any end to this besides our eventual dropping of the oldest operating systems?
Also, suppose I submitted a driver to Microsoft's portal for signing, but omitted (for example) the HLK 1607 tests. Does this mean the driver would not load on Server 2016? Is there actually anything in the signature that tells Server 2016 the driver isn't qualified on it?
I get that more testing is better; Microsoft and I are on the same side, here. But I'd like to understand what the practical constraints are, and how others are tackling the accumulation of testing platforms.
And I'm sorry if I horrify anyone by asking, but am I botching my submissions or is it normal for a submission with 5 sets of results to come back as a ZIP file containing 5 folders of the same driver? I'm attaching the driver binary and symbols to each results package, then when I create the package on the latest HLK, I merge all the results together. The signed drivers I get back seem to work, but am I misunderstanding the merge process?