- Newest
- Most votes
- Most comments
Hello.
Can you run the MSI installer with the command below and check the detailed log?
This log may contain information that can be useful for troubleshooting.
msiexec /i AWSCLIV2.msi /L*V install.log
This error occurs when the installer doesn't have sufficient permissions to write to the destination folder. Here are some solutions to try:
- Run the installer with explicit administrator privileges:
- Right-click on the AWS CLI MSI file
- Select "Run as administrator"
- Install to a different directory that you have write permissions for:
- When running the installer, choose a custom installation path
- Select a directory where you have full write permissions
- Check for existing processes that might be locking the file:
- Close any applications that might be using AWS CLI components
- Restart your computer to ensure no processes are holding locks on files
- If you previously attempted an installation, try removing any remnants:
- Delete the installer
- Download a fresh copy of the AWS CLI installer
- Run the new installer with administrator privileges
If you're still encountering issues, you could try an alternative installation method, such as using pip to install the AWS CLI in a Python environment where you have appropriate permissions.
Sources
Install the AWS SAM CLI - AWS Serverless Application Model
How to Fix servicemanager.pyd Access Denied Error during AWS Migration Service or Elastic Disaster Recovery Agent re-installation | AWS re:Post
Thanks, I ran the command , here are the last few lines from the log file. Would you like to have the whole file? Does this help? I did launch power shell as a administrator and then ran the command.
Property(C): DATABASE = C:\Users\sakth\Downloads\AWSCLIV2.msi
Property(C): OriginalDatabase = C:\Users\sakth\Downloads\AWSCLIV2.msi
Property(C): SOURCEDIR = C:\Users\sakth\Downloads
Property(C): VersionHandler = 5.00
Property(C): UILevel = 5
Property(C): ACTION = INSTALL
Property(C): EXECUTEACTION = INSTALL
Property(C): ROOTDRIVE = C:
Property(C): CostingComplete = 1
Property(C): OutOfDiskSpace = 0
Property(C): OutOfNoRbDiskSpace = 0
Property(C): PrimaryVolumeSpaceAvailable = 0
Property(C): PrimaryVolumeSpaceRequired = 0
Property(C): PrimaryVolumeSpaceRemaining = 0
Property(C): INSTALLLEVEL = 1
=== Logging stopped: 10/8/2025 23:01:16 ===
MSI (c) (58:F8) [23:01:16:045]: Note: 1: 1708
MSI (c) (58:F8) [23:01:16:045]: Note: 1: 2205 2: 3: Error
MSI (c) (58:F8) [23:01:16:045]: Note: 1: 2228 2: 3: Error 4: SELECT Message FROM Error WHERE Error = 1708
MSI (c) (58:F8) [23:01:16:045]: Note: 1: 2205 2: 3: Error
MSI (c) (58:F8) [23:01:16:045]: Note: 1: 2228 2: 3: Error 4: SELECT Message FROM Error WHERE Error = 1709
MSI (c) (58:F8) [23:01:16:045]: Product: AWS Command Line Interface v2 -- Installation failed.
MSI (c) (58:F8) [23:01:16:045]: Windows Installer installed the product. Product Name: AWS Command Line Interface v2. Product Version: 2.31.11.0. Product Language: 1033. Manufacturer: Amazon Web Services. Installation success or error status: 1603.
MSI (c) (58:F8) [23:01:16:045]: Grabbed execution mutex. MSI (c) (58:F8) [23:01:16:045]: Cleaning up uninstalled install packages, if any exist MSI (c) (58:F8) [23:01:16:045]: MainEngineThread is returning 1603 === Verbose logging stopped: 10/8/2025 23:01:16 ===
Relevant content
- asked 10 months ago
- asked 2 years ago

Do you have antivirus software installed on your PC? In rare cases, I've seen this software interfere with the installation of the AWS CLI. The log also contains an error message that occurs when you try to install an app that is already installed on your PC. This can also occur due to files created during a previous failed installation. I recommend that you first check the procedure for "Grant Full Control permissions to the SYSTEM account." in the following document. https://learn.microsoft.com/en-us/troubleshoot/windows-server/application-management/msi-installation-error-1603
I'm not sure if this will solve the problem, but why not try running the following command in a command prompt opened with administrator privileges to forcibly delete the AWS CLI remnant files?
(1)Yes, I have Norton Anti virus installed which used to prevent install in the first 10 seconds, but then i added the CLI as a acceptable exception, i was able to proceed. (2) Also i check each time, in control panel , programs menu -- once i had to delete a partial install. (3) IN further attempts, i see no AWSCLI in the programs menu- so i cant uninstall what is not showingup. I also checked for existence of a "amazon" or "amazocli" folder under c:\Programs\ and dont see such folder , uisng windows explorer. I guess its not a hidden folder. (4) Let me try the other steps of ownership etc and update the post here. Ty for all the help.
I tried this (https://learn.microsoft.com/en-us/troubleshoot/windows-server/application-management/msi-installation-error-1603) to ensure that the SYSTEM is having full control on the folder. Yes, it its. I have a screen shot too. but not able to paste it here to the comment. Let me try the icacls and takeown command- never used them before, will try.