Jump to content
CCleaner Community Forums

Website: Tweaking.com

Recommended Posts

I hate services running automatic just because they are there.


My old Laptop started up much faster and ran much sweeter when I used BlackViper and disabled or set to manual perhaps 50% of all "automatic" services.


When I used Acronis image backups the installation set many of its executables as "Automatic" services.

I switched them to MANUAL/DEMAND and whatever was needed was activated by Acronis when the Acronis Application was launched.


My preference would be an option for an aggressive reduction of Automatic running services,

plus a "repair" option to make Automatic those services that may be required.


The "repair" option could undo any harm,

regardless of whether that harm was done with your Tweaking tool,

or self inflicted harm by an amateur that independently "improved" her/his PC after a suggestion from a friend/forum.

Link to post
Share on other sites

So setting it to auto would fix those users who disabled it and didnt realize it or for users who have software that need it to auto.


The goal is to repair not tweak. So after words a user can go a tweak their services again if need be.


So by setting it to auto in the repair it will fix those 2 types of people :-)


Auto it is.



Link to post
Share on other sites
  • 3 weeks later...

I have a question for both Win 7 and Vista users. Does there exist a file called ""WBEMUPGD.DLL" in both Operating Systems ? And in which folder is that file located ?


To find that file one should/can use a program called ""Everything"" from ""voidtools"".


Link to post
Share on other sites

Thanks, Hazelnut.


The file is used in Windows Repair. Since I use XP I know it's present in XP but don't know whether it's in Win 7 and Vista as well. I checked on a friend's computer (win 7) and didn't find it. I thought it was removed but it looks like it's quite normal to be missing in Win 7. But I would like to know if this file can be found in Vista as well. It should be in ""%systemroot%\syswow64\wbem"" in Vista.


I tested the *.bat batch files, used in Windows Repair, (Tweaking.com) and came across a number of issues/flaws. And this was one of them.

Link to post
Share on other sites

I tested the *.bat batch files, used in Windows Repair, (Tweaking.com) and came across a number of issues/flaws. And this was one of them.


This isnt a flaw bud. The repairs are all in one bat files. These are safe to have in there. If they are not on the system the regsrv32.exe just says its not there and moves on. Thats why you see the syswow64 in there as well. They are ment to be ran on any version of windows. Since it was safe to do it this way instead of braking the regsvr32.exe commands apart for 32 & 64 bit then for each version of windows. Would have been a nightmare. :-)



Link to post
Share on other sites

Tweaking.com has a new program out: Advanced System Tweaker. Readers of this thread are encouraged to download it and test the program. Post your comments on the Tweaking.com forum website.

Link to post
Share on other sites
  • 5 months later...

Here's another shameless plug for the website Tweaking.com. There's a new program out, called Registry Backup. Out of Beta and already in version v1.2.1.



Post comments for this program on the Tweaking.com website and NOT here.

Edited by Willy2
Link to post
Share on other sites
  • 3 months later...
  • Moderators

the link is the site this thread is about ;)

the facebook post Wiley points to I think is

I will be making a new tool for the tweaking.com site.

I run a computer repair business and over the last week I have had multiple business customers who use Windows remote desktop being brute force attacked by bots. The bots or hackers (So far from Russia, china, the US and Canada, I think they are simply infected machines) have been trying to brute force hack the administrator password on the well known port 3389 of the remote desktop.


I first noticed this when I found in the event viewer hundreds of fail login attempts. But the way they where trying to connect the event viewer didn't tell me what IP they where connecting from. So I found what IP they where connecting from by loading up my old program cs fire monitor, which has a netstat option in it to let me quickly see all the connections on the system. And sure enough I found the IP trying to hack in on port 3389. I then used the ip sec security to block those IPs on the machine itself.


So I thought to myself, since this seems to be a problem right now I think I will make a program that will both log the IPs and monitor port 3389 (Or what ever single port the user wants) on the system so I can see who and when people are trying to hit the remote desktop. When they do I can block their IP.


So I am going to make this program and use it on my customers machines but I also plan on putting it on the site for others to use as well. This way my fellow techs or anyone who has remote desktop open to the net can at least keep an eye on anyone trying to get in through the remote desktop.


I just need to know what to call it lol All my tweaking.com sites start with "Tweaking.com - " Any ideas on what I should call this little tool?


This tool isn't for everyone, it will be for people who are techs or know what remote desktop is all about and such. But I think it will be useful, well at least it will be useful for me lol. I will make sure to include info on how to block the IPs and how to use the tool of course.


So tell me what you think and what a good name might be.




5 days ago on Oct 19th 2012 I posted that I will be making a new program to monitor the remote desktop port on a system and log and block ip's because some of my customers have been hit by bots trying to brute force the administrator password.


Well here is the first look at it, not bad for a few days work I think. You will see it has a tray icon and a few options. It is going to be simple and to the point of what I need it to do. Oh and of course this will be yet another free program for the site :-)


All that is left to get done is the saving the log to a file and getting the code done to block the IP's. I am working hard to get this out as soon as possible because I will be using it on a few of my customers servers to keep an eye on these hacking attempts.


So now the point of the post. How does it look so far? :-D


image can't be reproduced at this time

Link to post
Share on other sites
  • 1 month later...

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
  • Create New...