MSStoreHelper today, and why it fails closed #1
SysAdminDoc
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
MSStoreHelper downloads and installs Microsoft Store apps without the Store itself, which makes it useful on Windows LTSC, in locked-down environments, or on any machine where the Store has simply given up. GUI-driven.
The recent releases were about not corrupting state when things go wrong. Downloads are resumable and bound to their responses, so a dropped connection doesn't leave you with a silently truncated package. Persisted state is transactional. Windows discovery fails closed rather than guessing, and long-running operations are coordinated instead of stepping on each other.
The roadmap points at inspectable install plans, so you can see exactly what's going to be deployed before it happens, and a published support-and-trust contract, because a tool that installs system packages should be explicit about what it's doing.
The variable I can't cover is the matrix of Windows editions and the packages people actually chase. The thread pinned next to this one is for reporting what you installed, on which edition, and whether it went cleanly, especially the dependency-heavy apps where the framework packages are half the battle.
All reactions