Dustin L. Howett

Thanks! If you don't have the rights to reopen it, let one of us know and we will!

Ohhh crap it conflicts with the renderer changes on main.

@djsavvy Just to be clear, I meant "Yeah this should probably _be made to work_" :smile:

Honestly, if we could have updated the version that shipped with Windows 11 to add a notice, we would have updated it to just add the settings UI. It's one...

You should be able to update it from the store as per usual or install the latest build from this GitHub repository. Fortunately, these methods all lead to the same...

> Okay, it seems that it's already Store version, but the app itself doesn't suggest that it can be updated via Store. Win11 itself after first start also doesn't update...

I am totally down to add something in the about dialog to suggest you update, but beyond that we're getting into platform surfaces my team doesn't own/has very little sway...

@nrjank thanks so much for writing this up! I promoted it to a separate bug. The interaction between our new settings, legacy mode, _and_ shortcuts is a place that deserves...

Interesting. This reminds me of [LLVM-44483](https://bugs.llvm.org/show_bug.cgi?id=44483) "[Windows] evaluating a variable from an outer scope in a @finally inside a block causes an internal compiler error" as well. There's significant issues...

Huh, that's unexpected. We only throw that error in three cases: 1. the server changes the Etag 2. the server doesn't have an Etag and changes the last modified date...