Intel Community post for reference:
This driver pack has an expired signing certificate:
Windows will not allow these drivers to install because of the expired certificate. The signing certificate needs to be regenerated and the driver pack re-released.
I'd be interested to know why Intel generates signing certs with a 1-year validity period when the parent certificates in the chain are good for 10 years. You folks do realize that your drivers will be out in the wild for well over a year after they're released, yes?
Link Copied
I also encountered the same problem with I226-T1.
Driver version 28.2.1 dated 8/25/2023 has a valid signature instead of the latest version 29.0 driver. I am using this one.
The period in the image is probably the period in which you can attach the certificate. I don't think the attached certificate is valid. Since his 28.2.1 signature for the same certificate is valid. The problem is not the Intel certificate, but the Microsoft certificate. However, Intel is the one who included the expired certificate. Below are the properties of "PRO2500\Winx64\WS2022\e2f.sys" in 29.0.
[Original Japanese text before Google translation]
自分も I226-T1 で同じ問題に遭遇しました。
最新のバージョン 29.0 のドライバーではなく、8/25/2023 の日付のバージョン 28.2.1 のドライバーは署名が有効です。自分はこちらを使っています。
画像の期間は、証明書を添付できる期間でしょう。添付した証明書の有効期間では無いと思います。同じ証明書の 28.2.1 が署名が有効なので。問題はインテルの証明書ではなく、Microsoft の証明書です。ただし、期限切れの証明書を組み込んだのは、インテルでしょう。下記は 29.0 の "PRO2500\Winx64\WS2022\e2f.sys" のプロパティです。
Hello.
Tried it on my I226-T1 system. I tried it after a new clean install of Windows Server 2022 Standard.
The results for 29.0.1 are as follows: Same as 29.0 and doesn't work.
The result of 28.2.1 is as follows. It works.
