News:

The new Release 25.03 is out! You can download binaries for Windows and many major Linux distros here .

Main Menu

Permission denied Problem - Solved..

Started by ishade, November 24, 2011, 04:52:47 PM

Previous topic - Next topic

ishade

for all of you who are having the permission denied problem while pressing build and run, all you have to do is,
run codeblock as administrator on your computer..
1. press right click on cb shortcut ( close cb before doing that)
2. go to properties
3. go to the compability tab
4. press " run this program as an administrator".
5 problem solved

MortenMacFly

A better solution would be to find out what file cannot be accessed due to file permission rights and store this elsewhere in a path with proper access rights for the user.

Code::Blocks DOES NOT require admin privileges by default. In fact I wouldn't suggest to run any application with admin rights unless required for system administration.
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: [url="https://www.codeblocks.org/docs/main_codeblocks_en.html"]https://www.codeblocks.org/docs/main_codeblocks_en.html[/url]
C::B FAQ: [url="https://wiki.codeblocks.org/index.php?title=FAQ"]https://wiki.codeblocks.org/index.php?title=FAQ[/url]

ishade

normally i wouldnt suggest runing a program as administrator as well but when the program is not in anyway connected to the web, the chance a trojan or a security risk would appear is unlikely.

oBFusCATed

What about stupidity, then?
Do you dare to put "delete c:\*.*" in a post build step? (I don't know the correct windows command)  8)
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

zabzonk

#4
It doesn't solve the problem anyway. I always run as admin (for a variety of reasons), and re-experienced the problem last week. Shutting down my firewall and rebooting solved it, but I still haven't identified exactly what is causing it. However, simply running as admin won't fix it.