Common issues and solutions for PSADT deployments.
Before Troubleshooting
• Always test packages in a non-production environment first
• Check PSADT logs at C:\Windows\Logs\Software
• Review Intune Management Extension logs for deployment details
• Use the "Report Problem" button to report issues with the generator
Installation Errors
Error 1603 - Fatal error during installation
The MSI installer encountered a fatal error.
Solutions:
Check if the application is already installed
Ensure no related processes are running
Verify sufficient disk space
Check Windows Installer service is running
Review the MSI log file for specific errors
Error 1618 - Another installation is in progress
Windows Installer is busy with another installation.
Solutions:
Wait for the other installation to complete
Check Task Manager for running msiexec.exe processes
Restart the Windows Installer service
Error 1612 - Installation source not available
The installer cannot find the source files.
Solutions:
Verify all files are included in the package
Check file paths in the script match actual file locations
Ensure the Files folder is included in the .intunewin package
PSADT Script Errors
Parameter set cannot be resolved
PowerShell cannot determine which parameter set to use.
Solutions:
This often occurs with Show-ADTInstallationWelcome when combining incompatible parameters
CloseProcessesCountdown and BlockExecution require CloseProcesses to be set
Review the PSADT v4 documentation for valid parameter combinations
File signature validation failed
PSADT v4 validates file signatures and detects modifications.
Solutions:
Do not modify files in the AppDeployToolkit folder
Custom banners should replace existing files, not add new ones
If you need custom strings, use the Strings configuration files
Script execution policy error
PowerShell blocks script execution due to policy settings.
Solutions:
PSADT uses Deploy-Application.exe which bypasses execution policy
Ensure Intune is configured to run scripts in SYSTEM context
The .intunewin package handles execution properly
Intune Deployment Issues
Application shows as "Not installed" despite successful install
Detection rules are not matching correctly.
Solutions:
For MSI: Use the Product Code shown in the metadata preview
For EXE: Use file detection with the main executable path
Verify the detection path matches the actual installation location
Check version comparison operators (equals vs. greater than)
Installation fails in SYSTEM context
The application installs for the user but fails when deployed via Intune.
Solutions:
Some applications require user context - check the app's documentation
Verify the silent parameters work in SYSTEM context
Check if the app needs user profile access
Test with PSExec -s to simulate SYSTEM context
Timeout during installation
Intune reports timeout before installation completes.
Solutions:
Large applications may need more time - increase timeout in Intune
Default timeout is 60 minutes
Check if installation is actually completing after the timeout
Winget Issues
Winget not found in SYSTEM context
The scheduled task or deployment fails because Winget is not available.
Solutions:
Winget must be installed system-wide, not just for the current user
Windows 11 includes Winget by default
For Windows 10, ensure App Installer is installed from Microsoft Store
Deploy Winget via Intune before deploying Winget-based packages
Auto-update scheduled task not running
The daily update task is created but never executes.
Solutions:
Verify the task exists in Task Scheduler
Check the task is set to run as SYSTEM
Ensure devices have internet access at the scheduled time
Review Task Scheduler history for errors
Package not found in Winget
Search returns no results for the application.
Solutions:
Try searching by exact Package ID instead of name
Check if the package exists on winget.run
Some applications may not be in the Winget repository
Consider using "New Installation" mode with a direct download instead
Upload & Generation Issues
Large installer files (500MB+) like Citrix Workspace
Very large installers may timeout during upload or package generation.
Solutions:
Option 1: Use Winget Mode - Search for the application and let Winget download during deployment
Option 2: Winget + Template - Upload your existing PSADT script as a template to preserve branding and custom logic
Option 3: Upload anyway - The tool still analyzes the file and generates the complete package, but excludes the installer from the ZIP
For Option 3: Copy your installer into Toolkit/Files/ before running Create-IntuneWin.cmd
The README in the package includes detailed instructions for manual file placement
File upload fails
Unable to upload installer files to the tool.
Solutions:
Check file size - very large files may timeout
Verify your internet connection is stable
Try refreshing the page and uploading again
For large installers (500MB+), see the solution above
Metadata extraction fails
The tool cannot extract information from the installer.
Solutions:
Some EXE installers may not have extractable metadata
You can manually enter the metadata in the preview step
ZIP files with unusual structures may need manual adjustment
Script generation produces errors
The generated script has syntax errors.
Solutions:
Report the issue using the "Report Problem" button
Include the installer type and any error messages
Check if special characters in app name/vendor cause issues
Common MSI Error Codes
Code
Meaning
0
Success
1602
User cancelled installation
1603
Fatal error during installation
1605
Product not installed
1612
Installation source unavailable
1618
Another installation in progress
1619
Installation package could not be opened
1638
Another version already installed
3010
Reboot required to complete
Vendor-Specific Exit Codes
Some vendors use custom exit codes that Intune/SCCM doesn't recognize by default. The PSADT Generator automatically configures these as success codes in the script, but you also need to add them to Intune.
Vendor
Code
Meaning
Intune Action
Citrix
40008
Already installed
Add as Success
Citrix
3010
Reboot required
Add as Soft Reboot
VMware
3010
Reboot required
Default (Soft Reboot)
VMware
1641
Reboot initiated
Default (Hard Reboot)
Adobe
3010
Reboot required
Default (Soft Reboot)
Important: For Citrix installers, you must add exit code 40008 as "Success" in Intune. Go to: Win32 app → Properties → Return codes → Add: 40008 = Success. The generated README includes specific instructions for your vendor.
Still Need Help?
If you're still experiencing issues, you can:
Use the "Report Problem" button in the app to report issues with the generator.