Hello Chris, Yes, that is exactly what I'm saying. As per my observations so far, it looks like this behavior does not exhibit when the "Framework" option is checked. I've noticed this by observing the behavior for .NET Framework 4.8.1 which does not have the same outcome. Best regards, Ca...
Hello Markus, Thank you once again for the followup on this. That's really strange, as I've just tested this on a normal Windows VM and it launches the correct 64-bit PowerShell launcher. It's true, however, that I do not have access to a machine with a Windows like yours and therefore can not reall...
Hello, From what I can see, you are trying to look in the 64-bit version of the Program Files folder. By default, this search will be redirected to Program Files (x86) if your setup is of 32-bit (you can check this in the "Install Parameters" page). That being said, please make sure the se...
Hello Chris, Thank you very much for providing the sample project. Upon testing this, I can indeed confirm the behavior. I have forwarded this to our development team. In the meantime, I have noticed that this works as expected if you check the "Framework" option for the .NET Runtime prere...
Hello Obay, Apologies for the delayed reply. In order to achieve what you want, we need to make use of the updater's command options - Advanced Installer Updater . For instance, in your case, we can make use of the /silentall parameter. Now, in order to achieve that, we have to automatically call th...
Hello Johannes, That was happening because of some noise registry entries captured during the repackaging session. I will paste below the reply from email: I've finished my investigations regarding this and here would be the conclusions: - the keys from under SYSTEM\WaaS\WaaSMedic\TaskStore are syst...
Hello, What I find a bit confusing is this: - the MSI install the prerequisite and then uninstall them after that the installation freeze Could you please ellaborate more on this? How is the prerequisite installed and then uninstalled during the same installation process of the main package? Or even...
Hello Markus, First of all, I am glad you managed to find a workaround for the issue. Now, regarding the Powershell script, have you tried setting it as 64-bit? If so, did it help? Pretty sure that the 64-bit option should launch the 64-bit version of Powershell from the system. Best regards, Catalin
Hello Markus, If the script is not running, I would advise checking the execution policy set on that LTSB2016 machine. To do so, you can open a PowerShell and then run the following cmdlet: Get-ExecutionPolicy . For more information about execution policies, please refer to the following article: ab...
Hello and welcome to our forums, The fact that this only reproduces on one customer's machine means it will be quite hard to investigate, as most likely it's a corner case. I honestly can not think of any reason why setting the property would fail. Does your customer have any AV software installed? ...
Hello Matt, That might be happening if your MSI build is of 32-bit. If you have multiple builds, e.g. one for EXE and one for MSI, then the MSI build might be 32-bit. You can check this by going to the "Install Parameters" page and checking the bitness for your MSI build: Screenshot_130.pn...