✅ The Fix: Create Missing Windows Groups Before Installation
If you’re getting the “An error occurred while applying security settings. Users is not a valid user or group” error when installing VMware Workstation 17.6, here’s the immediate solution:
🔧 Quick Command Line Fix
Open Command Prompt as Administrator and run:
net localgroup /add "Users" net localgroup /add "Authenticated Users"
Restart your computer, then retry the VMware installation.
This error specifically affects VMware Workstation 17.6 on non-English Windows installations where local groups are named differently (like “Usuarios” in Spanish Windows). The installer hardcodes English group names but can’t find them on localized systems.
🔍 Why This Error Happens
VMware Workstation 17.6’s installer assumes that Windows user groups exist with specific English names. When you install VMware on a Spanish, French, German, or other non-English Windows system, these groups have localized names instead:
| Windows Language | Local Group Name | VMware Expects |
|---|---|---|
| Spanish | Usuarios | Users |
| French | Utilisateurs | Users |
| German | Benutzer | Users |
The installer fails because it can’t assign security permissions to groups that don’t exist with the expected English names.
📋 Step-by-Step Solutions
Method 1: Command Prompt (Recommended)
- Right-click Start button → Select “Command Prompt (Admin)” or “Windows PowerShell (Admin)”
- Run these exact commands:
net localgroup /add "Users" net localgroup /add "Authenticated Users"
- Verify creation: Both commands should return “The command completed successfully”
- Restart your computer
- Run VMware installer again
⚠️ Important: Group names are case-sensitive. Use exact capitalization as shown above.
Method 2: Computer Management GUI
- Press Windows + X → Select “Computer Management”
- Navigate to Local Users and Groups → Groups
- Right-click in the groups area → New Group
- Create a group named exactly “Users” (no description needed)
- Repeat for “Authenticated Users”
- Restart and retry VMware installation
🔄 Alternative Workarounds
Downgrade to VMware 17.5.2
If you can’t create the groups or prefer not to modify your system, download VMware Workstation 17.5.2 instead. This version doesn’t have the localization issue.
Upgrade to VMware 17.6.1 or Later
VMware fixed this bug in version 17.6.1. If available, download the latest version directly from Broadcom’s VMware portal.
🛠️ Additional Troubleshooting
If you still encounter security settings errors after creating the groups, try these additional steps:
Run as Administrator
- Right-click the VMware installer → “Run as administrator”
- Ensure you’re logged in with Administrator privileges
Check File Permissions
- Navigate to your download folder
- Right-click VMware installer → Properties → uncheck “Read-only” if selected
- Apply changes and retry
Temporarily Disable UAC
- Type “UAC” in Start menu → Open “Change User Account Control settings”
- Move slider to “Never notify”
- Restart computer
- Install VMware
- Re-enable UAC afterward for security
✅ Verification Steps
After creating the groups, verify they exist:
net localgroup "Users" net localgroup "Authenticated Users"
Both commands should show group information without errors. If successful, proceed with VMware installation.
🎯 Best Practices Moving Forward
- Check version compatibility: Always verify VMware version supports your Windows locale before downloading
- Keep groups: Leave the created English groups on your system—they won’t interfere with normal operation
- Update regularly: Newer VMware versions include better multi-language support
- Document changes: Note what groups you’ve added for future reference
💡 Pro Tip: This solution works for other software that assumes English Windows group names. Keep these groups if you frequently install development tools.
❓ Frequently Asked Questions
Will creating English group names affect my system?
No, adding English-named groups alongside your localized groups is safe and won’t affect system functionality or existing permissions.
Can I delete these groups after installation?
While technically possible, it’s recommended to keep them. Some VMware updates or other software might need them in the future.
Why doesn’t VMware fix this in all versions?
VMware acknowledged this as a localization bug and fixed it in version 17.6.1. Earlier versions require the manual workaround.
Does this affect VMware Player or other VMware products?
This specific issue primarily affects VMware Workstation 17.6. Other VMware products may have different installer behaviors.
What if I get “Access denied” when creating groups?
Ensure you’re running Command Prompt as Administrator. Right-click the Command Prompt shortcut and select “Run as administrator” explicitly.
Can I use PowerShell instead of Command Prompt?
Yes, the same net localgroup commands work in PowerShell when run as Administrator.