Error 1603 Driving me insane

Hi all, I'm having some major trouble with installing programs on this machine. I can live with a couple of the issues (design review & IES ve-ware), but I really need to install 1 of these programs asap (Autodesk 3ds max design) It will start the installation process absolutelly fine, when it gets about a minute in though (the status bar is at the 'writing registry values' stage) it just stops, throws up a splash screen telling me that nothing was installed, and directs me to the installation log. The log file simply says - 'Installation was aborted - error 1603'. I've done ALL the fixes for 1603 I could fins anywhere on the net. The drive I'm installing to is my C drive which is totally open, and the SYSTEM account has all access rights. I did install service pack 3 (against my will…) which was said to sort it out, but it didn't (so i've uninstalled it again…). I've run a HiJack This scan, just incase it enlightened any of you more technically gifted people to what the issue could be - see below… 📎HJT_Log.txt Any help would be greatly appreciated. Thanks

Ok.. First of all, your comment about Service Pack 3 is unfounded. To date I've never seen service pack 3 cause an issue after hundreds of installations. Service Pack 2 made many changes and broke many things. Service Pack 3 only brings you up to date with the most recent patches at the time Service Pack 3 was released.

You will be doing no harm by installing it and I recommend you put it back on and install the rest of your windows updates.

Next, if you are failing at "writing registry values…," it would be safe to assume that the installation is having trouble accessing a portion of the registry.

The first thing to do is turn off all security software such as your anti-virus and try again.

If it still fails, I recommend leaving the anti-virus software off temporarily and following the instructions found here:
http://support.microsoft.com/kb/949377
Read under "Advanced Troubleshooting: Method 1." The procedure will restore access to all portions of the registry and file system to any administrative user and resolve access problems.

On a side note, SYSTEM is not the "user" that needs access, it is your user account that needs to be able to access the particular file or registry entry because you are the one initiating the install.

Okie Dokie… All I used to hear is the pains of service pack 3 when it came out, which is why I've not bothered with it. I might give it a go here at work first… Every other 'fix' for this has mentioned the SYSTEM user needed access, which is why I tried that… Thanks for the info, I'll give it a go and let you know how I got on.

Right…

Well I tried using the Reset.exe and it didn't seem to make any difference. Install just failed at the same point again…

I have now installed SP3, uninstalled and deleted any files related to any version of 3ds max on the computer, and have run the Reset.exe again…

Before I try the install again, what else should I do?

There are no 3ds max 'folders' in the registry - but there are a few 3ds max keys (If I go to Edit > Find > '3ds' in the registry editor)


In a verbose log of the install the only lines that look out of place are these:
MSI © (30:A0) [17:33:47:157]: Disallowing installation of component: C__0C45265A45B14A4C96C86D79058DCE6E.9CD50E276F8D4F38BCF9A72F90323BAA since the registry keypath exists and the component is marked to never overwrite existing installations
MSI © (30:A0) [17:33:47:157]: Disallowing installation of component: C__16558A777D684150B6B44B845A44CB90.9CD50E276F8D4F38BCF9A72F90323BAA since the registry keypath exists and the component is marked to never overwrite existing installations
MSI © (30:A0) [17:33:47:157]: Disallowing installation of component: C__1AF1EAA38D734E1B8A6F0593760F4D3E.9CD50E276F8D4F38BCF9A72F90323BAA since the registry keypath exists and the component is marked to never overwrite existing installations
MSI © (30:A0) [17:33:47:157]: Disallowing installation of component: C__343942ED66FE485788366280EB1A772C.9CD50E276F8D4F38BCF9A72F90323BAA since the registry keypath exists and the component is marked to never overwrite existing installations
MSI © (30:A0) [17:33:47:157]: Disallowing installation of component: C__351D86F5CA604FABB7551F37F21A1C0C.9CD50E276F8D4F38BCF9A72F90323BAA since the registry keypath exists and the component is marked to never overwrite existing installations
MSI © (30:A0) [17:33:47:157]: Disallowing installation of component: C__409DAB7B9E8D449AB403C728A849D992.9CD50E276F8D4F38BCF9A72F90323BAA since the registry keypath exists and the component is marked to never overwrite existing installations
MSI © (30:A0) [17:33:47:157]: Disallowing installation of component: C__76354361459B414E9031531D989A3695.9CD50E276F8D4F38BCF9A72F90323BAA since the registry keypath exists and the component is marked to never overwrite existing installations
MSI © (30:A0) [17:33:47:157]: Disallowing installation of component: C__96B2FE0BD85B423DA1BABB051B48BB92.9CD50E276F8D4F38BCF9A72F90323BAA since the registry keypath exists and the component is marked to never overwrite existing installations
MSI © (30:A0) [17:33:47:157]: Disallowing installation of component: C__BF06D2FFDFD5480B8EB84771855823A7.9CD50E276F8D4F38BCF9A72F90323BAA since the registry keypath exists and the component is marked to never overwrite existing installations
MSI © (30:A0) [17:33:47:157]: Disallowing installation of component: C__CFC7A647FE38496D87F0163B82AF544C.9CD50E276F8D4F38BCF9A72F90323BAA since the registry keypath exists and the component is marked to never overwrite existing installations
MSI © (30:A0) [17:33:47:157]: Disallowing installation of component: C__E5C12F9CCE3041FF8E2B7DDD29CF45A7.9CD50E276F8D4F38BCF9A72F90323BAA since the registry keypath exists and the component is marked to never overwrite existing installations
MSI © (30:A0) [17:33:47:157]: Disallowing installation of component: C__350EB3E106944779BE07AB55A3B327D8.9CD50E276F8D4F38BCF9A72F90323BAA since the registry keypath exists and the component is marked to never overwrite existing installations
MSI © (30:A0) [17:33:47:157]: Disallowing installation of component: C__65A41EF2253341D0B7B596C0D811C246.9CD50E276F8D4F38BCF9A72F90323BAA since the registry keypath exists and the component is marked to never overwrite existing installations
MSI © (30:A0) [17:33:47:157]: Disallowing installation of component: C__955096E0A38844C48593C55DB06DB84A.9CD50E276F8D4F38BCF9A72F90323BAA since the registry keypath exists and the component is marked to never overwrite existing installations
MSI © (30:A0) [17:33:47:157]: Disallowing installation of component: C__99E42F83A77F499C863D4F59E3979545.9CD50E276F8D4F38BCF9A72F90323BAA since the registry keypath exists and the component is marked to never overwrite existing installations
MSI © (30:A0) [17:33:47:157]: Disallowing installation of component: C__A81618074DAF4C9C90AF6D0844D3C375.9CD50E276F8D4F38BCF9A72F90323BAA since the registry keypath exists and the component is marked to never overwrite existing installations
MSI © (30:A0) [17:33:47:157]: Disallowing installation of component: C__DB0B31F3F36141E08DF9DC8CFEA920F4.9CD50E276F8D4F38BCF9A72F90323BAA since the registry keypath exists and the component is marked to never overwrite existing installations


MSI © (30:A0) [17:33:51:269]: Disallowing installation of component: C__0C45265A45B14A4C96C86D79058DCE6E.9CD50E276F8D4F38BCF9A72F90323BAA since the registry keypath exists and the component is marked to never overwrite existing installations
MSI © (30:A0) [17:33:51:269]: Disallowing installation of component: C__16558A777D684150B6B44B845A44CB90.9CD50E276F8D4F38BCF9A72F90323BAA since the registry keypath exists and the component is marked to never overwrite existing installations
MSI © (30:A0) [17:33:51:269]: Disallowing installation of component: C__1AF1EAA38D734E1B8A6F0593760F4D3E.9CD50E276F8D4F38BCF9A72F90323BAA since the registry keypath exists and the component is marked to never overwrite existing installations
MSI © (30:A0) [17:33:51:269]: Disallowing installation of component: C__343942ED66FE485788366280EB1A772C.9CD50E276F8D4F38BCF9A72F90323BAA since the registry keypath exists and the component is marked to never overwrite existing installations
MSI © (30:A0) [17:33:51:269]: Disallowing installation of component: C__351D86F5CA604FABB7551F37F21A1C0C.9CD50E276F8D4F38BCF9A72F90323BAA since the registry keypath exists and the component is marked to never overwrite existing installations
MSI © (30:A0) [17:33:51:269]: Disallowing installation of component: C__409DAB7B9E8D449AB403C728A849D992.9CD50E276F8D4F38BCF9A72F90323BAA since the registry keypath exists and the component is marked to never overwrite existing installations
MSI © (30:A0) [17:33:51:269]: Disallowing installation of component: C__76354361459B414E9031531D989A3695.9CD50E276F8D4F38BCF9A72F90323BAA since the registry keypath exists and the component is marked to never overwrite existing installations
MSI © (30:A0) [17:33:51:269]: Disallowing installation of component: C__96B2FE0BD85B423DA1BABB051B48BB92.9CD50E276F8D4F38BCF9A72F90323BAA since the registry keypath exists and the component is marked to never overwrite existing installations
MSI © (30:A0) [17:33:51:269]: Disallowing installation of component: C__BF06D2FFDFD5480B8EB84771855823A7.9CD50E276F8D4F38BCF9A72F90323BAA since the registry keypath exists and the component is marked to never overwrite existing installations
MSI © (30:A0) [17:33:51:269]: Disallowing installation of component: C__CFC7A647FE38496D87F0163B82AF544C.9CD50E276F8D4F38BCF9A72F90323BAA since the registry keypath exists and the component is marked to never overwrite existing installations
MSI © (30:A0) [17:33:51:269]: Disallowing installation of component: C__E5C12F9CCE3041FF8E2B7DDD29CF45A7.9CD50E276F8D4F38BCF9A72F90323BAA since the registry keypath exists and the component is marked to never overwrite existing installations
MSI © (30:A0) [17:33:51:269]: Disallowing installation of component: C__350EB3E106944779BE07AB55A3B327D8.9CD50E276F8D4F38BCF9A72F90323BAA since the registry keypath exists and the component is marked to never overwrite existing installations
MSI © (30:A0) [17:33:51:269]: Disallowing installation of component: C__65A41EF2253341D0B7B596C0D811C246.9CD50E276F8D4F38BCF9A72F90323BAA since the registry keypath exists and the component is marked to never overwrite existing installations
MSI © (30:A0) [17:33:51:269]: Disallowing installation of component: C__955096E0A38844C48593C55DB06DB84A.9CD50E276F8D4F38BCF9A72F90323BAA since the registry keypath exists and the component is marked to never overwrite existing installations
MSI © (30:A0) [17:33:51:269]: Disallowing installation of component: C__99E42F83A77F499C863D4F59E3979545.9CD50E276F8D4F38BCF9A72F90323BAA since the registry keypath exists and the component is marked to never overwrite existing installations
MSI © (30:A0) [17:33:51:269]: Disallowing installation of component: C__A81618074DAF4C9C90AF6D0844D3C375.9CD50E276F8D4F38BCF9A72F90323BAA since the registry keypath exists and the component is marked to never overwrite existing installations
MSI © (30:A0) [17:33:51:269]: Disallowing installation of component: C__DB0B31F3F36141E08DF9DC8CFEA920F4.9CD50E276F8D4F38BCF9A72F90323BAA since the registry keypath exists and the component is marked to never overwrite existing installations


I tried this: http://blogs.msdn.com/astebner/archive/200…/01/446328.aspx

But there was no "return value 3" - only return value 1…

What else can I do to try and sort this issue out before trying another install?

Any help would be great.

Cheers

Hi Grumple… I only suggested a "permission" issue because of your comment about SYSTEM user having access to the registry. In fact, administrators should have access to most entries also, and the instructions I gave can correct that problem. However, I did research your problem some (probably something I should've done initially) and found that your installation problem has to do with two possible things, and so I need more detail. 1) You might have a 64-bit operating system installed, and need to use the 64-bit version of the software. 2) You are having a problem with the DVD drive reading the DVD installation disc, you are using the wrong disc, or you are trying to deploy over a network or from some other location. So, please tell me where the software has come from, if it is the original disc, and what procedure you are using to install the software.

Also, if you generated the verbose MSI log file that you read about in that link you provided, please attach that log to the forum for review. Do not copy and paste it. Only attach it please.

Hi Apple, Thanks for your help with this. I've poked it for ages today and have some more interesting bits to add. I have 2 programs behaving in different ways. I thought they must be experiencing the same problem (or similar) but I think I maye have 2 totally different problems! I totally uninstalled and cleaned up any remnants of both programs today. I logged in as admin on this machine only - installed program 1 - opened the program still as admin only on this machine and it is fine! However, I log in as me (on our network) and it acts as it did before - try to open and it just does nothing. So I logged in as another person (on our network) and it opens for them!!! ?! I have full admin rights on the Administrators group (which is higher than the other person I logged in as (debugger)) But at least it is working - just wish it'd work on my account : | The second program is the main issue. I have the full DVD etc So I tried another install today logged in on this machine only and as administrator - same problem. Just will not install. I tried using the wilogutl but I must have an old version because it won't read the log version 4.5 that the verbose lof creates (I say 'log' its more like 'logS' it makes about 8…) I will attach the logs that are made and hope they make some sense to you… Thanks again for your help, very much appreciated : ) (For some reason I am not permitted to upload this type of file… I'll go away and zip them and try again…)

When you say you log on to your network, you must mean a Windows domain? Are you using folder redirection policies? The problem on the first program is specific to your user profile. Therefore, it must be something in the registry or in the program's application data folder. You didn't mention what program that is. But, you need to probably navigate to your application data folder, find any folders related to that program and rename them with a .bak at the end of the name. When I say YOUR application data folder I mean the one contained in your user profile or where the folder is redirected to. This will effectively eliminate any previous settings that might be problematic. But, the problem still might be settings in the registry. That means you need to login with your user account, navigate to HKEY_CURRENT_USER, find anything related to that program and remove it. Usually that would be under the software key. You should make a backup of your registry before doing so.

These are the only ones I can attach - a couple are too big… No idea why there are loads…

Ok.. I'm really not seeing anything in those logs either. I see that you are installing several different components at once. It might help to do a "custom" install, and select only the max design software. For instance, documentation is also being installed. All of that is generating multiple log files and making it difficult. I look at the one log that appears to be for the max design program itself but I don't see anything hinting to what the problem is. Can you verify what version of Windows XP you are running, 32-bit or 64-bit? Secondly, try creating a folder on your desktop temporarily and copy the contents of the DVD to that folder. See if it is successful, and then run the setup program from within that folder rather than from the DVD.

Hi apple, I am on a 32-bit machine. I copied the DVD data to a folder and tried the install again. This time I selected just the program (good idea…) - But the same problem persists : ( I have some kind of log file called 'Max32Install' ini my temp folder (I did last time also) but it is too big for me to attach - the smallest it goes if I zip it is 430KB. JUST REALISED THE UPLOAD LIMIT HAS GONE UP!! File is attached! There is another MSI log file that is created at the same time as this which I have also attached. It still fails at the same point - the status bar says 'writing system registry values' Thanks again for your help

SOLVED!!! Found on an Autodesk forum - somewhere I had looked when all of this started. There is an option during the installation configuration to install the 'Satelite network rendering' capability… If you un-tick this option the install goes without a hitch! The satalite tick box also has a port number with it… Would this have something to do with .NET - which seems to be the cause of many of these 1603 errors ? Not sure if you can figure out WHY this option was causing the issue - but for now I'm just so relieved it is finally installed! Thanks for your help!