Changing Console Host breaks Win 11 boot #15872

Closed
opened 2026-01-31 04:51:00 +00:00 by claunia · 3 comments
Owner

Originally created by @pwasiewicz on GitHub (Nov 12, 2021).

Originally assigned to: @miniksa on GitHub.

Windows Terminal version (or Windows build number)

10.0.22000.0

Other Software

Oh My Posh

Steps to reproduce

  1. On Windows 11 (newest non-insider version)
  2. Install PowerShell Core 7.2
  3. Set as PowerShell as default shell
  4. Change Console Host to Windows Terminal
  5. Install and setup oh-my-posh
  6. After restart, win 11 goes into recovery loop - autofix not working (event safe mode!)

Expected Behavior

System should restart properly.

Actual Behavior

  1. Unable to start Windows
  2. Unable to boot with SafeMode
  3. No Srt logs created.

Reproduced twice on clean win install. Unfortunately I have no more time to test it - PC reset was required to make Windows boot again, everytime.

No issues on win 10

Originally created by @pwasiewicz on GitHub (Nov 12, 2021). Originally assigned to: @miniksa on GitHub. ### Windows Terminal version (or Windows build number) 10.0.22000.0 ### Other Software Oh My Posh ### Steps to reproduce 1. On Windows 11 (newest non-insider version) 2. Install PowerShell Core 7.2 3. Set as PowerShell as default shell 4. Change Console Host to Windows Terminal 5. Install and setup oh-my-posh 6. After restart, win 11 goes into recovery loop - autofix not working (event safe mode!) ### Expected Behavior System should restart properly. ### Actual Behavior 1. Unable to start Windows 2. Unable to boot with SafeMode 3. No Srt logs created. Reproduced twice on clean win install. Unfortunately I have no more time to test it - PC reset was required to make Windows boot again, everytime. No issues on win 10
Author
Owner

@zadjii-msft commented on GitHub (Nov 15, 2021):

HUH, that's bad. Might be similar to #11676. I'd suspect that the PowerShell Core bits don't necessarily have anything to do with the root cause... If they do that would raise more questions. Also maybe related: #11164

@zadjii-msft commented on GitHub (Nov 15, 2021): HUH, that's bad. Might be similar to #11676. I'd suspect that the PowerShell Core bits don't necessarily have anything to do with the root cause... If they do that would raise _more questions_. Also maybe related: #11164
Author
Owner

@DHowett commented on GitHub (Feb 17, 2022):

We've not seen any other reports of this on any other channels; I'm going to bump it from 1.14 for now.

@DHowett commented on GitHub (Feb 17, 2022): We've not seen any other reports of this on any other channels; I'm going to bump it from 1.14 for now.
Author
Owner

@miniksa commented on GitHub (Mar 11, 2022):

I've been unable to find a repro scenario of this even with all the other defapp issues I've seen recently. I'll have to resolve it for now.

@miniksa commented on GitHub (Mar 11, 2022): I've been unable to find a repro scenario of this even with all the other defapp issues I've seen recently. I'll have to resolve it for now.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#15872