Important Notice: On February 29th, this community was put into read-only mode. All existing posts will remain but customers are unable to add new posts or comment on existing. Please feel to join our Community Discord for any questions and discussions.

MSI Error 1603 on latest Edge and Chrome Library Packages

Joseph Stauffer

April 19, 2022 17:35

Hi All,

I hope you are having a nice day today. Is anyone else experiencing a ton of MSI 1603 errors with the latest Edge and Chrome packages from the Package Library? I have pushed both of these to all computers without issues 20-30 times in the past, but this push, it seems 80% or more are coming back with MSI error 1603. Any help or feedback is greatly appreciated. Thanks for your time and help!

Cheers, - Joe Stauffer

Comments

3 comments

Wayne Jolley
April 20, 2022 13:41

I'm not seeing 1603 errors with Edge and Chrome packages, but am seeing them with a ton of other packages.

I am able to run the packages on the desktop, or by command line, but trying the exact same thing with PDQ fails with 1603 error. As with you, these are packages that have been working fine, sometimes for several years.

1
Joseph Stauffer
April 21, 2022 15:37

Thank you for the response, Wayne. It is nice to know I am not the only one having issues. I pushed Java today with no problems, so it looks like it is only specific packages. I experienced the same results with installing the MSI's using CMD or PowerShell; it only fails in PDQ.

0
Wayne Jolley
April 21, 2022 16:12

Hey, Joe. Nice to hear that the problems aren't just me :)

I have managed to get some of the packages working. The fix has been to either;

- Remove the ALLUSERS=1 and /norestart from the package, and / or
- Use a command task in PDQ to robocopy the package locally , run msiexec /I to install, and then delete the package

This hasn't worked for all my failures, but only have a few left that are still failing now.

1