My installer window show up for a quarter of second then quits without installing
What can I do to find what causes this bug?
Restart machine, clear cache, download installer again and try again.
Related
I'm trying to make an update app feature for an electron app I'm working on. I am able to download the installer for the update, but when I try to run the installer I get this message:
Is there something that I need to do in order for the installer to not be flagged as unsafe?
Side Note: When I download the installer using chrome, it works just fine. But when I download it using my electron app, it shows that windows defender popup.
Sign your installer package to avoid smartscreen filtering. https://github.com/electron/windows-installer#sign-your-installer-or-else-bad-things-will-happen
We build an electron app which uses electron-builder to make a NSIS installer. Everything works fine except when the uninstaller is run in silent mode and the app is still running. The observed issue is that the app is not terminated (as expected), and the installation is only partially removed.
The electron-builder version is 19.48.3, which has a hardcoded dependency on nsis 3.0.1.13, and nsis-resources 3.3.0.
The documentation says the uninstaller has to be run with an /S option, and any MessageBoxes has to have a /SD option to designate a silent result, which is the case with the app.
Is there anything else I am missing which controls the behavior in this use case?
Thanks!
I had issues with the one click installers. To overcome that I made nsis configurations like this. You can give it a try, and see if that works out for you.
I have an app installed on Android Things, in a Raspberry Pi. I want to replace with a newer version, but it's overwritten with previous version after a reboot. That's weird!
This is what I've tried: Let's say the installed app package name is "com.myapp", I've run "adb uninstall com.myapp", and I get "Success". If I run uninstall command again, I get "Failure [DELETE_FAILED_INTERNAL_ERROR]", so the app is completely uninstalled.
Then, I've modified package name in build.gradle to "com.mynewapp", and I install and run it using Run button from Android Studio. Now "com.mynewapp" appears when I run "adb shell pm list packages".
Now I restart the Pi using "adb shell reboot". And after reboot, the old app is running. Executing "adb shell pm list packages" shows my old package: "com.myapp", and "com.mynewapp" does not appear in the list.
How can I completely remove the old app, and replace with a new one?
Uninstall the app using:
adb uninstall <pkg name>
I tried deleting all SD contents, and flash latest Android Things image, and I realized SD card is corrupt. I replaced SD card, and it's working fine.
You can not uninstall the app which you packed in the OS image and flashed in the SD card using adb (returns the error which you encountered Failure [DELETE_FAILED_INTERNAL_ERROR]). Only you can uninstall the app which you installed using adb or android studio.That is why first time you are seeing success,which is uninstalling the overwritten version but next time as you are actually trying to uninstall the OEM version of your app so,you are seeing this error.
Just format and reflash the SD card with only Android things OS (without your app) then install your app using adb/android studio,now you will have only the uninstallable copy of your app in the sd card. So you can replace or do whatever you like with that app as like normal app downloaded from playstore.
I am using Advanced Installer to create the installer of java based desktop application, it is working fine. I added a desktop shortcut icon of the EXE, when i install the application on my system its desktop icon is correct as i defined when created the installer, but when i uninstall the app and then reinstall it 2nd or 3rd time sometimes its desktop icon get changed by itself(replaced with no icon).
can someone tell me what is the issue. Thanks in advance.
Usually this is a sign of corrupted Windows Installer cache on your machine. Have you tried testing the package in a VM? The icons are cached by the OS in a special system folder, nothing special is done by the setup package or Advanced Installer in order for the icons to be set on the shortcuts.
I run the drvupdate-64 installer which runs until it closes and I get a notification in the tray icon that '"not supported bluetooth function"' was successfully installed as a driver.
I found that a bit weird and after that NOTHING happens with the installer, it just dissapers and doesn't come back.
In task manager I can see it running as 'driver_setup.exe' with the description 'windows mobile device center setup' but that's it, nothing else seems to be happening.
Any ideas what's going wrong and how I can fix this? I need it to get the windows mobile sdk to install.
I had to navigate to the install directory of WMDC Driver Update and find the installer to continue the process, the installer was bugging out on me and not proceeding to the next step for some reason...
I had a similar issue when installing on Dell laptops models 7480, 7280. I had tried updating removing device drivers as per Microsoft Answers with no success.
Having come across the above I did continue the installer process as per tweetypi comment but still had issues. I was able to install and get this working as per following steps:
After running the WMDC installer I could see that in task manager the install process "driver_setup.exe" was still running.
As per tweetypi answers I then navigated to the install directory for WMDC Driver Update to find the installer and continue the process:
C:\Windows\WindowsMobile
I opened each Drivers folder (Bluetooth, RNDIS, Serial) in turn and run the “wmupdate” installer.
Windows Mobile Device Centre was then listed on my programs list but would not launch.
I then opened Device Manager from Control Panel. Changed view to show hidden devices. This revealed 'Bluetooth Virtual Devices' > 'Not Supported Bluetooth function'.
I then uninstalled this driver and checked delete the driver software for this device
After this, I ended the “driver_setup.exe” process within task manager. Then run the “driver_setup.exe” install file once more. The install process was then able to complete and the Windows Mobile Device Centre was now launching.
The device I needed to connect was for USB, I'm not sure about functionality for Bluetooth after removing the virtual device.