ARM

I have not seen one if it exists.

After looking through the MSI logs, it is failing because it believes pgdriver.sys still exists.

I deleted PGDriver.sys from C:\Windows\System32\drivers, I searched in SysWOW64\drivers but it wasn't there. I deleted the copy of PGDriver.sys in System32\DriverStore\FileRepository. I checked for all of the following registry entries:

HKEY_LOCAL_MACHINE: 

SOFTWARE\Microsoft\Windows\CurrentVersion\DIFx\Services\PGDriver 

SYSTEM\CurrentControlSet\Enum\Root\LEGACY_PGDRIVER SYSTEM\CurrentControlSet\Services\PGDriver 

SYSTEM\Setup\FirstBoot\Services\PGDriver SOFTWARE\Microsoft\Windows\CurrentVersion\DIFx\DriverStore

I also ran a search on the entire C: drive for PGDriver.sys and found nothing. The installation still fails with the same error. Even on a brand new machine the installation fails with the same 1603 error code.

I did all of that, including following the document here: Endpoint Privilege Management - EPM-W installation error - Error 1720. A script required for this install to complete could not be run

These keys do not exist on the system:

HKLM\SOFTWARE\Avecto\Privilege Guard Client

HKLM\SOFTWARE\WOW6432Node\Avecto\Privilege Guard Client

Still getting the same result. Again, this is also happening on brand new Surface Laptop 7 out of the box. 

I’m sorry to hear it didn’t help your situation. As mentioned previously by Jens, at this point it would be best to enable advanced MSI installer logs, and get BT support to review those logs to assist further.

https://learn.microsoft.com/en-us/troubleshoot/windows-client/application-management/enable-windows-installer-logging

After the installer kicks off the QueryPGDriverInstall.ps1 I see a lot of “Couldn't resolve assembly by name” lines in the log. Not sure if that’s normal or not, but I wish I could get a copy of the QueryPGDriverInstall.ps1 script to run it manually. It gets cleaned up during the install so quickly that I cannot grab it.

I did, and I already have a ticket open. 

I have started using Package Manager, actually that is all I deploy now, and it installs the correct version of the Cloud Adapter and PMfW on the endpoint, ARM or x64.