[Resolved] Getting error 1603 during installation

altan wrote on 12/6/2020, 6:24 AM

Hi all, looking for a solution for this Error 1603 issue I encountered during the Music Maker (64bit) installation process.

I manage to download the Music Maker installer via the manager and it automatically starts the installation once download was complete. Everythign was fine until I clicked on the Accept and Install button and then it prompt an Installation Error with the details showing Error 1603 without any other reasons. I sent a couple of emails via the customer service inquiry in the installer but haven't gotten any replay yet.

I tried several possible solutions from cleaning out the registry, to deleting any possible folders related to Magix but to no avail.

I also had an issue with installing Acid Music Studio as well and this one did not prompt any errors, reaching 30% progress bar then said successfully installed but the app and folder doesn't exist on my HDD. I will create a separate post on this one.

It seems I'm unable to install any Magix product at this rate due to this error. Besides this is the first time I'm installing a product from Magix.

Would appreciate if this can be resolved asap.

Links to a pic of the errorhttps://imgur.com/ZO4Vo37

[Solution]:

Check if your windows update isn't having any issues.

Comments

SP. wrote on 12/6/2020, 6:23 PM

@altan It could be that your Windows user account doesn't have full rights to install software in the selected installation directories?

Maybe try to install Music Maker under C:\Users\YOUR_USER_NAME\Music Maker 2021\

altan wrote on 12/6/2020, 11:09 PM

@altan It could be that your Windows user account doesn't have full rights to install software in the selected installation directories?

Maybe try to install Music Maker under C:\Users\YOUR_USER_NAME\Music Maker 2021\

Thanks for the reply. One of the solutions I went through before making this post was to follow the windows documentation on MSI installation erorr 1603 (https://docs.microsoft.com/en-us/troubleshoot/windows-server/application-management/msi-installation-error-1603) and setup the system permission as stated in the instructions but the same error persist.

I tried changing the directory for the main location as well as the template, common files, and user files to C:\Users\"username"\... as well as installing it in another hard drive other than c: but that also did not work too.

johnebaker wrote on 12/7/2020, 8:40 AM

@altan

Hi see this comment from Magix support, you may need to add appropriate exceptions to your Antivirus - although the comment mentions AVG and Avast there are also known issues with Windows Defender and BitDefender security features causing the same issue..

John EB
Forum Moderator

altan wrote on 12/7/2020, 10:51 PM

@altan

Hi see this comment from Magix support, you may need to add appropriate exceptions to your Antivirus - although the comment mentions AVG and Avast there are also known issues with Windows Defender and BitDefender security features causing the same issue..

John EB
Forum Moderator

Hi John, thanks for the reply. I tried what you suggested and unfortunately the error still persist.

After I dug deeper regarding the error, I manage to find one solution that actually work. Apparently my Windows Update did not manage to complete one of its updates due to an update package getting stuck with an installation error, causing any new installations to have the same issue. The solution is simple and that is to just restart the update for a specific package and that resolves the 1603 error.

Now I can install both Music Maker and Acid Music Studio after resolving an issue with Windows Update.

johnebaker wrote on 12/8/2020, 6:01 AM

@altan

Thanks for letting us know the cause and that you are now up and running again.

John EB

davidr1 wrote on 1/27/2025, 5:29 AM

4 years later this is still a problem. Magix hasn’t updated the software since 2018. That’s what I learnt from Magix support. But Magix support blames the customer not their software for the issue. Now you’d think that the a p mount of feedbacks on the software and complaints here that Magix might have said we need to fix this but in reality they have gone bankrupt according to German News and were looking a buyer. I suspect the money wasn’t there to fix it. Now it could be that Windows 11 is at fault as they told me. They also told me that McAfee and Malearebytes might be at fault. If the protection is at fault by removing the said files why isn’t it flagging it as so? Normally McAfee and malewarebytes tell you that they remove and quarantine said files. Neither have these softwares flagged them as so. I am surprised that McAfee or Malewarebytes would remove files from a legit piece of software.

SP. wrote on 1/27/2025, 6:26 AM

@davidr1 McAfee? Oh boy...

johnebaker wrote on 1/27/2025, 10:43 AM

@davidr1

If you are running McAffee I agree with @SP.'s comment.

Assuming you mean you are getting the same Error code: 1603, the error code means the run permissions, or Temp folder access permissions, are incorrect. This can be caused by a Windows update failing, or blocked by some AntiVirus programs which are have over bloated and heavy handed protection features.

The Microsoft solution is here

John EB
Forum Moderator

davidr1 wrote on 1/28/2025, 2:43 AM

Could be worse Kasperky! I am just surprised that Magix Support hasn’t said error 1603 needs the following to install the software. They must know which folders that their software access to install it. There is also another error in the installation logs shows waasmedicservice has issue as well! It says failed to start. Even restarting the service doesn’t work.

SP. wrote on 1/28/2025, 3:07 AM

@davidr1 Error 1603 is a generic Windows error during an installation that can have a whole lot of different causes. It's not as easy as 'do this and that and it's done'.

SP. wrote on 1/28/2025, 3:12 AM

@davidr1 WaaSMediaService seems to be used to repair damaged Windows updates? Could be that your system has multiple problems.

Have you tried to repair it?

System File Checker is a utility in Windows that checks for problems with files on your computer. To run it, follow these steps:

Make sure you've installed the latest updates for Windows, and then restart your machine. To find out more, read Update Windows.

In the search box on the taskbar, type command prompt, and right-click or press and hold Command Prompt (Desktop app) from the list of results. Select Run as administrator, and then select Yes.

Type DISM.exe /Online /Cleanup-image /Restorehealth (note the space before each "/"), and then press Enter. (Note: This step may take a few minutes to start and complete.)

After you see a message that says "The operation completed successfully," type sfc /scannow (note the space between "sfc" and "/") and press Enter.

After you see a message that says, "Verification 100% complete," type exit and press Enter.

https://support.microsoft.com/en-us/windows/using-system-file-checker-in-windows-365e0031-36b1-6031-f804-8fd86e0ef4ca