[quote author="Lukas Geyer" date="1311332544"]This means that some piece of kernel mode code (driver, filter, service, ...) is accessing the file.
Be sure that your virus protection software is really disabled - most products keep running even though disabled and need a restart or a complete removal for having them turned off.
If you can exclude your virus protection software my next bet would be the bloody Application Experience (or Application Compatibility Assistant) which can be disabled by group policy Local Computer Policy -> Computer Configuration -> Administrative Templates -> Windows Components -> Application Compatibility and the Application Experience service.[/quote]
Actually the error has nothing to do with "Antivirus Software" (I don't run any) and doesn't even make sense to begin with unless the installer was trying to write to qmake.exe. The reason that the main system process shows up the second time you run handle is that handle uses that process to check for other open handles, if you exit the command prompt then run it again you'll get no matching handles again. Basically this issue just comes down to sloppy programming and shoddy QA.
I encountered the same problem along with about a half a dozen unrelated errors during the install process
until I eventually gave up and cancelled the installation. Never having heard of Qt I was pleased to learn of its existence and was looking forward to trying it out. However, even being a developer myself and fairly accustomed to bugs/glitches etc... I still feel that this type of thing goes way beyond what I consider to be an acceptable QA oversight. To be frank the fact that this IDE is being represented as a production/release quality product is simply ridiculous, personally I would be embarrassed to be associated with such a pathetic piece of crap.