Skip to content

Serialize concurrent sessions; demote critical-package retry note to Info - #12

Merged
rodchristiansen merged 1 commit into
mainfrom
fix/single-instance-guard
Jul 21, 2026
Merged

Serialize concurrent sessions; demote critical-package retry note to Info#12
rodchristiansen merged 1 commit into
mainfrom
fix/single-instance-guard

Conversation

@rodchristiansen

Copy link
Copy Markdown
Contributor

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.

…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.
@rodchristiansen
rodchristiansen merged commit 11def9a into main Jul 21, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant