#windows-installer — Public Fediverse posts

📬 Docker mit Sicherheitslücke CVE-2025-9164: Warum eine manuelle Installation empfehlenswert ist
#Cyberangriffe #ITSicherheit #CVE20259164 #DLLDatei #DLLHijacking #DockerDesktop #DownloadOrdner #Suchpfade #WindowsInstaller https://sc.tarnkappe.info/adb704

#InnoSetup 6.5.0 has been released (#SetupCreator / #WindowsInstaller / #JRSoftware) https://jrsoftware.org/isinfo.php

Neuer Artikel im Blog:

DDEV v1.24.7: Neuer Windows Installer und MariaDB 11.8 Unterstützung

https://wwagner.net/blog/a/ddev-v1247-neuer-windows-installer-und-mariadb-118-unterstuetzung

#DDEVUpdate #WindowsInstaller #MariaDBSupport

#InnoSetup 6.4.3 has been released (#SetupCreator / #WindowsInstaller / #JRSoftware) https://jrsoftware.org/isinfo.php

BassBoom is now easier to install!

We have made some of the biggest changes in BassBoom. This time, it’s about packaging the software for easier installation. Starting from BassBoom 0.1.12 and 0.2.7, we are providing the following package installers for different systems:

• Windows Installer for Windows systems
• Launchpad PPA for Ubuntu
• PKGBUILD for Arch Linux using the AUR

As we’ve promised, we’ve made installation of the BassBoom application easier than never before by shipping different types of installers apart from the regular distribution method that utilizes the packaged ZIP file for the application itself.

The documentation will be updated soon to provide instructions on how to install BassBoom using one of the above packaging methods that we’ve recently introduced. This will make your experience regarding installation of BassBoom smoother than before and save your time extracting the archive and remembering the path to the executable file.

If you’ve used the Windows Installer to install BassBoom, you’ll be greeted with this screen:

Just follow the instructions on the screen, and you’re done!

As for the Launchpad PPA, we’re uploading the packages that correspond to the API version of BassBoom releases to the archive. To install BassBoom, use the following commands:

$ sudo add-apt-repository ppa:eofla/bassboom$ sudo apt update$ sudo apt install bassboom

Then, follow the instructions on the screen to select a version series to install, currently being:

• bassboom-1: Installs BassBoom v0.1.x series
• bassboom-2: Installs BassBoom v0.2.x series

As for the Arch Linux distribution, use your AUR helper to install one of the following packages, depending on what series you want to install:

• bassboom-1: Installs BassBoom v0.1.x series from the latest release tag
• bassboom-1-git: Installs BassBoom v0.1.x series from the live servicing branch
• bassboom-2: Installs BassBoom v0.2.x series from the latest release tag
• bassboom-2-git: Installs BassBoom v0.2.x series from the live servicing branch
• bassboom-3-git: Installs an upcoming version of BassBoom from the live servicing branch

You can download BassBoom 0.1.13 and 0.2.8 here:

Image by freepik

#arch #ArchLinux #bassboom #deb #dpkg #Launchpad #LaunchpadPPA #news #PKGBUILD #Tech #Technology #Ubuntu #update #Windows #WindowsInstaller

#InnoSetup 6.4.1 has been released (#SetupCreator / #WindowsInstaller / #JRSoftware) https://jrsoftware.org/isinfo.php

Powershell - Clean up the Windows installer folder http://dlvr.it/THXJWr via PlanetPowerShell #PowerShell #Windows #MSIPatches #WindowsInstaller

#InnoSetup 6.3.1 has been released (#SetupCreator / #WindowsInstaller / #JRSoftware) https://jrsoftware.org/isinfo.php

Nothing like being asked to provide cross-platform support for my MSI #PowerShell cmdlets (https://github.com/heaths/psmsi) to extract the ProductCode - which is dubious since they depend on Windows-only APIs and most features would only work on Windows where MSIs can be installed - and saying you could write a simple #rustlang CLI using a crate that implements OLE docs and #WindowsInstaller's proprietary compression algorithm, only to realize you already did it a long time ago: https://github.com/heaths/msigetprop-rs

@m8urnett it gets even worse for #WindowsInstaller packages that will forever be stuck at #Windows 8.1: https://fosstodon.org/@heaths/109654404801981864 #MSI

There are also AppCompat shims that will lie about certain file versions, which are just as clunky as Windows versions, so "feature detection" based on implemention files often won't work. It's hostile behavior toward installers, pushing people back to custom, perhaps ill-behaved installers.