Qaar ka mid ah Windows 10 Isticmaalayaasha ayaa laga yaabaa inay la kulmaan fariinta qaladka " Ma jiro saxiix mawduuca^{(No signature was present in the subject)} " marka ay isku dayayaan inay arkaan sifooyinka saxiixa ee faylka xirmada darawalka. Maqaalkan, waxaanu ku siinaynaa sharaxaad kooban oo ku saabsan sababta aad u heli karto fariintan iyo waxa aad isku dayi karto inaad ka takhalusto fariinta faylka xirmada gaarka ah.

Nidaamyada^(Systems) Operating - ka waxaa laga yaabaa inay leeyihiin arrimo saxiix ah oo aan la garanayn ama darawalka oo aan saxiixin haddii kumbuyuutarka la tijaabinayo uusan ku xirneyn internetka. Haddii kumbiyuutarka la tijaabinayo uu ku xiran yahay internetka, markaa shahaadooyinka cusub si toos ah ayaa loo soo dejiyaa marka darawalka la rakibo mana jiri doono wax dhibaato ah. Mararka qaarkood iibiyeyaasha CA waxay sidoo kale awoodaan inay gacan ka geystaan ​​xallinta arrimaha marka kumbuyuutarka lagu tijaabinayo uusan ku xirnayn internetka.

Akhri^(Read) : Sida loo garto darawalada aan saxiixin ee isticmaalaya sigverif utility.^{(How to identify unsigned drivers using sigverif utility.)}

Wax saxiix ah kuma jirin mawduuca

Marka faylka buugga (.cat) la saxiixo iyadoo la adeegsanayo VeriSign cusub oo la sii daayay shahaado saxiixeed taasoo adeegsata SHA256 algorithm , haddii aad furto feylka bisadda ee saxiixan oo aad aragto saxiixa, waxaad ogaan kartaa saxiixa Ma jiro^{(No signature was present in the subject)} farriinta mawduuca.

Si loo xalliyo arrinta, waxaad waydiisan kartaa VeriSign inay bixiso shahaado beddelka ah iyada oo aan wax kharash ah lagu saxeexin algoorithmamka SHA1^(SHA1) .

Haddii kale, waxaad iibsan kartaa shahaado kale oo SHA1 oo waxaad ku saxeexi kartaa faylka laba saxeex sida hoos ku cad haddii aad rabto inaad haysato labada shahaado. Ogsoonow in faylasha .sys oo keliya ay noqon karaan laba saxiix sababtoo ah waa faylal PE ah.

Signtool sign /fd sha256 /ac C:\MyCrossCert\Crosscert.cer /s my /n “MyCompany Inc. “ /ph /as /sha1 ZZ...ZZ C:\DriverDir\toaster.SYS

Meesha ZZ...ZZ ay tahay xashiishka shahaadada aad u isticmaalayso saxiixa labaad. Ku dar /trsaxiixa timestamp

Ogeysiis dheeri ah^{(Additional note)} : Isticmaalka shahaadada SHA1 waxaa joojisay Microsoft laga bilaabo Janaayo 1^{(January 1)} , 2016. Dhammaan iibiyeyaasha CA waa inay ku bixiyaan shahaadooyin saxiixa SHA256 hash algorithm.

Daaqadaha^(Windows) waxay joojisay aqbasha SHA1 shahaadooyinka saxeexa koodka iyada oo aan waqti la haynin wixii ka dambeeya 1 Janaayo 2016^{(January 2016)} .

Microsoft ayaa sidoo kale hadda sheegtay in ka dib markii la rakibo KB4579311 , Windows 10 waxaa laga yaabaa inay kuu digto markaad rakibayso darawalada dhinac saddexaad :

This issue occurs when an improperly formatted catalog file is identified during validation by Windows. Starting with this release, Windows will require the validity of DER encoded PKCS#7 content in catalog files. Catalogs files must be signed per section 11.6 of describing DER-encoding for SET OF members in X.690,”

Waxaan rajeynayaa in tani ay ku caawineyso!

Qoraal la xidhiidha^{(Related post)} : Daaqadaha waxay u baahan yihiin darawal si dhijitaal ah u saxeexan .

No signature was present in the subject - Driver Signature Details

Some Windows 10 users might come acrоss the error mеssage “No signature was present in the subject” when trying to view the signature properties of a driver package file. In this post, we provide a brief description of why you may get this message and what you can try to get rid of the message for that particular package file.

Operating Systems may have unknown signing issues or driver not signed issues if the computer under test is not connected to the internet. If the computer under test is connected to the internet, then the new certificates are automatically downloaded when a driver is installed and there will not be any issues. Sometimes the CA vendors are also able to help out in resolving the issues when the computer under test is not connected to the internet.

Read: How to identify unsigned drivers using sigverif utility.

No signature was present in the subject

When a catalog file (.cat) is signed using a new VeriSign released signing certificate which uses the SHA256 algorithm, if you open the signed cat file and view signature, you may notice the No signature was present in the subject message.

To resolve the issue, you may ask VeriSign to provide a replacement certificate at no cost signed with the SHA1 hash algorithm.

Alternatively, you can buy another SHA1 certificate and sign the file with two signatures as shown below if you want to keep both certificates. Note that only .sys files can be dual signed because they are PE files.

Signtool sign /fd sha256 /ac C:\MyCrossCert\Crosscert.cer /s my /n “MyCompany Inc. “ /ph /as /sha1 ZZ...ZZ C:\DriverDir\toaster.SYS

Where ZZ…ZZ is the hash of the certificate you are using for the secondary signature. Add /tr to timestamp signing.

Additional note: Use of SHA1 certificate was deprecated by Microsoft starting from January 1, 2016. All CA vendors must issue signing certificates with the SHA256 hash algorithm.

Windows stopped accepting SHA1 code signing certificates without time stamps after 1 January 2016.

Microsoft has also stated now that after installing KB4579311, Windows 10 may warn you when installing some third-party drivers:

This issue occurs when an improperly formatted catalog file is identified during validation by Windows. Starting with this release, Windows will require the validity of DER encoded PKCS#7 content in catalog files. Catalogs files must be signed per section 11.6 of describing DER-encoding for SET OF members in X.690,”

Hope this helps!

Related post: Windows requires a digitally signed driver.

Related posts

• Daaqadaha ma xaqiijin karaan saxiixa dhijitaalka ah (Koodhka 52)

• Sida loo damiyo Cusbooneysiinta Dareewalka Tooska ah ee Windows 10

• Muujinta darawalka nvlddmkm ayaa joojiyay ka jawaabista oo si guul leh ayuu u soo kabsaday

• Qalabku wuxuu u baahan yahay cilad dheeri ah oo ku rakibida Windows 11/10

• Ku rakib Realtek HD Audio Driver Failure, Cilad OxC0000374 Windows 10

• Sida loo awood NVIDIA Low Latency Mode on Windows 11/10

• Cusbooneysiinta darawalka GPU-da ee xun oo dhibaato ku keenaysa Windows 11/10

• Soo deji darawalada Surface Pro ee ugu dambeeyay, firmware, software ka Microsoft

• HP 3D DriveGuard waxa uu Hard Drive-ka ka ilaaliyaa burbur ka dib marka uu shil dhaco

• Darawalka garaafyada ayaa heli waayay qalab sawireed ku haboon

• Darawalka Fiidiyowga ayaa shil galay oo dib loo dajiyay Windows 11/10

• Sida loo soo bandhigo liiska dhammaan aaladaha wadayaasha gudaha Windows 11/10 oo wata DriverView

• Demi dejinta daacadnimada xusuusta haddii Windows aysan soo dejin karin darawalka

• Darawalka Intel & Kaaliyaha Taageerada: Soo deji, rakib, cusboonaysii darawalada Intel

• Sida loo arko macluumaadka Shabakadda Wi-Fi ee darawalka Windows 11/10

• Darawalka qalabkan ayaa laga hor istaagay inuu bilaabo (Cod 48)

• Dhoofinta iyo Kaabta Aaladaha Isticmaalka PowerShell gudaha Windows 11/10

• Hagaaji dhibaatooyinka darawalada garaafka Intel ee Windows 11/10

• Halka laga soo dejiyo darawalada Windows 11/10

• Sida dib loogu bilaabo Driver Graphics gudaha Windows 11/10