If you’ve ever tried installing software on a Windows Server, especially in a Remote Desktop Services (RDS) environment, you might have encountered the frustrating pop-up message: “Please wait while the application is preparing for the first use.” This dialog, often tied to the Windows Installer Coordinator, can appear during installations and sometimes hangs indefinitely, preventing you from proceeding or even canceling the process. Whether you’re setting up accounting software like Thomson Reuters Fixed Assets CS, security tools like Enzoic, or even JDK on Windows Server 2012, this issue can grind your workflow to a halt.
In this blog post, we’ll dive into what this message really means, why it occurs, and most importantly, how to resolve it. By the end, you’ll have the tools to bypass this roadblock and get back to productive work.
What Does This Message Mean?
The “Please wait while the application is preparing for the first use” prompt is generated by the Windows Installer Coordinator, a component in Windows Server editions (like 2008, 2012, 2016, and later) designed to manage installations in multi-user environments, such as those using Remote Desktop Services. It’s meant to ensure that applications are properly configured for first-time use across sessions, but it often backfires due to compatibility issues.
This isn’t a generic loading screen—it’s specific to scenarios where the installer is handling chained or dependent installations (e.g., prerequisites like .NET Framework or Visual C++ redistributables). If it gets stuck, you might not be able to close the window, leading to lost time and potential system restarts.
Common software affected includes:
• Thomson Reuters products
• Enzoic password auditing tools
• Land F/X design software
• Acctivate inventory management
• BigHand workflow management in Citrix environments
It’s particularly prevalent on servers running RDS, where user sessions can interfere with installer behavior.
Why Does This Happen?
The root cause is often an incompatibility between the Windows Installer and Remote Desktop Services. In RDS-enabled systems, Windows enforces certain compatibility modes to prevent conflicts in multi-user setups. However, this can clash with how some installers are built, especially those that trigger multiple MSI (Microsoft Installer) packages in sequence.
Key triggers include:
• RDS Compatibility Settings: If “Windows Installer RDS Compatibility” is enabled (or disabled, depending on the context), it can cause the coordinator to loop or freeze.
• Chained Installers: Software that installs dependencies in the background can confuse the coordinator, leading to indefinite “preparation.”
• Server-Specific Issues: This is more common on Windows Servers than desktops, and factors like third-party antivirus or pending updates can exacerbate it.
• Citrix or Virtual Environments: In virtualized setups like Citrix, the message may persist until manually canceled, halting the entire install.
In essence, it’s a protective feature gone awry, designed to “prepare” the app but ending up stalling the process.
How to Fix It: Step-by-Step Solutions
Don’t worry—resolving this is usually straightforward and involves tweaking Group Policy settings. Here’s a reliable method that works across most reported cases. Always back up your system before making changes.
Method 1: Disable Windows Installer RDS Compatibility (Recommended for Most Cases)
1. Open Group Policy Editor: Press Windows + R, type gpedit.msc, and hit Enter. This opens the Local Group Policy Editor.
2. Navigate to the Setting: Go to Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Application Compatibility.
3. Edit the Policy: Find “Turn off Windows Installer RDS Compatibility” (or similar phrasing like “Windows Installer RDS Compatibility”). Set it to Enabled (or Disabled, depending on your current setup—test both if needed).
4. Apply and Restart: Click Apply, then OK. Restart your server or log off/on for changes to take effect.
5. Retry Installation: Run the installer again. The message should no longer appear or hang.
If you’re on a domain-controlled server, you may need to apply this via Group Policy Management Console (GPMC) instead.
Method 2: Additional Troubleshooting Steps
• Run as Administrator: Right-click the installer and select “Run as administrator.”
• Compatibility Mode: Right-click the installer > Properties > Compatibility tab > Run in compatibility mode for an older Windows version (e.g., Windows 7).
• Check for Updates: Ensure Windows is fully updated, as patches can resolve installer bugs.
• Disable Third-Party Interference: Temporarily pause antivirus or firewall software during installation.
• Force Close if Stuck: If the dialog won’t close, use Task Manager to end msiexec.exe processes (be cautious, as this can corrupt installs).
For Enzoic-specific fixes, ensure RDS Compatibility is enabled if it’s currently off. Always consult the software vendor’s support if these steps don’t work.
Prevention Tips
To avoid this headache in the future:
• Test installations in a non-RDS environment first.
• Use virtual machines for server setups to isolate issues.
• Keep Group Policy settings documented, especially in team environments.
• Opt for software with silent install options (/quiet flag in MSI installers) to bypass interactive prompts.
Conclusion
The “Please wait while the application is preparing for the first use” message is a common but solvable nuisance in Windows Server installations. By understanding its ties to RDS compatibility and following the Group Policy tweaks outlined above, you can quickly move past it. If you’re dealing with this in a production environment, consider reaching out to Microsoft Support or your software vendor for tailored advice.
Have you run into this error? Share your experiences in the comments below—I’d love to hear how you fixed it! Stay tuned for more tech troubleshooting tips.