Msconfig

Note the proper fix is not putting msconfig.exe into the system32 folder. Yes it will run, but this is not what you should be doing. It does not belong there and will be immediately question by anyone ever looking at malware type logs. The proper fix is to repair the registry key that points to it. The below is the fix for this. This registry key was mentioned in msg # 1 but that did not give you the fix. By default on all systems, the below should be setup. Note the below does assume the you have Windows installed on the C drive and that your Windows installation folder is named Windows If they are not, then change the registry patch to suit your installation. Also the fix assumes you have the file located properly which should be: C:\WINDOWS\PCHealth\helpctr\\Binaries\MSCONFIG.EXE

Copy the bold text below to notepad. Save it as fixME.reg to your desktop. Be sure the "Save as" type is set to "all files" Once you have saved it double click it and allow it to merge with the registry.

Make sure that you tell me if you receive a success message about adding the above
to the registry. If you do not get a success message, it definitely did not work.

 

As sach2 stated, you must make sure it is saved properly. The file has to be saved with a .reg extension and if you are not showing file extensions on your PC (which is a Windows default) you would not notice that the file may actually be named fixME.reg.txt instead of fixME.reg

 

Just download this MGtools.exe to C:\MGtools.exe. Then double click MGtools.exe to run it. It will fix the MSconfig appaths key automatically. Let it finish running. It will tell you when it is finished in the command prompt window. When finished it will create a file named C:\MGlogs.zip which will have some log file in it that we can check for a variety of things including whether the registry key has been fixed. Also it will tell me if your file association for registry files has been changed.

You can also test to see if you can run MSconfig.exe normally without having it in the system32 folder. If it does not run, you can attach the C:\MGlogs.zip file to your next message so I can check it out.

 

Yes because as I suspected, you have associated reg files with notepad. I will give you a fix below. You other issue with MSconfig Apppath has been fixed. I have noticed that you are using MSconfig to control startup. This is a very bad practice that even Microsoft does not recommed. Your PC should be booting in Normal Startup mode. Selective Startup (which you are using) should only be used for temporary debugging. You should read this: Dealing with Startup Processes


Now for your reg file association fix:

Now Copy the bold text below to notepad. Save it as RegFix.reg to your desktop. Be sure the "Save as" type is set to "all files". Then Click Start, Run, and enter regedit and click OK. This will open the Registry Editor.

In the Registry Editor click File and Import. Navigate to the RegFix.reg patch you saved on your Desktop and double click on it. Click OK at the prompt to add to the registry. Do you get a success message for this?

 

Since I have your logs, I also noticed you need to do the below.


Uninstall the below software:
J2SE Runtime Environment 5.0 Update 10
J2SE Runtime Environment 5.0 Update 6
Java(TM) 6 Update 2
Java(TM) 6 Update 3
Spybot - Search & Destroy 1.5.2.20
Viewpoint Media Player <-- should have been uninstalled in step 1 of the READ ME
Now reboot your PC and after reboot, now install the current version of Sun Java from: Sun Java Runtime Environment

 

Yes everything inside the quote box. REGEDIT4 needs to be the first line in the file. No blank lines can be above it.

 

Okay now just as a test, double click on the original fixME.reg patch and see if it now asks you about adding to the registry rather than opening up notepad.

 

You can say yes or you can say no since it was already fixed by running MGtools.

Did you delete the msconfig.exe file from the system32 folder? If not, you should do that and then test to make sure you can run msconfig normally.