Error 1603- fatal errorduring installation of IQSET on windows 11

Question

Error 1603- fatal errorduring installation of IQSET on windows 11

Jr, Sruthi 0

Hii,

I was trying to install IQSET tool in my laptop, I was getting this error

Feature transfer error

Error- 1603 : Fatal error during installation

Consult windows installer help(msi.chm) or MSDN for more information.

could you please help how to proceed further.

User's image

0 comments

3 answers

Your answer

Answer 1

Jr, Sruthi 0

I tried the ways mentioned above but didn't resolve the issue,

want to try enabling Windows Installer logging.

how to enable it?

Ramesh Srinivasan 88,460 Reputation points Independent Advisor

2026-10-01T06:51:21.3466667+00:00

The command-line example I posted runs setup with verbose logging.

Answer 2

Ramesh Srinivasan 88,460 Independent Advisor

Hi,

Please copy the installer package (.msi) file to the C:\ drive's root directory and launch the setup from admin Command Prompt.

For example, if the file name is setup.msi, open Command Prompt (admin) and run this command:

msiexec /i "C:\setup.msi" /l*vx "C:\installer.log"

This starts the setup with verbose logging.

If the setup fails, attach the file C:\installer.log in your reply.

Jr, Sruthi 0 Reputation points

2026-10-01T06:52:09.1166667+00:00

this package installer is an exe file
Jr, Sruthi 0 Reputation points

2026-10-01T06:54:14.07+00:00
in the log I got like this
=== Verbose logging started: 01-10-2026 12:20:51 Build type: SHIP UNICODE 5.00.10011.00 Calling process: C:\Windows\system32\msiexec.exe ===

MSI (c) (F8:F0) [12:20:51:452]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg

MSI (c) (F8:F0) [12:20:51:452]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg

MSI (c) (F8:08) [12:20:51:475]: Resetting cached policy values

MSI (c) (F8:08) [12:20:51:475]: Machine policy value 'Debug' is 0

MSI (c) (F8:08) [12:20:51:475]: ******* RunEngine:

******* Product: C:\SET_9_0_Alpha_39.exe ******* Action: ******* CommandLine: **********

MSI (c) (F8:08) [12:20:51:477]: Note: 1: 2203 2: C:\SET_9_0_Alpha_39.exe 3: -2147286960

MSI (c) (F8:08) [12:20:51:477]: MainEngineThread is returning 1620

=== Verbose logging stopped: 01-10-2026 12:20:51 ===
Ramesh Srinivasan 88,460 Reputation points Independent Advisor

2026-10-01T06:59:42.2066667+00:00
Looks like it's an EXE bootstrapper with an .msi enclosed in it.

Please try this command:

C:\SET_9_0_Alpha_39.exe /l*vx "C:\installer.log"
Jr, Sruthi 0 Reputation points

2026-10-01T07:33:21.0433333+00:00

Now it got installed. then I tried to open this System Engineering tool inorder to provide the license.but when I opened the SET tool window got opened and it displayed like license expired, then immedietly window got off. Not showing the page to add the license. could you please tell me why?
Ramesh Srinivasan 88,460 Reputation points Independent Advisor

2026-10-01T07:37:16.2433333+00:00

The license issue is specific to that app. Since IQSET is not a Microsoft product, the best option is to contact the software vendor to resolve the issue.

Answer 3

Error 1603 means Fatal error during installation.

Try these checks in order:

Check whether IQSET is already installed
- Open Start > Settings > System > Apps & features.
- Look for IQSET / SET / Trend related entries.
- If found, uninstall them, restart Windows, and try the installer again.
Install to a non-encrypted folder
- Error 1603 can occur if the target install folder is encrypted.
- If the installer lets the install path be changed, choose a normal local folder that is not encrypted.
Avoid substitute drives
- If installing to a mapped or substitute drive, install to a normal local drive such as the main Windows drive instead.
Check SYSTEM permissions on the target drive/folder
- Right-click the drive or folder where the app is being installed and select Properties.
- Open the Security tab.
- Verify that SYSTEM is listed.
- If it is missing, add it and grant Full Control.
- This is important because error 1603 can occur when the SYSTEM account does not have Full Control on the install location.
Enable Windows Installer logging and retry
- Retry the installation after enabling Windows Installer logging.
- Then check the new log in the %temp% folder.
- The log file name usually starts with Msi and ends with .log.
- When reviewing the log, look near Return value 3, which is typically close to the actual failure reason.
If another version is already present
- If Windows reports that another version of the product is already installed, remove the older version first from Settings > Apps and then install the required one again.

If the installer still fails after these steps, the MSI log is the next useful item because 1603 is a general installer failure and the log usually shows the exact blocked file, permission issue, or conflicting component.