Home Forums SharewareOnSale Deals Discussion WinUtilities Pro / Apr 13 2018

Viewing 16 post (of 16 total)
  • Author
    Posts
  • #10959607 Reply | Quote
    Gary
    Guest

    @Jan Neff-Sinclair;

    I am not endorsing this product, nor do I even consider it very useful for many, unless it were to be used on a system that it would not matter if the OS drive were about to be reformatted. Several modules of the program are available in other utilities, and most of those modules are merely the same options users already have that are provided by the Operating System, and they do not do any type of damage. Only those that can alter the registry is where the user could have problems.

    That said, your statement of warning about the software along with your job history suggesting it is superior to a “regular user” is not gelling well.

    You claim:

    >…. After it installed and rebooted my system, the system would not come up. When I did get it up, the network wouldn’t work. I had one problem after another and it took two hours to revive my computer. I used to be a network admin and tech support person, so if it took me that long to get my system working again, who knows how long it would take a regular user.

    >DO NOT INSTALL THIS SOFTWARE. IT WILL DAMAGE YOUR SYSTEM EVEN BEFORE YOU RUN IT!!!

    I hate to see any software be blamed without any justification, even if I do not think the software is very valuable myself. I’ve seen lots of good software also get blamed for all sorts of problems on user’s computers, all while many others had just the opposite experience, yet the blamer is predicting the same experience they had will happen to everyone. It just doesn’t make sense to blame some software for some arbitrary situation unless it comes with some believable justification.

    The Win Utilities software program cannot damage your system before you even run it. It can’t because it has not had the opportunity to do so UNTIL you run it. On the other hand, the install/setup program has been run, and could do some good things or some bad things to your system.

    If the setup/install were to be designed to do bad things, very soon, a lot of people would be raising total hell with the developer. In fact, the developer probably spends a considerable amount of time ensuring the install/setup is tested and works because their intent is to get the user to the point where they can run the Win Utilities program. Therefore, logic dictates that the install/setup program is not the problem if your system would not boot after the install. The problem has to be in the unique makeup of your computer before the software was installed. Otherwise, you would not be the only person experiencing the same problem. Most likely it was a situation in your computer that you were not aware of previously, and could have happened with probably any other software package that you were to install. I have experienced similar mysterious issues, all the while the user claiming that it had not happened before, and therefore must be the result of executing “the software” (whether it be an install or otherwise). But with a quick re-image, I have demonstrated that the problem happens repeatedly, but also with any other software. Each time, the problem was due to the condition of the OS before any of the mysterious happenings, not the execution of the software itself. Therefore, it is prudent to take precautions before installing any software.

    In fact, you might have considered installing this software with the hopes that it might resolve a problem you were already aware of or at least suspected.

    For many of the users, the software might not be of any great value because their system doesn’t have any serious issues. In your case, had you ever got the chance to run the program, it might have helped your system out. You should buy a blank hard drive, clone your system onto the new drive, then swap it in for your current drive, make a backup image of the OS, then try installing the Win Utilities software again. If the setup again crashes, restore from your image, and try installing a similar utility, repeat with another if the same problem happens. If they all have the same issue, it cannot be the individual installers. If (hopefully) you get any one to install successfully, make another separate image of the OS, then run the software. After it has “resolved” any issues it finds, re-boot and see how things work out. If they work for the better, then you benefited. If you are really ambitious, save another OS image, then try installing the Win Utilities onto that drive. If it succeeds this time, you might be less convinced that the installer was to blame for your earlier experience. Granted at this point, your system might be cleaned up, but at least you will have the WinUtilites as another tool to check things out.

    I wonder if during the days you were a network admin and tech support person, did you ever recommend that a user back up their OS or hard drive before installing a program? Did you recommend saving a system image, a system restore point, or even a bare-bones exported backup copy of the registry before installing any software? … And especially before any program that even hints that its intent is possibly to make changes to said registry? These are common practices that a “regular user” should know, unless they were tutored by a “tech support person” that never took those precautions to begin with themselves. Hopefully, the rest of us “regular user”s have not been taught to ignore common safety guidelines.

    It should not have taken two hours to revive your computer; it should have taken only a few minutes to restore from a backup, re-image your OS drive, do a System Restore provided by the Operating System, or even a Reboot to the “Last Known Good Configuration,” … that is unless as a “tech support person” you do not believe in those options as well.

    >who knows how long it would take a regular user.
    I do, and hopefully, now you do too.

    I am just glad you did not claim to be be anything higher up the technical chain than a “tech support person;” that would be far worse.

    Regardless of what you do (even if this were a bad-apple), you shouldn’t blame the Sharewareonsale.com website.

    I truly feel sorry as to what happened to your computer. It was bad enough that it happened at all. To admit it to the public should be embarrassing enough because it says that you clearly did not take standard common precautions to guard against such possibilities. To add on that it happened to a “tech support person” is priceless.

    At the rate you are going, you will probably end up doing something non-technical, like delivering pizza or similar.

Viewing 16 post (of 16 total)
Reply To: WinUtilities Pro / Apr 13 2018