Windows 10 Needs a Better App Uninstaller, Users Claim
-
I along with others who have said this before. . .create a recovery point prior to installing a program/application. If the application is not to your liking you can then either delete it with whatever uninstaller you choose, or do a recovery, thus hopefully when you do the one of your choice everything will be the way it was prior to the install. And, yes I know it is a pain in the a** put it works. You could also save a copy of the register to an another location, and if necessary save it back to your windows folder. . .just some thoughts. . .:)
-
-
I along with others who have said this before. . .create a recovery point prior to installing a program/application. If the application is not to your liking you can then either delete it with whatever uninstaller you choose, or do a recovery, thus hopefully when you do the one of your choice everything will be the way it was prior to the install. And, yes I know it is a pain in the a** put it works. You could also save a copy of the register to an another location, and if necessary save it back to your windows folder. . .just some thoughts. . .:)
That can work too but only if you want to get rid of it immediately, few days later and you could loose other stuff changed by than.
-
![]()
The uninstall routines in Programs & Features use the install/uninstaller routines the application *developers* put together. It's the developer's job to make sure that his program both installs and uninstalls completely. For obvious reasons, there's no way that Microsoft can uninstall every nook & cranny of a 3rd-party program...because, of course, Microsoft didn't create the application, and of course Microsoft has no control or knowledge of where a 3rd-party program will put files and settings and other things when it installs.
It's no different with the Mac--except that most OS X users have no idea what is underneath the GUI they use and could care less frankly...it's really funny, the ignorance one encounters--I once had a conversation with an OS X user who believed that OS X didn't use any "drivers" for its hardware (unlike Windows, he thought)--simply because Apple hides them from view and easy manipulation, whereas Microsoft puts them front & center in Windows. It's a difference in philosophy: Microsoft credits Windows users with enough sense and knowledge to manipulate certain things (regardless of whether that may be true); the Apple view is that OS X users are too dumb to do simple things like install driver updates, so Apple buries them from view in the OS X GUI, and Apple hides hardware driver updates inside the general OS X updates the company releases for OS X. Primary source for OS X drivers is Apple; whereas with Windows the user can go directly to the manufacturer of his hardware and obtain the latest Windows drivers.
-
I along with others who have said this before. . .create a recovery point prior to installing a program/application. If the application is not to your liking you can then either delete it with whatever uninstaller you choose, or do a recovery, thus hopefully when you do the one of your choice everything will be the way it was prior to the install. And, yes I know it is a pain in the a** put it works. You could also save a copy of the register to an another location, and if necessary save it back to your windows folder. . .just some thoughts. . .:)
That can work too but only if you want to get rid of it immediately, few days later and you could loose other stuff changed by than.
What's your point Mike. . .Everything I pointed out works thus leaving you right where you started prior to the install. . .Clean. . .:)
-
-
![]()
I along with others who have said this before. . .create a recovery point prior to installing a program/application. If the application is not to your liking you can then either delete it with whatever uninstaller you choose, or do a recovery, thus hopefully when you do the one of your choice everything will be the way it was prior to the install. And, yes I know it is a pain in the a** put it works. You could also save a copy of the register to an another location, and if necessary save it back to your windows folder. . .just some thoughts. . .:)
That can work too but only if you want to get rid of it immediately, few days later and you could loose other stuff changed by than.
What's your point Mike. . .Everything I pointed out works thus leaving you right where you started prior to the install. . .Clean. . .:)
CountMike is referring to other software and windows updates you might install afterwards. I am not really sure a system restore really leaves it clean. I have noticed system restore leaves things behind it shouldn't. I don't use system restore much anymore. I use Free Macrium to restore.
-
A recovery point would be OK if you uninstall the program before any other changes are made to the OS. When it comes to uninstalling programs I want as much of the program removed as possible. It also bugs me when I see the exclamation mark in device manager. Maybe I'm a little OCD when it comes to my computer. :)
-
A recovery point would be OK if you uninstall the program before any other changes are made to the OS. When it comes to uninstalling programs I want as much of the program removed as possible. It also bugs me when I see the exclamation mark in device manager. Maybe I'm a little OCD when it comes to my computer. :)
Exactly. Also anything but green in device manager is no good.
-
Going off topic. When I installed the first build of Win 10 I spent hours tracking down drivers for my computer until I got rid of the 3 exclamation marks in device manager. The ones from HP wouldn't install because the installers didn't recognize the OS. When build 9926 was released I had to go through the whole process again. Not planning ahead I didn't save them. Now I have them saved to a external hard drive so I don't have to go through that again.
-
![]()
I along with others who have said this before. . .create a recovery point prior to installing a program/application. If the application is not to your liking you can then either delete it with whatever uninstaller you choose, or do a recovery, thus hopefully when you do the one of your choice everything will be the way it was prior to the install. And, yes I know it is a pain in the a** put it works. You could also save a copy of the register to an another location, and if necessary save it back to your windows folder. . .just some thoughts. . .:)
That can work too but only if you want to get rid of it immediately, few days later and you could loose other stuff changed by than.
What's your point Mike. . .Everything I pointed out works thus leaving you right where you started prior to the install. . .Clean. . .:)
CountMike is referring to other software and windows updates you might install afterwards. I am not really sure a system restore really leaves it clean. I have noticed system restore leaves things behind it shouldn't. I don't use system restore much anymore. I use Free Macrium to restore.
I know what he was referring to, however the point I made is regardless whether you install something now or later you do the same thing each and every time. And, as I said yes it is a pain in the a**, but if you do it you shouldn't have a problem. . .hopefully. . .:)
-
-
I don't see how that would work without a lot of extra work. I make a recovery point ,then install program A. A few windows updates later I make a recovery point and install program B. A few more Windows updates later I make a recovery point and install program C. A few more windows updates later I decide to uninstall program A and run the recovery point before installing program A. Wouldn't I be back to square 1 and have to start over again or am I missing something? 
Quote