BiztalkFactory.Powershell.Extensions is not installed on this computer



    PowerShell - BizTalkFactory PowerShell Provider

    1. Download and install

    2. Navigate to: C:\Program Files (x86)\Microsoft BizTalk Server 2013 R2\SDK\Utilities\PowerShell

    1. Open the readme.txt and follow the steps:

    1. Open a command prompt as an administrator

    2. Change directory to the folder containing the binaries - \SDK\Utilities\PowerShell under the base install location

    3. Run the following command to install/register the dlls %windir%\Microsoft.NET\Framework\v4.0.30319\InstallUtil.exe .\BizTalkFactory.PowerShell.Extensions.dll

    4. Open a powershell console as admin in x86 mode and set execution policy as remote-signed:Set-ExecutionPolicy –ExecutionPolicy RemoteSigned

    5. Add the PS snap-in using the usual approach:

       Add-PSSnapin –Name BiztalkFactory.Powershell.Extensions

    cd C:\Program Files (x86)\Microsoft BizTalk Server 2013 R2\SDK\Utilities\PowerShell

    %windir%\Microsoft.NET\Framework\v4.0.30319\InstallUtil.exe .\BizTalkFactory.PowerShell.Extensions.dll

    In the PowerShell window as administrator:  Set-ExecutionPolicy –ExecutionPolicy RemoteSigned   type “Y” when asked

    Add-PSSnapin –Name BiztalkFactory.Powershell.Extensions

    1. Why ?

    Monday, March 20, 2017 4:08 PM

All replies

  • By default, Windows PowerShell targets .net framework 2.0.In order to be able to use the provider with BizTalk Server 2013 or BizTalk Server 2013 R2 assemblies, 
    Windows PowerShell must be configured to explicitly support both versions of the .net framework. 
    Therefore, the configuration file for Windows PowerShell must be updated like so: 
    •     First, find the location of the Windows PowerShell configuration file: %SystemRoot%\syswow64\WindowsPowerShell\v1.0\powershell.exe.config [x64] %SystemRoot%\system32\WindowsPowerShell\v1.0\powershell.exe.config [x86]

    •     If this file does not exist, it must be created. 
    •     In the configuration file, add the relevant section, 
    highlighted in the following text: 


    <supportedRuntimeversion="v4.0" />     

    Did you do that?

    Monday, March 20, 2017 4:23 PM
    1. File created - powershell.exe.config

    <?xml version="1.0" encoding="utf-8"?>



    <supportedRuntime version="v4.0" />     



    Monday, March 20, 2017 6:33 PM
  • Please note:

    System32 is the64-bit Windows system directory and SysWOW64 is the 32-bit Windows system directory.

    On your picture the system32 directory is shown, so I think you started the 64 -bit powershell version, be sure that you start the x86 version (32-bit) version of powershell.

    Monday, March 20, 2017 6:57 PM