Sign in to follow this  
NETdoinganythingwrong

Paint.NET refusing to install on Windows 10 due to .NET already existing

Recommended Posts

Hi, I just upgraded from Windows 7 to Windows 10 (both x64) and now Paint.NET refuses to install because .NET 4.7.1 is already on the computer.

 

I tried installing an older version in the process of reinstalling everything I use before getting to Paint.NET and it also understandably refused to install as a newer version was already on the PC, however with Paint.NET the installation shuts down abruptly without giving me any type of error or message, it just refuses to continue as it can't install .NET.

 

Any help please? I've been using this software for years and it's been dead reliable and practical for pretty much anything.

 

Thank you!

  • Like 1

Share this post


Link to post
Share on other sites

Have you installed all Windows Updates yet? If you've done a "fresh" Windows 10 install or upgrade then you might not be on the latest "big" update.

 

If this is the case, then going to Windows Update and installing everything, rebooting, and then repeating until the well is dry ... and theninstalling Paint.NET, will fix things.

 

https://blog.getpaint.net/2017/10/23/paint-net-4-0-20-and-net-4-7/

 

I'm planning on making this clearer in subsequent updates. Not just "oops failed" but more like "hey you need Windows 10 v1607 or newer, go get your Windows Updates installed".

Share this post


Link to post
Share on other sites

Glad it's working now :D

 

Can't do that. Paint.NET requires .NET to install. That setup UI is written using .NET. You can't install something without the dependency.

 

Also, I'm not going to spend a lot of time to engineer something that is only useful occasionally by someone who hasn't installed their updates. Just install your updates! The solution here is just a better way of communicating this to the user so they don't have to scratch their head and wander on to the forum for a solution.

Share this post


Link to post
Share on other sites

I'm sorry, I didn't know that was the case or that it would be difficult to engineer such an option. I don't know anything about programming and presumed it would've just required a toggle switch to not install .NET so I could install it separately beforehand.

 

Thanks for your time!

Share this post


Link to post
Share on other sites

Nah. The setup UI uses .NET, therefore .NET has to be installed before even the setup UI can execute. Installing .NET beforehand isn't just convention, it's legitimately required.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this