uninstall

How do I uninstall a Windows Service when there is no executable for it left on the system? I can not run installutil -u since there is not executable left on the system. I can still see an entry for the service in the Services console. The reason for this state is probably because of a problem in the msi package that does not remove the service correctly, but how do I fix it once the service is in this state? Treb You should be able to uninstall it using sc.exe (I think it is included in the Windows Resource Kit) by running the following in an "administrator" command prompt: sc.exe delete

I want to build app like parental control, so when child try to uninstall/remove my app I would like to require that a user type a password before being allowed to uninstall/remove my application. i try this, but still don't understand : Require a password to uninstall/remove application Any suggest? You can lock the device if you use device administration. Users can't uninstall active device admins, then you can lock the device if they try to disable device admin, then the parent could type in the password to unlock it. In your manifest: <receiver android:name=".AdminReceiver" android:label=

i want my app to have a password protected uninstall ... (like app lock) im using folling code it works on Android 2.3 but not on Android 4+ versions MANIFEST FILE <receiver android:name="fyp.invisibleink.UninstallIntentReceiver" > <intent-filter android:priority="0" > <action android:name="android.intent.action.QUERY_PACKAGE_RESTART" /> <data android:scheme="package" /> </intent-filter> </receiver> Uninstalling Activity code ublic class Uninstalling extends Activity { @Override protected void onCreate(Bundle savedInstanceState) { super.onCreate(savedInstanceState); setContentView(R.layout

I use InnoSetup 5.5.1 (a) for my Delphi 6 software installations. A user just informed me that the old uninstall entries pile up in the Control Panel Remove Programs list if not uninstalled manually. I'm thinking of changing my install to remove old entries automatically but I don't want to remove old entries that are valid. Some users like to keep an old version or two around in case they don't like a later version or for fear a later version will break something. For clarity's sake, I am referring specifically to the typical situation where a user usually accepts the default installation

We have a product, 1.0, in the field. I am trying to update the installer for that product so it can install over the old version, to install a new version, 2.0. I'm using a Visual Studio 2010 setup project to do this. I have maintained the UpgradeCode, and set remove earlier versions to true, and the new installer will successfully install over the old one, removing the old one. However, it appears that the uninstall of the old MSI happens after the install of the new MSI. Both MSIs deploy the same registry keys (since our code that uses them hasn't changed)... but that means when the old MSI