AtBroker.exe - Application Error

[Bob Boudreaux]

"The application was unable to start correctly (0xc0000022). Click
OK to close the application."

done. next error -

explorer.exe - Application Error
"The application was unable to start correctly (0xc0000022). Click
to close the application."

done. result?

Black screen blinking cursor from pointer to blue busy circle. Will
go no further.

I searched the web, see this must be a common problem going back at
least two years, and also was happening in Vista.

My computer had been running as admin and connected overnight. Only
changes made previous day were downloading a windows defender
update, but subsequent reboot was ok. I tried safe mode system
restore, nothing!

 

[Bob Boudreaux]

"The application was unable to start correctly (0xc0000022). Click
OK to close the application."

done. next error -

explorer.exe - Application Error
"The application was unable to start correctly (0xc0000022). Click
to close the application."

done. result?

Black screen blinking cursor from pointer to blue busy circle. Will
go no further.

I searched the web, see this must be a common problem going back at
least two years, and also was happening in Vista.

My computer had been running as admin and connected overnight. Only
changes made previous day were downloading a windows defender
update, but subsequent reboot was ok. I tried safe mode system
restore, nothing!

Booting from Windows 7 "repair disk," all I get is
"Error 0x4001100200001012" great stuff isn't it?

 

[Paul]

Booting from Windows 7 "repair disk," all I get is
"Error 0x4001100200001012" great stuff isn't it?

This seems to be Dell-specific problem (somehow, the repair disc is bad).

http://answers.microsoft.com/en-us/...ror-code/0565a440-3c80-4af7-8f03-e994d3cdb3fc

A repair disc is not a full installer disc, and won't reinstall the OS.
But it does give access to a command prompt, and perhaps even allow
you to do a system restore or whatever.

You download the correct version for your OS. You either have a 32 bit OS
install or a 64 bit one. You download the ISO9660 file and use a burning
program that knows how to convert that format. An example of a free burner
program is Imgburn. (If you select the option in Windows to prepare one
of these discs, Windows uses IMAPI2 built-in burning support to do the
burning. Recommending Imgburn, is in case you're on some older Windows
machine or want the comfort of a separate burner program.)

http://en.wikipedia.org/wiki/Imgburn

Neosmart has links to the repair discs, but they're
BitTorrent files. When I needed a disc like that the first time, I got
it by using a Linux LiveCD and a BitTorrent client (it's the only BitTorrent
transfer I've ever tried). So this would involve some extra work, depending
on whether you're set up to do it or not.

http://neosmart.net/blog/2009/windows-7-system-repair-discs/ (torrent links)

One thing that has slowed me up, is I've been trying MD5SUM on several
different versions of the repair disk, and I'm getting different answers.
And I'm not getting confirmation of correctness, by using the MD5SUM in
a search engine. This could mean, that the repair disk differs slightly,
depending on the source (and this would be a horrible thing, if true).
As a consequence of this problem, I'm not including an MD5SUM, because
I don't really know what the right answer is. The Windows 7 x64 rescue disc should be
somewhere around 273,377,280 bytes and the x32 versions around 150,194,176 bytes.
Too bad Microsoft doesn't have these for download on their website,
to remove all doubt. (Since these are not installer CDs, there isn't
any loss of proprietary information by offering them for download.
It's not like these are a full OS or anything.)

When the repair disc is booted, these are the options you should see.

http://cdn.raymond.cc/images/system-recovery-options.png

Paul

 

[Paul]

"The application was unable to start correctly (0xc0000022). Click
OK to close the application."

done. next error -

explorer.exe - Application Error
"The application was unable to start correctly (0xc0000022). Click
to close the application."

done. result?

Black screen blinking cursor from pointer to blue busy circle. Will
go no further.

I searched the web, see this must be a common problem going back at
least two years, and also was happening in Vista.

My computer had been running as admin and connected overnight. Only
changes made previous day were downloading a windows defender
update, but subsequent reboot was ok. I tried safe mode system
restore, nothing!

There are a few ideas here, but you've probably tried all these.

http://www.sevenforums.com/general-discussion/59325-cant-login-atbroker-exe-error.html

I think one poster tried removing a bunch of Windows Updates and got
relief, but that probably isn't the problem either (that might have
been some time ago, and you could be at SP1 now).

Paul

 

[VanguardLH]

This seems to be Dell-specific problem (somehow, the repair disc is bad).

_To Paul_

From http://www.fileinspect.com/fileinfo/atbroker-exe/:

The AtBroker.exe is a Transitions Accessible technologies between
desktops.

This file is part of Microsoft® Windows® Operating System.
AtBroker.exe is developed by Microsoft Corporation. Itÿs a system and
hidden file. AtBroker.exe is usually located in the %SYSTEM% folder
and its usual size is 29,184 bytes.

Also see: http://www.faultwire.com/file_report/atbroker.exe.html

So if it were a Dell-specific problem then it would be a conflict
between this Microsoft program and something else Dell dumped in their
OEM'ed version of Windows.


_To Bob_

I'm not at a Vista or 7 host right now. Is there an NT service by the
"Transitions Accessible technologies between desktops" or similar name?
From what I've read, atbroker.exe should be seen as a running process
(which means something had to load it). If there is, that's probably
why this service doesn't run when Windows is booted into its safe mode.
Non-critical services aren't loaded in safe mode.

Since this appears sometimes related to remote access via RDP then
perhaps disabling the Remote Assistance and Remote Desktop features
might help, especially if the OP isn't using them or even allowing them
in the firewall. Although it appears this Transitions feature has
something to do with the UI for apps, it also appears the remote desktop
feature is causing a problem with the local desktop. Since atbroker
looks to be associated with desktop(s), an RDP client could be switching
to the primary or secure desktop which pulls the output away from a
monitor on the secondary output.

I've seen some users find that their local desktop had switched over to
display #2 on their video card (and why their monitor connected to the
display #1 output on the video card looked black). Or the problem is
both monitors are black but the commonality is a dual monitor setup. Of
course, this symptom would only appear for a video card that supports
dual monitors. Perhaps going into the video card's setup software might
provide a means of detecting the displays and/or disabling the secondary
display, especially if there isn't one. If you notice your primary (or
only) monitor is on output 2 then it probably should be on output 1.

http://support.microsoft.com/kb/940542

Notice it says, "This timing issue causes Windows Vista to start the
Atbroker.exe process on the wrong desktop." So atbroker.exe does appear
to be something about the local desktop(s). As I recall, Ctrl+Alt+Del
is one solution and logging out and back on as this probably resumes
output to the active output (desktop). Leaving the computer running
with RDP ends up with it timing out to its login screen or with your
host in "locked workstation" mode (i.e., screensaver, login screen).

 

[Paul]

_To Paul_

From http://www.fileinspect.com/fileinfo/atbroker-exe/:

The AtBroker.exe is a Transitions Accessible technologies between
desktops.

This file is part of Microsoft® Windows® Operating System.
AtBroker.exe is developed by Microsoft Corporation. Itÿs a system and
hidden file. AtBroker.exe is usually located in the %SYSTEM% folder
and its usual size is 29,184 bytes.

Also see: http://www.faultwire.com/file_report/atbroker.exe.html

So if it were a Dell-specific problem then it would be a conflict
between this Microsoft program and something else Dell dumped in their
OEM'ed version of Windows.

I was referring to the "Error 0x4001100200001012". It seems to be
associated with Rescue CD's burned using a Dell computer, rather than
a more generic (affecting all computers) type of problem.

One of the things I don't like about some "dumbed down" burning method,
is the inability to adjust things. For example, I've had burners before,
where I know I can only get a good disc, if I burn at 4X or whatever. It's
nice, when knowing that, for all burner applications to offer me the
option of adjusting the burn speed (to something I know works). There
is point for a totally automated method to burn at 12X and make a coaster,
if I know the media I bought only works good at 4X.

My current burner doesn't have a problem like that, but I have some others
that were always "flaky pastry", even when they had the manufacturer's
firmware update installed. I have a habit now, when writing identifying
info on discs, to write the burn speed on them, so later I have
a "log" of what works.

Paul

 

[Bob Boudreaux]

There are a few ideas here, but you've probably tried all these.

http://www.sevenforums.com/general-discussion/59325-cant-login-atbroker-exe-error.html

Paul, yes, I did read that site.

I think one poster tried removing a bunch of Windows Updates and got
relief, but that probably isn't the problem either (that might have
been some time ago, and you could be at SP1 now).

Paul

Thanks to both of you, and (VanguardLH), Paul, it is a Dell! Amazing.

I went what turned out to be the easy route, I had a month old
"image," (created with win7), on an external disk and was glad I got
to try it out. It worked flawlessly to fix the problem...I have a
lot to review from within your comments still! Thanks so much again!

Bob

 

[Paul]

Paul, yes, I did read that site.


Thanks to both of you, and (VanguardLH), Paul, it is a Dell! Amazing.

I went what turned out to be the easy route, I had a month old
"image," (created with win7), on an external disk and was glad I got
to try it out. It worked flawlessly to fix the problem...I have a
lot to review from within your comments still! Thanks so much again!

Bob

The repair disc is one that can be burned from within your OS. My Acer
laptop had that function, and it's a Microsoft option rather than one
provided by Acer. That's one source of the 64 bit version of the
rescue disc. (Neosmart is where I got copies of it, before I got
the laptop.) The repair disc can even be used when you're working
on a WinXP system, because it gives you a command prompt.

In the Sevenforums thread, one respondent mentioned some Windows Updates
he removed. Now that you've restored a one month old image, perhaps
you'll be visiting Windows Update again at some point. If it was
a Windows Update that is breaking "atbroker", you may get to see
the problem again. So don't discard that "good" image just yet.

Paul

 

[KCB]

Paul, yes, I did read that site.


Thanks to both of you, and (VanguardLH), Paul, it is a Dell! Amazing.

I went what turned out to be the easy route, I had a month old
"image," (created with win7), on an external disk and was glad I got
to try it out. It worked flawlessly to fix the problem...I have a
lot to review from within your comments still! Thanks so much again!

Bob

Bob, some users had an issue with their AV software, and the problem was
fixed by excluding certain files from AV action. See this forum:
http://answers.microsoft.com/en-us/...rokerexe/8921785c-d081-46c6-99c6-e91380d83d99