Trojan.Gen, still there...I think

Backed so soon?

Your Hitman log is only that large because you have not emptied all the junk in your Norton Quarantine folder.

Uninstall the below very old versions of software:
Java(TM) 6 Update 13

Please download OTM by Old Timer and save it to your Desktop.

• Run it by double clicking on it (Note: if using Vista, Win7, or Win8, don't double click, use right click and select Run As Administrator).
• Copy the lines from the below codebox to the clipboard by highlighting ALL of them and pressing CTRL + C
  (or, after highlighting, right-click and choose Copy): Do not include the word Code: which is just a title line of
  the code box

Code:

:Processes
explorer.exe
 
:Files
C:\Documents and Settings\Michelle\Local Settings\Application Data\Dell\gdfnxyjg.dll
C:\RECYCLER\S-1-5-21-3718337389-2549028977-250921185-2186\$0ceb964bc0e49d36c5d8e33f04456f27\@
C:\RECYCLER\S-1-5-21-3718337389-2549028977-250921185-2186\$0ceb964bc0e49d36c5d8e33f04456f27\U
C:\RECYCLER\S-1-5-21-3718337389-2549028977-250921185-2186\$0ceb964bc0e49d36c5d8e33f04456f27\L
C:\RECYCLER\S-1-5-21-3718337389-2549028977-250921185-2186\$0ceb964bc0e49d36c5d8e33f04456f27
C:\Documents and Settings\administrator.RJM\Local Settings\Application Data\ApplicationHistory\ProcessDll.exe.cd116cf9.ini
C:\Documents and Settings\All Users\Application Data\cd52ufX.dat
C:\Documents and Settings\All Users\Application Data\VGsPX3k7.exe.b
C:\Documents and Settings\All Users\Application Data\VGsPX3k7.exe_.b
C:\WINDOWS\Temp\*.*
C:\Documents and Settings\administrator.RJM\Local Settings\Temp\*.*
:Commands
[purity]
[EmptyTemp]
[start explorer]
[Reboot]

• Return to OTM, right click in the Paste List of Files/Folders to Move window (under the yellow bar
  ) and choose Paste.
• Now click the large http://forums.majorgeeks.com/chaslang/images/MoveIt!.png button.
• If OTM asks to reboot your computer, allow it to do so. The report should appear in Notepad after the reboot.
• Close OTM.

Now navigate to the C:\_OTM\MovedFiles folder ( assuming your Windows drive is C). This is where your log will be
saved in the form of Date and Time mmddyyyy_hhmmss.log. Just look for the most recent .log file. Attach
this log file to your next message.


Now run the C:\MGtools\GetLogs.bat file by double clicking on it (Note: if using Vista or Win7, don't double click, use right click and select Run As Administrator).

Then attach the below logs:

• the C:\_OTM\MovedFiles log
• C:\MGlogs.zip

Make sure you tell me how things are working now!

 

You forgot to tell me how things are working. But before answering that, first please run the below.

Be patient while doing the below. The fixes can sometimes take quite awhile to run. Especially the permissions repairs. It may be best to kick it off and goto bed or do something else. It is better not to run anything while the repairs are going on.


Download Windows Repair by Tweaking.com and unzip the contents into a newly created folder on your desktop.

• Now run Repair_Windows.exe by double clicking on it ( if you are running Vista or Win 7, use right click and select Run As Administrator)
• Now select the Start Repairs tab.
• The click the Start button.
• Create a System Restore point if prompted.
• On the next screen, click the Unselect All button to first deselect all repairs.
• Now select the following repair options:
  • Reset Registry Permissions
  • Reset File Permissions
  • Register System Files
  • Repair WMI
  • Remove Policies Set By Infections
  • Repair Windows Updates
  • Repair MSI (Windows Installer)
• Now on the lower right side check the box to Restart/Shutdown System When Finished
• Then make sure the Restart System radio button is enabled.
• Shutdown any other programs that you are running now before continuing.
• Now click the Start button.
• Be patient while the tool repairs the selected items.
• It should reboot automatically when finished.

Now run the C:\MGtools\GetLogs.bat file by double clicking on it (Note: if using Vista or Win7, don't double click, use right click and select Run As Administrator).


Then attach the below logs:

• C:\MGlogs.zip

Make sure you tell me how things are working now!