[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: Fail Update XenNet Network Driver - Windows 2016/2019
Hi,I think I had this issue quite some time ago when I was using Windows Server 2012 as DomU and had to install the Xen PV drivers manually. IIRC, I had to switch driver signature testing off to install the drivers. However, with newer Windows versions, the Citrix drivers are installed automatically via Windows driver upate and are working quite well. Are there any advantages of the GPLPV drivers I am not aware of? Best regards, Paul Am 11.09.2022 um 22:21 schrieb Chuck Zmudzinski: On 9/11/2022 1:18 PM, Ronny Wagner wrote:Hallo @all, i have problems to update my Network driver on Windows 2019 domU. I see, there is a Trusted Root Certificates fail message. Have anybody a idea to find the Certificate for the "xennet.tar". Thanks very much!!! Ronny Fail Message in setupapi.dev.log:[Setup Import Driver Package - c:\users\USER\downloads\xen-windows treiber - 22-07-2022\xennet (xen pv network driver)\x64\xennet.inf] Section start 2022/09/11 18:58:27.570cmd: "C:\Users\USER\Downloads\XEN-Windows Treiber - 22-07-2022\xennet (Xen PV Network Driver)\x64\dpinst.exe" inf: Provider: Xen Project inf: Class GUID: {4d36e972-e325-11ce-bfc1-08002be10318} inf: Driver Version: 07/11/2022,9.1.0.121 inf: Catalog File: xennet.cat sto: {Copy Driver Package: c:\users\USER\downloads\xen-windows treiber - 22-07-2022\xennet (xen pv network driver)\x64\xennet.inf} 18:58:27.633 sto: Driver Package = c:\users\USER\downloads\xen-windows treiber - 22-07-2022\xennet (xen pv network driver)\x64\xennet.inf sto: Flags = 0x00000007 sto: Destination = C:\Users\USER\AppData\Local\Temp\{78a3932e-9323-6947-b29e-4d0452194609} sto: Copying driver package files to 'C:\Users\USER\AppData\Local\Temp\{78a3932e-9323-6947-b29e-4d0452194609}'. flq: Copying 'c:\users\USER\downloads\xen-windows treiber - 22-07-2022\xennet (xen pv network driver)\x64\xennet.inf' to 'C:\Users\USER\AppData\Local\Temp\{78a3932e-9323-6947-b29e-4d0452194609}\xennet.inf'. flq: Copying 'c:\users\USER\downloads\xen-windows treiber - 22-07-2022\xennet (xen pv network driver)\x64\xennet.sys' to 'C:\Users\USER\AppData\Local\Temp\{78a3932e-9323-6947-b29e-4d0452194609}\xennet.sys'. flq: Copying 'c:\users\USER\downloads\xen-windows treiber - 22-07-2022\xennet (xen pv network driver)\x64\xennet_coinst.dll' to 'C:\Users\USER\AppData\Local\Temp\{78a3932e-9323-6947-b29e-4d0452194609}\xennet_coinst.dll'. flq: Copying 'c:\users\USER\downloads\xen-windows treiber - 22-07-2022\xennet (xen pv network driver)\x64\xennet.cat' to 'C:\Users\USER\AppData\Local\Temp\{78a3932e-9323-6947-b29e-4d0452194609}\xennet.cat'. sto: {Copy Driver Package: exit(0x00000000)} 18:58:27.805 pol: {Driver package policy check} 18:58:27.883 pol: {Driver package policy check - exit(0x00000000)} 18:58:27.883 sto: {Stage Driver Package: C:\Users\USER\AppData\Local\Temp\{78a3932e-9323-6947-b29e-4d0452194609}\xennet.inf} 18:58:27.883 inf: {Query Configurability: C:\Users\USER\AppData\Local\Temp\{78a3932e-9323-6947-b29e-4d0452194609}\xennet.inf} 18:58:27.899 ! inf: Found legacy AddReg operation defining co-installers (CoInstallers32). Code = 1303 ! inf: Driver package 'xennet.inf' is NOT configurable. inf: {Query Configurability: exit(0x00000000)} 18:58:27.914 flq: Copying 'C:\Users\USER\AppData\Local\Temp\{78a3932e-9323-6947-b29e-4d0452194609}\xennet.inf' to 'C:\Windows\System32\DriverStore\Temp\{1a129509-5587-1848-a7ec-8402b49aa81f}\xennet.inf'. flq: Copying 'C:\Users\USER\AppData\Local\Temp\{78a3932e-9323-6947-b29e-4d0452194609}\xennet.sys' to 'C:\Windows\System32\DriverStore\Temp\{1a129509-5587-1848-a7ec-8402b49aa81f}\xennet.sys'. flq: Copying 'C:\Users\USER\AppData\Local\Temp\{78a3932e-9323-6947-b29e-4d0452194609}\xennet_coinst.dll' to 'C:\Windows\System32\DriverStore\Temp\{1a129509-5587-1848-a7ec-8402b49aa81f}\xennet_coinst.dll'. flq: Copying 'C:\Users\USER\AppData\Local\Temp\{78a3932e-9323-6947-b29e-4d0452194609}\xennet.cat' to 'C:\Windows\System32\DriverStore\Temp\{1a129509-5587-1848-a7ec-8402b49aa81f}\xennet.cat'. sto: {DRIVERSTORE IMPORT VALIDATE} 18:58:28.024 sig: {_VERIFY_FILE_SIGNATURE} 18:58:28.134 sig: Key = xennet.inf sig: FilePath = C:\Windows\System32\DriverStore\Temp\{1a129509-5587-1848-a7ec-8402b49aa81f}\xennet.inf sig: Catalog = C:\Windows\System32\DriverStore\Temp\{1a129509-5587-1848-a7ec-8402b49aa81f}\xennet.cat ! sig: Verifying file against specific (valid) catalog failed. sig: {_VERIFY_FILE_SIGNATURE exit(0x800b0109)} 18:58:28.149 sig: {_VERIFY_FILE_SIGNATURE} 18:58:28.149 sig: Key = xennet.inf sig: FilePath = C:\Windows\System32\DriverStore\Temp\{1a129509-5587-1848-a7ec-8402b49aa81f}\xennet.inf sig: Catalog = C:\Windows\System32\DriverStore\Temp\{1a129509-5587-1848-a7ec-8402b49aa81f}\xennet.cat ! sig: Verifying file against specific Authenticode(tm) catalog failed. sig: {_VERIFY_FILE_SIGNATURE exit(0x800b0109)} 18:58:28.165 !!! sig: Driver package catalog file certificate does not belong to Trusted Root Certificates, and Code Integrity is enforced. !!! sig: Driver package failed signature validation. Error = 0xE0000247 sto: {DRIVERSTORE IMPORT VALIDATE: exit(0xe0000247)} 18:58:28.165 !!! sig: Driver package failed signature verification. Error = 0xE0000247 !!! sto: Failed to import driver package into Driver Store. Error = 0xE0000247 sto: {Stage Driver Package: exit(0xe0000247)} 18:58:28.180 <<< Section end 2022/09/11 18:58:28.211 <<< [Exit status: FAILURE(0xe0000247)]Hi Ronny, I had this issue when I installed the gplpv Windows drivers about 3 years ago. IIRC, there is an option to trust the Xen Project's software, I think it was a box you need to check or select when running the dpinst.exe file. Once you do that, the certificate is trusted by Windows and you can install the Xen gplpv drivers from the Xen Project. Best regards, Chuck -- Paul Leiber Klostergang 62c 38104 Braunschweig Tel.: 0176 23170320
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |