If you’re seeing customaction 1603 error on your computer, check out these repair tips.

Error code 1603 is a simple Windows Installer error code when a custom action throws an error/exception. The Windows Installer does not show the actual error/exception in the installation logs. To check the actual error/exception, we can debug the custom action. Confirm if the custom action throws an error/exception.


Sorry, something was wrong.

Copy link

How do I fix error code 1603?

Close background software.Check if any software is already installed.Check carefully who has enough disk space for the program.Open the program installation and hence uninstall the troubleshooter.Delete temporary files from the Windows temporary folder.Restart the Windows Installer service.


@IngridAtMicrosoft Ingrid At Microsoft Commented 16. October 2021

Thank you for your commitment to our documentation at last. If we were unable to check your issue in time, we sincerely apologize for the late response. We collect the information you have for verification purposes. We’re closing the thread for now, but if you think this is still the goal, please reply and keep that in mind. If you notice that there may be another update to our documentation And don’t hesitate to contact us again. #please close

Join the conversation

customaction error 1603

Use existing MySonicWall accounts for authorization. To create a free MySonicWall account, click Sign Up.

All Time Community Leader

As mentioned earlier, error code 1603 is most often returned when almost every action in the installation fails. Also, this most often indicates that user actions in the MSI failed.
When we encounter a configuration that no longer works and returns code 1603, the following steps must be taken on this website:
Guide Retry the configuration detailed logging. using steps similar to the methods listed here.
Step i: Create a verbose log file that will be accepted as msi*.log in the %temp% directory the next time the installation package is run.
Step 2. OpenRead the exact verbose log in a text editor such as Notepad and look for the string “return value 3” in order. In almost all cases, this leads us to the section of each verbose log that lists the policies that caused the build to be canceled in the first place.
Step 3: Examine the contents of the log file just above the “return 3” value stream to determine which custom action could have caused the default action to fail. Depending on the type of action that failed, we will ask you to continue here in more detail after debugging.
You may find that often our biggest problem when debugging a failed configuration is to focus on the part of the configuration that is on doesn’t really work. , and this trick along with looking for the value “return 3” speeds up the process pretty well in almost all cases.
Of course, the situation doesn’t work 100% of the time. In particular, when you run the installer on a non-English Windows model, the string “Return Rate 3” is written to the mapping file in the OS language, not English, soString search doesn’t really work.
Link:< br>Aaron Stebner’s weblog

Benutzeraktionsfehler 1603
Erro De Acao Personalizada 1603
Error De Accion Personalizada 1603
Oshibka Nastrojki 1603
사용자 지정 작업 오류 1603
Customaction Error 1603
Errore Di Azione Personalizzata 1603
Customaction Fout 1603
Erreur D Action Personnalisee 1603