-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Windows: Command failed: powershell.exe ... Get-AuthenticodeSignature #3059
Comments
You can help us out by opening up a Command Prompt, typing |
@scottnonnenberg Running the Requested Command:
|
Just got the same error message when launching Signal Desktop (after launching it again, it updated itself to 1.20.0):
Yes (e. g. Chocolatey) |
The next thing we could try is to try to run the command shown above (maybe choose an arbitrary binary as a target, or a newly-downloaded Signal Desktop installer) and see what the specific error coming back from powershell is. |
Which command? This?
If yes, this is the output with a newly downloaded Signal Desktop installer:
|
Okay, now pipe it to the JSON tool with the rest of the command line: |
Does this piping work with the cmd console? I've tried the full command before, but this only seems to work without an error (the result is basically the same output as mentioned above, messily formatted) inside of PowerShell. Using the cmd console, I'm getting an error (it says that "ConvertTo-Json" is misspelled or cannot be found). |
This page seems to show examples of using it piped: https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.utility/convertto-json?view=powershell-6 In the past we've had problems due to customization of powershell configuration... but this seems a bit like a command just isn't available anymore or something. Maybe the pipe needs to be escaped because Command Prompt is parsing it differently? The whole thing is strange, because this has worked in the past. Is it a new Powershell version causing the problem? Configuration on a specific machine? Installation source for Powershell, if you're installing via Chocolatey? |
Just |
@scottnonnenberg-signal Command:
Output:
|
Running the command gets me this:
|
@c0fe |
@RiseT ok this is the output:
|
It does seem to be a quotation thing. Very interesting. Also might just be a breaking change in a new version of powershell causing this, as well. |
I got the same error today as reported above. Signal crashed, but when I reopened it it opened fine. Here's what I get when I run the command in powershell:
Here's the contents of that folder (the file mentioned is not there):
|
@dbolton Though I suppose it could be a problem with the target file not existing on disk when that command is run. Too bad the error message from running that command isn't printed to the console. |
This happened again:
Signal Version: 1.21.0 Debug Log: https://debuglogs.org/bb8bb77d89bb9762ae9150d8bdd73d7abce7ade9fa576c8d62f7f49a494e9416 |
So is the theory that the file is actually not there sometimes, and that's why we run into errors? |
@scottnonnenberg-signal So do you consider it unlikely that the missing quotation marks as mentioned above could be the culprit? |
Looks like the latest version of the powershell exec code does manage all the various arguments better: https://github.com/electron-userland/electron-builder/blob/a0026a7422977b449709f8a662d9dd30600a31b1/packages/electron-updater/src/windowsExecutableCodeSignatureVerifier.ts#L13 As of v1.21.0 we're on a version of |
@scottnonnenberg i haven't seen this reoccur. Maybe close the issue? |
@scottnonnenberg I spoke too soon. The issue has occurred again. Here are the details: Signal Version: 1.22.0 Error:
|
I got this as a rejected promise from another computer: https://debuglogs.org/c46a6ae95b2a185d06d3d4a366a32d43537e8189fd390fb02e2046aa0e215101 |
@c0fe Which rejected promise, exactly? Logs are big; we need a little help to know where to look in the log. |
@scottnonnenberg not sure, I forgot to grab the error message. will try again. |
We can replace the PowerShell with a native verify signature module to resolve all powershell problems. |
Bug Description
I was not using my PC for a little while, the screen turned back. When I came back and turned the PC on I saw the error message.
Steps to Reproduce
Not sure on how to reproduce, was not able to.
Platform Info
Signal Version:
1.19.0
Operating System:
Windows 10 Professional
Linked Device Version:
4.31.6
Error:
Link to Debug Log
https://debuglogs.org/a05dcdfb5897c94eef2359f6fc2e06db301c2408f26f342d6e861b5f912f2396
The text was updated successfully, but these errors were encountered: