Hello, Evgenie Muzychenko, you wrote: I eat> Be convinced that you fulfilled all necessary for signing of the driver steps. Sending in MS their file signed by your certificate is the single-valued procedure necessary for registration Developer's Account. After that it is necessary to send each assembly of the driver for the signature. Also this procedure under PnP-drivers is ground - that is, in a sent CAB-package there should be an INF-file for which MS generates and signs a CAT-file. Also they sign also SYS-files. To tell the truth, I (not without simplification) delegated this registration to a manager, but I too understood it as sending of each assembly by it for the additional signature, but he assured that is not necessary. Means, the circus proceeds I eat> Actually your driver is not obliged to be PnP, but syntactically it is necessary to make the correct INF-file (to use it then not mandatory). How to make such legacy an INF-file, it is written somewhere in articles on site MS. Instead of that minimum INF-file taken from examples WDK suffices? At registration through Inno setup it is not used, but used manually at testing. I eat> If at the prohibition of check of the signature all works normally - means, Inno Setup puts the driver in the correct directory (but be convinced that all works and in 64-digit systems). Well and to check driver loading really it is immediate - through sc query or debugging messages from the driver as request IRP_CREATE can not reach and the operating driver better, and you will search for a problem not there. With folders precisely all , the problem arose only in Windows 10, before both amd64 and x86 worked perfectly. Thanks!