Link to home
Start Free TrialLog in
Avatar of comptom
comptom

asked on

Atbroker.exe error preventing log in

I have two PCs running Windows 7 pro on a Windows 2008 R2 Server domain that are experiencing the same issue. The common factors seem to be both use GoToMyPC for remote access, both use SonicWALL/McAfee enforced antivirus and both problems seem to be related to a Windows update.  The problem is that when the domain user tries to log in at Ctr-Alt-Del they receive an atbroker.exe error and the screen goes black with just the mouse cursor and stops.  The system will boot into safe mode and can log on as administrator. I have tried the suggested Ctr-Alt-End but this does nothing. It also seems there may be a timing issue of something starting up involved because if the system is rebooted numerous times it will occasionally log in correctly.
I was only able to resolve the first PC by a reload and am trying to find what the problem really is.  Going back to a earlier restore point did not resolve the issue.  Thanks
ASKER CERTIFIED SOLUTION
Avatar of Eng. Nidal Kamal
Eng. Nidal Kamal

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
comptom--
Run SFC /SCANNOW from an administrative command prompt.  Reboot.

If no help run a Repair Install.
http://www.sevenforums.com/tutorials/3413-repair-install.html
Avatar of David Johnson, CD
which program uses atbroker.exe it is not a normal windows executable.
I have various versions of atbroker (exe, exe.mui) on my Win 7 PC.  I have never gotten an atbroker error. I scan for viruses and malware at least once a week.

Right click on one of those files|Properties|Details tab says
Product Name: Microsoft Windows Operating System
File Description: Transitions Accessible technologies between desktops
Avatar of comptom
comptom

ASKER

I have tried running the Hitman Pro malware removal program as suggested by Eng. Nidal Kamal. The Hitman pro found 3 Trojan instances which were removed. After this the system seemed to log in normally. We will test the system for a couple of days before we are sure this is the solution.  





 






Eng. Nidal Kamal