microsoft / microsoft/AzureStorageExplorer

Electron 43 Windows executable fails PME real signing

Open
#9,165 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

:copilot: copilot
Dominant language
No language data
Stars
452
Forks
92
Avg merge
15h 20m
Merged PRs (30d)
3

Description

Bug description

The scheduled Storage Explorer 1.46.0 release build fails PME real signing for both Windows x64 and ARM64. StorageExplorer.exe is rejected with SignTool Error: SignedCode::Sign returned 0x800700C1 (ERROR_BAD_EXE_FORMAT).

Evidence

The prior test-sign validation build succeeded but is not valid release proof because it was a pull request build using test signing: https://dev.azure.com/devdiv/DevDiv/_build/results?buildId=15101623

The earlier fix PR upgraded @electron/fuses to v2 but did not fix the official PME signing path: https://dev.azure.com/devdiv/DevDiv/_git/StorageExplorer/pullrequest/774218

A canceled manually queued build is explicitly excluded as evidence. Final validation must come from a scheduled real-signed build on rel/1.46.0.

Expected behavior

The packaged Electron 43 Windows executable remains a valid, signable PE after all packaging mutations and succeeds in the scheduled PME real-signing release pipeline.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by inspecting the Electron 43 packaging mutations on rel/1.46.0 and the earlier @electron/fuses v2 fix, then review the PME real-signing release pipeline. Done means StorageExplorer.exe remains a valid PE and a scheduled real-signed build succeeds for both Windows x64 and ARM64.

Written by the indexing model from the issue text.

Assessment

Tech stack
electron
Domain
build-system, release, security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.