V4.0.5 or V4.0.6 Install Error per Machine variables are not resolved
OS/Powershell
Windows 11 24H2 5.1.26100.2161
Winndows 11 23H2 5.1.22621.4391
Windows 10 22H2 5.1.19041.5486
I always test all functions on all three operating systems using language, install, repair, remove, and sometimes OS staging in provisioning mode before releasing it.
If there are any problems, I always try it in Powershell mode to find more detailed errors (as you recommended).
According to the reg, both values are strings.
DisplayVersion REG_SZ
DisplayName REG_SZ Adobe Acrobat (64-bit)
It works on 790 Clients.
What is it trying to convert? It’s a string and remains a string.
All variables are not processed properly on the client, except for this package. It works on another package at the same time that has the same variable logic/syntax/template
Message : The specified conversion is invalid
FullyQualifiedErrorId : System.InvalidCastException,Get-ADTApplication
ScriptStackTrace : bei Get-ADTApplication<Process>, C:\Windows\ccmcache\z8\PSAppDeployToolkit\PSAppDeployToolkit.psm1: Zeile 6836
bei Install-ADTDeployment, C:\Windows\ccmcache\z8\Invoke-AppDeployToolkit.ps1: Zeile 157
bei <ScriptBlock>, C:\Windows\ccmcache\z8\Invoke-AppDeployToolkit.ps1: Zeile 540
PositionMessage : In C:\Windows\ccmcache\z8\Invoke-AppDeployToolkit.ps1:157 Zeichen:23
+ ... g]$MyAdobe=(Get-ADTApplication -Name 'Adobe Acrobat (64-bit)' -NameMa ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
FYI: If you use the Preformatted text button (</>) on the toolbar or Press Ctrl+e, you can then paste your code or the content of your log between the 2 lines of 3 escape characters (```) so it displays correctly on this forum
I beat Toni to fix his post with the Preformatted text button (</> ).
The error message in German says it blows up in PSAppDeployToolkit.psm1 at line 6836.
In 4.0.6, it’s a blank line
in 4.0.5, it’s this: $installedApplication = & $Script:CommandTable.'Get-ItemProperty' -Path $uninstallKeyPaths -ErrorAction Ignore | & {
which then processes a huge inline scriptblock to sanitise the ARP entry from the registry. (I’m not going to try to figure that out…)
If you feel lucky, you could try V4.0.6 but I think there is something special in the registry that is not handled in the huge inline scriptblock.
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{AC76BA86-1033-FF00-7760-BC15014EA700}]
"DisplayVersion"="24.005.20414"
"DisplayName"="Adobe Acrobat (64-bit)"
I ask about the query whether I need to do a patch installation or a full installation
Get-ADTApplication
you don’t allow to include -ErrorAction SilentlyContinue
I agree with @That-Annoying-Guy that there’s something dodgy in your registry data, possibly not related to Adobe Acrobat at all but some other entry.
I’m one of the developers of PSAppDeployToolkit v4, if you felt you could export the entire HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall key and all subkeys, then send to me privately, I’d be able to investigate.
Hello Mjr,
Unfortunately, I can’t access the original anymore, which means I changed the value. This happened on a Windows 10 client. Do you still want it?
As mentioned above, I have a zip which I am not allowed to attach here and it is reproduced as listed, but not from Problem Client, there I manually raised it, I could not wait
I tried to send it as a performed text, the logs don’t work, but the rest
Invoke-AppDeployToolkit.ps1
Adobe Acrobat - W10-24.005.20414.reg
W11-23.006.202380.reg
Cancel the test.
I may be able to get the machine back for testing before I upgrade it to Windows 11 24H2.
The machine has a general problem and has various special production programs installed.
I suspect that one of the programs might have changed the environment variables.
I always test it per OS, per language, and if necessary in provisioning mode - Install, Repair, Remove.
Currently, I have three options:
per user
per machine
BIOS update per machine
The syntax is sometimes different and more complicated, but V4.0.5 and V4.0.6 have passed all tests so far.
Thanks for the help