Download Dm-launcher.msi [VERIFIED]

I then used a browser to connect to ASA5512-x. It connected ok and tried to install ASDM from there. It downloaded dm-launcher.msi and jxpiinstall.exe. Running jxpiinstall upgraded Java to jre1.8.0_171 but running dm-launcher.msi does not add or change anything to "C:\program Files\Cisco System\ASDM\" folder.

Apparently with this latest release, Cisco has a .bin file that contains a bundled OpenJRE so that when you download dm-launcher.msi from the admin page, it will install without requiring a compatible version of Java to be installed. And then launching it uses the local install of the JRE instead of anything from the system path. You're looking for asdm-openjre-7122.bin on the Cisco ASA download site.

Download Dm-launcher.msi

Download 🔥 https://tlniurl.com/2y4Pbm 🔥

The problem with this is that only the first time that I downloaded dm-launcher.msi was it the 30MB version containing the bundled JRE. Every successive download gave me the classic dm-launcher.msi that requires a compatible system level JRE (apparently AdoptOpenJDK isn't compatible, or isn't installed properly for the ASDM installer to find). I did switch around versions a bit, so maybe something got weird and it cached the non-bundle version, but I tried the openjre image on another ASA and it was giving the old dm-launcher still. Not sure what went wrong here.

However, if I "re-installed" ASDM via the "dm-launcher.msi", the first time it was spawned by the installer, everything worked fine. Subsequent launches from the application shortcuts failed. A quick check with Process Explorer revealed the issue. The dm-launcher installer launched the java app using "C:\Windows\SysWOW64\javaw.exe", whereas the shortcut would use "C:\Windows\system32\javaw.exe". e24fc04721