Anith Gopal

An often-requested feature for VSTO add-ins is the ability to install an add-in for all users of a machine.

Hallo, man kann bei der Installation des App-V Clients unterschiedliche Parameter angeben um den Client gleich zu konfigurieren. Doch es gibt Situationen in denen diese Einstellungen, die man dem Installer mitgibt nicht gesetzt werden da andere Einstellungen Vorrang haben

I have seen few customers running into this issue. This forced me to write this blog.

In an attempt to make this easier to read here are a few terms I will be using frequently in this article: VSTOR = Visual Studio Tools for the Microsoft Office System (version 3.0 Runtime) (x86) VSTORSP1 = Visual Studio Tools for the Microsoft Office System (version 3.0 Runtime) Service Pack 1(x86) Bootstrapper = the clickonce bootstrapper that gets deployed with a VSTO customization when there are prerequisites checked (setup.exe) Some of our customers have raised an issue with the bootstrapper failing after deploying their customizations onto a user’s machine that has previously had VSTOR & VSTORSP1 installed. The problem occurs when an end user installs VSTOR followed by VSTORSP1 then subsequently uninstalls VSTOR from the Add/Remove Programs wizard

The TechNet forum post Windows Installer Crash  appears to have find a workaround for the issue by using start regedit navigate to HKLMSoftwareMicrosoftSQMClientWindowsDisabledSessions rename MachineThrottling to _MachineThrottling Original credit for the workaround was attributed to http://chris123nt.com/2009/01/18/sqm-client-causing-crashing-in-windows-7/