ARM

Yes, I have gotten that installed and working just as smooth as on regular windows.

Typically the 1603 is remnants from a failed installation attempt.
Clean up folders, and Registry and try again.

As well, if you’re running into errors, support is always a recommended path because it helps us see trends & gets you up and running right away. 

Support also has some scripts they can share with you to help locate and clean up those failed installation records that are causing the issue :) I had a couple x86 and x64 machines that were being plagued with 1603 errors and I couldn’t figure out what was hanging them up. Amine and I were able to come up with a really good PowerShell script to do the work for us so we didn’t have to run manual commands. The last revision I saw worked both locally and remotely.

BT Tech Support team is always willing to dig in and find a way to help make lives easier for everyone :)

appreciate the feedback. case was opened first so just testing out the community as additional resource. its strange as this is freshly reset test device. no problem installing the adapter (saw this after first testing automated client/adapter from intune like our std x64 win32 app) and it shows the object in our console. but client had failed. dont see any avecto in the file ssytem (including new program files (arm) folder. will continue working with support.

We’ve added our first ARM64 devices to the service. It went pretty well.

was able to resolve our issue and all is well with arm version deployment. didnt realize the privilege guard driver remained even thru a system reset when using remove all files and cloud download config via ms autopliot. was able to use pnputil to find the avecto driver and unnstall it. which removed the pgdriver and allowed the new prod 24.7 arm client/adapter install to complete successfully. we had access to early preprod version of the arm client so may have been variable. thanks.

I’m seeing the same issue. This is on brand new devices, so there are no remnants of an old install. Adapter installs fine, client fails with 1603. Sometimes rebooting and retrying resolves the problem, sometimes it does not. Trying to work out what the issue is, verbose MSI logging didn’t show me much. This is on Surface Laptop 7.

If that is the case I would enable advanced MSI installer logs, and get BT support to run over those logs.

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

This will leave a default log in %temp% on the computer for the installation.

I think we might actually have a KB on this one.

If we don't then let me know and we will get one created, we should really have something for this given it's fairly common issue.

in our case a pgdriver (system32>drivers) remained even thru a system reset when using remove all files and cloud download from ms. we were able to use pnputil to find the avecto driver and unnstall it. which removed the pgdriver and allowed the new 24.7 arm client install to complete successfully. we had access to early version of the arm client so not sure if that was a variable or not.

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.