Chocky

You are wrong. So, don't mess with registry. I bet only "registry-messing" paint.net doing is creating its setting branch, adding itself to uninstall list and file association. Any of these "messing" are not serious enough to use restoration points. Most pathetic argument. There are no need to be a cook to know that a dish is foul.

Unfortunately, this developer understands only this kind of language. When he was asked nicely this moron just wrote: viewtopic.php?f=12&t=32924 and immediately closed thread. Looks like this guy is very interested in reasonable discussion. Maybe if my reasoning will be expressed in these words, I'll got his attention. Excellent advise! I'll translate this to human language: So, you guys can kiss his < no swearing > as long as you want, but this won't make stupid decision any smarter.

You'll be surprised, but this OS feature is for a system restoration in case of some deeply integrated software such as windows update, antivirus, firewall, service or driver will fall and make whole system disabled. This is not for every 2cents utility. This is a last chance measure, not for everyday use, it even can delete any file, created on a system disk after restore points, if system can't be restored with a restore point, reinstallation is the only way. Checked now, my 1TB system drive contains only two restore points and one of them created today with paint.net installation. Oldest available restore point created two days ago. What if I'll find that some of windows update, installed for example, a week ago, have broken, for example, printing? I won't be able to restore system because one dumb developer likes to create restore points on every opportunity. Stop this. Paint.net doesn't deserves this honor, at least until it'll start to install a couple of drivers.