blocks|key|66898|text|我假设您使用的是签名选项卡--但它只对setup.exe进行签名--而不是实际的application.exe文件。这样，在安装应用程序时，您不会得到“警告”提示，但在运行应用程序时，您会得到它。您需要分别对application.exe进行签名--而且在Visual中没有UI，您需要使用PostBuild任务：https://stackoverflow.com/a/18636102/1246870|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|66899|我不知道为什么这在Windows+7中运行良好--在我的例子中，Win7也不起作用--但是根据您的评论，这可以是解决方案……|66900|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/18636102/1246870^0|4D|18|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]]|C|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]]]

I assume you are using Signing tab - but it only signs setup.exe - and not the actual application.exe file. This way you don't get a "warning" prompt when you install the app, but you get it when you run it. You need to sign application.exe separately - and there is no UI for that in Visual Studio, you need to use PostBuild task: <a href="https://stackoverflow.com/a/18636102/1246870">https://stackoverflow.com/a/18636102/1246870</a>

i'm not sure why this works okay in Windows 7 - in my case Win7 did not work as well - but based on your comment, this can be the solution...

blocks|key|1236026|text|非常感谢avs099+--把它标记为答案，因为它使我得到了迄今为止最接近的答案！最后我使用了BeforePublish..。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1236027|使用IE11，我将证书导出到一个目录(+Internet选项>内容>证书>导出)，然后将其复制并粘贴到项目中。然后卸载项目，并在|1236028|<Target+Name="BeforePublish">
</Target>|code-block|syntax|javascript|1236029|标签|1236030|<Exec+Command="&quot;C:\Program+Files+(x86)\Microsoft+SDKs\Windows\v7.1A\Bin\signtool.exe&quot;+sign+/f+&quot;MyCert_2016.pfx&quot;+/p+&quot;MySecretPassword&quot;+/t+http://timestamp.comodoca.com/authenticode+&quot;C:\Users\MyName\My+Documents\Visual+Studio+2015\Projects\MyProject\MyProject\obj\Release\My.exe&quot;"+/>|1236031|然后重新加载该项目--已经发布，现在它在Windows+10上运行，没有任何异议--就像它从蓝色警告变为红色警告一样：|1236032|​|1236033|📷|atomic|offset|length|1236034|1236035|在avs099和此链接的回答之间，在大量构建错误之后，我理解了这一点--+本站提供了一些信息，但是将证书放置在一个完整的路径中，而不是相对的。|1236036|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/506cc1802e593cd3184452d6073c1b6c.jpg|imageAlt|1|LINK|MUTABLE|url|http://blogs.msdn.com/b/vsnetsetup/archive/2013/01/09/windows-smartscreen-prevented-an-unrecognized-app-from-running-running-this-app-might-put-your-pc-at-risk.aspx/|2|https://robindotnet.wordpress.com/2013/02/24/windows-8-and-clickonce-the-definitive-answer-2/^0|0|0|0|0|0|0|0|0|1|0|0|0|8|3|1|11|2|2|0^^$0|@$1|2|3|4|5|6|7|1E|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1F|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|1G|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|1H|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|1I|8|@]|9|@]|A|$G|H]]|$1|M|3|N|5|6|7|1J|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|1K|8|@]|9|@]|A|$]]|$1|Q|3|R|5|S|7|1L|8|@]|9|@$T|1M|U|1N|1|1O]]|A|$]]|$1|V|3|P|5|6|7|1P|8|@]|9|@]|A|$]]|$1|W|3|X|5|6|7|1Q|8|@]|9|@$T|1R|U|1S|1|1T]|$T|1U|U|1V|1|1W]]|A|$]]|$1|Y|3|-4|5|6|7|1X|8|@]|9|@]|A|$]]]|Z|$10|$5|11|12|13|A|$14|15|16|-4]]|17|$5|18|12|19|A|$1A|1B]]|1C|$5|18|12|19|A|$1A|1D]]]]

With many thanks to avs099 - have marked that as the answer as it got me the closest so far! I ended up using BeforePublish..

Using IE11 I exported the certificate to a directory ( Internet Options > Content > Certificates > Export ), then copied and pasted it into the project. Then unloaded the project and added the following between

<pre><code>&lt;Target Name="BeforePublish"&gt;
&lt;/Target&gt;
</code></pre>

tags

<pre><code>&lt;Exec Command="&amp;quot;C:\Program Files (x86)\Microsoft SDKs\Windows\v7.1A\Bin\signtool.exe&amp;quot; sign /f &amp;quot;MyCert_2016.pfx&amp;quot; /p &amp;quot;MySecretPassword&amp;quot; /t http://timestamp.comodoca.com/authenticode &amp;quot;C:\Users\MyName\My Documents\Visual Studio 2015\Projects\MyProject\MyProject\obj\Release\My.exe&amp;quot;" /&gt;
</code></pre>

Then reloaded the project - published and now it runs on Windows 10 without any objections - just as well as it had gone from blue warnings to red ones :-(

<a href="https://i.stack.imgur.com/2GoEO.jpg" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/2GoEO.jpg" alt="Red Warning"></a>

Between the answer by avs099 and <a href="http://blogs.msdn.com/b/vsnetsetup/archive/2013/01/09/windows-smartscreen-prevented-an-unrecognized-app-from-running-running-this-app-might-put-your-pc-at-risk.aspx/" rel="nofollow noreferrer" title="This Link">this link</a> I made sense out of it after lots of build errors - <a href="https://robindotnet.wordpress.com/2013/02/24/windows-8-and-clickonce-the-definitive-answer-2/" rel="nofollow noreferrer">this site</a> was informative but placed the certificate in a full path, not relative

blocks|key|1236094|text|为了任何在2021年面临这种情况的人的利益：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1236095|不要使用Comodo/Sectigo时间戳服务器。|1236096|当我切换到Digicert的服务器时，我的问题就消失了(使用"http://timestamp.digicert.com“代替时间戳服务器URL)。|offset|length|1236097|或者，您可以将时间戳服务器保留为空白--但是如果没有加密时间戳，则当证书过期时，代码的签名将无效。(有了时间戳，只要创建时间戳时签名是有效的，签名就仍然有效。)|1236098|在Sectigo时间戳服务器总是使用SHA384而不是SHA1上有更多的细节。|1236099|entityMap|0|LINK|mutability|MUTABLE|url|http://timestamp.digicert.com/|1|https://stackoverflow.com/questions/65146785/sectigo-timestamp-server-always-using-sha384-instead-of-sha1^0|0|0|V|T|0|0|0|1|U|1|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|W|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|X|8|@]|9|@$F|Y|G|Z|1|10]]|A|$]]|$1|H|3|I|5|6|7|11|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|12|8|@]|9|@$F|13|G|14|1|15]]|A|$]]|$1|L|3|-4|5|6|7|16|8|@]|9|@]|A|$]]]|M|$N|$5|O|P|Q|A|$R|S]]|T|$5|O|P|Q|A|$R|U]]]]

For the benefit of anyone facing this in 2021:
Don't use the Comodo/Sectigo timestamp server.
My issues went away when I switched to Digicert's server (use &quot;http://timestamp.digicert.com&quot; instead for the Timestamp Server URL).
Alternatively, you can leave the timestamp server blank -- but without a cryptographic timestamp, your code's signature will be invalid when the certificate expires. (With a timestamp, the signature will stay valid so long as it was valid when the timestamp was created.)
More details at <a href="https://stackoverflow.com/questions/65146785/sectigo-timestamp-server-always-using-sha384-instead-of-sha1">Sectigo timestamp server always using SHA384 instead of SHA1</a>.

blocks|key|67086|text|我看到您使用sha1证书和不建议使用sha1是因为这些原因。如果您有sha256证书，则可以使用"http://timestamp.comodoca.com/?td=sha256"。参见更多信息..。“。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|67087|entityMap|0|LINK|mutability|MUTABLE|url|https://sectigo.com/knowledge-base/detail/Important-change-announcement-deprecation-of-SHA-1-1527076085906/kA01N000000zFKE|1|https://pkic.org/2014/01/30/why-we-need-to-move-to-sha-2/|2|http://timestamp.comodoca.com/?td=sha256|3|https://sectigo.com/knowledge-base/detail/Code-Signing-for-Windows-1527076085065/kA01N000000zFK1^0|D|9|0|P|4|1|1D|15|2|2L|7|3|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@$A|S|B|T|1|U]|$A|V|B|W|1|X]|$A|Y|B|Z|1|10]|$A|11|B|12|1|13]]|C|$]]|$1|D|3|-4|5|6|7|14|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]|L|$5|G|H|I|C|$J|M]]|N|$5|G|H|I|C|$J|O]]|P|$5|G|H|I|C|$J|Q]]]]

I see you are using sha1 certificate and <a href="https://sectigo.com/knowledge-base/detail/Important-change-announcement-deprecation-of-SHA-1-1527076085906/kA01N000000zFKE" rel="nofollow noreferrer">sha1 is deprecated</a> because of <a href="https://pkic.org/2014/01/30/why-we-need-to-move-to-sha-2/" rel="nofollow noreferrer">these reasons</a>. If you have a sha256 cert you can use &quot;http://timestamp.comodoca.com/?td=sha256&quot;. See <a href="https://sectigo.com/knowledge-base/detail/Code-Signing-for-Windows-1527076085065/kA01N000000zFK1" rel="nofollow noreferrer">more info...</a>

blocks|key|67150|text|如果有人在2022年搜索时出现在这里：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|67151|我更新了我的证书(SHA384)，并收到了同样的“未知发布者”警告。|67152|我尝试了几个时间戳服务器，新的项目，但ClickOnce发布总是使用sha1摘要签名的执行，安装和清单。|67153|原来是bug+in+MSBuild+<+17.0|offset|length|67154|即使是最新版本的VS2019也无法工作(MSBuild+16)，所以我不得不升级到VS2022社区。|67155|提示:+Sectigo时间戳服务器http://timestamp.sectigo.com/似乎运行良好|67156|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/dotnet/msbuild/issues/6732|1|http://timestamp.sectigo.com/^0|0|0|0|3|L|0|0|0|H|T|1|0^^$0|@$1|2|3|4|5|6|7|X|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Y|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|Z|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|10|8|@]|9|@$H|11|I|12|1|13]]|A|$]]|$1|J|3|K|5|6|7|14|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|15|8|@]|9|@$H|16|I|17|1|18]]|A|$]]|$1|N|3|-4|5|6|7|19|8|@]|9|@]|A|$]]]|O|$P|$5|Q|R|S|A|$T|U]]|V|$5|Q|R|S|A|$T|W]]]]

In case anyone ends up here while googling in 2022:
I renewed my certificate (SHA384) and got the same &quot;Unknown Publisher&quot; warning.
I tried several timestamping servers, fresh new project but ClickOnce publishing was always using sha1 digest for signing the exe, setup and manifest.
Turns out its a <a href="https://github.com/dotnet/msbuild/issues/6732" rel="nofollow noreferrer">bug in MSBuild &lt; 17.0</a>
Even the latest Version of VS2019 didn't work (MSBuild 16) so i had to upgrade to VS2022 Community.
Hint: The Sectigo timestamp server <a href="http://timestamp.sectigo.com" rel="nofollow noreferrer">http://timestamp.sectigo.com</a> seems to work fine

The vast majority of our business users run Windows 7, and our ClickOnce application installs, updates and runs as it should without any pop-up warnings. 

The same application is throwing up the following on Windows 10

<a href="https://i.stack.imgur.com/nQRma.jpg" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/nQRma.jpg" alt="Warning number one"></a>

<a href="https://i.stack.imgur.com/ShSIO.jpg" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/ShSIO.jpg" alt="Unknown Publisher"></a>

Of course 'More info' appears to be part of the text rather than something you can click with 'Don't run' appearing to be the only option

If you do click 'More Info' it states the publisher is unknown (although it displayed it just fine whilst updating!!!)

The Code Signing Certificate is valid and it still installs/updates and runs without warnings on Win 7 boxes.

Any ideas what they have changed now?

Thanks

<a href="https://i.stack.imgur.com/tbFJM.jpg" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/tbFJM.jpg" alt="enter image description here"></a>

Signed ClickOnce app throwing 'Unknown Publisher' with Windows 10

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我们绝大多数的业务用户运行Windows 7，我们的ClickOnce应用程序安装、更新和运行都是应该的，没有任何弹出警告。在Windows 10上，同样的应用程序会弹出以下内容​​​​当然，“更多的信息”似乎是文本的一部分，而不是您可以单击的“不要运行”，这似乎是唯一的选择如果您确实单击了“更多信息”，它就会声明发布...

问有签名的ClickOnce应用程序用Windows 10抛出“未知发行者”
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问有签名的ClickOnce应用程序用Windows 10抛出“未知发行者”EN