Martin Hinshelwood

A Scottish software developer: SSW Solution Architect & Microsoft Visual Studio ALM MVP
posts - 401, comments - 554, trackbacks - 57

My Links

News

Disclaimer

The opinions expressed herein are my own personal opinions and do not represent my employer's view in any way.






TwitterCounter for @MrHinsh

Locations of visitors to this page

Personal

Twitter












Tag Cloud

Article Categories

Archives

Post Categories

Image Galleries

Blogs I read

Blogs of Friends

Personal

Projects

VSTS

VS2005 - Signtool requires CAPICOM version 2.1.0.1

 

If you get the following error publishing a project,


Error    32    SignTool reported an error SignTool Error: Signtool requires CAPICOM version 2.1.0.1 or higher. Please copy the latest version of CAPICOM.dll into the directory that contains SignTool.exe. If CAPICOM.dll exists, you may not have proper permissions to install CAPICOM.
Follow these steps

  1. Download a self-extracting zip file from here.
  2. Extract capicom.dll from this zip file 
  3. Copy Paste capicom.dll into your "C:/windows/system32" directory 
  4. click Start -> Run and type "REGSVR32 capicom.dll" and press OK 
  5. You should now be able to publish via ClickOnce.

 

 

 

Print | posted on Wednesday, February 07, 2007 3:09 PM | Filed Under [ .NET ]

Feedback

Gravatar

# re: VS2005 - Signtool requires CAPICOM version 2.1.0.1

you rock!!
3/30/2007 6:55 PM | tony m
Gravatar

# re: VS2005 - Signtool requires CAPICOM version 2.1.0.1

Thank you for the hint :) It did the trick for me :)
6/12/2007 2:53 PM | Destro
Gravatar

# re: VS2005 - Signtool requires CAPICOM version 2.1.0.1

Finaly it works. Thanks for your help.
Ludwig
8/9/2007 9:01 PM | Ludwig
Gravatar

# re: VS2005 - Signtool requires CAPICOM version 2.1.0.1

10x, it took me some time to figure it out!
8/19/2007 4:06 PM | Alex Pinsker
Gravatar

# re: VS2005 - Signtool requires CAPICOM version 2.1.0.1

Thank You!
9/14/2007 6:38 PM | Eric
Gravatar

# re: VS2005 - Signtool requires CAPICOM version 2.1.0.1

I didn't have the same luck, instead it still doesn't work, but it was working yesterday... thank you for your support anyway
10/19/2007 12:26 PM | piero
Gravatar

# re: VS2005 - Signtool requires CAPICOM version 2.1.0.1

Thanks but your link to microsoft doesnt work, i found capicom.dll manually.
Great
11/2/2007 3:03 PM | Tyler
Gravatar

# re: VS2005 - Signtool requires CAPICOM version 2.1.0.1

Worked for me. Thanks for the link!
11/12/2007 4:01 PM | Andy
Gravatar

# re: VS2005 - Signtool requires CAPICOM version 2.1.0.1

Hello. I resolved this problem but i have a new problem.

My new error is this:
"SignTool Error: No certificates were found that met all the given criteria"

Anybody knows why this message appear in my execution?

This is the command line:
signtool sign -f datos\c1.pfx -p "pepito" -v datos\pepito.cab

where c1.pfx has been generated by IExplorer menu option.

Thanks!!! (sorry for my english ..........)
11/13/2007 12:21 PM | amparo
Gravatar

# re: VS2005 - Signtool requires CAPICOM version 2.1.0.1

That did it for me, too! Thanks a lot.

FYI, CAPICOM.dll is located at
c:\Program Files\Common\Microsoft Shared\CAPICOM

I also did copy the CAPICOM.dll from
Program Files\Common\Microsoft Shared\CAPICOM to the SignTool.exe directory, as recommended here: http://msdn2.microsoft.com/en-us/vstudio/aa.aspx

the SignTool.exe directory is
c:\Program Files\Microsoft Visual Studio 8\SDK\v2.0\Bin
source: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=&SiteID=1
11/13/2007 4:48 PM | Giuseppe Taibi
Gravatar

# re: VS2005 - Signtool requires CAPICOM version 2.1.0.1

Thanks you!!!!
3/10/2008 4:03 PM | yoshi
Gravatar

# re: VS2005 - Signtool requires CAPICOM version 2.1.0.1

Thanks a lot for the help.
3/28/2008 5:43 PM | Sachin
Gravatar

# re: VS2005 - Signtool requires CAPICOM version 2.1.0.1

Just wanted to add that this also can happen in Visual Studio 2008.

Copying capicom.dll from "c:\Program Files\Common\Microsoft Shared\CAPICOM" to "c:\windows\system32" and registering it with regsvr32 works fine...
4/9/2008 1:18 PM | Lars Peter Larsen
Comments have been closed on this topic.

Powered by: