With the correct spelling:
msiexec /i <Path to MSI file> ALLUSERS=1
Main Topics
Browse All TopicsI get this error during .msi installation - But during installation this merge module gives an error: "1: ALLUSERS property is not 1 - the MSM cannot be used for a per-user or fallback-to-per-user install
Where is this ALLUSERS property so i can change it?
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
i tried that but it only installs if i select the option for 'Everyone'. yes, i am aware
of msiexec /i MyPackage.msi ALLUSERS="1"
The .msi installer should also be able to install per user/machine.
the command line does not work. Is there a property in the .msi pi project where i can enter this command?
You can modify this value internally using a program called ORCA which is available in the Windows Installer SDK.
http://support.microsoft.c
This program lets you look at the tables within the MSI or MST and modify them (preferably after a backup)
One of the tables is called 'Property'. You should find the ALLUSERS value in here and be able to change it to 2.
okay, i just found out that having orca running at the same time as the .msi installation causes the '1619' error. Can you please explain why the .msi installer still does not install per user/machine even if i change the ALLUSERS value to 1 or 2? What else is there? Do i have to re-build the setup project?
ALLUSERS=2 is not a specific mode: the Installer service works out if the user is an admin and if so, installs it per-machine. If the user is not an admin, it attempts to install it per user (equivalent to ALLUSERS=0). If you want a per-user install, set ALLUSERS=0. However, it will fail if the package attempts to install to restricted areas.
If you're still getting problems, set the install to create a verbose log, using the commandline switch /L*V <Log filename>. This will give you more information.
I heard from another customer with the same problem. On their system, the .NET Framework 2.0 had been advertised on their system as a per-user install, likely by an Active Directory group policy deployment on their network. They were able to solve this issue by uninstalling the advertised version of the .NET Framework from Add/Remove Programs and then re-running the dotnetfx.exe installer to install the .NET Framework 2.0.
If uninstalling from Add/Remove Programs doesn't help, or if you don't have an Add/Remove Programs entry for the .NET Framework 2.0, you may need to use the automated cleanup tool described at http://blogs.msdn.com/aste
Business Accounts
Answer for Membership
by: smilingpolitelyPosted on 2006-06-13 at 14:33:23ID: 16897993
You can specify it at the commandline:
msiexec /i <Path to MSI file> ALLUESRS=1