How to use SDBINST to install SDB fixes


SDB files (databases), which we’d call shims, can easily be installed with the following command

sdbinst -q path_to_sdbfile

-q means quiet mode and the prompts for confirmation are auto accepted.

Another parameter used during installations is -p, which will allow SDBs containing patches. Not that common, though.


Once installed, there will be an entry in Add/Remove Programs, with the name given to the fix in the ACT (Application Compatibility Toolkit).




In order to uninstall a  shim, sdbinst can be called with the following parameters

-q                     quiet mode, same as for the installation

-u File.sdb      this will remove the shim installed by the provided SDB file


-u {guid}         this will uninstall based on the guid

-n name          this will uninstall based on the internal name (the one



Known issues

See what issues might occur when using sdbinst in our related article.


SDBINST issues on Windows 7 and Windows 10

Possible Problems

When migrating packages Windows 7 (or older) to Windows 10, or when simply targeting multiple OS’s with the same package, one might to pay attention on the way SDBINST.exe is used for compatibility fixes (shims).
In case the executable is included in the package (simply as a file or in the binary table, inside an MSI), there could be issues like error exit codes of sdbinst, or worse, like an incorrect behaviour even though the SDB file would appear to be installed.

Long story short:

  • the SDBINST from Windows 7 will behave incorrectly on Windows 10 (shim/sdb will appear as installed but won’t do what it’s supposed to do)
  • the SDBINST.exe from Windows 10 will not work at all on Windows 7 (visible in the exit code)



Adapt the package so that SDBINST.exe is excluded from it and use the executable found on the system, whether it’s an Win7 or Win10 OS.

In case this is done inside an MSI via custom action, make sure to change it from “Execute from Installation” in Wise or “EXE – Stored in Binary Table/Installed with Product” in InstallShiled to “Execute from Destination” – Wise or “EXE – Path from Directory”. That will result in a custom action with type 3106 (0x0c22) if you’re executing in Deferred – System Context, Synchronous.


More info

For more info on sdbinst.exe and how to use it, check our other post about this topic.



InstallAnywhere Silent Installations

<h1>InstallAnywhere Silent Installation</h1>

According to Wikipedia InstallAnywhere is a Java-based software used to create software packages.

On Windows, InstallAnywhere packages come as executables.

In order to install such a package silently, we need to follow these steps:

1. Create a configuration replay file ( by starting the setup in replay mode.
<setup.exe> -r
2. Complete the installation by selecting the desired options.
3. Edit the newly file. Add this line before the install directory definition.
4. Save
5. Run the following command:
<setup.exe> -i silent -f “<pathto>\”

ATTENTION: Try to keep the path to the .properties file short (no spaces). Otherwise, the setup might fail (Problem opening install properties file). Try something like c:\tmp or c:\temp…

By default, log files (or something close) can be found in c:\tmp.

<h1>InstallAnywhere Silent Uninstall</h1>

In order to uninstall the software silently, look for an Uninstall*.exe in the installation directory. Run it with the -i silent parameter.

Office Installation

Microsoft provides an uniform way of silent customizing Office products’ installations: OCT (Office Customization Tool).

In order to start it, run the setup executable of the office installation you want to start (32 or 64-bit) with /admin parameter. (setup.exe /admin)

This will start a wizard where you can configure many options, from feature selection, to the smallest details one can imagine.

Once you’re done with the configuration, save the changes. This will create an MSP file that you can use for the silent installation.

In order to install it, run the following command line:

setup.exe /adminfile <pathToMsp>

However, there’s also the possibility of using a configuration xml file for the silent installation, based on the template config.xml that can be found in the core_product_folder_name.WW folder.

Also, an XML file can be created for a silent uninstall.



OCT is available for Office (2007 or later) but other related software such as Microsoft Lync, Visio, Project, OneNote etc.

Hiding an entry in Add/Remove Programs

At some point, one might want to hide one or more entries added by software setup(s) in Add/Remove Programs (also known as “Programs and Features”, ” Uninstall a Program”, “Add or Remove Programs” under Windows 7).

Here’s a neat trick to do this:

  • Open regedit
  • Look for the Uninstall key of the software. That’s under:
    • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall          OR
    • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall (in case of a 32-bit installation on a 64-bit machine)
  • The key can be a GUID or an actual software name (like “Adobe AIR”, for example).
  • Under that key, create a DWORD value called SystemComponent and set it to 1
  • Done.

In case of a silent installation of an MSI, you can add ARPSYSTEMCOMPONENT=1 to the command line. This will have the same effect as the manual sequence described above.

Stealth Google Chrome 34


For those who are not able to install Google Chrome on their work PC, due to proxy blocking the original installer or due to lack of permissions, I’ve created a stripped-down version of the Chrome installation.

Also, some corporations forbid browser alternatives, forcing you to use Internet Explorer. Usually, they scan the users’ PCs and send them warnings (or worse) if a “forbidden” software is found installed. This version tries to be as stealth as possible while keeping the complete functionality. Some files are renamed, some others removed. Registry info is also changed so that SCCM (or other tools that might be used) won’t be able to find it. Of course, this doesn’t mean it is completely stealth, but you have a fair chance of getting away it with. 🙂



If you have admin permission, download it here.

If you do NOT have admin permissions on the PC, then download this version.

The installation will run unattended. There is no interaction needed.

If you want to install the application in a different folder than the default one (chosen by us), use the following command line:

msiexec /i [full_path_of_MSI] INSTALLDIR=[your_desired_installdir_here]



Please note that this version will NOT be able to install updates automatically. Therefore, please check our *Stealth Google Chrome Download page* on a regular basis, for package updates.



Right click on the MSI file and select Uninstall to remove it, or go to Add/Remove Programs and remove it from there (Stealth GC).

Internet Explorer Silent Installation and Uninstall

This article applies to Internet Explorer 9, Internet Explorer 10 and Internet Explorer 11.

Internet Explorer Silent Installation


IE 9 can be downloaded here. SourceFile = IE9-Windows7-x64-enu.exe
I’ve downloaded the English 64bit version, for Windows 7. It’s not really relevant, the command line will be the same.

IE 10 can be downloaded here. SourceFile = IE10-Windows6.1-x64-en-us.exe
IE 11 can be downloaded here. SourceFile = IE11-Windows6.1-x64-en-us.exe

Silent Install

PathtoSourceFile\SourceFile /quiet /update-no /norestart /log:LogFolder

Attention: the log parameter refers to the folder in which a log file will be created.

With this command line, you can safely upgrade an existing installation; no extra actions are required.

Internet Explorer Silent Uninstall (Rollback)

Uninstalling is the trickier part.

Create a batch file with the following content:

FORFILES /P %WINDIR%\servicing\Packages /M Microsoft-Windows-InternetExplorer-*~XXX.?.????.?????.mum /c “cmd /c echo Uninstalling package @fname && start /w pkgmgr /up:@fname /norestart /quiet”

where XXX is “9”, “10” or “11”, depending on which version you need to remove.
This command line will remove the mum files belonging to the corresponding version of IE, from Windows\servicing\Packages.

The end result will be a rollback to the previous version of IE. If you’re uninstalling “11” and you had 9, then that’s what you’ll obtain. If you apply the same removal procedure for “9”, then you’ll rollback to 8 or whatever was present on the machine initially.

A reboot will be needed after each installation OR uninstall.

Error 40007

If, during the installation of IE, you get an error code of 40007, it means that some prerequisites (hotfixes) are missing. It can also be that they’ve just been installed, but the PC hasn’t rebooted. Reboot the machine and try the installation again.

Silent Installations using Inno Setup

Inno Setup is a free installer for Windows software. It is not as popular as Windows Installer (MSI), but still widely used.

Applications distributed using Inno Setup can usually be installed silently, unless there are custom actions that didn’t take into consideration the scenario of a silent install.

The most used parameters of an Inno Setup are:

/SILENT – Runs the setup silently. The wizard and the background window are not displayed. However, the installation progress will be shown. In case of a necessary reboot, if the /NOREBOOT parameter is NOT mentioned, there will be a prompt asking for reboot.
/VERYSILENT – Same as /SILENT, but it doesn’t show the progress. If the /NOREBOOT switch is not used and a reboot is needed, the setup will automatically restart the machine.
/LOG=”filename” – logs the installation to a file. Quotes are important.
/NORESTART – suppresses the reboot messages and instructs setup not to restart when the installation is done, even if it’s needed.
/SAVEINF=”filename” – saves the installation configuration to the specified file. Quotes are important.
/LOADINF=”filename” – loads a previously saved installation configuration.

Other switches:
/SUPPRESSMSGBOXES – only when combined with the /SILENT and /VERYSILENT switches, it suppresses most of the dialog boxes. When there’s a choice, it uses the default option (No for overwriting files, Abort when there’s an Abort/Retry option, Yes when asked about keeping a newer file, Yes for restart).
/SP- – disables the “This will install…” prompt at the beginning.
/CLOSEAPPLICATIONS – Closes applications that hold files needing to be updated.
/NOCLOSEAPPLICATIONS – Prevents the setup from closing applications that hold files needing to be updated.
/RESTARTAPPLICATIONS – Applications closed by the setup will restart.
/NORESTARTAPPLICATIONS – Closed applications will not restart.
/DIR=”path” – Sets the installation directory. It overrides whatever the user has mentioned in the Select Destination Path wizard page. Full path.
/GROUP=”folder name” – Provides the name of the shortcut folder.
/NOICONS – No shortcuts created.
/TYPE=typeName – Overrides the default setup type (Complete, Custom, Minimal)
/COMPONENTS=”component1,component2,etc” – selects a list of components to be installed
/TASKS=”task1,task2,etc” – selects a number of tasks (such as desktopicon, fileassoc)
/MERGETASKS=”task3,task4″ – adds additional tasks to the default ones.
Both task params can also negate (!) a task: !desktopicon
/PASSWORD=password – specifies a password to use

For Uninstall, the unins000.exe (or higher index) from the installation directory must be called, with one of the following parameters:

Adobe Flash Player 12 Silent Installation

For the deployment of Adobe Flash Player 12, one needs to apply for a distribution license (link here). Afterwards, you’ll receive a link where you can download the two MSIs:



Install them silently, using the following command lines:

msiexec /i “sourceFolder\install_flash_player_12_active_x.msi” REBOOT=ReallySuppress ALLUSERS=1 /qn /L*v C:\WINDOWS\Temp\flash_player_12_active_x.log

msiexec /i “sourceFolder\install_flash_player_12_plugin.msi” ” REBOOT=ReallySuppress ALLUSERS=1 /qn /L*v C:\WINDOWS\Temp\flash_player_12_plugin.log

Most probably, you`ll also want to disable the Auto Update feature. You can do that by creating/copying a file called mms.cfg in Windows\System32\macromed\flash\ (Or Windows\syswow64\macromed\flash for 64bit installations). The file must contain the following 3 lines:




To do a silent uninstall, run msiexec /x productCodeHere /qn /l*v logFileName for each msi, using its product code.

SAP Visual Enterprise Client Silent Installation

Assuming that you have the installer from SAP, called VisualEnterpriseViewer_7.0.1.178_Complete.exe, this is how to install SAP Visual Enterprise Viewer silently.

There is an easy way to install it with default options:

VisualEnterpriseViewer_7.0.1.178_Complete.exe /Silent

But that’s not the way we would recommend. There’s a more elegant way of doing it.

  1.  First, unzip the executable to a folder of your choice.
  2. Run Setup\NwSapSetupAdmin.exe
  3. Create New Package. Give it a relevant name, for example: “SAPVisualEnterpriseViewer_7.0.1.178_Complete”
  4. Customize your installation by selecting the desired options
  5. Close it.

Your SAP “package” info will be stored in Setup\SapPackageSetup.xml

In order to install it silently, run the following command line:

Setup\NwSapSetup.exe /Silent /Package=”SAPVisualEnterpriseViewer_7.0.1.178_Complete”

Log files will be created under %ProgramFiles%\SAP\SapSetup\LOGs (or ProgramFiles(x86) ).


For a silent removal of the package, run the following command line:

%ProgramFiles%\SAP\SapSetup\NWSapSetup.exe /uninstall /Product=”DVM+DVC” /Silent

(Or %ProgramFiles(x86)% )