AppX deployment subsystem corrupted after 26H2 feature update: StartupTask record lost + Store reinstall permanently fails with 0x80073CF9 / 0x8007177E
Mantenedores costumam responder em até 2 dias
Ninguém assumiu esta issue ainda.
Avaliação
- Dificuldade
- 5/5
- Tempo estimado
- Mais de uma semana
- Facilidade para iniciantes
- 5/100
- Tipo de issue
- Bug
- Clareza
- Precisa de esclarecimento
- Status de atividade
- Ativa
- Stack de tecnologia
- shell
- Domínio
- infrastructure
Direção de pesquisa
The payload names no repository files, tests or entry points. The failures sit in Windows AppX deployment state (StartupTask registry mirror, the AppXDeploymentServer Operational log, Add-AppxPackage re-registration, DISM /RestoreHealth), which is outside this repo's code. Reproducing needs a Windows 11 machine with the affected package, and the fix is likely OS-side. Done would mean a reproducible diagnosis or a maintainer-confirmed workaround, not a patch here.
Escrita pelo modelo de indexação a partir do texto da issue.
Descrição
AppX deployment subsystem corrupted after 26H2 feature update: StartupTask record lost + Store reinstall permanently fails with 0x80073CF9 / 0x8007177E
Environment
- Windows 11 26H2, Build 26300.9711 (feature update from 26200, cumulative update 26100.9711)
- Affected app: KingjetNetwork.DitoPaste ("PPaste", ProductId 9PK30SK8LD80), UWP/Store version 2.4.0.0
- Reported via
winget install --id 9PK30SK8LD80 --source msstore
Symptom 1: StartupTask record lost after feature update
After the 26200 → 26300 feature update, the app's StartupTask no longer functions and the app is hidden from Settings > Apps > Startup.
Evidence:
Windows.ApplicationModel.StartupTask.GetAsync("PPaste_jiantieban")returns0x80070490(ERROR_NOT_FOUND)- Registry mirror still present:
HKCU\Software\Classes\Local Settings\...\SystemAppData\KingjetNetwork.DitoPaste_0h07hjapzra4r\PPaste_jiantiebanwithState=2 - AppxManifest still declares
<uap5:StartupTask TaskId="PPaste_jiantieban" Enabled="true" /> - Re-registering the same package is idempotently skipped —
Add-AppxPackage -DisableDevelopmentMode -Register <manifest>succeeds but does NOT rebuild the StartupTask record in StateRepository
Symptom 2: Store reinstall permanently fails
After Remove-AppxPackage, reinstalling from either Microsoft Store UI or winget msstore fails every time with 0x80073CF9 (ERROR_INSTALL_REGISTRATION_FAILURE).
Microsoft-Windows-AppXDeploymentServer/Operational log, every attempt:
Event 403/404: Deployment failed with 0x8007177E:
"Unable to read staged session for the update object:
7402f80e58f26b0e443ea6cff7f53588fbc92e61"
Key observations:
- The same fixed hash appears on every attempt across days and multiple reboots — a persistent stuck reference
- Exhaustive search (filename + file content + registry) across
C:\ProgramData\Microsoft\Windows\AppRepository(full recursive tree),C:\Windows\SoftwareDistribution, CBS and AppModel registry hives finds no match for this hash anywhere StateRepository-Deployment.srdpasses SQLiteintegrity_checkand contains no session tables → the stuck reference lives inside the InstallService internal queue, unreachable by any non-destructive means- Attempted cleanup also logs Event 627: staged remnants
KingjetNetwork.DitoPaste_2.3.2.0/_2.4.0.0"cannot be removed because the app is not installed for the current user"
Symptom 3: System-wide blast radius
- Event ID 484: package registration state read failures for user S-1-5-18 (SYSTEM) on unrelated packages (Microsoft.OneDriveSync, Microsoft.6365217CE6EB4)
DISM /Online /Cleanup-Image /RestoreHealthhangs at the command-routing stage for 43+ minutes (dism.log zero writes, TiWorker zero CPU), requiring manual termination
Already attempted, all ineffective
| Attempt | Result |
|---|---|
| Reboot (full) | Stuck session hash persists |
wsreset.exe |
No effect |
Admin Get-AppxPackage -AllUsers *DitoPaste* + Remove-AppxPackage -AllUsers |
Nothing found — system level is clean |
Registry UserEnabledStartupOnce rebuild + re-register |
GetAsync still NOT_FOUND |
| System Restore to prior restore point | Deployment queue state NOT rolled back — error persists identically |
DISM /RestoreHealth |
Hangs (see Symptom 3) |
Expected behavior
- Investigate the state migration bug in the 26200 → 26H2 upgrade path that corrupts StateRepository/InstallService session state
- Provide a supported way to rebuild lost StartupTask records (the idempotent-skip logic in re-registration currently blocks the obvious fix)
- Provide an official tool or command to clear orphaned staged-session references so affected users can reinstall from Store without an in-place repair upgrade
Workaround that worked
Installing the vendor's Win32 (Inno Setup) build of the same app — bypassing the AppX pipeline entirely. The UWP package and Store channel remain unusable on this machine.
- Linguagem predominante
- C++
- Estrelas
- 26.6k
- Forks
- 1.8k
- Merge médio
- 3d 10h
- PRs com merge (30d)
- 41
Preparar o ambiente
- Sem Dockerfile nem arquivo Docker Compose
- Tem um modelo de pull request
- Ler o guia de contribuição
Primeiros passos
- Leia a issue inteira e depois o guia de contribuição do projeto.
- Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
- Faça um fork do repositório e trabalhe em uma branch.
- Abra um pull request que referencie o número da issue.
Mais de microsoft/winget-cli
-
Issue-Docs Needs-Triage
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 70/100
microsoft/winget-cli#6692 ·
Mantenedores costumam responder em até 2 dias
-
Issue-Docs Possible-Duplicate
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 76/100
microsoft/winget-cli#6493 · 1 comentário ·
Mantenedores costumam responder em até 2 dias
-
WinGetSourceCreator: PackWithMappingFile should verify makeappx.exe exists before invoking itAbertaIssue-Feature
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 68/100
microsoft/winget-cli#6427 ·
Mantenedores costumam responder em até 2 dias
-
Issue-Docs msstore
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 64/100
microsoft/winget-cli#6331 · 1 comentário ·
Mantenedores costumam responder em até 2 dias
-
Command-Source Issue-Bug
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 68/100
microsoft/winget-cli#6148 ·
Mantenedores costumam responder em até 2 dias
Todas as issues de microsoft/winget-cli
Issues semelhantes
-
feat
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 65/100
Mantenedores costumam responder em até 1 dia
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 68/100
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 75/100
stratum-mining/sv2-tp#167 ·
Mantenedores costumam responder em até 1 dia
-
better error message bug low priority semantics strings
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 72/100
Mantenedores costumam responder em até 1 dia
-
Sign up button opens the Sign in page instead of the Sign up page for Enterprise edition serversAbertaauth bug ui/ux
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 72/100
MerginMaps/mobile#4795 ·
Mantenedores costumam responder em até 2 dias