1603 Error when in Non-Default Location

[Dandy]

I've gotten the 1603 error several times in the past. The posted instructions don't work for me. What did work was using the default install instead of specifying a custom installation directory (D:\paint.net).

 

Don't be fooled: This is not a Windows problem. If it were a Windows problem - a corrupt system file or what have you - then the installation would fail regardless of where you install the product. Note also that Microsoft Fix It did nothing to fix the problem for me, nor did the ancient and forever-suggested link given by barbieq25 above.

 

A Symantec page gives a "non-exhaustive" list of conditions that can cause the error. Among other items on the list are:

• An Install Script custom action is prototyped incorrectly.
• The setup was corrupted after installation and, therefore, fails with this error during un-installation.

In other words, the error can happen in circumstances other than a corrupt Windows system. My own experience confirms this. If the nice folks here at Paint.NET try to insist that the problem is in your Windows installation, you have no reason to believe them. Press them to solve the real problem, whatever it is.

Edited September 20, 2013 by Dandy

[david.atwell]

Well, that's certainly an inflammatory way of saying things.  How 'bout if you try to help track down this problem you say Paint.NET is having, instead of just slinging arrows over the wall?  Tell us more about your problem, tell us when you encountered it, tell us what you have installed, that sort of thing.

 

Don't be fooled:  You are not being helpful.  How about you put on your big boy pants, take off the entitled troll face, and try that post again?

 

 

[...] If the nice folks here at Paint.NET try to insist that the problem is in your Windows installation, you have no reason to believe them.  [...]

 

Says the guy with one post.  Hilarious.

[Simon Brown]

I had this problem recently and sfc didn't find anything (FixIt didn't list PDN). Changing the install directory fixed it. This

Microsoft page lists some more possible causes, although I don't think any of them applied to me.

[Rick Brewster]

Dandy is clearly the expert here? O_o Smoke a bowl, chill out, be nice.

[Dandy]

Well, that's certainly an inflammatory way of saying things.  How 'bout if you try to help track down this problem you say Paint.NET is having, instead of just slinging arrows over the wall?  Tell us more about your problem, tell us when you encountered it, tell us what you have installed, that sort of thing.

 

Don't be fooled:  You are not being helpful.  How about you put on your big boy pants, take off the entitled troll face, and try that post again?

 

 

 

Says the guy with one post.  Hilarious.

 

Look at my post again. Note its observation that the link to the long-standing forum "solution" post didn't work for me - as it hasn't worked for others. Note also that it mentions a workaround (install to the default directory).

 

Then look at Simon Brown's post, just below yours. Note that, contrary to what you say about my "not being helpful", my post helped him to get past the 1603 error and finally get Paint.NET installed. That's one post, one person helped. I wonder what the general average is.

 

Your post, by contrast, contained 0% help, 100% sarcasm. So enough childish projection about "big boy pants" - how about addressing the points I raised instead? Can you say where the problem might be, given that the only change that Simon Brown and I made was to point at the default install directory? Doesn't that mean that Windows file corruption is a red herring? Is it possible that the install script may be "prototyped incorrectly", as the Symantec page says, in a way that is revealed by requesting a non-default install directory?

Edited September 20, 2013 by Dandy

[Simon Brown]

I fixed the problem before Dandy's post based on the Microsoft link (although I didn't post it). I don't think it's a problem with Paint.NET, but for anyone getting the error, it's worth trying a different install path.

[david.atwell]

Simon Brown has been a member for the better part of a decade, is a plugin author, and has had Paint.NET installed for the entire time.  You may also note that he, in fact, solved it himself, and even posted a link that refuted your conclusion that it was a Paint.NET problem.

 

After that, Rick Brewster (the sole developer on the project) posted.  He works at Microsoft, and I have a feeling has more experience with both Windows  and his own program than you do - especially to be able to track down a problem.

 

I'm sorry if you were offended by my post, but it certainly was meant to be more funny than offensive.  You took it exactly the wrong way.  I wanted to encourage you to be more forgiving and less arrogant, and you went the wrong way with that.

[Dandy]

Simon Brown has been a member for the better part of a decade, is a plugin author, and has had Paint.NET installed for the entire time.  You may also note that he, in fact, solved it himself, and even posted a link that refuted your conclusion that it was a Paint.NET problem.

 

After that, Rick Brewster (the sole developer on the project) posted.  He works at Microsoft, and I have a feeling has more experience with both Windows  and his own program than you do - especially to be able to track down a problem.

 

I'm sorry if you were offended by my post, but it certainly was meant to be more funny than offensive.  You took it exactly the wrong way.  I wanted to encourage you to be more forgiving and less arrogant, and you went the wrong way with that.

 

Simon Brown affirmed that my workaround was helpful. His link was to an abbreviated and also non-exhaustive list of possible causes that appear to be unrelated to my workaround.

 

Rick Brewster said "chill out", which may be in order, but has nothing to do with tracking down a problem in Paint.NET.

 

Your post contained "slinging arrows", "not being helpful", "big boy pants", "troll face", and "hilarious". I think you can see the offensiveness in that, especially when it's in a first response to a stranger. I encourage you to be more respectful and less arrogant. I hope you go the right way with that.

 

I also hope that my observations have been of use to the adults on the forum. There's something going on in the Paint.NET installer that doesn't have to do with Windows file corruption, services, and so on. Maybe a tracing capability would help.

Edited September 20, 2013 by Dandy

[david.atwell]

We've derailed this thread a bit.  I'll send you a PM.

 

As I should have said in my first post:  Welcome to the forum, and let us know if you find any clues to the problem you've identified.  Thanks!

[Dandy]

Thank you. I don't have any clues as to why the directory change works, only that it works. The directories have equal permissions, and I'm doing both installations under the same user ID. Obviously, there is also no change in Windows system files or services between them. So far as I know, there is no installation log that I can provide or look at myself. If one exists, please let me know where I can find it. I'll be happy to send it along.

Edited September 20, 2013 by Dandy

[Simon Brown]

Would it be possible to put the directory change solution in somewhere like the install trouble thread?

[david.atwell]

Would it be possible to put the directory change solution in somewhere like the install trouble thread?

 

Good call.  Added as #10a.

[Simon Brown]

I'm not sure if it's always with a non-default location. I had it installed to C:\Program Files\Paint.NET3 (not the default location, but still in Program Files) when it broke, and fixed it by installing to C:\Paint.NET. Then I changed it back, and it worked.

It could just be about installing it somewhere different to where it was previously (but further installs to the same location worked fine).

[david.atwell]

I feel like that is a bit complicated for a basic troubleshoot thread. Did I get the gist incorrect, though? That's my big worry, having not received this error before.

[Simon Brown]

I think it's worth trying even if Paint.NET is installed in the default location (maybe as a last resort).

[david.atwell]

Edited. I'm also going to break this tangent out to its own thread.