Intune SYSTEM account issue causing Windows Installer reconfigure msg
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
I’ve created a PowerShell script that installs AutoCAD 2025 and deployed it to my pilot laptop for testing but I’m getting a 1st time error when launching the start menu shortcut where windows installer appears for a few secs and says reconfiguring or repairing which I thought was odd so checked event viewer and saw ID 1035 for windows installer reconfiguring it?
Any ideas of it might be a broken shortcut or something? I tested this on my VM too but didn’t experience this odd behaviour?
ID 1040
Beginning a Windows Installer transaction: {28B89EEF-8101-0409-2102-CF3F3A09B77D}. Client Process Id: 3548.
ID 10005
Product: AutoCAD 2025 - English -- Run Setup.exe to install AutoCAD 2025 - English.
ID 11729
Product: AutoCAD 2025 - English -- Configuration failed
ID 1035
Windows Installer reconfigured the product. Product Name: AutoCAD 2025 - English. Product Version: 25.0.58.0. Product Language: 3081. Manufacturer: Autodesk. Reconfiguration success or error status: 1603.
ID 1042
Ending a Windows Installer transaction: {28B89EEF-8101-0409-2102-CF3F3A09B77D}. Client Process Id: 3548.
ID 1040
Beginning a Windows Installer transaction: {28B89EEF-8101-0409-2102-CF3F3A09B77D}. Client Process Id: 8572.
ID 11728
Product: AutoCAD 2025 - English -- Configuration completed successfully.
ID 1035
Windows Installer reconfigured the product. Product Name: AutoCAD 2025 - English. Product Version: 25.0.58.0. Product Language: 3081. Manufacturer: Autodesk. Reconfiguration success or error status: 0.
ID 1042
Ending a Windows Installer transaction: {28B89EEF-8101-0409-2102-CF3F3A09B77D}. Client Process Id: 8572.
EDIT: I've just tested this w/ an older 2024 pkg and same issue when deploying from Intune SYSTEM account? obviously not an issue for local ADM....
$msiPath = "C:\Windows\Installer\b69dc.msi"
$targetDirectory = "C:\Program Files\Autodesk\AutoCAD 2025\UserDataCache"
Ensure target directory exists
if (-not (Test-Path $targetDirectory)) {
New-Item -ItemType Directory -Path $targetDirectory -Force
}
Set working directory and arguments
$processStartInfo = @{
FilePath = "msiexec.exe"
ArgumentList = @(
"/i"
""$msiPath""
"/qb"
"REINSTALL=UserData"
"REINSTALLMODE=uos"
"ACAD_SECONDARY_INSTALL=1"
"CURRENTDIRECTORY="$targetDirectory""
"CLIENTUILEVEL=2"
"CLIENTPROCESSID=$($PID)"
)
WorkingDirectory = $targetDirectory
Wait = $true
NoNewWindow = $true
}
Execute with specific working directory
Start-Process @processStartInfo
After further testing came up with above code to reinstall the userdata as once I switched on Windows Installer logging it created a log under %TEMP% and I was able to see what the Windows Installer i.e 1035 error was doing from this log, it appears it was trying to reinstall the local userdata that was missing... interesting stuff but waste of time... looks like I'll have to leave it as badly designed app
