Spat's WebLog (Steve Patrick)

The exception code in that termiantion dialog can be found in ntstatus.h in the WDK. It translates to STATUS_DLL_INIT_FAILED (Initialization of the dynamic link library %hs failed. The process is terminating abnormally.) My guess is those applications when trying to init user32 as part of their dynamic load-time links, user32 saw it was on secure desktop and freaked and wouldnt load.

I am remoted into my home workstation almost all the time I am not home and have an Internet connection.

Thanks for the work around. I was just short of picking up my lazy self and run to office as I had some work to complete, and could not remote in, thanks to the atbroker issue. But, your work around saved the day. Thanks again!

i have had alot off error codes that i have recently sent to tech department in regards to atbroker.exe and various windows explorer seizure codes. they have since infrmed in  8 weels a scheduled service pack 1 will be released which is to stabilize compatibilty and explorer issues

Sweet, this helped me out tonight - thanks!

I see this issue on my Vista Enterprise 64bit system occasionally as well.   Seems to mainly happen when I’m using a different OS to RDP into my Vista system.  It mostly happens with using RDP in Windows XP, but have also seen it when using rdesktop in Linux.    But like everyone else, doesn’t always happen.

Another workaround I’ve used to get your screen back without logging off, is to use another Vista system, RDP in the problem Vista system, log out and you should have your console back.

Thanks a million for this post. Saved me a trip to the office :-)

This saved my day too! Thanks a lot!

Wow.  Probably like a lot of folks who stumbled on your post here, I am really grateful!

I woke up Saturday morning to do some quick little things and hit this problem.  Wanted to scream because the drive to work and back would have been 10x the actually work time.

Saved my weekend, pal.  Your trick worked like a charm.

Also, I'll give this a shot on the other side -- I often find a blank screen when I get into work Monday after I've remoted over the weekend.  

비스타 원격제어시 ArBroker.exe 에러메세지가 나올 경우 해결 방법은 CTRL + ALT + END 를 누르는 것이다! - 출처

Thanks from me as well!  I use RDP all the time and had never seen this one.  I didn't even remember how to send a ctrl-alt-del, so thanks for that reminder as well.

Me too.  I got the Atbroker.exe error after connecting from XP SP2 to Vista Enterprise SP1, clicked OK and was staring at a black screen.

I tried Ctrl + Alt + End, then picked Task Manager.  The desktop appeared with 2 error messages that said "transitions accessible technologies between desktops has stopped working".  I closed those error messages, and was able to use my Vista machine across RDP once again.

I have find a solution. You can connect with a another user account name (adminitrators group account) but all programs will be closed. After that you can close the session or restart the computer and try again with your account.

any chance anyone installed "logmein"?

Ctrl+Alt+End is a good solution. Thanks for that dude.

And select "Task manager", it will take you right into your desktop!! and you can continue to use it just fine after closing task manager.

Thanks CTRl+ Alt +End worked like magic, thanks!

...add me to the list who just started getting this error.  Vista Ultimate.  Transition Accessible Technologies seems to be culprit.  Ctrl+Alt+End, Task Manager, worked for me.  Thanks to all for this post and comments!

worked like a charm. many thanks save me a lot of frustration.

I often have the problem now. I use Ctrl-Alt-End to bring the logoff screen, and then click "cancel". This way I get my desktop back.

I just had this happen in Windows 7 RC 64bit. You fix worked though.

Many thanks! (Got to cancel log off once tried too :P!)

I install a theme for windows vista this theme replace the shell32.dll and the browseui.dll I replace for the olders by prompt and that´s all I got no more black screen

I hope this could be helpfull

Thaanks!!! That saved me for a trip to my job!

Hi, thanks for the tip! I was going from Vista Ult. to Win 7 Ult. and got this error. CTRL-ALT-END saved the day.