We’ve just released a small maintenance update for Windows 7:
Renoise 2.5.1 fixes problems with UAC on Windows 7, with the latest security patches installed.
This update is only necessary if you got annoyed by “C:\ Location Not available. Access is denied” messages from Windows when running Renoise.
If you don’t got those messages, you don’t need to update from Renoise 2.5.0 final. Mac OSX and Linux builds only have been updated to set the version number to 2.5.1.
Songs saved with Renoise 2.5.1 can of course be opened in Renoise 2.5.0 and vice versa. This update !only! fixes the above mentioned UAC problems.
There seem to be more UAC related problems with audio apps in general on windows 7. With windows getting more and more restrictive, security wise, ReWire might often also neglect to work. If you have problems getting ReWire working on windows, try to disable UAC. When even this fails, try running the applications as administrator (right click -> Run as Administrator). From my personal experience, this seems to be the only way to get for example Reaper running as ReWire Slave or Master.
I’ve had some issues with the psp plugs (reg window pops up) on w7 x64… they work, but registration didn’t seem to take. Then I started to run the host app as admin, and it all worked like a charm. No idea why, but it did This was in 2.5.
If you run your app as admin you will never have these problems. It remains similar to “Sudo” an app.
What i don’t know if installing your applications and plugins “as” admin would resolve running problems later.
It doesn’t seem that Windows 7 has a proper “system wide” install option like you have in Linux.
Application writers are getting more and more restricted to perform actions in temporary folders (which is not a bad thing) but it requires quite an adjustment from the user that some stuff ain’t working that easy out of the box anylonger.
As the others said: If you have some old plugins which neglect to register themself, then running Renoise once as admin will fix this. You only have to run them once as admin, not all the time as admin.
Alternatively, try updating your plugins to make sure they no longer try to write at places where they are not allowed to.
Yeah, i had a similar problem with windows 7, and yeah, running whatever programme you are having problems with as admin seems to work(note, this doesn’t mean having an admin account, it means right clicking on the program’s icon, and selecting “run as admin”)
As I wrote a couple of posts above there is a difference to be an admin and running stuff in Admin Approval Mode.
The later is the same as “Run as Admin”, having an admin account is just basicly a supped up normal account where you get a “continue/cancel” popup (sometimes).
Edit: sorry, it was in the original thread that I wrote about admin approval mode