I can confirm that. On my XP SP3 laptop I aborted the update after more than an hour had passed and the updater was still copying cmdagent.exe and using 98% CPU in the proces. Tried again, same problem. Rebooted, tried again, same problem.
I was hoping for a new cmdagent which wouldn’t monopolise the CPU, but apparently it is not to be.
Unless anyone has a better idea, I think I’ll download the complete installer tomorrow and try it that way.