Hello, greatis, you wrote: G> to Do the test of the driver and to send? G> but after all the driver should work and for other Windows versions. As already wrote above - for normal Windows 10, it is enough to sign on portal MS. It is called attestation signing. If in the driver is CAT files, it is necessary to hold two versions as last versions of Windows do not understand signature MS for Windows 10, and CAT file AFAIR can carry only one signature: 1) Signed by the certificate for last Windows versions 2) Signed on portal MS for Windows 10, On an expert did not check, but MS speaks that the driver signed on a portal will not be launched on Windows Server 2016, for this purpose it is necessary to transit HLK tests that there is rather a procedure. Briefly, it is possible to lift two , in one Windows Server and HLK controler, in the second Client in which actually tested driver. For last to take better at once Windows Server Core without , one of tests demands that the driver could work without the user interface. The complete set of tests can occupy more than 24 hours and special stability in operation does not differ. For magnification of speed it is possible to throw off on FRAMES a disk, but the heap of storage is required. In my case tests occupied about 20 hours on Xeon c 96 GB RAM, with hundreds reboots of the client.