title: Cannot import the keyfile 'blah.pfx' - error 'The keyfile may be password protected'
body: <p>We just upgraded our Visual Studio 2008 projects to Visual Studio 2010. All of our assemblies were strong signed using a <a href="http://en.wikipedia.org/wiki/Verisign" rel="noreferrer">Verisign</a> code signing certificate. Since the upgrade we continuously get the following error:</p>
  
  <blockquote>
    <p>Cannot import the following key file: companyname.pfx. The key file may be password protected. To correct this, try to import the certificate again or manually install the certificate to the Strong Name CSP with the following key container name: VS_KEY_3E185446540E7F7A </p>
  </blockquote>
  
  <p>This happens on some developer machines and not others. Some methods used to fix this that worked some of the time include:</p>
  
  <ul>
  <li>Re-installing the key file from Windows Explorer (right click on the PFX file and click Install)</li>
  <li>Installing Visual Studio 2010 on a fresh machine for the first time prompts you for the password the first time you open the project, and then it works. On machines upgraded from Visual&nbsp;Studio&nbsp;2008, you don't get this option.</li>
  </ul>
  
  <p>I've tried using the <a href="http://msdn.microsoft.com/en-us/library/k5b5tt23.aspx" rel="noreferrer">SN.EXE</a> utility (Strong Name Tool) to register the key with the Strong Name CSP as the error message suggests, but whenever I run the tool with any options using the version that came with Visual Studio 2010, SN.EXE just lists its command line arguments instead of doing anything. This happens regardless of what arguments I supply.</p>
  
  <p>Why is this happening, and what are clear steps to fix it?  I'm about to give up on <a href="http://en.wikipedia.org/wiki/ClickOnce" rel="noreferrer">ClickOnce</a> installs and Microsoft code signing.</p>