Unsigned Update.exe file populating in squirreltemp files when using MSTeamsSetup.exe - AppLocker blocking

TryingNotToBeLikeABullInAChinaShop 30 Reputation points
2025-10-30T12:12:13.91+00:00

Given all the advice for AppLocker is to allow by publisher, this seems counter productive. Can obviously do a path or hash exclusion but path exclusions for "update.exe" file seems easily guessed at this point if hackers know about Microsoft needing these exceptions to update, and hash could change any time you update the installer. Can these files be singed going forwards? The MSTeamsSetup.exe is signed so runs fine but then calls the updater which is not signed.
If these cant be signed, what is Microsoft's official advice for these types of file? Thanks

Microsoft Teams | Development
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Steven-N 11,780 Reputation points Microsoft External Staff Moderator
    2025-10-30T13:49:23.53+00:00

    Hi TryingNotToBeLikeABullInAChinaShop

    Thank you for reaching out to Microsoft Q&A forum

    Based on your description, you’re concerned about AppLocker guidance recommending publisher rules, but certain updater executables (like update.exe for Microsoft Teams) are unsigned. This makes publisher rules ineffective, while path rules seem risky and hash rules require frequent updates and you’re asking whether these files can be signed in the future and what Microsoft’s official advice is for handling them.

    As stated in AppLocker application control policies in Microsoft Teams. AppLocker is designed to enforce application control through conditions such as publisher, path, and file hash. Publisher rules are preferred because they remain valid across updates and provide stronger security than path or hash rules. However, unsigned executables cannot use publisher conditions, which creates a challenge for components like update.exe in Teams.

    Unsigned files pose a higher security risk because:

    • Path rules can be exploited if the directory is user-writable.
    • Hash rules break after every update, requiring constant maintenance.

    Currently, Microsoft temporary does not guarantee that all updater components will be signed in future releases. Therefore, organizations must plan for scenarios where unsigned files exist.

    That said, in order to maintain security and operational continuity, you should consider these steps:

    1. Use Publisher Rules for Signed Components Apply publisher conditions for the main Teams executables and other signed binaries.
    2. Apply Hash Rules for Unsigned Updaters If the updater must run, create hash-based rules for those files. Test in audit mode before enforcement to avoid breaking updates.
    3. Avoid Broad Path Rules Do not allow entire user-writable directories. If path rules are unavoidable, lock down permissions to reduce exploitation risk.
    4. Evaluate WDAC (Windows Defender Application Control) For stronger enforcement, WDAC ensures only signed code runs and offers better protection than AppLocker.
    5. Monitor and Review Regularly Reassess rules after updates and maintain a change management process for hash-based exceptions.

    For more information:

    https://free.blessedness.top/en-us/windows/security/application-security/application-control/app-control-for-business/applocker/applocker-overview

    https://free.blessedness.top/en-us/windows/security/application-security/application-control/app-control-for-business/appcontrol

    Please feel free to leave a comment below if you require any additional help. 

    Best regards


    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".     

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.