topic Re: PVSCSI drivers 1.3.25.0 not signed in Windows Discussions

PVSCSI drivers 1.3.25.0 not signed

dlaumor — Fri, 09 Dec 2022 09:29:22 GMT

Hi everyone,

I try to create a Windows Server 2019 template with VMware Paravirtual SCSI controller.

As Windows Server 2019 installer does not have PVSCSI driver, I need to load it manually from VMware Tools iso image during the installation process.

When I browse to D:\Program Files\VMware\VMware Tools\Drivers\pvscsi\Win10\amd64 to select the driver, I have an error message saying "No signed device drivers were found".

The problem exists since VMware Tools 12.0.5 (with PVSCSI drivers 1.3.25.0).

In VMware Tools 12.0.0 (PVSCSI driver 1.3.17.0), there is no problem.

Drivers in D:\Program Files\VMware\VMware Tools\Drivers\pvscsi\Win8\amd64 seems correctly signed as well.

Please VMware Team, can you sign PVSCSI driver and update VMware Tools?

Versions:

VMware Infrastructure: VMware vSphere 7.0.3.00700

ESXi version: VMware ESXi, 7.0.3, 20328353

VMware Tools version: 12325 (12.1.5)

Steps to reproduce:

Create a VM with VMware Paravirtual SCSI controller
Boot on Windows Server 2019 iso file
During the installation process, you couldn't see any disk drive to install Windows. Click on "Load driver" and browse to D:\Program Files\VMware\VMware Tools\Drivers\pvscsi\Win10\amd64

Expected results:

VMware PVSCSI driver loads correctly.

Actual results:

Unable to load PVSCSI driver with this error message: No signed device drivers were found

Re: PVSCSI drivers 1.3.25.0 not signed

robinsonjl3 — Sun, 18 Dec 2022 13:15:45 GMT

I ran into this problem as well and ended up using the Win8 drivers as those were signed.

Re: PVSCSI drivers 1.3.25.0 not signed

bayarea-vmware — Sat, 31 Dec 2022 23:06:54 GMT

Whew - glad I'm not the only going what the heck happened!

Same issue here try to setup a windows 10 golden image.

Re: PVSCSI drivers 1.3.25.0 not signed

dlaumor — Fri, 06 Jan 2023 12:00:40 GMT

@robinsonjl3 Personally, as I don't really know the difference between Win8 and Win10 drivers, I'm using an old version of the VMware Tools (12.0.0) during the Windows installation, then I'm upgrading VMware Tools through the vCenter interface.

Re: PVSCSI drivers 1.3.25.0 not signed

Pontificus — Wed, 11 Jan 2023 15:35:50 GMT

Confirmed - I saw the same thing. The instructions at https://techzone.vmware.com/resource/manually-creating-optimized-windows-images-vmware-horizon-vms#install-windows do NOT match up to reality for me. I'm going to try the Win8 drivers (which DO appear) and hope for the best.

Re: PVSCSI drivers 1.3.25.0 not signed

sWORDs — Thu, 12 Jan 2023 19:34:55 GMT

The Win10 version is for 10.0.20124 and later (Windows 11 21H2), the Win8 version is for Windows 8.0/8.1 and Windows 10/Server 2016/Server 2019.

A bit confusing, but you can see it in the .inf file:

; Build for 3 different driver versions that support Windows versions:
; - 6.0 and 6.1
; - 6.2, 6.3, 10.0 but not 10.0.20124 and later.
; - 10.0.20124 and later

So:

Name	Version	PVSCSI
Windows 10/Server 2019	1809 17763	Win8 Folder
Windows 10	20H2 19042	Win8 Folder
Windows 10	21H1 19043	Win8 Folder
Windows 10	21H2 19044	Win8 Folder
Windows 10	22H2 19045	Win8 Folder
Windows 11	21H2 22000	Win10 folder
Windows 11	22H2 22621	Builtin
Windows Server 2022	21H2 20348	Builtin

We'll add some text to the techzone guide to clarify it.

Re: PVSCSI drivers 1.3.25.0 not signed

amarmhetre — Thu, 23 Feb 2023 15:55:02 GMT

How to identify best matching section for 10.x OS. As new Model section 10.0.20124 is empty stating this driver is not applicable for the mentioned OS. Old algorithms still gives this new section for 10.x OS, is this the reason newer version 1.3.26.0 of driver has removed the manufacturer entries for 10.x.