1

Topic: SPAPI_E_SIGNATURE_OSATTRIBUTE_MISMATCH Under Win 8/8.1

At setting of the driver signed all accessible on SysDev by signatures, under Win 8 or 8.1 x64, UpdateDriverForPlugAndPlayDevices returns error SPAPI_E_SIGNATURE_OSATTRIBUTE_MISMATCH _HRESULT_TYPEDEF _ (0x800F0244). To install the driver it is possible only reboot in mode Disable Driver Signature Enforcement (after reboot in a normal mode the driver boots and works). Sketchy  anything distinct did not find. If to install the driver signed only by the EV-certificate - is put and boots normally. In Win10 16299.15 and Win7 SP1 x64 any variants are normally installed. Whether it is possible to force Win 8/8.1 to install the general-purpose packet of the driver signed through SysDev? Or it is necessary to spread separately a packet for ten, signed through SysDev, and separately for 8/8.1? A pancake as they tired with the stupid claims for compatibility/safety...

2

Re: SPAPI_E_SIGNATURE_OSATTRIBUTE_MISMATCH Under Win 8/8.1

Hello, Evgenie Muzychenko, you wrote: I eat> In Win10 16299.15 and Win7 SP1 x64 any variants are normally installed. Whether I eat> It is possible to force Win 8/8.1 to install the general-purpose packet of the driver signed through SysDev? Or it is necessary to spread separately a packet for ten, signed through SysDev, and separately for 8/8.1? If the signature authenticode from Microsoft, alas, it  only for ten means. An official position: or spread separately for old, separately for win10, or undergo procedure HLK, this signature is accepted by all systems. https://blogs.msdn.microsoft.com/window … sion-1607/ How do I sign a driver so that it is compatible with Windows Vista, Windows 7, Windows 8, Windows 8.1, and Windows 10? All you need to do is run the HLK tests for Windows 10 and run the HCK tests for Windows 8.1 and earlier versions as you have in the past. Then, using the Windows 10 HLK, merge the two test logs and submit your driver along with the merged HLK/HCK test results to the Windows Hardware Developer Center Dashboard portal. The portal will sign the driver correctly such that it will work on all platforms that you indicate. I eat> the Pancake as they tired with the stupid claims for compatibility/safety... +1

3

Re: SPAPI_E_SIGNATURE_OSATTRIBUTE_MISMATCH Under Win 8/8.1

Hello, CaptainFlint, you wrote: CF> If the signature authenticode from Microsoft, alas, it  only for ten means. A counter that not so long ago the updated seven successfully accepts this signature though to generate such error it too is able. Interesting, in MS though somebody understands practical sense which they would like to receive from the similar policy?

4

Re: SPAPI_E_SIGNATURE_OSATTRIBUTE_MISMATCH Under Win 8/8.1

Hello, Evgenie Muzychenko, you wrote: CF>> If the signature authenticode from Microsoft, alas, it  only for ten means. I eat> the Counter that not so long ago the updated seven successfully accepts this signature though to generate such error it too is able.  ... When I pottered with self-assembly VirtualBox, the interesting counter of the eight was found out. How much I could understand,  and  parts of a fitter of drivers demand performance of different conditions. In a mode with the allowed self-signed drivers the eight refused to install the driver, saying that it with not entrusted signature, and wanted to spit that it is loaded in a test mode. It recovered certificate adding root storage. In the seven of anything similar it was not required, put at once. Perhaps, in this case works something similar? What if to add this  the certificate in root storage? I eat> interesting, in MS though somebody understands practical sense which they would like to receive from the similar policy? Certainly, understand. All to head for ten, and the more will be problems for support of the previous systems, the better. Perhaps, specially this task did not put in this case, and simply did not think over, but then saw that turned out, and .

5

Re: SPAPI_E_SIGNATURE_OSATTRIBUTE_MISMATCH Under Win 8/8.1

Hello, Evgenie Muzychenko, you wrote: I eat>... I eat> Or it is necessary to spread separately a packet for ten, signed through SysDev, and separately for 8/8.1? It is necessary to do separately. Attestation signing it is supported only for Windows 10. Even if the driver somewhere is installed without errors, it, most likely, a bug (or a bago-feature).

6

Re: SPAPI_E_SIGNATURE_OSATTRIBUTE_MISMATCH Under Win 8/8.1

Hello, okman, you wrote: O> It is necessary to do separately. Attestation signing it is supported only for Windows 10. O> Even if the driver somewhere is installed without errors, it, most likely, a bug (or a bago-feature). Sadly. I while got out, adding in a packet copy INF with other name and self-signed CAT to it. In tens I select the main INF (for it there lies CAT, signed through SysDev), and from remaining systems - this copy. INF-files completely identical, refer to the same SYS-files in x86/x64 so the size of a packet did not increase almost. By the way, at me it turned out to sign through SysDev one CAB-package a little x86/x64 units in "canonical" layout when in a tree root one lies general-purpose INF with sections NTx86/NTamd64, and in subdirectories x86/x64 - SYS-files with identical names.