1622 error when running msi as user

Thank you and understood. Like I said, I very rarely use per user functions.

The ALLUSERS=1 thing for this install, tried installshield etc. They have properly locked it down. I dont get why though considering they allowed it for the past ten years. Anyway, thats for me to worry about.

The O365 comment is interesting, I use the ADT GUI to show progress anyway with an approx. timeframe but, didnt know that was a thing not to do (the O365 progress).