Hello.
I'm Aleksandar Vacić, professional web developer and wine maker in the making.
Learn more about me or see what I can do for you.
Some of the stuff here also apply to problems appearing during installation or use of iTunes 9 on Windows XP, Vista or Windows 2008. Meaning – do try them, it might help you solve the issues you’re having.
If you have any of these issue, this article will most likely help you.
My wife uses Windows 2003 as development machine and I had all of these happening.
Apple is — like many other companies do in the last year or two — touting iTunes 9 as compatible only with Windows XP and Vista or Windows 7. This is safe net for them. If you run Windows 2003, this is just about the same thing as XP, regarding ordinary software.
Thus, solution here is to kill the OS-based launch conditions, which good people at WebKeyDesign have already explained how to do. The solution goes like this:

InstEd — removing launch conditions

QuickTime has two conditions, remove both
Once you’re done with all of them, install them, one by one. Start with AppleApplicationSupport, then AppleMobileDeviceSupport and then continue until iTunes as the last. Ignore SetupAdmin.exe
At the end of iTunes installation, it will try to start iPodService.exe. This fails and manifests in a variety of ways. There’s an amazing number of “solutions” on the net, but remarkably none has pinpointed the actual cause.
It’s Data Execution Prevention feature of the Windows — it will kill the process as soon as it tries to run. DEP is made to prevent malicious software using private or undocumented API or doing any sort of suspected malicious activity. iPodService.exe falls into this trap according to DEP, so we need to tell DEP to let it go as exception to the rule.
Here’s how:

Data Execution Prevention is what kills iPodService.exe
You click, they appear to start but then fail. The reason is the same as above: DEP. Add both .exe files (they are in Program Files\iTunes folder) to the DEP exception window and they will start just fine afterwards.
To expand this a bit — every time you have a known, valid software failing to start, always add them to DEP and see if they work. Most likely they would.

Hmm…say again?
This is in Windows Explorer, copying/moving files across networked disks.
Given my experience so far in big software projects, this kind of bad UI is direct consequence of the background API being done before front-end people had any say. At the moment when front-end work came to play, there was probably no info to determine is the current operation a copy or move, so they did what they could. Or it could be sloppy FE work, but I somehow believe it’s the former.

Funny bit is that in this case it sounded almost completely legit. They missed the “hello” at the start. :)
I tried to register on Adobe’s site to download trial version of Fireworks CS4. I tried several times, from two computers and networks, with few of my email addresses. In all cases I got this:

The data entered is correct. Error message is far from helpful and tells me nothing useful. Sending web site feedback also yields nothing, as they don’t answer it.
Jolly. :(

I mean, really…it lasts close to forever, and is the only thing able to drive my Core Duo 1.83GHz close to 70 degrees Celsius.