uac

I noticed the following phenomenon: An executable built with Delphi 7 and part of the name including "Update" (e.g. "UpdateMyApp.exe") causes UAC to step in to display a warning like "do you want to allow the program to make changes to your computer". This happens with a simple hello world application. Showing the file in explorer shows the shield symbol overlayed to the application icon. As soon as you rename the exe the shield disappears and the application starts without warnings. As mentioned this only happens to programs built with Delphi 7 and started on Windows 7 (I assume same on Vista

I thought that CSIDL_COMMON_APPDATA\company\product should be the place to put files that are common for all users of the application and that the application can modify, however, on Vista this is a read-only location, unless modified by the installer (as per MSDN - http://msdn.microsoft.com/en-us/library/ms995853.aspx ), so... what's best? Modify the location's security settings to allow writing or use CSIDL_COMMON_DOCUMENTS\company\product instead? Maybe there's a third option? Also, is there an "official" Microsoft recommendation on this somewhere? Modify just the security on a specific sub

I have a simple PowerShell script to stop a process: $p = get-process $args if ( $p -ne $null ) { $p | stop-process $p | select ProcessName, ID, HasExited, CPU, Handles } else { "No such process" } If I try to stop a process not started by the current user; it works on Windows Server 2003. However, on Windows Server 2008 (and other Windows flavours with User Account Control), I get the following error: Stop-Process : Cannot stop process "w3wp (5312)" because of the following error: Access is denied Is there any way to get around this without running PowerShell with elevated privileges ? It

In my VB6 application I open other EXE files. My application runs without any UAC prompt, but I have an EXE which checks for updates to software. This prompts the UAC prompt. So how does Windows decide whether to show the UAC prompt? I saw this link . So does it depend on the code I wrote in my application? It is interesting that my application (that is the main EXE file) does not prompt UAC whereas a small EXE which checks and downloads updates prompts the UAC. I have all the EXE files digitally signed. I already had a glance at following links: http://msdn.microsoft.com/en-us/library/windows

I have a CustomAction as part of an MSI. It MUST run as a domain account that is also a member of the local Administrators account. It can't use the NoImpersonate flag to run the custom action as NT Authority\System as it will not then get access to network resources. On Vista/2008 with UAC enabled if NoImpersonate is off then it will run as the executing user but with the unprivileged token and not get access to local resources such as .installState. See UAC Architecture Anyone know of a way to either Force the MSI to run with the elevated token in the same way that running from an elevated

I have created a .NET C# WinForms application on Win 7 RTM x64, which let's say I have called DataInstaller. When I run this program outside of the debugger (just an empty form with no functionality at the moment), it works fine until I close the form. I then get a message from the Program Compatibility Assistant that says: This program might not have installed correctly I then get the option to reinstall using recommended settings or to say that the install did work as expected. If I name the app 'DataThingy' this isn't an issue, I guess this is related to the way that programs called *Setup

I have one major problem with my app. I have an app & updater as a separate exe files. When an update is available, updater does the update, and on process completion it starts my app. The main problem is - app is installed in program files folder, so updater need UAC admin privileges, and that's ok, but when I need to run my app updater needs to run it as a normal user, because if it's run as an administrator drag and drop doesn't work (not an app problem, UAC blocks it). I've tried several different solutions, and even this one: How to run NOT elevated in Vista (.NET) It haven't helped me -