Download ESET's Service Repair http://kb.eset.com/l...vicesRepair.exe and Save it then right click on it and Run As Admin.
OK I have done everything that you told me. The Security Center and Firewall problem are now fixed as well as the Windows .NET framework update problem. This was all fixed by tweaking.com all-in-one Windows repair.
MSE uninstall was a breeze with Revo Uninstaller. I have downloaded and installed Avast and will run the scan as you instructed overnight tonight.
HOWEVER, I think it is important to let you know that the Avast installer FORCED a Google Toolbar install on me as it was installing the program. There was no way to stop it nor did it ask me before it did it. It just said "Now installing Google Toolbar, please wait. This may take a while" . While it was installing it, the "cancel' button on the installer was made inactive.
I personally think that this is a bad thing for a security software company to force a toolbar on you upon installation of it's security program. But I will use it as you suggested for the purposes of fixing my problem. Just thought I would forewarn you about this since many PC security professionals consider the Google toolbar a form of malware/spyware. Avast needs to rethink this.
Will post my Avast log tomorrow.
The Computer Browser service terminated with the following error: The specified service does not exist as an installed service.
The helpsvc service failed to start due to the following error: The system cannot find the file specified.
Fax Service failed to initialize any assigned fax devices (virtual or TAPI). No faxes can be sent or received until a fax device is installed.
Edited by LVAD, 04 October 2013 - 03:04 AM.
Start, All Programs, Accessories, Command Prompt to bring up a Command Window. Right click and Paste (or Edit then Paste) and the copied lines will appear. Hit Enter. Did you get an error? If not that should correct the errors shown in VEW.
That should be all unless you need some help getting rid of Google Toolbar. It should be running OK now. Is it?
The registration is good for 12-14 months then you will need to register again. They will, of course, try to talk you into buying the product but you can always register again for another year free tho it won't be the default option.
If you use Firefox or Chome then get the AdBlock Plus Add-on.
"'SC' is not recognized as an internal or external command, operable program or batch file."
Also, how about the problems Avast found in the log I posted above? Do these not need addressed?
Edited by LVAD, 04 October 2013 - 06:36 PM.
Avast moved all of the infected items to its Chest which is a quarantine thing so they are no longer a danger. If you click on the Avast ball, Maintenance, Virus Chest you can then delete them if you want to.
If you want to delete it yourself you can. It's not going to hurt anything it's just unusable.
OK, had to do it manually in services.msc. SC.exe does exist in my System32 folder as you stated, but it simply will not work in my command prompt as you initially instructed.
About my router, security is set to WPA2-PSK [AES], is this what you mean by "encryption"?
Which one should I be using in your opinion?
WPA2-PSK [AES] is the correct encryption to use.
When my PC goes into hibernation mode, after I bring it out of hibernation, I get a balloon popup in my system tray that alerts me that my internet connection had has either limited connectivity or is completely unavailable. Using the "repair" function does not restore the connection to normal because the repair fails and states that the reason for the fail is that a new IP address could not be established. The only simple way I found to restore the connection is to go into "network connections, disable the connection and then enable it again. While it is an easy and simple solution, it is an annoyance that it happens and to have to reestablish the connection.
It is important to note that this only happens when I bring my PC out of hibernation mode. It does not happen if I reboot my PC.
Right click on My Computer and select Manage then Device Manager. Find the Network Adapters and click on the + in front. Find the adapter you are using to connect and right click on it and select Properties. There should be a Power Management tab, click on it. Usually there is a box to check/uncheck that says Allow the Computer to turn off this device to save Power. Usually this is checked by default. Try unchecking it - if it is checked then try unchecking then OK and reboot. Does it still not connect after Hibernate? Make sure you have the latest driver for the network adapter that is giving you a problem. There is a known problem with Intel 82579V Gigabit Ethernet PHY Network which causes it to not connect after Hibernate.
OK, everything seems to be now. If there are still issues with this connectivity problem, I will open a thread in another forum.
I think this thread can be marked as "solved".