starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-03 21:25:34 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Windows Store install fails when default app save location not set to C: #2382

New Issue
Open
opened 2026-01-30 22:53:37 +00:00 by claunia · 2 comments
claunia commented 2026-01-30 22:53:37 +00:00
Owner
Copy Link

Originally created by @bedlam-au on GitHub (Jun 29, 2019).

When default new app save location was set to D:, WT would download and attempt to install but then fail with a non-specific error (sorry no screenshot but should be repeatable). Changing the default app save location to C: allowed it to install.

There are a pair of Event Logs describing the event:

Fault bucket 1222364994692753289, type 5
Event Name: AppxDeploymentFailureBlue
Response: Not available
Cab Id: 0

Problem signature:
P1: 80073D13
P2: 5
P3: 0
P4: NONE
P5: 10.0.18362.175
P6: 765
P7: 
P8: 
P9: 
P10: 

Attached files:
[large number of log paths redacted]

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\NonCritical_80073D13_e3ddba5cc7432f8eac6ff587b7cea67b50cc29f4_00000000_614f2c6e-6497-4c50-998f-0bf772615a9e

Analysis symbol: 
Rechecking for solution: 0
Report Id: 614f2c6e-6497-4c50-998f-0bf772615a9e
Report Status: 268435456
Hashed bucket: b966d53c8a39f29fd0f6b67c7e88a789
Cab Guid: 0

and

Fault bucket 1439638532761225254, type 5
Event Name: StoreAgentDownloadFailure1
Response: Not available
Cab Id: 0

Problem signature:
P1: Acquisition;PTIClient
P2: 80073d13
P3: 18362
P4: 175
P5: Windows.Desktop
P6: 1
P7: 
P8: 
P9: 
P10: 

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER195D.tmp.WERInternalMetadata.xml

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\NonCritical_Acquisition;PTIC_2431d4c27ca3d41ba382d17ec8f30eadeab812e_00000000_fd9920f6-19ed-4ead-b665-b667864e43cc

Analysis symbol: 
Rechecking for solution: 0
Report Id: fd9920f6-19ed-4ead-b665-b667864e43cc
Report Status: 2147487744
Hashed bucket: 8ef9d1b328f66c23c3fa9f9e36328826
Cab Guid: 0
Originally created by @bedlam-au on GitHub (Jun 29, 2019). When default new app save location was set to D:, WT would download and attempt to install but then fail with a non-specific error (sorry no screenshot but should be repeatable). Changing the default app save location to C: allowed it to install. There are a pair of Event Logs describing the event: ``` Fault bucket 1222364994692753289, type 5 Event Name: AppxDeploymentFailureBlue Response: Not available Cab Id: 0 Problem signature: P1: 80073D13 P2: 5 P3: 0 P4: NONE P5: 10.0.18362.175 P6: 765 P7: P8: P9: P10: Attached files: [large number of log paths redacted] These files may be available here: \\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\NonCritical_80073D13_e3ddba5cc7432f8eac6ff587b7cea67b50cc29f4_00000000_614f2c6e-6497-4c50-998f-0bf772615a9e Analysis symbol: Rechecking for solution: 0 Report Id: 614f2c6e-6497-4c50-998f-0bf772615a9e Report Status: 268435456 Hashed bucket: b966d53c8a39f29fd0f6b67c7e88a789 Cab Guid: 0 ``` and ``` Fault bucket 1439638532761225254, type 5 Event Name: StoreAgentDownloadFailure1 Response: Not available Cab Id: 0 Problem signature: P1: Acquisition;PTIClient P2: 80073d13 P3: 18362 P4: 175 P5: Windows.Desktop P6: 1 P7: P8: P9: P10: Attached files: \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER195D.tmp.WERInternalMetadata.xml These files may be available here: \\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\NonCritical_Acquisition;PTIC_2431d4c27ca3d41ba382d17ec8f30eadeab812e_00000000_fd9920f6-19ed-4ead-b665-b667864e43cc Analysis symbol: Rechecking for solution: 0 Report Id: fd9920f6-19ed-4ead-b665-b667864e43cc Report Status: 2147487744 Hashed bucket: 8ef9d1b328f66c23c3fa9f9e36328826 Cab Guid: 0 ```
claunia added the Resolution-ExternalNeeds-Tag-FixProduct-Terminal labels 2026-01-30 22:53:38 +00:00
claunia commented 2026-01-30 22:53:38 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Jul 2, 2019):

Wow! I'm going to file an internal bug to the store folks, as this should absolutely not be the case.

@DHowett-MSFT commented on GitHub (Jul 2, 2019): Wow! I'm going to file an internal bug to the store folks, as this should absolutely not be the case.
claunia commented 2026-01-30 22:53:39 +00:00
Author
Owner
Copy Link

@Dean-NC commented on GitHub (Jul 4, 2020):

Still a problem with same event log error (except error code is 80073CF3) on Windows 2004 19041.208

@Dean-NC commented on GitHub (Jul 4, 2020): Still a problem with same event log error (except error code is 80073CF3) on Windows 2004 19041.208
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Needs-Tag-Fix Product-Terminal Resolution-External
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#2382
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?