Cant Install the latest sdk, qmake.exe being used by another process
-
Hi, I am facing the same problem while installing it on my machine. But when I installed it on a colleague's machine it worked like a charm. Now the difference is I already have older versions of SDK on my machine and colleague's machine didn't have any. Could that be the reason?
BR
Rupesh -
Hi,
Thanks for suggestion, I just tried what you said. but that doesn't work either. :(
BR
Rupesh -
-
Have you tried to figure out "which process":http://technet.microsoft.com/de-de/sysinternals/bb896655 is accessing qmake?
@
handle qmake.exe
@ -
The output is
@
E:\Downloads\Handle>handle qmake.exeHandle v3.46
Copyright (C) 1997-2011 Mark Russinovich
Sysinternals - www.sysinternals.comNo matching handles found.
@
Then I clicked on Retry! And ran handle again. Output:
@
E:\Downloads\Handle>handle qmake.exeHandle v3.46
Copyright (C) 1997-2011 Mark Russinovich
Sysinternals - www.sysinternals.comSystem pid: 4 type: File CC0: E:\QtSDK\Desktop\Qt\4.7
.3\mingw\bin\qmake.exe
@After some moments it showed same error again. Running handle again produces same output
@E:\Downloads\Handle>handle qmake.exeHandle v3.46
Copyright (C) 1997-2011 Mark Russinovich
Sysinternals - www.sysinternals.comSystem pid: 4 type: File CC0: E:\QtSDK\Desktop\Qt\4.7
.3\mingw\bin\qmake.exe
@ -
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.
-
Hi, I am not sure how to change the policies. But I uninstalled the AV and restarted the machine and re-ran the installer. I got the same error. What should I try next?
BR
Rupesh -
I get "Windows can't find gpedit.msc. Make sure you typed the name correctly, and then try again.
I have Windows 7 Home Basic Edition. Does that have anything to do missing gpedit.msc?
I searched whole PC for gpedit.msc but found none! :( -
[quote author="rupeshbhurke" date="1311430568"]I get "Windows can't find gpedit.msc. Make sure you typed the name correctly, and then try again.
I have Windows 7 Home Basic Edition. Does that have anything to do missing gpedit.msc?
I searched whole PC for gpedit.msc but found none! :([/quote]The Group Policy Editor is not included in Home editions. However, it is just a MMC snap-in which operates on registry entries.
See "this list":http://www.microsoft.com/downloads/info.aspx?na=41&srcfamilyid=18c90c80-8b0a-4906-a4f5-ff24cc2030fb&srcdisplaylang=en&u=http://download.microsoft.com/download/8/F/B/8FBD2E85-8852-45EC-8465-92756EBD9365/WindowsServer2008R2andWindows7GroupPolicySettings.xlsx, Administrative Templates, line 16+.
-
I had the same problem.
I tried to solve it so:- use unlocker, handle (from sysinternals.com) to find and remove locked deskriptor
- disable antivirus (NOD 32)
- uninstall antivirus
But when run qt installer with windows xp sp3 compatibility it works fine.
PS: OS - Windows7 Ultimate 32Bit -
[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. -
Right, looks like a compatibility issue w/Win 7. I've had the same problem installing ... same qmake error.
GOOD NEWS!!! 100% success running the offline installer under Windows XP SP3 compatibility mode ("run as admin" checked, but not sure if necessary).
Right-click the .exe, select Properties, and then the Compatibility tab.
Give it a try. I haven't tested the app yet, but looks solid at a glance.
-
@kerlaeda said in Cant Install the latest sdk, qmake.exe being used by another process:
I had the same problem.
I tried to solve it so:- use unlocker, handle (from sysinternals.com) to find and remove locked deskriptor
- disable antivirus (NOD 32)
- uninstall antivirus
But when run qt installer with windows xp sp3 compatibility it works fine.
PS: OS - Windows7 Ultimate 32BitThank you so much! You saved my day ;)
Had the same error, but running the QT- installer with windows xp sp3 compatibility ("run as admin" checked) worked smoothly :)
I also disabled my antivirus- software for the time of installation.
My system: Windows 7 Home Premium 64BitBest regards from Berlin