On the same Lync Server, some admins could open the Lync Server Management Shell normally while others got a blank blue window: no PS> prompt, no error, and no response to typing. I've seen this several times while running Lync 2013 and Skype for Business 2015 front-end pools. The cause is almost always one of the four below, and the quickest workaround is to load the Lync module yourself from a normal PowerShell window.

Applies to: Lync Server 2010 / 2013, Skype for Business Server 2015 / 2019 on Windows Server.

Lync PowerShell Blank

Quick fix: load the Lync module manually

Close the blank shell, open Windows PowerShell as Administrator, and run:

powershell.exe -noexit -command "cd $env:UserProfile; Import-Module 'C:\Program Files\Common Files\Microsoft Lync Server 2013\Modules\Lync\Lync.psd1'"

This is the same command the Lync Server Management Shell shortcut runs. Running it yourself from an elevated window gets around most per-user problems with the shortcut. Once it works, the normal Lync Management Shell shortcut usually starts working again too.

Lync Management Shell No Prompt

The module path depends on the version:

Version Module path
Lync Server 2010 C:\Program Files\Common Files\Microsoft Lync Server 2010\Modules\Lync\Lync.psd1
Lync Server 2013 C:\Program Files\Common Files\Microsoft Lync Server 2013\Modules\Lync\Lync.psd1
Skype for Business Server 2015 / 2019 C:\Program Files\Common Files\Skype for Business Server 2015\Modules\SkypeForBusiness\SkypeForBusiness.psd1

If you're not sure, check the Target field of the Management Shell shortcut (right-click → Properties).

Why the shell stays blank

1. The window is paused by QuickEdit mode

If someone clicked inside the console while it was loading, Windows pauses all output and the title bar starts with Select. The shell looks frozen but is just waiting. Press Esc or Enter and the prompt appears. This is the first thing to check, because it costs nothing.

2. Certificate revocation checks are timing out

The Lync cmdlets are signed, and Windows checks the publisher certificate's revocation list when loading them. On servers without internet access, that check can take minutes to time out, and the shell looks dead until it finishes. Typical signs:

  • The shell eventually opens if you wait 2–5 minutes.
  • It affects some admin accounts but not others, because the setting is per user.

To fix it, allow the server to reach Microsoft's CRL endpoints through your proxy. As a per-user workaround, open Internet Options → Advanced and clear Check for publisher's certificate revocation, then reopen the shell.

3. The account isn't elevated or lacks Lync rights

The shortcut needs to run elevated, and the account needs Lync admin rights, either membership in RTCUniversalServerAdmins or a Lync RBAC role such as CsAdministrator. If UAC blocks elevation or the account is missing these rights, the module can fail to load without showing an error. Run the shell with Run as administrator and check the account's groups:

whoami /groups | findstr /i "RTC CS"

4. A broken PowerShell profile for that user

Because it happens to "some admins but not others", look at the per-user PowerShell profile. A profile script that waits for input or errors early can block the prompt. Test without it:

powershell.exe -NoProfile -noexit -command "Import-Module 'C:\Program Files\Common Files\Microsoft Lync Server 2013\Modules\Lync\Lync.psd1'"

If this works, rename $PROFILE and fix the script inside it.

Check that the module loaded

Get-Module Lync
Get-CsPool | Select-Object Identity, Services

If Get-CsPool returns your pools, the shell is working.

A note on support status

Lync Server 2010 and 2013 are out of support, and Skype for Business Server 2015 and 2019 reached end of support in October 2025. If you still run one of these, plan the move to Skype for Business Server Subscription Edition or Teams. The troubleshooting steps above work the same on all of them.

Related: Install-CsMirrorDatabase failed on SfB 2015 / Lync 2013 · Enable-CsAdForest failed