Joshua Boelter

I was able to get tailscale working in WSL on Ubuntu 20.04 after disabling ipv6 in the wsl environment. I haven't dug further yet, but there's a discrepancy between what...

@zadjii-msft I poked around at this a bit, forcing some failures by removing files, removing permissions, trying unprivileged user accounts, trying the non-store win10 build (unzipping in place). The various...

Repro'd a version of the crash loop with the default `Administrator` account. The issue stems from the way IsElevated() is checking for elevation. edit: these instructions reproduce the bug; I'm...

procmon trace (screenshot) of the loop on latest 1.16.10261.0. This is running under the default Administrator account on 10.0.22621.1105 with elevate=true in the defaults. The sequence doesn't look right given...

Just came here looking for this issue, here's a screenshot. 

Process Monitor Trace shows the shim launching an elevated WindowsTerminal.exe, however -- note the paths used to resolve DLLs is different than the unelevated process (and fails). [WindowsTerminal-ProcMon.zip](https://github.com/microsoft/terminal/files/10171970/WindowsTerminal-ProcMon.zip)

I took dump snapshots (via Task Manager) of WindowsTerminal.exe of unelevated (after initial launch) and the elevated process (while the initial error dialog is on screen). Notable, the DllPath is...

Finally; you can verify this on a working system by attaching a debugger to WindowsTerminal.exe and inspecting the loaded modules for an unelevated vs elevated process. Note the image path...

I went down quite the rabbit hole exploring how a new process is created with ShellExecuteEx runas. It was also a good excuse to learn more about Time Travel Debug...

It looks like there is a viable path with minimal changes (still uses the shim and ShellExecute); it would require some state to determine if the original process was launched...