Morten, thanks for the quick reply. Here's what I think you can do to reproduce the issue.
1. On a Windows 7 64-Bit box, login from an account that has administrative privileges - not a "Standard User", not the user "Administrator" either.
2. Run the MingGW-bundle setup of Code::Blocks 12.11 by double-clicking on the exe - don't run as administrator yet.
3. Specify "C:\Program Files (x86)\CodeBlocks" as the installation directory.
Going through the installation wizard will throw a "cannot create folder" kind of an error. I'm sorry, I do not remember the exact error message.
Now try the same thing again, but this time, right-click on the setup and run it "as Administrator". Specify "C:\Program Files (x86)\CodeBlocks" as the installation directory again. This time, you will be able to complete the setup successfully. But...
Go to "Programs and Features" in the control panel, and uninstall Code::Blocks from there. The progress bar moves ahead, but nothing is actually deleted from disk. I think I saw an error message again at the end of the "uninstall" process, but I can't be sure of that right now. Simply navigate to "C:\Program Files (x86)", and you'll see that the "CodeBlocks" directory, with all its files and sub-directories, is still there ! The start menu shortcuts are not deleted either.
This should reproduce the exact issue we're facing.
It has changed in r8122 to user.
Well the idea here was not to UAC prompt all the time, even if you install it into an accessible (i.e. portable) folder.
We can change that but this means it will always UAC prompt, even if you install it on a USB drive.
If thats more useful, I am happy to assist.
Edit: Maybe to clarify a bit more: For me, its always suspicious if installer request UAC at first place. Usually it should do that on runtime, if needed (which is not implemented). But I might be alone.
I hear you, but the
vast majority of users will install Code::Blocks to a local hard drive, most probably to the "Program Files (x86)" directory. A UAC request is perfectly normal - and expected - for all setups, unless the setup is built to install a program for the current standard user only. Honestly, I get suspicious when I need to explicitly run an installer "as Administrator", even though I have administrative privileges on my account. I'd request you to fix this behaviour and release a new setup for all of us. Many thanks, in advance.