Skip to main content
Question

Microsoft App Control and ETX

  • June 22, 2026
  • 4 replies
  • 44 views

uelsner


My company intends to increase the security of clients by using Microsoft App Control.
This basically means that any executable not located in %programfiles...% must be digitally signed with our company key.
Now signing the executables is  a bit of a hassle but generally not really a problem. 
But for ETX, two security mechanisms come in to conflict. The ETX launcher checks the hash value of the main (Native Client) executable but if the executable is signed by us the hash value changes. 


So: 
sign the main executable -> The ETX Launcher won't start it.
Don't sign the main executable: Microsoft App Control prevent execution.
Oops!

Has anybody found a solution for this problem?

4 replies

Nathan Kidd
  • Rocketeer
  • June 22, 2026

That’s an interesting problem. As you note, ETX does verify the whole file hash, and that’s incompatible with adding additional signatures. I’ve started an internal discussion, and recommend you open a ticket via https://support.rocketsoftware.com/ that we can eventually link to.


uelsner
  • Author
  • New Participant
  • June 23, 2026

Created case 01173194


Nathan Kidd
  • Rocketeer
  • June 24, 2026

I see you’re getting help there. For public record, ETX does support using an ETX Client that has been manually deployed to Program Files. (Though as an admin I’d really rather add the Rocket certificate to an approved list, if possible, to avoid manual deployment work.)


uelsner
  • Author
  • New Participant
  • June 25, 2026

I agree that adding the Rocket certificate would be easier (for my app at least).
But my colleagues need to administer a large amount of clients (I believe we are close to 6 digit Windows clients) so I can understand why they try for a very standardized approach.