Wingetlywingetly
← Back to blooming-blockery

Silent install command for blooming-blockery 0.0.10

The exact silent switches the blooming-blockery installer accepts, plus a one-line command you can paste into a script, Intune Win32 app, or Configuration Manager package.

One-line silent install (x64)
msiexec.exe /i blooming-blockery-x86_64-pc-windows-msvc.msi /quiet /norestart

Run from the directory containing blooming-blockery-x86_64-pc-windows-msvc.msi. Download the installer from the Direct link below first.

ArchitectureScopeTypeSilent switchesSource
x64-MSI
WiX
Default for WiX (MSI)
  • Declared by publisher means the switches come straight from the winget manifest the publisher (or community maintainer) submitted to microsoft/winget-pkgs.
  • Default for {type} means the manifest doesn't specify silent switches, so the framework's standard switches are shown (e.g. /S for NSIS, /quiet /norestart for MSI).

Frequently asked questions

What is the silent install command for blooming-blockery?
blooming-blockery uses MSI (WiX). After downloading the installer, run: msiexec.exe /i blooming-blockery-x86_64-pc-windows-msvc.msi /quiet /norestart. The silent install switches are /quiet /norestart.
How do I deploy blooming-blockery via Intune or Configuration Manager?
Use winget for the cleanest path: winget install --id Miorin.BloomingBlockery --exact 0.0.10 --silent --accept-package-agreements --accept-source-agreements. If winget isn't viable in your environment, package the publisher's installer directly using the silent switches above.

Prefer the winget route? See the full blooming-blockery install page.