Task Manager repair

I am using Windows XP and nothing happens when I press Ctrl-Alt-Delete. I downloaded Super AntiSpyware for another problem and see that there is a repair program on that software. Is it safe to use the Enable Taskmanager repair from SAS?

Will Task Manager open if you RIGHT click on an empty portion of your bottom toolbar (the part between Start and the system tray icons) and choose Task Manager?

No. That doesn't work either.

Then you should try using SAS task manager repair.
Let us know if it works.
I've never had to use that function of SAS, but I did a quick search of using it and everything I saw recommends it.

Edited by Queen-Evie, 13 September 2009 - 09:53 AM.

Infections can disable Task Manager

I just tried to run the Enable Taskmanager repair on SAS but nothing happened. I did have 647 infections yesterday but found this site and successfully removed them all. Task Manager has not been working for months. Does anyone have any other suggestions?

Re-enable project http://www.raymond.cc/forum/general-forum/...uggestions.html

I downloaded Re-Enable Portable as suggested. I ran it with only Task Manager checked then rebooted as requested. My anti-virus then opened and said that what I downloaded was an infection and wanted me to remove 8 things (Registry keys, 2 Hijacker and 6 Spyware) with names like Disable_RegistryTools, Disable_CMD. I didn't remove them yet? Should I? They sound like they would be legit. Anyway, regardless, Task Manager still doesn't work. Is that because my antivirus stopped it?

I am moving this to the Am I Infected forum till we are sure it's clean.
Post your Log.

Next run MBAM (MalwareBytes):

NOTE: Before saving MBAM please rename it to zztoy.exe....now save it to your desktop.

Please download Malwarebytes Anti-Malware and save it to your desktop.

alternate download link

MBAM may "make changes to your registry" as part of its disinfection routine. If using other security programs that detect registry changes (ie Spybot's Teatimer), they may interfere or alert you. Temporarily disable such programs or permit them to allow the changes.

• Make sure you are connected to the Internet.
• Double-click on mbam-setup.exe to install the application.
• When the installation begins, follow the prompts and do not make any changes to default settings.
• When installation has finished, make sure you leave both of these checked:
  • Update Malwarebytes' Anti-Malware
  • Launch Malwarebytes' Anti-Malware
• Then click Finish.

MBAM will automatically start and you will be asked to update the program before performing a scan.

• If an update is found, the program will automatically update itself. Press the OK button to close that box and continue.
• If you encounter any problems while downloading the definition updates, manually download them from here and just double-click on mbam-rules.exe to install.

On the Scanner tab:

• Make sure the "Perform Quick Scan" option is selected.
• Then click on the Scan button.
• If asked to select the drives to scan, leave all the drives selected and click on the Start Scan button.
• The scan will begin and "Scan in progress" will show at the top. It may take some time to complete so please be patient.
• When the scan is finished, a message box will say "The scan completed successfully. Click 'Show Results' to display all objects found".
• Click OK to close the message box and continue with the removal process.

Back at the main Scanner screen:

• Click on the Show Results button to see a list of any malware that was found.
• Make sure that everything is checked, and click Remove Selected.
• When removal is completed, a log report will open in Notepad.
• The log is automatically saved and can be viewed by clicking the Logs tab in MBAM.
• Copy and paste the contents of that report in your next reply. Be sure to post the complete log to include the top portion which shows MBAM's database version and your operating system.
• Exit MBAM when done.

Note: If MBAM encounters a file that is difficult to remove, you will be asked to reboot your computer so MBAM can proceed with the disinfection process. If asked to restart the computer, please do so immediately. Failure to reboot normally (not into safe mode) will prevent MBAM from removing all the malware.

Here is the log:

Malwarebytes' Anti-Malware 1.41
Database version: 2782
Windows 5.1.2600 Service Pack 2

9/17/2009 2:26:43 PM
mbam-log-2009-09-17 (14-26-43).txt

Scan type: Quick Scan
Objects scanned: 157296
Time elapsed: 9 minute(s), 12 second(s)

Memory Processes Infected: 0
Memory Modules Infected: 0
Registry Keys Infected: 0
Registry Values Infected: 0
Registry Data Items Infected: 0
Folders Infected: 0
Files Infected: 0

Memory Processes Infected:
(No malicious items detected)

Memory Modules Infected:
(No malicious items detected)

Registry Keys Infected:
(No malicious items detected)

Registry Values Infected:
(No malicious items detected)

Registry Data Items Infected:
(No malicious items detected)

Folders Infected:
(No malicious items detected)

Files Infected:
(No malicious items detected)

his step involves making changes in the registry. Always back up your registry before making any changes.

Go to Start » Run and type: regedit
Click OK.
On the left side, click to highlight My Computer at the top.
Go up to File » Export
Make sure in that window there is a tick next to "All" under Export Branch.
Leave the "Save As Type" as "Registration Files".
Under "Filename" put RegBackup.
Choose to save it to C:\
Click save and then go to File » Exit.
Or you can download and use ERUNTwhich is an excellent free tool that allows you to to take a snapshot (backup) of your registry before making changes and restore it when needed.

Click on the link below:
http://www.kellys-korner-xp.com/xp_tweaks.htm
Scroll down to #275 and click "Lift Restrictions - TM, Regedit and CMD" in the left column. Go to File, choose "Save page as" All Files and save regtmcmdrestore.vbs to your desktop. Double-click on that file to allow the script to run and reboot when done. Since the script modifies certain registry settings your anti-virus package may warn you about it. Ignore the warning and allow it to run.

I tried the tweak from Kelly's Corner as suggested. Once regtmcmdrestore.vbs was on my Desktop and I double-clicked it, instantly a tiny window pops up and says "Finished." It doesn't seem like it does anything. Still I rebooted. Task Manager still doesn't work.

I'm rather hesitant of whether to "bump" in here, as I'm no more than just a random computer user, and no expert whatsoever, at all. The reason I normally come to the forum myself is to search for info or ask for help too. Thus I apologise in advance if I'll add nonsense in any way. (Or if my post is unsuitable, please do remove it, and thank you at once for your understanding.) Yet, if somehow helpful to come to resolve this case, I thought I'd add my "experience" with having Task Manager inaccessible (nothing would happen when pressing CTRL+ALT+DEL either):

In my case it resulted from an infection as described by this ThreatExpert report:

http://www.threatexpert.com/report.aspx?md...f19102ffc0db9de

From what I figured from what I read by then, this was the culprit of Task Manager not being accessible, this registry setting newly created by that infection:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\taskmgr.exe]
"Debugger"="0"

As I understand it, let's say that "hijacked" the execution of Task Manager (in this case, not to execute any other specific program instead, but rather to simply block the execution of Task Manager; I gather that's what the "0" in there must stand for, right?...).

(For reference, further reading about this "Image File Execution Options" registry key for example here.)

Could it by any chance be that your case is any way similar, melissamc212? Could you please check in your registry whether such key eventually exists and what value corresponds to it? You mention that Task Manager hasn't been working for months, so that may perhaps be some leftover trace from some old infection?...

Anyway, by then, the way I came to try and fix that "hijacking" of Task Manager was to sort of "hijack" it back. I suppose that was a strike of luck, as I didn't really know by then that my fix attempt would have a direct "cause-effect" result, but in the end it did and it worked for the result I hopped, so I got happy anyway. So, what I did was to use Sysinternals Process Explorer and set it to replace Task Manager (under Options > Replace Task Manager). As I say, I didn't know it by then, but afterwards I could notice that, when choosing this option in Process Explorer, what it does is to exactly use the "Image File Execution Options" registry key to set Process Explorer to be executed when Task Manager is invoked (such as from CTRL+ALT+DEL). So, in the end, what it did in fact was clearing that bad value which was created by the infection and which was preventing the execution of Task Manager, "Debugger"="0", as it replaced that with the corresponding value for executing Process Explorer instead.

Just to add it as example, this is that same "Image File Execution Options" key exported from our registry here, when I have that option turned on on Process Explorer, i.e. have it set to replace Task Manager:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\taskmgr.exe]
"Debugger"="\"C:\\UTILITIES\\PROCESS EXPLORER\\PROCEXP.EXE\""

Ok, so, next then I set Process Explorer to restore Task Manager (again, under Options > now, Restore Task Manager). And so I had Task Manager back to being executed from CTRL+ALT+DEL.

I wonder, thus, whether in the end this info may be in any way helpful?...

Edited by DeLuk, 24 September 2009 - 07:52 PM.