Intellisense patch for PowerGUI Script Editor 2.4

If you experience intellisense issues when working with Exchange cmdlets in PowerGUI Script Editor (and by issues I mean that you have the Exchange snapin selected in File / PowerShell Libraries, and cmdlets work in your scripts just fine but intellisense does not appear) – suffer no more, there is now a fix available.

To get the patch simply:

  1. In PowerShell Script Editor, on the Tools menu, click Find Add-Ons Online,
  2. In the dialog box search for ‘fix‘,
  3. Select and Install the PowerGUI 2.4 IntelliSense issue fix (Exchange cmdlets).


3 Responses to “Intellisense patch for PowerGUI Script Editor 2.4”

  1. 2 March 22, 2011 at 11:34 am

    In my company I have problems to go online with PowerGui to install the fix. What can I do to install the “Fix” manually?

    • 3 Dmitry Sotnikov March 22, 2011 at 4:29 pm


      Yes, manual install is quite easy:

      1. Download this file:

      2. If you are on Vista/2008/Win7/2008 R2, right-click the zip file, and on the Properties dialog box, click the Unblock button.

      3. Extract the contents of the zip file into your Documents\WindowsPowerShell\Modules folder. You will have to create this folder if it does not exist.

      4. Open the PowerGUI Script Editor.

      5. Select File | PowerShell Libraries to open the Snapins/Modules dialog.

      6. Select the checkbox next to the “PowerGUI 2.4 IntelliSense issue fix” entry in the list of modules.

      7. Click on OK to close the Snapins/Modules dialog. At this point the fix is loaded.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

My Recent Tweets


The posts on this blog are provided “as is” with no warranties and confer no rights. The opinions expressed on this site are mine and mine alone, and do not necessarily represent those of my employer - WSO2 or anyone else for that matter. All trademarks acknowledged.

© 2007-2014 Dmitry Sotnikov

March 2011

%d bloggers like this: