Windows 10: Some digital certificate of service running on os ar signed by Microsoft Windows Publisher

Hi to all ...Reading a post in other discussion about security of running process, one of method used for find if is good service or not, is just view digital certificate property.But, i have observed that:Some digital certificate of service running on os ar signed by "Microsoft Windows Publisher" and other again signed by microsoft and released to "Microsoft Windows", and other again by "Microsoft Corporation" is it normal ?I have also see process runned by file named "WUDFHost.exe" in system32. It Seem part of wsl subsystem but in property of that tab called "Digital Firm" are not prese

:)

 

Can't run program with 'unknown publisher'

A little background might help.

Before you run a program, it's very important to be sure that the program is actually what it claims to be. For example: Just because a file
calls itself Winword.exe, how do you know it really is Microsoft Word?

Software developers vouch for their identity by obtaining a digital certificate, which is a proof of identity not unlike a passport or a driver's license. Digital certificates are issued by trustworthy organizations called certificate authorities.

Most people wouldn't begin to know (and why should they) how to check whether a program they want to run has a valid digital certificate, so the operating system does that for you by consulting the list of known and accepted certificate authorities included
in the operating system.

So here's what happened: Windows won't open your program because the certificate authority (the 'publisher') is not, or is no longer, on the list of known and accepted certificate authorities. The publisher might have been known and accepted in an earlier
list of certificate authorities, but the lists are updated frequently. The April 2018 update, or another update, revised the list of known publishers, and the publisher for your program ain't no longer on it.

None of this was invented by Microsoft, who is simply complying with internationally accepted standards for safe computing.

You're seeing the message because Windows can no longer guarantee that the program is safe to use.

 

Unknown Publisher when trying the installer(exe/msi) on windows 10

I'm using Visual Studio 2019 and have build "Installers(msi/exe)" using "Setup Wizard".

When i'm running the set.exe installer, the application "publisher" is being reported as "Unknown".

I've gone through some references and found that the setup.exe needs to be digitally signed with the certificate. So,

i have followed below steps to add digital signature to the setup.exe

1. Create Digital certificate (https://knowledge.digicert.com/solution/SO26065.html)

2. Using signtool i have digitally signed setup.exe

signtool.exe sign /f "E:\sample.pfx" /p "sample@123" /tr
http://timestamp.comodoca.com/rfc3161 /v "E:\setup.exeWhen
i try to run setup.exe locally, the application "publisher" is reported as "localhost" instead of "Unknown", but if i

run the same setup.exe on another system application "publisher" is reported as "Unknown"Please provide any suggestions on fixing this "Unknown
Publisher" issue

 

Microsoft May Already Have a Reliability Strategy

This is all they really had to do:

1. Update a code signing certificate - Windows 10 hardware dev