ANAVEM
Languagefr
How to Fix AutoCAD Admin Credential Requests After Windows Security Update

How to Fix AutoCAD Admin Credential Requests After Windows Security Update

Resolve AutoCAD UAC prompts and Error 1730 that appeared after Microsoft's August 2025 security updates. Learn Group Policy solutions, registry fixes, and enterprise deployment strategies.

Evan MaelEvan Mael
March 26, 2026 15 min
mediumautocad 7 steps 15 min

Why Do AutoCAD Admin Prompts Appear After Windows Updates?

Microsoft's August 2025 security updates (KB5063875, KB5064010 for Windows 11, and KB5063877 for Windows 10) introduced stricter controls for MSI repair operations to address CVE-2025-50173. While this enhanced security, it inadvertently caused AutoCAD versions 2022-2026 to trigger User Account Control (UAC) prompts or display "Error 1730" when standard users attempt to launch the application.

The root cause lies in how AutoCAD's installer registers certain components that require repair verification on first launch. The August updates made these repair operations require administrative privileges, even for applications that previously ran fine with standard user accounts.

What Are the Available Solutions for This AutoCAD Issue?

Microsoft released corrective updates on September 9, 2025 (KB5065426 for Windows 11 24H2 and KB5065431 for Windows 11 22H2/23H2) that resolve this issue properly. However, many organizations haven't deployed these updates yet or need immediate workarounds.

This tutorial provides multiple approaches: installing the official Microsoft fixes, implementing Group Policy solutions for enterprise environments, applying registry modifications for immediate relief, and configuring compatibility settings for edge cases. Each method includes verification steps and rollback procedures to ensure you can safely implement and reverse changes as needed.

How Does This Fix Impact Enterprise AutoCAD Deployments?

For organizations managing multiple AutoCAD installations, this issue can significantly disrupt productivity. The solutions in this tutorial are designed with enterprise environments in mind, providing Group Policy-based approaches that can be deployed across entire domains, PowerShell scripts for automated remediation, and comprehensive testing procedures to ensure compatibility with existing IT infrastructure.

Implementation Guide

Full Procedure

01

Install Microsoft September 2025 Security Updates

The primary fix is installing Microsoft's September 2025 updates that address the MSI repair UAC issue. These updates specifically resolve CVE-2025-50173 without breaking AutoCAD functionality.

First, install the PowerShell Windows Update module:

Install-Module PSWindowsUpdate -Force -Scope AllUsers
Import-Module PSWindowsUpdate

Check for and install the September 2025 updates:

Get-WindowsUpdate | Where-Object {$_.Title -like "*September*2025*"} | Install-WindowsUpdate -AcceptAll -AutoReboot

For Windows 11 systems, you're looking for KB5065426 (24H2) or KB5065431 (22H2/23H2). For Windows 10, the equivalent September update will be available.

Verification: Run Get-HotFix | Where-Object {$_.HotFixID -like "*5065*"} to confirm the updates are installed. Check the build number with winver - you should see builds 26100.6584 or 22621.5909/22631.5909 for Windows 11.

Pro tip: Test these updates in a non-production environment first, especially if you have custom AutoCAD configurations or third-party plugins.
02

Configure Group Policy to Disable MSI Repair Prompts

For enterprise environments, use Group Policy to prevent MSI repair prompts across all domain computers. This is the recommended approach for organizations with multiple AutoCAD installations.

Open Group Policy Management Console and navigate to your target OU. Create or edit a Computer Configuration policy:

Navigate to: Computer Configuration > Preferences > Windows Settings > Registry

Create a new Registry Item with these settings:

  • Action: Update
  • Hive: HKEY_LOCAL_MACHINE
  • Key Path: SOFTWARE\Policies\Microsoft\Windows\Installer
  • Value name: DisableMSI
  • Value type: REG_DWORD
  • Value data: 2

Apply the policy and force a Group Policy update on target machines:

gpupdate /force

Verification: Check the registry on a target machine: reg query "HKLM\SOFTWARE\Policies\Microsoft\Windows\Installer" /v DisableMSI. The value should be 0x2 (2).

Warning: Setting DisableMSI to 2 prevents all MSI repair operations. Only use this as a temporary workaround until Microsoft updates are applied.
03

Apply Registry Fix Using PowerShell

For standalone machines or immediate fixes, use PowerShell to modify the registry directly. This creates the same registry entry as the Group Policy method.

Run PowerShell as Administrator and execute this script:

$registryPath = "HKLM:\SOFTWARE\Policies\Microsoft\Windows\Installer"
$registryName = "DisableMSI"
$registryValue = 2

# Create the registry path if it doesn't exist
if (!(Test-Path $registryPath)) {
    New-Item -Path $registryPath -Force | Out-Null
    Write-Host "Created registry path: $registryPath" -ForegroundColor Green
}

# Set the registry value
Set-ItemProperty -Path $registryPath -Name $registryName -Value $registryValue -Type DWord
Write-Host "Set $registryName to $registryValue" -ForegroundColor Green

# Verify the setting
$currentValue = Get-ItemProperty -Path $registryPath -Name $registryName -ErrorAction SilentlyContinue
if ($currentValue.$registryName -eq $registryValue) {
    Write-Host "Registry modification successful!" -ForegroundColor Green
} else {
    Write-Host "Registry modification failed!" -ForegroundColor Red
}

Verification: Launch AutoCAD without admin privileges. It should start normally without UAC prompts. Check the registry value persists after reboot with Get-ItemProperty -Path "HKLM:\SOFTWARE\Policies\Microsoft\Windows\Installer" -Name DisableMSI.

Pro tip: Save this script as a .ps1 file for easy deployment across multiple machines using remote PowerShell or configuration management tools.
04

Restart Windows Installer Service

If AutoCAD still shows Error 1730 or MSI-related errors after applying the registry fix, restart the Windows Installer service to clear any cached repair operations.

Stop the Windows Installer service:

net stop msiserver

Wait 10 seconds, then restart it:

net start msiserver

Re-register the Windows Installer service:

msiexec /unregister
msiexec /regserver

Clear temporary MSI files that might be causing conflicts:

Remove-Item -Path "$env:TEMP\*.msi" -Force -ErrorAction SilentlyContinue
Remove-Item -Path "$env:WINDIR\Temp\*.msi" -Force -ErrorAction SilentlyContinue
Remove-Item -Path "$env:WINDIR\Installer\$PatchCache$\*" -Recurse -Force -ErrorAction SilentlyContinue

Verification: Check the service status with sc query msiserver. The STATE should show "RUNNING". Launch AutoCAD to test if the credential prompts are resolved.

Warning: Clearing the patch cache may require reinstalling some applications if they need repair operations later. Document which files you remove.
05

Configure AutoCAD Compatibility Settings

If the previous steps don't resolve the issue completely, configure AutoCAD executables to run with appropriate compatibility settings. This addresses edge cases where the application still triggers UAC.

Use PowerShell to set compatibility flags for all AutoCAD versions:

$autocadPaths = @(
    "C:\Program Files\Autodesk\AutoCAD 2022\acad.exe",
    "C:\Program Files\Autodesk\AutoCAD 2023\acad.exe",
    "C:\Program Files\Autodesk\AutoCAD 2024\acad.exe",
    "C:\Program Files\Autodesk\AutoCAD 2025\acad.exe",
    "C:\Program Files\Autodesk\AutoCAD 2026\acad.exe"
)

$regPath = "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers"

# Ensure the registry path exists
if (!(Test-Path $regPath)) {
    New-Item -Path $regPath -Force | Out-Null
}

foreach ($path in $autocadPaths) {
    if (Test-Path $path) {
        Write-Host "Configuring compatibility for: $path" -ForegroundColor Yellow
        Set-ItemProperty -Path $regPath -Name $path -Value "HIGHDPIAWARE" -ErrorAction SilentlyContinue
        Write-Host "Applied HIGHDPIAWARE compatibility flag" -ForegroundColor Green
    }
}

For systems that still require elevated privileges, you can temporarily set RUNASADMIN flag:

# Only use this if other methods fail
# Set-ItemProperty -Path $regPath -Name $path -Value "RUNASADMIN" -ErrorAction SilentlyContinue

Verification: Check the compatibility settings in the registry: Get-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers". Launch AutoCAD and verify it starts without prompts.

06

Test and Validate the Fix Across User Profiles

Test the solution across different user profiles to ensure it works for all users, including new profiles that haven't launched AutoCAD before.

Create a test script to validate the fix:

# AutoCAD UAC Fix Validation Script
$testResults = @()

# Check registry setting
$regCheck = Get-ItemProperty -Path "HKLM:\SOFTWARE\Policies\Microsoft\Windows\Installer" -Name "DisableMSI" -ErrorAction SilentlyContinue
if ($regCheck.DisableMSI -eq 2) {
    $testResults += "✓ Registry fix applied correctly"
} else {
    $testResults += "✗ Registry fix missing or incorrect"
}

# Check Windows Installer service
$serviceStatus = Get-Service -Name "msiserver" -ErrorAction SilentlyContinue
if ($serviceStatus.Status -eq "Running") {
    $testResults += "✓ Windows Installer service is running"
} else {
    $testResults += "✗ Windows Installer service is not running"
}

# Check for September 2025 updates
$updates = Get-HotFix | Where-Object {$_.HotFixID -like "*5065*"}
if ($updates) {
    $testResults += "✓ September 2025 security updates installed"
} else {
    $testResults += "⚠ September 2025 updates not detected - check Windows Update"
}

# Display results
Write-Host "AutoCAD UAC Fix Validation Results:" -ForegroundColor Cyan
$testResults | ForEach-Object { Write-Host $_ }

# Test AutoCAD launch (if available)
$autocadExe = Get-ChildItem -Path "C:\Program Files\Autodesk" -Recurse -Name "acad.exe" -ErrorAction SilentlyContinue | Select-Object -First 1
if ($autocadExe) {
    Write-Host "\nFound AutoCAD at: $autocadExe" -ForegroundColor Yellow
    Write-Host "Test launching AutoCAD manually to verify no UAC prompts appear." -ForegroundColor Yellow
}

Test with different user accounts:

runas /user:testuser "C:\Program Files\Autodesk\AutoCAD 2026\acad.exe"

Verification: The validation script should show all green checkmarks. Test AutoCAD launch with both admin and standard user accounts. No UAC prompts should appear for standard users.

Pro tip: Save this validation script and run it after any Windows updates to ensure the fix remains in place.
07

Create Rollback Plan and Documentation

Document the changes made and create a rollback plan in case issues arise. This is crucial for enterprise environments and compliance requirements.

Create a rollback script:

# AutoCAD UAC Fix Rollback Script
Write-Host "Rolling back AutoCAD UAC fix..." -ForegroundColor Yellow

# Remove registry setting
$regPath = "HKLM:\SOFTWARE\Policies\Microsoft\Windows\Installer"
try {
    Remove-ItemProperty -Path $regPath -Name "DisableMSI" -ErrorAction Stop
    Write-Host "✓ Removed DisableMSI registry setting" -ForegroundColor Green
} catch {
    Write-Host "⚠ DisableMSI setting not found or already removed" -ForegroundColor Yellow
}

# Remove compatibility flags
$compatPath = "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers"
$autocadPaths = @(
    "C:\Program Files\Autodesk\AutoCAD 2022\acad.exe",
    "C:\Program Files\Autodesk\AutoCAD 2023\acad.exe",
    "C:\Program Files\Autodesk\AutoCAD 2024\acad.exe",
    "C:\Program Files\Autodesk\AutoCAD 2025\acad.exe",
    "C:\Program Files\Autodesk\AutoCAD 2026\acad.exe"
)

foreach ($path in $autocadPaths) {
    try {
        Remove-ItemProperty -Path $compatPath -Name $path -ErrorAction SilentlyContinue
        Write-Host "✓ Removed compatibility flag for $path" -ForegroundColor Green
    } catch {
        # Silently continue if property doesn't exist
    }
}

Write-Host "\nRollback completed. Restart required for full effect." -ForegroundColor Cyan
Write-Host "Note: Microsoft September 2025 updates remain installed (recommended)." -ForegroundColor Yellow

Document the implementation:

AutoCAD UAC Fix Implementation Log
Date: [Current Date]
Implemented by: [Your Name]
Affected Systems: [List systems/OUs]

Changes Made:
1. Registry: HKLM\SOFTWARE\Policies\Microsoft\Windows\Installer\DisableMSI = 2
2. Windows Updates: KB5065426/KB5065431 installed
3. Compatibility flags: Applied to AutoCAD executables

Testing Results:
- Standard users can launch AutoCAD without UAC prompts: [Pass/Fail]
- Admin users retain full functionality: [Pass/Fail]
- No impact on other MSI-based applications: [Pass/Fail]

Rollback Procedure:
- Run rollback script: rollback-autocad-fix.ps1
- Force Group Policy update: gpupdate /force
- Restart affected systems

Verification: Test the rollback script in a lab environment. Ensure you can fully reverse all changes. Keep the documentation updated with any system-specific modifications.

Warning: Always test rollback procedures before implementing fixes in production. Some changes may require system restarts to take full effect.

Frequently Asked Questions

Why does AutoCAD suddenly ask for admin credentials after Windows updates?+
Microsoft's August 2025 security updates (KB5063875, KB5064010, KB5063877) introduced stricter MSI repair operation controls to address CVE-2025-50173. AutoCAD's installer components trigger these repair checks on first launch, now requiring administrative privileges that weren't needed before. This affects AutoCAD versions 2022-2026 specifically.
Is it safe to disable MSI repair prompts using the DisableMSI registry setting?+
Setting DisableMSI to 2 is a temporary workaround that prevents all MSI repair operations system-wide. While effective for resolving AutoCAD issues, it should only be used until Microsoft's September 2025 updates (KB5065426/KB5065431) are installed. The registry setting can prevent legitimate software repairs, so implement it carefully and document for rollback.
Which Microsoft updates fix the AutoCAD UAC prompt issue permanently?+
Microsoft released fixes on September 9, 2025: KB5065426 for Windows 11 24H2 (build 26100.6584) and KB5065431 for Windows 11 22H2/23H2 (builds 22621.5909/22631.5909). These updates resolve the MSI repair UAC issue without requiring registry modifications or Group Policy workarounds. Install these updates for the permanent, official solution.
Can this AutoCAD fix be deployed across an entire domain using Group Policy?+
Yes, use Group Policy Preferences to create a registry item at Computer Configuration > Preferences > Windows Settings > Registry. Set HKLM\SOFTWARE\Policies\Microsoft\Windows\Installer\DisableMSI to REG_DWORD value 2. This deploys the fix to all domain computers automatically. Remember to remove this policy after installing Microsoft's September 2025 updates.
What should I do if AutoCAD still shows Error 1730 after applying the registry fix?+
Restart the Windows Installer service using 'net stop msiserver' then 'net start msiserver'. Re-register the service with 'msiexec /unregister' and 'msiexec /regserver'. Clear temporary MSI files from %TEMP% and %WINDIR%\Temp. If issues persist, check for third-party security software interference and consider reinstalling AutoCAD with administrative privileges to rebuild the MSI cache.
Evan Mael
Written by

Evan Mael

Microsoft MCSA-certified Cloud Architect | Fortinet-focused. I modernize cloud, hybrid & on-prem infrastructure for reliability, security, performance and cost control - sharing field-tested ops & troubleshooting.

Discussion

Share your thoughts and insights

Sign in to join the discussion