Sign in to follow this  
Followers 0
toki

fatal installation error 1603 Fix

52 posts in this topic

I had the fatal error during installation 1603 I tried all the fixes in this thread and a lot of others:

but nothing worked! after a month or so i solved the problem as it turns out my TrustedInstaller.exe which is a windows service was corrupted

I had a tough time getting a copy,The reason why u cant find a download anywhere on the internet, is because it isn't a program its a windows service luckily a friend of mine had 64bit and 32bit computers i extracted the trustedInstaller and uploaded it with a set of instructions i wrote to help people fix this !

Download the copy of TrustedInstaller.exe+instructions here:only download If corrupted

http://www.mediafire.com/?1mnyzmmzfqd

after all this i finally had everything in place and working so i downloaded paint.net tried to install and what do i see! a new error!

error 1601 i went crazy XD but thankfully i found a quick fix to the problem using the vista fix from this article:

http://www.ehow.com/how_5325924_fix-windows-installer-error.html

After i used the fix i tried to re-install paint.net and it was successful!!

I posted this so i could help future people who may encounter this horrid problem

Edited by toki
0

Share this post


Link to post
Share on other sites

Pinned. Hopefully it helps others as well. Unfortunately, there are numerous causes for a 1603 error, and I doubt this will fix them all.

0

Share this post


Link to post
Share on other sites

Well this is certainly good news. Thanks!

I must advise against installing system files from an untrusted* (or at least unofficial) source. However since I don't have an alternative solution, it's certainly worth keeping this around.

The next time someone runs into this, I recommend that we ask them to run a little utility that comes with Windows called "SFC" (System File Checker). You can run it from an elevated command prompt (cmd.exe).

C:\Windows\system32>sfc

Microsoft (R) Windows (R) Resource Checker Version 6.0
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

Scans the integrity of all protected system files and replaces incorrect versions with
correct Microsoft versions.

SFC [/sCANNOW] [/VERIFYONLY] [/sCANFILE=<file>] [/VERIFYFILE=<file>]
[/OFFWINDIR=<offline windows directory> /OFFBOOTDIR=<offline boot directory>]

/SCANNOW 	Scans integrity of all protected system files and repairs files with problems when possible.
/VERIFYONLY 	Scans integrity of all protected system files. No repair operation is performed.
/SCANFILE 	Scans integrity of the referenced file, repairs file if problems are identified. Specify full path <file>
/VERIFYFILE 	Verifies the integrity of the file with full path <file>. No repair operation is performed.
/OFFBOOTDIR 	For offline repair specify the location of the offline boot directory
/OFFWINDIR 	For offline repair specify the location of the offline windows directory

e.g.

	sfc /SCANNOW
	sfc /VERIFYFILE=c:\windows\system32\kernel32.dll
	sfc /SCANFILE=d:\windows\system32\kernel32.dll /OFFBOOTDIR=d:\ /OFFWINDIR=d:\windows
	sfc /VERIFYONLY

* This isn't to say "I don't trust you." I'm using the word trust in the technical, not emotional, sense.

0

Share this post


Link to post
Share on other sites

It should be noted that it is possible to get this error if you try to install Paint.NET after updating windows and postponing restarting. This had happened to me and I wasted 2 hours trying to get it to work.

0

Share this post


Link to post
Share on other sites

FYI, I will be doing the "fix" thing, but want to know why. Am just curious as to why it is broken for paint.net and not anything else that I have downloaded. Have had Windows 7 since end of March and am installing anything *except this* as wanted/needed. So why this?

Thank you!

0

Share this post


Link to post
Share on other sites

Canna, I don't know why this 1603 error happens for some people. I have uninstalled, installed, and updated Paint.NET thousands of times and never had this problem.

However, for this specific fix, the problem has nothing to do with Paint.NET. A system file became corrupt and there are ways to fix it (I recommend using SFC, and not downloading a random version from some website). Paint.NET cannot be blamed for that.

0

Share this post


Link to post
Share on other sites

The 1603 error problem occurred for me when updating to version 3.5.5 from 3.5.4. I then reinstalled 3.5.4 with no problem . Perhaps 3.5.5. expects to find something that 3.5.4 does not?

best wishes,

Chris Stoddart

0

Share this post


Link to post
Share on other sites

The new requirements are:

XP - Service Pack 3

Vista - Service Pack 1

0

Share this post


Link to post
Share on other sites

Canna, I don't know why this 1603 error happens for some people. I have uninstalled, installed, and updated Paint.NET thousands of times and never had this problem.

However, for this specific fix, the problem has nothing to do with Paint.NET. A system file became corrupt and there are ways to fix it (I recommend using SFC, and not downloading a random version from some website). Paint.NET cannot be blamed for that.

For me this was not true. It had nothing to do with the system but obviously with some paint.net registry values.

The problem occured for me when I installed Paint.net v.3.5.5 on a drive other than my System drive (Windows 7). I had some problems with my Vista boot which was on that partition and long story's short, the program data of paint.net(and some other programs I installed under Windows 7) got corrupted.

I was forced to uninstall all the programs on this partition and for most this was no problem. The uninstaller of Bad Company 2, Skype, VLC worked with no problem but I was unable to uninstall Paint.net (stated that a program needed for uninstallation is not running properly) neither could I install it over the old installation due to this 1603 error.

I tried SFC.exe which found no errors in my system (no wonder the installation is brand new), I cleand the registry with CCleaner and removed all files from the trash.. Nothing helped.

Now I finally was able to install it properly, this is what I did:

1. Uninstall the Program via Add/Remove Programs (it won't work but remove the program from the list)

2. Use Ccleaner to clean your registry

3. Move to "C:\Users\MyUsername\AppData(Hidden)\Local\Temp" and delete everything in it

4. Open CMD:Regedt32

5. Search for "Paint.net" and delete all entries for paint.net (you can leave those associated with filetypes like png, or jpeg). You will find some references for temp-files, dll's, exe's and a cryptic Windows installer folder consisting only of numbers and letters.

Then run the installation and it should succeed..

However, as always there's no guarantee this will work and you could seriously damage your system if you mess with the registry...

But I think the problem lies within the temporary files, or references to those, which cannot be overwritten or something.. I believe that the PdN installer messes something up..

Could be the reg keys:

[HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Compatibility Assistant\Persisted]

"C:\\Users\\USER\\AppData\\Local\\Temp\\Temp1_Paint.NET.3.5.5.Install.zip\\Paint.NET.3.5.5.Install.exe"=dword:00000001

[...]

"D:\\Programme Win7\\Staging\\Paint.NET.3.5.5.Install.exe"=dword:00000001

Or a bunch of keys looked similar to this ones(tons of file references which are, of course, no longer existing once they are deleted)

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Assemblies\D:|Programme Win7|Paint.net|ICSharpCode.SharpZipLib.dll]

Long story's short: I'm glad I could fix everything and it is working as intended now..

0

Share this post


Link to post
Share on other sites

Deleting registry keys all over the place is a VERY BAD IDEA.

If you didn't try the Windows Installer Cleanup program, then you should have. Otherwise you are just randomly hitting your computer with a hammer until it works again. The collateral damage could be significant.

0

Share this post


Link to post
Share on other sites

Yeah it could seriously damage my computer if I would delete the reg keys randomly.. But I'm not "hiting it randomly with a hammer"..

Enlight me: What can go wrong if I delete Reg-Keys of a program which is not installed on my computer and is not working properly anyway?

Sometimes you have to use brute-force.. Windows Install Cleanup does basically the same thing. It just removes the installer references - as did I..

Install CleanUp is a good idea anyway..

Edited by RavenTheJust
0

Share this post


Link to post
Share on other sites

Can anyone tell me where I can download the Windows Installer Cleanup Utility? I have searched the internet and cannot find it. It seems that Microsoft no longer distributes the utility. I have tried every other fix I have found for this error 1603 and nothing is working. I am completely lost without my Paint.net.

0

Share this post


Link to post
Share on other sites

I ran the sfc with the scannow promt. It said that some files were corrupt and it was unable to fix all of them. I tried to install the program again, and I still got the 1603 error. I don't know my way around the computer very well, but I really want my paint.net back. I still got the error while trying to install an older version as well. :( I don't want to mess around with the computer too much since I don't really know what I am doing.

0

Share this post


Link to post
Share on other sites

Sometimes sfc /scannow needs to be run 3 to 4 times in succession.

It might fix only one thing per scan, so repeating the scan may fix more things.

0

Share this post


Link to post
Share on other sites

There are 4 errors all for tcpmon.ini. It says "Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch" From what I have read, SFC will be unable to repair these itself. Could this be what is causing my issue with paint.net or is it something else?

Edited by janderson
0

Share this post


Link to post
Share on other sites

Finally figured it out on my own. I disabled my UAC (user account controls) temporarily and my spyware doctor. Don't know which was the issue, but problem solved! Don't know what my SFC scan errors are about, but oh well. Just thought I would post this simple solution for other people to try. :)

0

Share this post


Link to post
Share on other sites

Finally figured it out on my own. I disabled my UAC (user account controls) temporarily and my spyware doctor. Don't know which was the issue, but problem solved! Don't know what my SFC scan errors are about, but oh well. Just thought I would post this simple solution for other people to try. :)

Janderson, thanks for the tip.

I use AVG Anti-Virus Free Ed 2011 and the installation worked after disabling its "Identity Protection" component.

0

Share this post


Link to post
Share on other sites

I've tried toki's, raven's, and brewster's solutions and I still get the 1603 error. I've had this problem since last weekend when I uninstalled 3.5.4 to install 3.5.6. I've even googled for generic 1603 errors and tried other solutions to no avail. What's worse is I get this error when I try reinstalling 3.5.4.

0

Share this post


Link to post
Share on other sites

For future reference, you don't need to uninstall to update Paint.Net. Just run the installer and it will do all the clever bits for you.

0

Share this post


Link to post
Share on other sites

Hey guys :),

I would just like to report a successful resolution of the 1603 issue. Rick is right, the issue has different ways of fixing it and you can't apply one fix to all errors.

If you cannot find the pdnmsiinstall.log in the temp folder (start->run-> Type "%temp%" (without quotes)) then :

Enable logging for the MSI Installer. In the Registry editor navigate to:

HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer

Add a new string called Logging and make the value "voicewarmup".

Try the installation once again. Once it fails, go start->run-> Type "%temp%" (without quotes), press enter and find PdnMsiInstall.log. Open it up and see what is happening. Also PdnSetupNgenInstall.log will tell you what is happening, but it's a bit more verbose.

For my issue I found out that it wasn't able to automatically uninstall the previous installation (it was giving a 1721 error in the log file). My solution was to re-register msi installer by going Start->run->cmd->msiexec /unregister->msiexec /regserver->exit. Then to uninstall the previous installation of PDN from add/remove programs. Then install.

Also, I would like to reiterate what Rick said that deleting registry settings without knowing what they do is a big no-no, even though they maybe attached to one particular programme, they may have other programmes or shell classes that are dependent on those values.

Hope this helps

Edit

================

Corrected msiexec /regserver command

Edited by jpnboy
0

Share this post


Link to post
Share on other sites

Go start->run-> Type "%temp%" (without quotes), press enter and find PdnMsiInstall.log. Open it up and see what is happening. Also PdnSetupNgenInstall.log will tell you what is happening, but it's a bit more verbose.

Well I think that's been the most help so far. Although I don't have the same problem, at least I have something that tells me a little more about why it's not installing. I don't have PdnSetupNgenInstall.log, which might be because Pdn never made it that far into the install.

PdnMsiInstall.log says this:

=== Logging started: 12/5/2010 17:30:49 ===

Error 1935. An error occurred during the installation of assembly 'Microsoft.VC90.CRT,version="9.0.30729.4148",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="amd64",type="win32"'. Please refer to Help and Support for more information. HRESULT: 0x80070003. assembly interface: IAssemblyCache, function: CreateAssemblyCacheItem, component: {3FA0170E-227C-37C7-BAC0-64691A992C81}

=== Logging stopped: 12/5/2010 17:31:12 ===

I think the problem is that 1, I have Intel not AMD, and 2, I have Vista 64-bit not 32-bit (I'm assuming that's what win32 means anyways). I'm going to try reregistering the msi installer anyway though and see if that fixes this error. I'll report back soon.

Edit: Same error number, but slightly different data return (although it still claims I have an AMD processor and win32).

=== Logging started: 12/6/2010 22:33:38 ===

Error 1935. An error occurred during the installation of assembly 'Microsoft.VC90.OpenMP,version="9.0.30729.4148",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="amd64",type="win32"'. Please refer to Help and Support for more information. HRESULT: 0x80070003. assembly interface: IAssemblyCache, function: CreateAssemblyCacheItem, component: {A4B2FE85-8F48-3997-B1FD-EE92A70018C7}

=== Logging stopped: 12/6/2010 22:34:11 ===

Now lets see what google has to say about 1935 errors...

Edited by Amauros
0

Share this post


Link to post
Share on other sites

Hey Amauros,

Essentially this error (HRESULT: 0x80070003) means that it cannot find the specified folder. Make sure that the previous installation of PDN is uninstalled using the Add/Remove programs and delete any temp files from the %temp% directory relating to pdn. Also another idea, just be sure that you install it by right clicking and going install as administrator.

0

Share this post


Link to post
Share on other sites

What specified folder? I've done all those things to no avail.

Edited by Amauros
0

Share this post


Link to post
Share on other sites

It's either the temp folder for the installation or the installation folder. In any case, if you did the stuff I said and it didn't work, then we need more info. Can you post your PdnSetupNgenInstall.log and PdnSetupShim.log

0

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.
Sign in to follow this  
Followers 0