Yea, again today, I got both windows back, but the buffer state was what it was the previous time I had quit the Terminal. So, whatever happened during the update meant that the Terminal didn't actually persist the buffer.

I found that this tool can be used for shutdown tests:

C:\Program Files (x86)\Windows Kits\10\App Certification Kit\rmlogotest.exe

For instance:

& "C:\Program Files (x86)\Windows Kits\10\App Certification Kit\rmlogotest.exe" (ps -Name WindowsTerminal).Id

I couldn't reproduce any issues on the main branch, even with multiple windows that have multiple tabs, and no matter how I re-launched the app.

tl;dr: handoff doesn't assign a SessionId!

I figured out how to reproduce multiple issues (probably even the issue):

• Launch
• (Register that version of WT as the default)
• Close all tabs (Ctrl+Shift+W)
• Bug: persistedWindowLayouts is non-empty
• Launch cmd/pwsh via handoff, but use the one that's not your default profile
• (Known) Bug: You got 2 windows now instead of 1 (this is a consequence of the previous bug)
• Close the tab with the default profile (= the extra window)
• Close window with the handoff'd non-default profile (= press red X)
• Bug: Buffer doesn't get persisted, and no SessionId gets stored

So yea here's the thing - defterm wasn't involved (to the best of my knowledge) in my scenario. I almost never open things via defterm anymore - pretty sure Stable is set as my defterm handler. Normally quitting the terminal will persist just fine - there's something specific about updates that makes the terminal not persist the current state of the buffer 🤷

My understanding is that this shipped with v1.22. Today was the first time that my workstation performed Windows updates while having 1.22 installed, and Terminal successfully restored its state after logging back in, and also respected the change to show some of the restored history without scrolling up. Thanks!

1.22.10731.0 - still doesn't restore windows if you close terminal, and then reboot the computer with a shutdown -r -t 0. Maybe Terminal needs a couple minutes to write the session file? Not sure what the issue might be.

@lhecker Don't think this fix handles that ^

Tangentially, I noticed that my tabs/history in my Terminal Preview app didn't get persisted across the last couple of Windows updates. However I was traveling and accessing my usual remote workstation through a much smaller laptop screen and really wasn't paying close enough attention to what I had open when these updates restarted the workstation, so I'm not 100% sure exactly what happened.