Serialize concurrent sessions; demote critical-package retry note to Info - #12
Merged
Merged
Conversation
…Info Two BootstrapMate sessions running at once (an MDM-triggered run racing an interactive one) share the cache directory and the Windows Installer mutex, so they corrupt each other: 1618s, cache files deleted mid-install, "file in use" failures. Add a Global\BootstrapMate.SingleInstance mutex - the second session waits (up to 30 minutes) for the first to finish, then runs normally, so concurrency becomes a queue instead of an error class. Also log "CRITICAL PACKAGE ... aggressive retry strategy" at Info: it describes normal behavior for critical packages, not a problem.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Companion to windowsadmins/sbin-installer#9. A second BootstrapMate session now waits on Global\BootstrapMate.SingleInstance instead of racing the first (shared cache + MSI mutex made concurrent runs cascade into 1618/file-in-use failures, as seen 2026-07-21). Also demotes the critical-package aggressive-retry line from Warning to Info.