Can't login, Atbroker.exe error

[Capt.Jack Sparrow]

Hi guys i'm new to t he forum. I just want to add what i have experienced as well. Windows 7 is a GREAT!! OS, but it appears this Atbroker.exe application ERROR is a real killer and once you get it. There is nothing you can do about it pretty much, but reinstall. Now hear his the thing that many people are referring to resolving the issue and that that's the CTRL+ALT+END command, but that only works if you are already logged into a Windows OS and your accessing Win7 from Remote Desktop.

The issue that the main poster is facing is the same issue I'm having. You start Windows it comes to the load screen. You enter your password and it acts like like its about to load. Then you get ERROR: AtBroker.exe Application error and Explorer.exe Application error.

Doesn't matter is you click "ok" or close it out. You are still doomed to be staring at a "BLACK SCREEN". Nothing seems to work. System restore, desk check, driver restores, or anything. I'm logged into SAFE MODE now and that's how I'm able to post my information on the forum now. These 2 ERRORS that you get before and after you try to log in have to be the worst things you can get on Windows 7. I'm not giving up though. If I find a fix for this I will post it ASAP!!! cause it seems to be a well known problem and Microsoft is not able to fix either. This ERROR was even on vista and you would think they would have came up with some sort of fix for it before releasing Windows 7.

Just out of curiousity are you able to Create a New Profile (Administrator) in Safe Mode and login under that profile. ??

- Captain

 

[Shahid Malik]

If you using CA antivirus try this:

restart in "safe mode with command prompt"
run sfc /scannow

restart in safe mode
set exclusion for \windows\system32\shell32.dll in CAAV options panel for Real Time and On Demand virus checks.

It worked for me. thanks to Win32/WebSearch infection - CA Home and Home Office Forum

 

[ccollard]

Atbrocker error happen after a patch was installed, I need advise on how to repiar please
have tried ALT-CTL-DEL no luck
can start i safe mode but can not repair
all scans are good

 

[Profnut]

I found a fix

I use CA Security suite and after the latest updates from Microsoft my CA antivirus
kept finding a problem with shell32.exe. This was an error, the virus signature dat for some reason identified shell32.exe as a threat after the updates. To fix this I:
restarted in safe mode
set exclusion for \windows\system32\shell32.dll in CAAV options panel for Real Time and On Demand virus checks.
Once excluded from Quarintine a re-boot and all was well.
Also on a second machine, I
restarted in safe mode
Updated the CA dat files and all worked.
Hope this helps. Maybe more antivirus programs see the updated Shell32.exe as a threat and are blocking it.

 

[brianrota]

I am having the same problem and also running CA. The exclusion didn't help me. I'm stilling having the problem at log in. I Hope someone can figure this out since tech support from Dell, CA, and Microsoft have all denied responsibility for this and a complete restore is not an option.

 

[brianrota]

Update.
My problem is fixed after excluding the win32.sys file. I'm actually not sure if it is the virus or not but it gets through those errors to log in.

 

[suedeuno]

I had CA also and excluding shell32 worked for me. Thanks to everyone who posted replies. I should have known something would happen when I saw that CA was unsupported during the windows 7 install. Hopefully there are no more issues.

 

[ageajo]

Solution to atbroker.exe crashing on windows 7 login

An even easier solution is to boot into safe mode, and uninstall CA antivirus.

Soon as you do this reboot your system and it will work. Get rid of CA only causes problems in my experience. Go with Norton, Pccillin, nod32.

 

[williewillus]

Would a full restore work? We have a home server and we do weekly backups
Safe mode doesn't work
Dulabooting with LinuxMint...haven't used windows in like a week or two.
Cheers,
Willie

 

[Gew]

This sucks. I'm starting to dislike W7 more and more. I installed it on my home workstation. Since I work on the fly I'm hardly ever home. I log on remotely through RDP. Now, the other day I got that annoying message. I don't know what else there is to say, except that it sucks.

 

[LisaUMD]

Ctrl-Alt-End works but ...

this solution worked for me. I did discover that when leaving my workstation at work I would normally do the Windows key + L to lock the workstation. If I use the mouse and the Start button to lock the workstation I don't seem to get the AtBroker.exe error. At least the last time I didn't get it.

 

[Entity]

I was having a same problem and since lots of people stumble upon this issue every now and then i guess it won't hurt to post my solutions.

I was modifying my visual style and ended up messing up the shell32.dll, and next time i restarted the machine the atbroker.exe problem appear.
The logon screen was normal but when i logged in it was just black screen. I tried to logged using safe mode but the problem persisted. Task manager wasn't working, no luck in system restore too.

The solution is log in using Safe Mode with command prompt. When the command prompt loaded, type "sfc/scannow" without the quotation mark and wait until the scan complete. After that, restart the computer by typing "shutdown -r -t 00" without the quotation mark.

Works for me.

 

[Grunge]

Thanks Entity.

Searched for a couple days before I found a solution to the Atbroker.exe error problem I had. But your fix worked for me.