Sign in to follow this  
Nickie

Error 1603's after Paint.NET asked me to install an update

Recommended Posts

As stated in the title, I opened up paint.NET and it prompted me to update it so I did. It gave me this 1603 fatal error thing and now keeps doing it after attempts to install it again.

 

1. https://support.microsoft.com/en-us/help/17588/windows-fix-problems-that-block-programs-being-installed-or-removed This did not work. (It did not find anything paint.NET related on my PC) 

2. The sfc/ SCANNOW method did nothing either.

3. After the attempted install, it creates a paint.net folder with a "Staging" folder in it, with two files that when clicked just tell me to install it using an installer.

 

 

 

 

 

As a side note, I have kept two plugins I had (psd and alphamask dll files) in a folder called placeholder. Doubt these are actually doing anything but I thought I'd mention it. 

Share this post


Link to post
Share on other sites

Anyone? I see someone attempted to respond but I don't see the message now.

 

Another side note. Paint.NET was working perfectly fine on my system until I (attempted) to install that update that ended up not only breaking my current version but made me unable to reinstall it. Would installing an older version work? 

 

Edit: Installing Paint.NET v3.5.9 worked flawlessly. Maybe this new version is incompatible with my PC somehow. No versions above 3.5.11 work for some reason.

Edited by Nickie

Share this post


Link to post
Share on other sites
20 minutes ago, Nickie said:

No versions above 3.5.11 work for some reason.

 

What Windows version are you using?

Share this post


Link to post
Share on other sites
8 minutes ago, BoltBait said:

 

What Windows version are you using?

 

 

Windows 10. I was using paint.NET 4.0.5 (I believe, I don't remember exactly what version it was, but I know for a fact it was above 4.0.0) and it worked fine until the update.

 

I believe that 3.5.11 is a windows 7 version, but it works with the psd plugin and the alpha mask plugin so it would be exactly the same as the 4.0.0 versions and above except it looks slightly different.. 

 

 

Edited by Nickie

Share this post


Link to post
Share on other sites

Make sure ALL of your Windows Updates are applied.

 

Then, install the .NET v4.8 via this link: https://dotnet.microsoft.com/download/thank-you/net48

 

Once that's installed, make sure all of your Windows Updates are applied.

 

Then, try to install the latest Paint.NET again from this link: https://www.dotpdn.com/downloads/pdn.html (Upper right corner of screen)

Share this post


Link to post
Share on other sites
2 hours ago, BoltBait said:

Make sure ALL of your Windows Updates are applied.

 

Then, install the .NET v4.8 via this link: https://dotnet.microsoft.com/download/thank-you/net48

 

Once that's installed, make sure all of your Windows Updates are applied.

 

Then, try to install the latest Paint.NET again from this link: https://www.dotpdn.com/downloads/pdn.html (Upper right corner of screen)

 

Already have .NET v4.8. All of my Windows Updates are applied. And I have tried like ten times using that link. As of now, only paint.NET v3.5.11 works for me (and I'm using it currently for stuff). It really doesn't make sense to me though, this is such a strange bug. 

Edited by Nickie

Share this post


Link to post
Share on other sites

You've said that the removal tool didn't work. That used to be our go-to solution for the 1603 error during installation.

 

Prior to the removal tool, @toe_head2001 wrote an install logger to help diagnose this problem (no longer available).

 

Prior to that, a few users got the /createmsi trick to work  https://forums.getpaint.net/topic/30437-win7-error-1603-32-bit-msi-may-not-be-installed-on-64-bit-os/

 

Share this post


Link to post
Share on other sites
4 hours ago, Ego Eram Reputo said:

You've said that the removal tool didn't work. That used to be our go-to solution for the 1603 error during installation.

 

Prior to the removal tool, @toe_head2001 wrote an install logger to help diagnose this problem (no longer available).

 

Prior to that, a few users got the /createmsi trick to work  https://forums.getpaint.net/topic/30437-win7-error-1603-32-bit-msi-may-not-be-installed-on-64-bit-os/

 

 

I tried the /createmsi trick a few days ago, but it would always tell me this:

 

image.png.5310c0ca2e7854a974f52f3296fffab7.png

Share this post


Link to post
Share on other sites
19 minutes ago, Ego Eram Reputo said:

Try it with the latest version. If you're still messing around with 4.0.5 that might be your trouble right there.

 

Yeah, I did and that same message popped up.

 

image.png.3afdeeceae08abe2a5f07bbc56b4e8d4.png

 

 

However, in regards to that forum post you linked, I believe I have the same issue as him. Paint.NET keeps trying to install as x86 but my operating system is x64. 

 

Disregard the above. Also try to remember that before attempting to update paint.NET, a version above 4.0.0 ran perfectly fine. I believe it was the one right before 4.1.6. Also, one thing I have noticed is that it does this fatal error after a decently longer bit of time has passed with the install attempt. If I try to re-reinstall it directly after the first fail, it does it instantly. Leads me to believe it might be something on my PC that is affecting it. 

Edited by Nickie

Share this post


Link to post
Share on other sites

Before issuing DOS commands, you must CD to the directory where that file exists.

 

For example, if you put the paint.net.4.1.6.install.exe file on your desktop, open a CMD window and type:

 

cd %USERPROFILE%\Desktop

Share this post


Link to post
Share on other sites

Thank you for your help.

 

With a friend I was able to figure out that I wasn't supposed to run it from a CMD window, but from a Powershell window and type a completely different command:

 

PS C:\Users\USERPROFILE\Desktop> .\paint.net.4.1.6.install /createMsi did the trick. Installed 4.1.6 flawlessly with this.

 

The problem seemed to lie in an x86 attempting to install on a x64 bit machine. This could be a useful way to debug this in the future should anyone have this issue.

 

WINDOWS 10 exclusive bug probably, since Windows Powershell is not present on previous versions. 

Share this post


Link to post
Share on other sites

I'm glad to hear you got this working!

 

👍

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this