Windows Terminal crashes when dragging a tab #20215

Open
opened 2026-01-31 07:06:50 +00:00 by claunia · 60 comments
Owner

Originally created by @mwaltersbmc on GitHub (Jul 11, 2023).

Originally assigned to: @zadjii-msft on GitHub.

Windows Terminal version

1.17.11461.0 and 1.18.1462.0

Windows build number

10.0.22000.1936

Other Software

No response

Steps to reproduce

Open Terminal and create a session of any type eg Command Prompt, ssh connection, Powershell

Left click on session tab and drag

Expected Behavior

Reorder tabs

Actual Behavior

Terminal crashes with no visible error message

Crashdumps are created in %LOCALAPPDATA%\CrashDumps

Originally created by @mwaltersbmc on GitHub (Jul 11, 2023). Originally assigned to: @zadjii-msft on GitHub. ### Windows Terminal version 1.17.11461.0 and 1.18.1462.0 ### Windows build number 10.0.22000.1936 ### Other Software _No response_ ### Steps to reproduce Open Terminal and create a session of any type eg Command Prompt, ssh connection, Powershell Left click on session tab and drag ### Expected Behavior Reorder tabs ### Actual Behavior Terminal crashes with no visible error message Crashdumps are created in %LOCALAPPDATA%\CrashDumps
claunia added the Issue-BugNeeds-Tag-FixProduct-TerminalSeverity-Crash labels 2026-01-31 07:06:50 +00:00
Author
Owner

@mwaltersbmc commented on GitHub (Jul 11, 2023):

Also tested with Terminal 1.17.11461.0 on Windows 10.0.19045.3086 and the problem does not happen

@mwaltersbmc commented on GitHub (Jul 11, 2023): Also tested with Terminal 1.17.11461.0 on Windows 10.0.19045.3086 and the problem does not happen
Author
Owner

@zadjii-msft commented on GitHub (Jul 11, 2023):

Can you share the crash dump with us/? There are some notes on this wiki page. Thanks!

@zadjii-msft commented on GitHub (Jul 11, 2023): Can you share the crash dump with us/? There are some notes on [this wiki page](https://github.com/microsoft/terminal/wiki/Toubleshooting-Tips#share-with-the-team). Thanks!
Author
Owner

@microsoft-github-policy-service[bot] commented on GitHub (Jul 16, 2023):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@microsoft-github-policy-service[bot] commented on GitHub (Jul 16, 2023): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**.
Author
Owner

@microsoft-github-policy-service[bot] commented on GitHub (Jul 16, 2023):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@microsoft-github-policy-service[bot] commented on GitHub (Jul 16, 2023): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**.
Author
Owner

@mwaltersbmc commented on GitHub (Jul 17, 2023):

Dump file provided privately

@mwaltersbmc commented on GitHub (Jul 17, 2023): Dump file provided privately
Author
Owner

@zadjii-msft commented on GitHub (Jul 25, 2023):

Sorry, out of curiousity, who did you send the dump to? I can't seem to find it in my emails anywhere 😕

EDIT gah I finally found it in the spam folder. That filter's a little too aggressive some times (and not nearly aggressive enough others)

@zadjii-msft commented on GitHub (Jul 25, 2023): ~Sorry, out of curiousity, who did you send the dump to? I can't seem to find it in my emails anywhere 😕~ **EDIT** gah I finally found it in the spam folder. That filter's a little too aggressive some times (and not nearly aggressive enough others)
Author
Owner

@mwaltersbmc commented on GitHub (Jul 25, 2023):

Just to add - I have a colleague, also using W11, that can reproduce the issue using the same steps.

@mwaltersbmc commented on GitHub (Jul 25, 2023): Just to add - I have a colleague, also using W11, that can reproduce the issue using the same steps.
Author
Owner

@zadjii-msft commented on GitHub (Jul 25, 2023):

    Key  : Failure.Bucket
    Value: STOWED_EXCEPTION_c000027b_ntdll.dll!ZwWaitForWorkViaWorkerFactory

    Key  : Failure.Hash
    Value: {c2e540cf-b248-7db6-f41f-c703b9b4c1e5}

    Key  : Statistics.LastEvent.Exception.Code
    Value: 0xC000027B

    Key  : WER.OS.Version
    Value: 10.0.22000.1

    Key  : WER.Process.Version
    Value: 1.17.2305.26001

no dumps in watson.

stack
 # Child-SP          RetAddr               Call Site
00 00000066`a8cfdc30 00007ffa`532f0969     KERNELBASE!RaiseFailFastException+0x152 [minkernel\kernelbase\xcpt.c @ 1198] 
01 00000066`a8cfe210 00007ffa`39e5fe10     combase!RoFailFastWithErrorContextInternal2+0x4d9 [onecore\com\combase\winrt\error\error.cpp @ 1468] 
02 00000066`a8cfe480 00007ffa`39e60021     Windows_UI_Xaml!DirectUI::ErrorHelper::ProcessUnhandledError+0xf4 [onecoreuap\windows\dxaml\xcp\dxaml\lib\errorhelper.cpp @ 616] 
03 00000066`a8cfe4c0 00007ffa`39acac74     Windows_UI_Xaml!DirectUI::ErrorHelper::ReportUnhandledError+0xf1 [onecoreuap\windows\dxaml\xcp\dxaml\lib\errorhelper.cpp @ 502] 
04 (Inline Function) --------`--------     Windows_UI_Xaml!DirectUI::DXamlCore::FireEvent+0x32441a [onecoreuap\windows\dxaml\xcp\dxaml\lib\dxamlcore.cpp @ 2003] 
05 (Inline Function) --------`--------     Windows_UI_Xaml!AgCoreCallbacks::FireEvent+0x324443 [onecoreuap\windows\dxaml\xcp\dxaml\lib\fxcallbacks.cpp @ 93] 
06 (Inline Function) --------`--------     Windows_UI_Xaml!CFxCallbacks::JoltHelper_FireEvent+0x324443 [onecoreuap\windows\dxaml\xcp\dxaml\lib\fxcallbacks.cpp @ 1019] 
07 00000066`a8cfe540 00007ffa`397a666d     Windows_UI_Xaml!CCoreServices::CLR_FireEvent+0x3245e4 [onecoreuap\windows\dxaml\xcp\core\dll\xcpcore.cpp @ 3230] 
08 00000066`a8cfe610 00007ffa`398e353c     Windows_UI_Xaml!CommonBrowserHost::CLR_FireEvent+0x1d [onecoreuap\Windows\dxaml\xcp\control\common\shared\CommonBrowserHost.hpp @ 771] 
09 00000066`a8cfe650 00007ffa`3983d71a     Windows_UI_Xaml!CControlBase::ScriptCallback+0x16c [onecoreuap\windows\dxaml\xcp\control\common\shared\controlbase.cpp @ 267] 
0a 00000066`a8cfe6e0 00007ffa`3983d44d     Windows_UI_Xaml!CXcpDispatcher::OnScriptCallback+0x13a [onecoreuap\windows\dxaml\xcp\win\shared\xcpwindow.cpp @ 1376] 
0b 00000066`a8cfe780 00007ffa`3983d322     Windows_UI_Xaml!CXcpDispatcher::OnWindowMessage+0x3d [onecoreuap\windows\dxaml\xcp\win\shared\xcpwindow.cpp @ 1218] 
0c 00000066`a8cfe7c0 00007ffa`3983d220     Windows_UI_Xaml!CXcpDispatcher::ProcessMessage+0x72 [onecoreuap\windows\dxaml\xcp\win\shared\xcpwindow.cpp @ 927] 
0d 00000066`a8cfe800 00007ffa`53df1cac     Windows_UI_Xaml!CXcpDispatcher::WindowProc+0x90 [onecoreuap\windows\dxaml\xcp\win\shared\xcpwindow.cpp @ 841] 
0e 00000066`a8cfe870 00007ffa`53df17fc     user32!UserCallWinProcCheckWow+0x33c [clientcore\windows\core\ntuser\client\clmsg.cxx @ 282] 
0f 00000066`a8cfe9e0 00007ffa`53e04c6d     user32!DispatchClientMessage+0x9c [clientcore\windows\core\ntuser\client\daytona\objfre\amd64\client.cxx @ 3435] 
10 00000066`a8cfea40 00007ffa`55307b24     user32!__fnDWORD+0x3d [onecoreuap\restricted\windows\inc\ntuser\inc\ntcb.h @ 1214] 
11 00000066`a8cfeaa0 00007ffa`52d91434     ntdll!KiUserCallbackDispatcherContinue [minkernel\ntos\rtl\amd64\trampoln.asm @ 603] 
12 00000066`a8cfeb28 00007ffa`53df0ac4     win32u!ZwUserMessageCall+0x14 [onecoreuap\windows\core\umode\moderncore\objfre\amd64\usrstubs.asm @ 197] 
13 00000066`a8cfeb30 00007ffa`53df0797     user32!SendMessageWorker+0x2c4 [clientcore\windows\core\ntuser\client\clmsg.cxx @ 665] 
14 (Inline Function) --------`--------     user32!SendMessageInternal+0xfb [clientcore\windows\core\ntuser\client\clmsg.cxx @ 3633] 
15 00000066`a8cfebd0 00007ffa`398daa76     user32!SendMessageW+0x137 [onecoreuap\restricted\windows\inc\private\core\ntuser\client\cltxt.h @ 899] 
16 (Inline Function) --------`--------     Windows_UI_Xaml!CXcpDispatcher::SendMessageW+0x12 [onecoreuap\windows\dxaml\xcp\win\shared\xcpwindow.cpp @ 811] 
17 00000066`a8cfec30 00007ffa`39815203     Windows_UI_Xaml!CXcpBrowserHost::SyncScriptCallbackRequest+0x146 [onecoreuap\windows\dxaml\xcp\host\win\browserdesktop\winbrowserhost.cpp @ 1048] 
18 (Inline Function) --------`--------     Windows_UI_Xaml!CEventManager::RaiseControlEvents+0x19a [onecoreuap\windows\dxaml\xcp\core\dll\eventmgr.cpp @ 1133] 
19 00000066`a8cfecc0 00007ffa`39814bb7     Windows_UI_Xaml!CEventManager::Raise+0x513 [onecoreuap\windows\dxaml\xcp\core\dll\eventmgr.cpp @ 887] 
1a 00000066`a8cfedc0 00007ffa`399e89c0     Windows_UI_Xaml!CEventManager::RaiseRoutedEventBubbling+0x197 [onecoreuap\windows\dxaml\xcp\core\dll\eventmgr.cpp @ 1334] 
1b 00000066`a8cfee60 00007ffa`397ef572     Windows_UI_Xaml!ContentRootInput::PointerInputProcessor::ProcessPointerInput+0xd94 [onecoreuap\windows\dxaml\xcp\components\contentroot\pointerinputprocessor.cpp @ 591] 
1c 00000066`a8cfefd0 00007ffa`397ef391     Windows_UI_Xaml!CInputServices::ProcessInput+0x1c2 [onecoreuap\windows\dxaml\xcp\core\input\inputservices.cpp @ 888] 
1d 00000066`a8cff020 00007ffa`397ef206     Windows_UI_Xaml!CCoreServices::ProcessInput+0x45 [onecoreuap\windows\dxaml\xcp\core\dll\xcpcore.cpp @ 992] 
1e 00000066`a8cff050 00007ffa`399f8858     Windows_UI_Xaml!CXcpBrowserHost::HandleInputMessage+0x136 [onecoreuap\windows\dxaml\xcp\host\win\browserdesktop\winbrowserhost.cpp @ 1411] 
1f 00000066`a8cff120 00007ffa`399f86cc     Windows_UI_Xaml!CJupiterControl::HandlePointerMessage+0xfc [onecoreuap\windows\dxaml\xcp\dxaml\lib\jupitercontrol.cpp @ 754] 
20 00000066`a8cff1e0 00007ffa`399f857d     Windows_UI_Xaml!CJupiterWindow::OnIslandPointerMessage+0x108 [onecoreuap\windows\dxaml\xcp\dxaml\lib\jupiterwindow.cpp @ 2367] 
21 00000066`a8cff270 00007ffa`399f83d9     Windows_UI_Xaml!CXamlIslandRoot::InjectPointerMessage+0x65 [onecoreuap\windows\dxaml\xcp\core\core\elements\xamlislandroot.cpp @ 634] 
22 (Inline Function) --------`--------     Windows_UI_Xaml!CXamlIslandRoot::OnIslandPointerMoved+0x12 [onecoreuap\windows\dxaml\xcp\core\core\elements\xamlislandroot.cpp @ 558] 
23 (Inline Function) --------`--------     Windows_UI_Xaml!CXamlIslandRoot::SubscribeToPointerInputObserverEvents::__l27::<lambda_18714c66bdc179464f83501e730ba3b5>::operator()+0x2b [onecoreuap\windows\dxaml\xcp\core\core\elements\xamlislandroot.cpp @ 1452] 
24 00000066`a8cff2a0 00007ffa`36ad1607     Windows_UI_Xaml!Microsoft::WRL::Details::DelegateArgTraits<long (__cdecl Windows::Foundation::ITypedEventHandler_impl<Windows::Foundation::Internal::AggregateType<Windows::UI::Internal::Input::PointerInputObserver *,Windows::UI::Internal::Input::IPointerInputObserver *>,Windows::Foundation::Internal::AggregateType<Windows::UI::Core::PointerEventArgs *,Windows::UI::Core::IPointerEventArgs *> >::*)(Windows::UI::Internal::Input::IPointerInputObserver *,Windows::UI::Core::IPointerEventArgs *)>::DelegateInvokeHelper<Microsoft::WRL::Implements<Microsoft::WRL::RuntimeClassFlags<2>,Windows::Foundation::ITypedEventHandler<Windows::UI::Internal::Input::PointerInputObserver *,Windows::UI::Core::PointerEventArgs *>,Microsoft::WRL::FtmBase>,<lambda_18714c66bdc179464f83501e730ba3b5> &,-1,Windows::UI::Internal::Input::IPointerInputObserver *,Windows::UI::Core::IPointerEventArgs *>::Invoke+0x39 [onecore\external\sdk\inc\wrl\event.h @ 354] 
25 (Inline Function) --------`--------     InputHost!Microsoft::WRL::Details::CreateAgileHelper::__l2::<lambda_b5222d234632a4a0be2fddaf062a0811>::operator()+0x3d [onecore\external\sdk\inc\wrl\event.h @ 440] 
26 00000066`a8cff2d0 00007ffa`36ad017a     InputHost!Microsoft::WRL::Details::DelegateArgTraits<long (__cdecl Windows::Foundation::ITypedEventHandler_impl<Windows::Foundation::Internal::AggregateType<Windows::UI::Internal::Input::PointerInputObserver *,Windows::UI::Internal::Input::IPointerInputObserver *>,Windows::Foundation::Internal::AggregateType<Windows::UI::Core::PointerEventArgs *,Windows::UI::Core::IPointerEventArgs *> >::*)(Windows::UI::Internal::Input::IPointerInputObserver *,Windows::UI::Core::IPointerEventArgs *)>::DelegateInvokeHelper<Microsoft::WRL::Implements<Microsoft::WRL::RuntimeClassFlags<2>,Windows::Foundation::ITypedEventHandler<Windows::UI::Internal::Input::PointerInputObserver *,Windows::UI::Core::PointerEventArgs *>,Microsoft::WRL::FtmBase>,<lambda_b5222d234632a4a0be2fddaf062a0811>,-1,Windows::UI::Internal::Input::IPointerInputObserver *,Windows::UI::Core::IPointerEventArgs *>::Invoke+0x57 [onecore\external\sdk\inc\wrl\event.h @ 354] 
27 (Inline Function) --------`--------     InputHost!Microsoft::WRL::EventSource<Windows::Foundation::ITypedEventHandler<Windows::UI::Internal::Input::PointerInputObserver *,Windows::UI::Core::PointerEventArgs *>,Microsoft::WRL::InvokeModeOptions<-2> >::InvokeAll::__l2::<lambda_f45aed66b5921ed661cdce4c5fc41fcc>::operator()+0x28 [onecore\external\sdk\inc\wrl\event.h @ 964] 
28 00000066`a8cff300 00007ffa`36acff4d     InputHost!Microsoft::WRL::InvokeTraits<-2>::InvokeDelegates<<lambda_f45aed66b5921ed661cdce4c5fc41fcc>,Windows::Foundation::ITypedEventHandler<Windows::UI::Internal::Input::PointerInputObserver *,Windows::UI::Core::PointerEventArgs *> >+0x72 [onecore\internal\sdk\inc\wrl\internalevent.h @ 121] 
29 00000066`a8cff360 00007ffa`36ad0633     InputHost!Microsoft::WRL::EventSource<Windows::Foundation::ITypedEventHandler<Windows::UI::Internal::Input::PointerInputObserver *,Windows::UI::Core::PointerEventArgs *>,Microsoft::WRL::InvokeModeOptions<-2> >::DoInvoke<<lambda_f45aed66b5921ed661cdce4c5fc41fcc> >+0x75 [onecore\external\sdk\inc\wrl\event.h @ 954] 
2a (Inline Function) --------`--------     InputHost!Microsoft::WRL::EventSource<Windows::Foundation::ITypedEventHandler<Windows::UI::Internal::Input::PointerInputObserver *,Windows::UI::Core::PointerEventArgs *>,Microsoft::WRL::InvokeModeOptions<-2> >::InvokeAll+0x35 [onecore\external\sdk\inc\wrl\event.h @ 964] 
2b (Inline Function) --------`--------     InputHost!PointerInputObserverWinRT::InvokeEventDirectlyHelper_Callback::__l2::<lambda_e3ec73fb4105148165e124077d5d30c6>::operator()+0x4d [onecoreuap\windows\moderncore\inputv2\components\attachableinputobject\system\windowsmessagedelivery\client\lib\PointerInputObserverWinRT.h @ 121] 
2c 00000066`a8cff3a0 00007ffa`36ad02c4     InputHost!Microsoft::WRL2::ContextSession::LeaveSession_Callback<<lambda_e3ec73fb4105148165e124077d5d30c6> >+0x77 [onecore\private\sdk\inc\wrl2\Wrl2Agile.h @ 1140] 
2d 00000066`a8cff400 00007ffa`36ad048d     InputHost!PointerInputObserverWinRT::InvokeEventDirectlyHelper_Callback<Microsoft::WRL2::ContextEventSource<Windows::Foundation::ITypedEventHandler<Windows::UI::Internal::Input::PointerInputObserver *,Windows::UI::Core::PointerEventArgs *>,Microsoft::WRL::InvokeModeOptions<-2> >,PointerInputObserverWinRT::Api>+0x2c [onecoreuap\windows\moderncore\inputv2\components\attachableinputobject\system\windowsmessagedelivery\client\lib\PointerInputObserverWinRT.h @ 125] 
2e 00000066`a8cff450 00007ffa`36ad1993     InputHost!PointerInputObserverWinRT::InvokeEventHelper_Callback<Microsoft::WRL2::ContextEventSource<Windows::Foundation::ITypedEventHandler<Windows::UI::Internal::Input::PointerInputObserver *,Windows::UI::Core::PointerEventArgs *>,Microsoft::WRL::InvokeModeOptions<-2> >,PointerInputObserverWinRT::Api>+0x59 [onecoreuap\windows\moderncore\inputv2\components\attachableinputobject\system\windowsmessagedelivery\client\lib\PointerInputObserverWinRT.h @ 182] 
2f (Inline Function) --------`--------     InputHost!Microsoft::WRL::operator!=+0x39 [onecore\external\sdk\inc\wrl\client.h @ 823] 
30 00000066`a8cff490 00007ffa`36aab70f     InputHost!PointerInputObserverWinRT::OnWindowMessage_Callback+0xb3 [onecoreuap\windows\moderncore\inputv2\components\attachableinputobject\system\windowsmessagedelivery\client\lib\pointerinputobserverwinrt.cpp @ 437] 
31 00000066`a8cff4c0 00007ffa`36aaac66     InputHost!<lambda_7ff7aeac0ddd8d862d847848f86f2968>::operator()+0x43 [onecoreuap\windows\moderncore\inputv2\components\inputsitemanager\client\lib\system\windowsmessagedeliveryinputsitewinrt.cpp @ 142] 
32 00000066`a8cff4f0 00007ffa`36aab9fd     InputHost!InputSiteWinRT::ForEachAttachedObject+0xca [onecoreuap\windows\moderncore\inputv2\components\inputsitemanager\client\lib\system\inputsitewinrt.cpp @ 138] 
33 00000066`a8cff550 00007ffa`36aad148     InputHost!WindowsMessageDeliveryInputSiteWinRT::OnWindowMessage_Callback+0x8d [onecoreuap\windows\moderncore\inputv2\components\inputsitemanager\client\lib\system\windowsmessagedeliveryinputsitewinrt.cpp @ 137] 
34 00000066`a8cff610 00007ffa`36aab8f6     InputHost!SystemIslandInputSiteWinRT::OnWindowMessage_Callback+0x58 [onecoreuap\windows\moderncore\inputv2\components\inputsitemanager\client\lib\system\islandinputsitewinrt.cpp @ 304] 
35 00000066`a8cff640 00007ffa`36aadbd1     InputHost!WindowsMessageDeliveryInputSiteWinRT::Private::OnWindowMessage_Callback+0x96 [onecoreuap\windows\moderncore\inputv2\components\inputsitemanager\client\lib\system\windowsmessagedeliveryinputsitewinrt.cpp @ 262] 
36 00000066`a8cff710 00007ffa`36aadecf     InputHost!WindowsMessageDeliveryAdapter::ProcessWindowMessage_NoLock+0x10d [onecoreuap\windows\moderncore\inputv2\components\inputsitemanager\client\lib\system\windowsmessagedeliveryadapter.cpp @ 320] 
37 00000066`a8cff7f0 00007ffa`53df1cac     InputHost!WindowsMessageDeliveryAdapter::StaticWndProc+0xcf [onecoreuap\windows\moderncore\inputv2\components\inputsitemanager\client\lib\system\windowsmessagedeliveryadapter.cpp @ 262] 
38 00000066`a8cff830 00007ffa`53df0f06     user32!UserCallWinProcCheckWow+0x33c [clientcore\windows\core\ntuser\client\clmsg.cxx @ 282] 
39 00000066`a8cff9a0 00007ff6`51d21404     user32!DispatchMessageWorker+0x2a6 [clientcore\windows\core\ntuser\client\clmsg.cxx @ 3167] 
3a 00000066`a8cffa20 00007ff6`51d2f962     WindowsTerminal!wWinMain+0x194 [C:\a\_work\1\s\src\cascadia\WindowsTerminal\main.cpp @ 149] 
3b (Inline Function) --------`--------     WindowsTerminal!invoke_main+0x21 [D:\a\_work\1\s\src\vctools\crt\vcstartup\src\startup\exe_common.inl @ 118] 
3c 00000066`a8cffe10 00007ffa`547e55a0     WindowsTerminal!__scrt_common_main_seh+0x106 [D:\a\_work\1\s\src\vctools\crt\vcstartup\src\startup\exe_common.inl @ 288] 
3d 00000066`a8cffe50 00007ffa`5526485b     kernel32!BaseThreadInitThunk+0x10 [clientcore\base\win32\client\thread.c @ 75] 
3e 00000066`a8cffe80 00000000`00000000     ntdll!RtlUserThreadStart+0x2b [minkernel\ntdll\rtlstrt.c @ 1152] 

Oh boy that looks like a XAML crash. Great. I'll try and find anything else like it.

Any chance this repros with the WinUI 2 Gallery? There's a page in that app that's got a TabView for testing

@zadjii-msft commented on GitHub (Jul 25, 2023): ``` Key : Failure.Bucket Value: STOWED_EXCEPTION_c000027b_ntdll.dll!ZwWaitForWorkViaWorkerFactory Key : Failure.Hash Value: {c2e540cf-b248-7db6-f41f-c703b9b4c1e5} Key : Statistics.LastEvent.Exception.Code Value: 0xC000027B Key : WER.OS.Version Value: 10.0.22000.1 Key : WER.Process.Version Value: 1.17.2305.26001 ``` no dumps in watson. <details> <summary>stack</summary> ``` # Child-SP RetAddr Call Site 00 00000066`a8cfdc30 00007ffa`532f0969 KERNELBASE!RaiseFailFastException+0x152 [minkernel\kernelbase\xcpt.c @ 1198] 01 00000066`a8cfe210 00007ffa`39e5fe10 combase!RoFailFastWithErrorContextInternal2+0x4d9 [onecore\com\combase\winrt\error\error.cpp @ 1468] 02 00000066`a8cfe480 00007ffa`39e60021 Windows_UI_Xaml!DirectUI::ErrorHelper::ProcessUnhandledError+0xf4 [onecoreuap\windows\dxaml\xcp\dxaml\lib\errorhelper.cpp @ 616] 03 00000066`a8cfe4c0 00007ffa`39acac74 Windows_UI_Xaml!DirectUI::ErrorHelper::ReportUnhandledError+0xf1 [onecoreuap\windows\dxaml\xcp\dxaml\lib\errorhelper.cpp @ 502] 04 (Inline Function) --------`-------- Windows_UI_Xaml!DirectUI::DXamlCore::FireEvent+0x32441a [onecoreuap\windows\dxaml\xcp\dxaml\lib\dxamlcore.cpp @ 2003] 05 (Inline Function) --------`-------- Windows_UI_Xaml!AgCoreCallbacks::FireEvent+0x324443 [onecoreuap\windows\dxaml\xcp\dxaml\lib\fxcallbacks.cpp @ 93] 06 (Inline Function) --------`-------- Windows_UI_Xaml!CFxCallbacks::JoltHelper_FireEvent+0x324443 [onecoreuap\windows\dxaml\xcp\dxaml\lib\fxcallbacks.cpp @ 1019] 07 00000066`a8cfe540 00007ffa`397a666d Windows_UI_Xaml!CCoreServices::CLR_FireEvent+0x3245e4 [onecoreuap\windows\dxaml\xcp\core\dll\xcpcore.cpp @ 3230] 08 00000066`a8cfe610 00007ffa`398e353c Windows_UI_Xaml!CommonBrowserHost::CLR_FireEvent+0x1d [onecoreuap\Windows\dxaml\xcp\control\common\shared\CommonBrowserHost.hpp @ 771] 09 00000066`a8cfe650 00007ffa`3983d71a Windows_UI_Xaml!CControlBase::ScriptCallback+0x16c [onecoreuap\windows\dxaml\xcp\control\common\shared\controlbase.cpp @ 267] 0a 00000066`a8cfe6e0 00007ffa`3983d44d Windows_UI_Xaml!CXcpDispatcher::OnScriptCallback+0x13a [onecoreuap\windows\dxaml\xcp\win\shared\xcpwindow.cpp @ 1376] 0b 00000066`a8cfe780 00007ffa`3983d322 Windows_UI_Xaml!CXcpDispatcher::OnWindowMessage+0x3d [onecoreuap\windows\dxaml\xcp\win\shared\xcpwindow.cpp @ 1218] 0c 00000066`a8cfe7c0 00007ffa`3983d220 Windows_UI_Xaml!CXcpDispatcher::ProcessMessage+0x72 [onecoreuap\windows\dxaml\xcp\win\shared\xcpwindow.cpp @ 927] 0d 00000066`a8cfe800 00007ffa`53df1cac Windows_UI_Xaml!CXcpDispatcher::WindowProc+0x90 [onecoreuap\windows\dxaml\xcp\win\shared\xcpwindow.cpp @ 841] 0e 00000066`a8cfe870 00007ffa`53df17fc user32!UserCallWinProcCheckWow+0x33c [clientcore\windows\core\ntuser\client\clmsg.cxx @ 282] 0f 00000066`a8cfe9e0 00007ffa`53e04c6d user32!DispatchClientMessage+0x9c [clientcore\windows\core\ntuser\client\daytona\objfre\amd64\client.cxx @ 3435] 10 00000066`a8cfea40 00007ffa`55307b24 user32!__fnDWORD+0x3d [onecoreuap\restricted\windows\inc\ntuser\inc\ntcb.h @ 1214] 11 00000066`a8cfeaa0 00007ffa`52d91434 ntdll!KiUserCallbackDispatcherContinue [minkernel\ntos\rtl\amd64\trampoln.asm @ 603] 12 00000066`a8cfeb28 00007ffa`53df0ac4 win32u!ZwUserMessageCall+0x14 [onecoreuap\windows\core\umode\moderncore\objfre\amd64\usrstubs.asm @ 197] 13 00000066`a8cfeb30 00007ffa`53df0797 user32!SendMessageWorker+0x2c4 [clientcore\windows\core\ntuser\client\clmsg.cxx @ 665] 14 (Inline Function) --------`-------- user32!SendMessageInternal+0xfb [clientcore\windows\core\ntuser\client\clmsg.cxx @ 3633] 15 00000066`a8cfebd0 00007ffa`398daa76 user32!SendMessageW+0x137 [onecoreuap\restricted\windows\inc\private\core\ntuser\client\cltxt.h @ 899] 16 (Inline Function) --------`-------- Windows_UI_Xaml!CXcpDispatcher::SendMessageW+0x12 [onecoreuap\windows\dxaml\xcp\win\shared\xcpwindow.cpp @ 811] 17 00000066`a8cfec30 00007ffa`39815203 Windows_UI_Xaml!CXcpBrowserHost::SyncScriptCallbackRequest+0x146 [onecoreuap\windows\dxaml\xcp\host\win\browserdesktop\winbrowserhost.cpp @ 1048] 18 (Inline Function) --------`-------- Windows_UI_Xaml!CEventManager::RaiseControlEvents+0x19a [onecoreuap\windows\dxaml\xcp\core\dll\eventmgr.cpp @ 1133] 19 00000066`a8cfecc0 00007ffa`39814bb7 Windows_UI_Xaml!CEventManager::Raise+0x513 [onecoreuap\windows\dxaml\xcp\core\dll\eventmgr.cpp @ 887] 1a 00000066`a8cfedc0 00007ffa`399e89c0 Windows_UI_Xaml!CEventManager::RaiseRoutedEventBubbling+0x197 [onecoreuap\windows\dxaml\xcp\core\dll\eventmgr.cpp @ 1334] 1b 00000066`a8cfee60 00007ffa`397ef572 Windows_UI_Xaml!ContentRootInput::PointerInputProcessor::ProcessPointerInput+0xd94 [onecoreuap\windows\dxaml\xcp\components\contentroot\pointerinputprocessor.cpp @ 591] 1c 00000066`a8cfefd0 00007ffa`397ef391 Windows_UI_Xaml!CInputServices::ProcessInput+0x1c2 [onecoreuap\windows\dxaml\xcp\core\input\inputservices.cpp @ 888] 1d 00000066`a8cff020 00007ffa`397ef206 Windows_UI_Xaml!CCoreServices::ProcessInput+0x45 [onecoreuap\windows\dxaml\xcp\core\dll\xcpcore.cpp @ 992] 1e 00000066`a8cff050 00007ffa`399f8858 Windows_UI_Xaml!CXcpBrowserHost::HandleInputMessage+0x136 [onecoreuap\windows\dxaml\xcp\host\win\browserdesktop\winbrowserhost.cpp @ 1411] 1f 00000066`a8cff120 00007ffa`399f86cc Windows_UI_Xaml!CJupiterControl::HandlePointerMessage+0xfc [onecoreuap\windows\dxaml\xcp\dxaml\lib\jupitercontrol.cpp @ 754] 20 00000066`a8cff1e0 00007ffa`399f857d Windows_UI_Xaml!CJupiterWindow::OnIslandPointerMessage+0x108 [onecoreuap\windows\dxaml\xcp\dxaml\lib\jupiterwindow.cpp @ 2367] 21 00000066`a8cff270 00007ffa`399f83d9 Windows_UI_Xaml!CXamlIslandRoot::InjectPointerMessage+0x65 [onecoreuap\windows\dxaml\xcp\core\core\elements\xamlislandroot.cpp @ 634] 22 (Inline Function) --------`-------- Windows_UI_Xaml!CXamlIslandRoot::OnIslandPointerMoved+0x12 [onecoreuap\windows\dxaml\xcp\core\core\elements\xamlislandroot.cpp @ 558] 23 (Inline Function) --------`-------- Windows_UI_Xaml!CXamlIslandRoot::SubscribeToPointerInputObserverEvents::__l27::<lambda_18714c66bdc179464f83501e730ba3b5>::operator()+0x2b [onecoreuap\windows\dxaml\xcp\core\core\elements\xamlislandroot.cpp @ 1452] 24 00000066`a8cff2a0 00007ffa`36ad1607 Windows_UI_Xaml!Microsoft::WRL::Details::DelegateArgTraits<long (__cdecl Windows::Foundation::ITypedEventHandler_impl<Windows::Foundation::Internal::AggregateType<Windows::UI::Internal::Input::PointerInputObserver *,Windows::UI::Internal::Input::IPointerInputObserver *>,Windows::Foundation::Internal::AggregateType<Windows::UI::Core::PointerEventArgs *,Windows::UI::Core::IPointerEventArgs *> >::*)(Windows::UI::Internal::Input::IPointerInputObserver *,Windows::UI::Core::IPointerEventArgs *)>::DelegateInvokeHelper<Microsoft::WRL::Implements<Microsoft::WRL::RuntimeClassFlags<2>,Windows::Foundation::ITypedEventHandler<Windows::UI::Internal::Input::PointerInputObserver *,Windows::UI::Core::PointerEventArgs *>,Microsoft::WRL::FtmBase>,<lambda_18714c66bdc179464f83501e730ba3b5> &,-1,Windows::UI::Internal::Input::IPointerInputObserver *,Windows::UI::Core::IPointerEventArgs *>::Invoke+0x39 [onecore\external\sdk\inc\wrl\event.h @ 354] 25 (Inline Function) --------`-------- InputHost!Microsoft::WRL::Details::CreateAgileHelper::__l2::<lambda_b5222d234632a4a0be2fddaf062a0811>::operator()+0x3d [onecore\external\sdk\inc\wrl\event.h @ 440] 26 00000066`a8cff2d0 00007ffa`36ad017a InputHost!Microsoft::WRL::Details::DelegateArgTraits<long (__cdecl Windows::Foundation::ITypedEventHandler_impl<Windows::Foundation::Internal::AggregateType<Windows::UI::Internal::Input::PointerInputObserver *,Windows::UI::Internal::Input::IPointerInputObserver *>,Windows::Foundation::Internal::AggregateType<Windows::UI::Core::PointerEventArgs *,Windows::UI::Core::IPointerEventArgs *> >::*)(Windows::UI::Internal::Input::IPointerInputObserver *,Windows::UI::Core::IPointerEventArgs *)>::DelegateInvokeHelper<Microsoft::WRL::Implements<Microsoft::WRL::RuntimeClassFlags<2>,Windows::Foundation::ITypedEventHandler<Windows::UI::Internal::Input::PointerInputObserver *,Windows::UI::Core::PointerEventArgs *>,Microsoft::WRL::FtmBase>,<lambda_b5222d234632a4a0be2fddaf062a0811>,-1,Windows::UI::Internal::Input::IPointerInputObserver *,Windows::UI::Core::IPointerEventArgs *>::Invoke+0x57 [onecore\external\sdk\inc\wrl\event.h @ 354] 27 (Inline Function) --------`-------- InputHost!Microsoft::WRL::EventSource<Windows::Foundation::ITypedEventHandler<Windows::UI::Internal::Input::PointerInputObserver *,Windows::UI::Core::PointerEventArgs *>,Microsoft::WRL::InvokeModeOptions<-2> >::InvokeAll::__l2::<lambda_f45aed66b5921ed661cdce4c5fc41fcc>::operator()+0x28 [onecore\external\sdk\inc\wrl\event.h @ 964] 28 00000066`a8cff300 00007ffa`36acff4d InputHost!Microsoft::WRL::InvokeTraits<-2>::InvokeDelegates<<lambda_f45aed66b5921ed661cdce4c5fc41fcc>,Windows::Foundation::ITypedEventHandler<Windows::UI::Internal::Input::PointerInputObserver *,Windows::UI::Core::PointerEventArgs *> >+0x72 [onecore\internal\sdk\inc\wrl\internalevent.h @ 121] 29 00000066`a8cff360 00007ffa`36ad0633 InputHost!Microsoft::WRL::EventSource<Windows::Foundation::ITypedEventHandler<Windows::UI::Internal::Input::PointerInputObserver *,Windows::UI::Core::PointerEventArgs *>,Microsoft::WRL::InvokeModeOptions<-2> >::DoInvoke<<lambda_f45aed66b5921ed661cdce4c5fc41fcc> >+0x75 [onecore\external\sdk\inc\wrl\event.h @ 954] 2a (Inline Function) --------`-------- InputHost!Microsoft::WRL::EventSource<Windows::Foundation::ITypedEventHandler<Windows::UI::Internal::Input::PointerInputObserver *,Windows::UI::Core::PointerEventArgs *>,Microsoft::WRL::InvokeModeOptions<-2> >::InvokeAll+0x35 [onecore\external\sdk\inc\wrl\event.h @ 964] 2b (Inline Function) --------`-------- InputHost!PointerInputObserverWinRT::InvokeEventDirectlyHelper_Callback::__l2::<lambda_e3ec73fb4105148165e124077d5d30c6>::operator()+0x4d [onecoreuap\windows\moderncore\inputv2\components\attachableinputobject\system\windowsmessagedelivery\client\lib\PointerInputObserverWinRT.h @ 121] 2c 00000066`a8cff3a0 00007ffa`36ad02c4 InputHost!Microsoft::WRL2::ContextSession::LeaveSession_Callback<<lambda_e3ec73fb4105148165e124077d5d30c6> >+0x77 [onecore\private\sdk\inc\wrl2\Wrl2Agile.h @ 1140] 2d 00000066`a8cff400 00007ffa`36ad048d InputHost!PointerInputObserverWinRT::InvokeEventDirectlyHelper_Callback<Microsoft::WRL2::ContextEventSource<Windows::Foundation::ITypedEventHandler<Windows::UI::Internal::Input::PointerInputObserver *,Windows::UI::Core::PointerEventArgs *>,Microsoft::WRL::InvokeModeOptions<-2> >,PointerInputObserverWinRT::Api>+0x2c [onecoreuap\windows\moderncore\inputv2\components\attachableinputobject\system\windowsmessagedelivery\client\lib\PointerInputObserverWinRT.h @ 125] 2e 00000066`a8cff450 00007ffa`36ad1993 InputHost!PointerInputObserverWinRT::InvokeEventHelper_Callback<Microsoft::WRL2::ContextEventSource<Windows::Foundation::ITypedEventHandler<Windows::UI::Internal::Input::PointerInputObserver *,Windows::UI::Core::PointerEventArgs *>,Microsoft::WRL::InvokeModeOptions<-2> >,PointerInputObserverWinRT::Api>+0x59 [onecoreuap\windows\moderncore\inputv2\components\attachableinputobject\system\windowsmessagedelivery\client\lib\PointerInputObserverWinRT.h @ 182] 2f (Inline Function) --------`-------- InputHost!Microsoft::WRL::operator!=+0x39 [onecore\external\sdk\inc\wrl\client.h @ 823] 30 00000066`a8cff490 00007ffa`36aab70f InputHost!PointerInputObserverWinRT::OnWindowMessage_Callback+0xb3 [onecoreuap\windows\moderncore\inputv2\components\attachableinputobject\system\windowsmessagedelivery\client\lib\pointerinputobserverwinrt.cpp @ 437] 31 00000066`a8cff4c0 00007ffa`36aaac66 InputHost!<lambda_7ff7aeac0ddd8d862d847848f86f2968>::operator()+0x43 [onecoreuap\windows\moderncore\inputv2\components\inputsitemanager\client\lib\system\windowsmessagedeliveryinputsitewinrt.cpp @ 142] 32 00000066`a8cff4f0 00007ffa`36aab9fd InputHost!InputSiteWinRT::ForEachAttachedObject+0xca [onecoreuap\windows\moderncore\inputv2\components\inputsitemanager\client\lib\system\inputsitewinrt.cpp @ 138] 33 00000066`a8cff550 00007ffa`36aad148 InputHost!WindowsMessageDeliveryInputSiteWinRT::OnWindowMessage_Callback+0x8d [onecoreuap\windows\moderncore\inputv2\components\inputsitemanager\client\lib\system\windowsmessagedeliveryinputsitewinrt.cpp @ 137] 34 00000066`a8cff610 00007ffa`36aab8f6 InputHost!SystemIslandInputSiteWinRT::OnWindowMessage_Callback+0x58 [onecoreuap\windows\moderncore\inputv2\components\inputsitemanager\client\lib\system\islandinputsitewinrt.cpp @ 304] 35 00000066`a8cff640 00007ffa`36aadbd1 InputHost!WindowsMessageDeliveryInputSiteWinRT::Private::OnWindowMessage_Callback+0x96 [onecoreuap\windows\moderncore\inputv2\components\inputsitemanager\client\lib\system\windowsmessagedeliveryinputsitewinrt.cpp @ 262] 36 00000066`a8cff710 00007ffa`36aadecf InputHost!WindowsMessageDeliveryAdapter::ProcessWindowMessage_NoLock+0x10d [onecoreuap\windows\moderncore\inputv2\components\inputsitemanager\client\lib\system\windowsmessagedeliveryadapter.cpp @ 320] 37 00000066`a8cff7f0 00007ffa`53df1cac InputHost!WindowsMessageDeliveryAdapter::StaticWndProc+0xcf [onecoreuap\windows\moderncore\inputv2\components\inputsitemanager\client\lib\system\windowsmessagedeliveryadapter.cpp @ 262] 38 00000066`a8cff830 00007ffa`53df0f06 user32!UserCallWinProcCheckWow+0x33c [clientcore\windows\core\ntuser\client\clmsg.cxx @ 282] 39 00000066`a8cff9a0 00007ff6`51d21404 user32!DispatchMessageWorker+0x2a6 [clientcore\windows\core\ntuser\client\clmsg.cxx @ 3167] 3a 00000066`a8cffa20 00007ff6`51d2f962 WindowsTerminal!wWinMain+0x194 [C:\a\_work\1\s\src\cascadia\WindowsTerminal\main.cpp @ 149] 3b (Inline Function) --------`-------- WindowsTerminal!invoke_main+0x21 [D:\a\_work\1\s\src\vctools\crt\vcstartup\src\startup\exe_common.inl @ 118] 3c 00000066`a8cffe10 00007ffa`547e55a0 WindowsTerminal!__scrt_common_main_seh+0x106 [D:\a\_work\1\s\src\vctools\crt\vcstartup\src\startup\exe_common.inl @ 288] 3d 00000066`a8cffe50 00007ffa`5526485b kernel32!BaseThreadInitThunk+0x10 [clientcore\base\win32\client\thread.c @ 75] 3e 00000066`a8cffe80 00000000`00000000 ntdll!RtlUserThreadStart+0x2b [minkernel\ntdll\rtlstrt.c @ 1152] ``` </details> Oh boy that looks like a XAML crash. Great. I'll try and find anything else like it. Any chance this repros with the [WinUI 2 Gallery](https://apps.microsoft.com/store/detail/winui-2-gallery/9MSVH128X2ZT)? There's a page in that app that's got a TabView for testing
Author
Owner

@zadjii-msft commented on GitHub (Jul 26, 2023):

Out of curiosity, are you running the Terminal elevated? Or with UAC disabled (the EnableLua=0 thing)/?

@zadjii-msft commented on GitHub (Jul 26, 2023): Out of curiosity, are you running the Terminal elevated? Or with UAC disabled (the EnableLua=0 thing)/?
Author
Owner

@mwaltersbmc commented on GitHub (Jul 27, 2023):

Out of curiosity, are you running the Terminal elevated? Or with UAC disabled (the EnableLua=0 thing)/?

It's a corporate PC that has BeyondTrust privilege management software installed so I don't have options to run elevated.

@mwaltersbmc commented on GitHub (Jul 27, 2023): > Out of curiosity, are you running the Terminal elevated? Or with UAC disabled (the EnableLua=0 thing)/? It's a corporate PC that has BeyondTrust privilege management software installed so I don't have options to run elevated.
Author
Owner

@mwaltersbmc commented on GitHub (Jul 27, 2023):

Re WinUI - I installed and used the TabView samples under the Navigation section and was able to rearrange tabs on all the examples without a crash. I also launched the sample app and it too worked.

@mwaltersbmc commented on GitHub (Jul 27, 2023): Re WinUI - I installed and used the TabView samples under the Navigation section and was able to rearrange tabs on all the examples without a crash. I also launched the sample app and it too worked.
Author
Owner

@zadjii-msft commented on GitHub (Jul 27, 2023):

It's a corporate PC that has BeyondTrust privilege management software installed

WELL That's sure an interesting observation.

Sorry to be just seemingly shooting in the dark on this. We've really ruled out most of the... usual... things that cause crashes like this, so I'm a bit shooting blindly.

As a test, can you rearrange tabs with the moveTab action?

@zadjii-msft commented on GitHub (Jul 27, 2023): > It's a corporate PC that has BeyondTrust privilege management software installed WELL That's sure an interesting observation. Sorry to be just seemingly shooting in the dark on this. We've really ruled out most of the... usual... things that cause crashes like this, so I'm a bit shooting blindly. As a test, can you rearrange tabs with the [`moveTab`](https://learn.microsoft.com/en-us/windows/terminal/customize-settings/actions#move-tab) action?
Author
Owner

@mwaltersbmc commented on GitHub (Jul 27, 2023):

I set ctrl+u to be move tab forward and then move tab backwards. In both cases it worked as expected and did not cause a crash.

@mwaltersbmc commented on GitHub (Jul 27, 2023): I set ctrl+u to be move tab forward and then move tab backwards. In both cases it worked as expected and did not cause a crash.
Author
Owner

@zadjii-msft commented on GitHub (Jul 27, 2023):

Okay, well at least that very specifically reduces the problem space to the drag/drop interaction, and not necessarily the "move tabs" implementation.

But it also doesn't repro in the XAML controls gallery. We're not doing too much different than what they do, especially in 1.17. Hmm.

Maybe my contacts on XAML will have some insight as to why I couldn't find the stowed exception, or how to get it out of the dump. That might help point a finger.

@zadjii-msft commented on GitHub (Jul 27, 2023): Okay, well at least that very specifically reduces the problem space to the drag/drop interaction, and not necessarily the "move tabs" implementation. But it also doesn't repro in the XAML controls gallery. We're not doing too much different than what they do, especially in 1.17. Hmm. Maybe my contacts on XAML will have some insight as to why I couldn't find the stowed exception, or how to get it out of the dump. That might help point a finger.
Author
Owner

@mwaltersbmc commented on GitHub (Jul 27, 2023):

Thanks - happy to do any further tests if required.

@mwaltersbmc commented on GitHub (Jul 27, 2023): Thanks - happy to do any further tests if required.
Author
Owner

@zadjii-msft commented on GitHub (Jul 27, 2023):

Ah, I didn't have a chance to write something longer up before I leave for the weekend. My XAML friends had this to say:

and users who set the regkeys to capture a mini dump {don't actually end up getting everything we need}

DumpType=2 is what I've recommended for XAML crashes:
https://github.com/microsoft/microsoft-ui-xaml/blob/main/docs/debugging_crashes.md#other-options

Turns out our docs need updating. Where you added those other reg keys, can you add a DumpType=2 DWORD, and capture the crash again? That should get the real stowed exception.

https://learn.microsoft.com/en-us/windows/win32/wer/collecting-user-mode-dumps

@zadjii-msft commented on GitHub (Jul 27, 2023): Ah, I didn't have a chance to write something longer up before I leave for the weekend. My XAML friends had this to say: > and users who set the regkeys to capture a mini dump {don't actually end up getting everything we need} > > DumpType=2 is what I've recommended for XAML crashes: > https://github.com/microsoft/microsoft-ui-xaml/blob/main/docs/debugging_crashes.md#other-options Turns out our docs need updating. Where you added those other reg keys, can you add a `DumpType=2` DWORD, and capture the crash again? That should get the _real_ stowed exception. https://learn.microsoft.com/en-us/windows/win32/wer/collecting-user-mode-dumps
Author
Owner

@mwaltersbmc commented on GitHub (Jul 28, 2023):

Sent OneDrive link to dump files collected after setting DumpType 2

@mwaltersbmc commented on GitHub (Jul 28, 2023): Sent OneDrive link to dump files collected after setting DumpType 2
Author
Owner

@zadjii-msft commented on GitHub (Aug 1, 2023):

0:000> !xamltriage
-------------------------
Callstack for hr=80070005 - Access is denied.
  Error message: "Access is denied."

    combase!RoOriginateLanguageException+0x57  (7ffd188f2de7) [onecore\com\combase\winrt\error\error.cpp @ 1517]
    Microsoft_UI_Xaml!winrt::hresult_error::originate+0x6f  (7ffc707aae43) [C:\a\_work\1\s\BuildOutput\Intermediates\x64\Microsoft.UI.Xaml\obj\Generated Files\winrt\base.h @ 4697]
    Microsoft_UI_Xaml!winrt::hresult_error::hresult_error+0x19f  (7ffc707a8b23) [C:\a\_work\1\s\BuildOutput\Intermediates\x64\Microsoft.UI.Xaml\obj\Generated Files\winrt\base.h @ 4630]
    Microsoft_UI_Xaml!winrt::throw_hresult+0x79  (7ffc707ab42d) [C:\a\_work\1\s\BuildOutput\Intermediates\x64\Microsoft.UI.Xaml\obj\Generated Files\winrt\base.h @ 4829]
    Microsoft_UI_Xaml!winrt::impl::consume_Windows_UI_Xaml_Controls_IControlOverrides<winrt::Windows::UI::Xaml::Controls::IControlOverrides>::OnPointerMoved+0x27  (7ffc7075c377) [C:\a\_work\1\s\BuildOutput\Intermediates\x64\Microsoft.UI.Xaml\obj\Generated Files\winrt\Windows.UI.Xaml.Controls.h @ 5128]
    Microsoft_UI_Xaml!winrt::impl::produce<ColorPicker,winrt::Windows::UI::Xaml::Controls::IControlOverrides>::OnPointerMoved+0xa5  (7ffc708179b5) [C:\a\_work\1\s\BuildOutput\Intermediates\x64\Microsoft.UI.Xaml\obj\Generated Files\winrt\Windows.UI.Xaml.Controls.h @ 30979]
    Windows_UI_Xaml!DirectUI::ControlGenerated::OnPointerMovedProtected+0x1d5686  (7ffcfd7b833a) [onecoreuap\windows\dxaml\xcp\dxaml\lib\winrtgeneratedclasses\control.g.cpp @ 1438]
    Windows_UI_Xaml!DirectUI::Control::FireEvent+0x2d3  (7ffcfd386483) [onecoreuap\windows\dxaml\xcp\dxaml\lib\control_partial.cpp @ 251]
    Windows_UI_Xaml!CCoreServices::CLR_FireEvent+0x277  (7ffcfd386907) [onecoreuap\windows\dxaml\xcp\core\dll\xcpcore.cpp @ 3230]
    Windows_UI_Xaml!CommonBrowserHost::CLR_FireEvent+0x1d  (7ffcfd38666d) [onecoreuap\Windows\dxaml\xcp\control\common\shared\CommonBrowserHost.hpp @ 771]
    Windows_UI_Xaml!CControlBase::ScriptCallback+0x16c  (7ffcfd4c353c) [onecoreuap\windows\dxaml\xcp\control\common\shared\controlbase.cpp @ 267]
    Windows_UI_Xaml!CXcpDispatcher::OnScriptCallback+0x13a  (7ffcfd41d71a) [onecoreuap\windows\dxaml\xcp\win\shared\xcpwindow.cpp @ 1376]
    Windows_UI_Xaml!CXcpDispatcher::OnWindowMessage+0x3d  (7ffcfd41d44d) [onecoreuap\windows\dxaml\xcp\win\shared\xcpwindow.cpp @ 1218]
    Windows_UI_Xaml!CXcpDispatcher::ProcessMessage+0x72  (7ffcfd41d322) [onecoreuap\windows\dxaml\xcp\win\shared\xcpwindow.cpp @ 927]
    Windows_UI_Xaml!CXcpDispatcher::WindowProc+0x90  (7ffcfd41d220) [onecoreuap\windows\dxaml\xcp\win\shared\xcpwindow.cpp @ 841]
    user32!UserCallWinProcCheckWow+0x33c  (7ffd18b91cac) [clientcore\windows\core\ntuser\client\clmsg.cxx @ 282]
    user32!DispatchClientMessage+0x9c  (7ffd18b917fc) [clientcore\windows\core\ntuser\client\daytona\objfre\amd64\client.cxx @ 3435]
    user32!__fnDWORD+0x3d  (7ffd18ba4c6d) [onecoreuap\restricted\windows\inc\ntuser\inc\ntcb.h @ 1214]
    ntdll!KiUserCallbackDispatcherContinue  (7ffd1a967b84) [minkernel\ntos\rtl\amd64\trampoln.asm @ 607]
    win32u!ZwUserMessageCall+0x14  (7ffd17dd1434) [onecoreuap\windows\core\umode\moderncore\objfre\amd64\usrstubs.asm @ 197]
    user32!SendMessageWorker+0x2c4  (7ffd18b90ac4) [clientcore\windows\core\ntuser\client\clmsg.cxx @ 665]
    user32!SendMessageW+0x137  (7ffd18b90797) [onecoreuap\restricted\windows\inc\private\core\ntuser\client\cltxt.h @ 899]
    Windows_UI_Xaml!CXcpBrowserHost::SyncScriptCallbackRequest+0x146  (7ffcfd4baa76) [onecoreuap\windows\dxaml\xcp\host\win\browserdesktop\winbrowserhost.cpp @ 1048]
    Windows_UI_Xaml!CEventManager::Raise+0x513  (7ffcfd3f5203) [onecoreuap\windows\dxaml\xcp\core\dll\eventmgr.cpp @ 887]
    Windows_UI_Xaml!CEventManager::RaiseRoutedEventBubbling+0x197  (7ffcfd3f4bb7) [onecoreuap\windows\dxaml\xcp\core\dll\eventmgr.cpp @ 1334]
    Windows_UI_Xaml!ContentRootInput::PointerInputProcessor::ProcessPointerInput+0xd94  (7ffcfd5c89c0) [onecoreuap\windows\dxaml\xcp\components\contentroot\pointerinputprocessor.cpp @ 591]
    Windows_UI_Xaml!CInputServices::ProcessInput+0x1c2  (7ffcfd3cf572) [onecoreuap\windows\dxaml\xcp\core\input\inputservices.cpp @ 888]
    Windows_UI_Xaml!CCoreServices::ProcessInput+0x45  (7ffcfd3cf391) [onecoreuap\windows\dxaml\xcp\core\dll\xcpcore.cpp @ 992]
    Windows_UI_Xaml!CXcpBrowserHost::HandleInputMessage+0x136  (7ffcfd3cf206) [onecoreuap\windows\dxaml\xcp\host\win\browserdesktop\winbrowserhost.cpp @ 1411]
    Windows_UI_Xaml!CJupiterControl::HandlePointerMessage+0xfc  (7ffcfd5d8858) [onecoreuap\windows\dxaml\xcp\dxaml\lib\jupitercontrol.cpp @ 754]
    Windows_UI_Xaml!CJupiterWindow::OnIslandPointerMessage+0x108  (7ffcfd5d86cc) [onecoreuap\windows\dxaml\xcp\dxaml\lib\jupiterwindow.cpp @ 2367]
    Windows_UI_Xaml!CXamlIslandRoot::InjectPointerMessage+0x65  (7ffcfd5d857d) [onecoreuap\windows\dxaml\xcp\core\core\elements\xamlislandroot.cpp @ 634]
    Windows_UI_Xaml!Microsoft::WRL::Details::DelegateArgTraits<long  (7ffcfd5d83d9) [onecore\external\sdk\inc\wrl\event.h @ 354]
    InputHost!Microsoft::WRL::Details::DelegateArgTraits<long  (7ffcfaa41607) [onecore\external\sdk\inc\wrl\event.h @ 354]
    InputHost!Microsoft::WRL::InvokeTraits<-2>::InvokeDelegates<<lambda_f45aed66b5921ed661cdce4c5fc41fcc>,Windows::Foundation::ITypedEventHandler<Windows::UI::Internal::Input::PointerInputObserver *,Windows::UI::Core::PointerEventArgs *> >+0x72  (7ffcfaa4017a) [onecore\internal\sdk\inc\wrl\internalevent.h @ 121]
    InputHost!Microsoft::WRL::EventSource<Windows::Foundation::ITypedEventHandler<Windows::UI::Internal::Input::PointerInputObserver *,Windows::UI::Core::PointerEventArgs *>,Microsoft::WRL::InvokeModeOptions<-2> >::DoInvoke<<lambda_f45aed66b5921ed661cdce4c5fc41fcc> >+0x75  (7ffcfaa3ff4d) [onecore\external\sdk\inc\wrl\event.h @ 954]
    InputHost!Microsoft::WRL2::ContextSession::LeaveSession_Callback<<lambda_e3ec73fb4105148165e124077d5d30c6> >+0x77  (7ffcfaa40633) [onecore\private\sdk\inc\wrl2\Wrl2Agile.h @ 1140]
    InputHost!PointerInputObserverWinRT::InvokeEventDirectlyHelper_Callback<Microsoft::WRL2::ContextEventSource<Windows::Foundation::ITypedEventHandler<Windows::UI::Internal::Input::PointerInputObserver *,Windows::UI::Core::PointerEventArgs *>,Microsoft::WRL::InvokeModeOptions<-2> >,PointerInputObserverWinRT::Api>+0x2c  (7ffcfaa402c4) [onecoreuap\windows\moderncore\inputv2\components\attachableinputobject\system\windowsmessagedelivery\client\lib\PointerInputObserverWinRT.h @ 125]
    InputHost!PointerInputObserverWinRT::InvokeEventHelper_Callback<Microsoft::WRL2::ContextEventSource<Windows::Foundation::ITypedEventHandler<Windows::UI::Internal::Input::PointerInputObserver *,Windows::UI::Core::PointerEventArgs *>,Microsoft::WRL::InvokeModeOptions<-2> >,PointerInputObserverWinRT::Api>+0x59  (7ffcfaa4048d) [onecoreuap\windows\moderncore\inputv2\components\attachableinputobject\system\windowsmessagedelivery\client\lib\PointerInputObserverWinRT.h @ 182]
    InputHost!PointerInputObserverWinRT::OnWindowMessage_Callback+0xb3  (7ffcfaa41993) [onecoreuap\windows\moderncore\inputv2\components\attachableinputobject\system\windowsmessagedelivery\client\lib\pointerinputobserverwinrt.cpp @ 437]
    InputHost!<lambda_7ff7aeac0ddd8d862d847848f86f2968>::operator  (7ffcfaa1b70f) [onecoreuap\windows\moderncore\inputv2\components\inputsitemanager\client\lib\system\windowsmessagedeliveryinputsitewinrt.cpp @ 142]
    InputHost!InputSiteWinRT::ForEachAttachedObject+0xca  (7ffcfaa1ac66) [onecoreuap\windows\moderncore\inputv2\components\inputsitemanager\client\lib\system\inputsitewinrt.cpp @ 138]
    InputHost!WindowsMessageDeliveryInputSiteWinRT::OnWindowMessage_Callback+0x8d  (7ffcfaa1b9fd) [onecoreuap\windows\moderncore\inputv2\components\inputsitemanager\client\lib\system\windowsmessagedeliveryinputsitewinrt.cpp @ 137]
    InputHost!SystemIslandInputSiteWinRT::OnWindowMessage_Callback+0x58  (7ffcfaa1d148) [onecoreuap\windows\moderncore\inputv2\components\inputsitemanager\client\lib\system\islandinputsitewinrt.cpp @ 304]
    InputHost!WindowsMessageDeliveryInputSiteWinRT::Private::OnWindowMessage_Callback+0x96  (7ffcfaa1b8f6) [onecoreuap\windows\moderncore\inputv2\components\inputsitemanager\client\lib\system\windowsmessagedeliveryinputsitewinrt.cpp @ 262]
    InputHost!WindowsMessageDeliveryAdapter::ProcessWindowMessage_NoLock+0x10d  (7ffcfaa1dbd1) [onecoreuap\windows\moderncore\inputv2\components\inputsitemanager\client\lib\system\windowsmessagedeliveryadapter.cpp @ 320]
    InputHost!WindowsMessageDeliveryAdapter::StaticWndProc+0xcf  (7ffcfaa1decf) [onecoreuap\windows\moderncore\inputv2\components\inputsitemanager\client\lib\system\windowsmessagedeliveryadapter.cpp @ 262]
    user32!UserCallWinProcCheckWow+0x33c  (7ffd18b91cac) [clientcore\windows\core\ntuser\client\clmsg.cxx @ 282]
    user32!DispatchMessageWorker+0x2a6  (7ffd18b90f06) [clientcore\windows\core\ntuser\client\clmsg.cxx @ 3167]
    WindowsTerminal!wWinMain+0x194  (7ff7bef81404) [C:\a\_work\1\s\src\cascadia\WindowsTerminal\main.cpp @ 149]
    WindowsTerminal!__scrt_common_main_seh+0x106  (7ff7bef8f962) [D:\a\_work\1\s\src\vctools\crt\vcstartup\src\startup\exe_common.inl @ 288]
    kernel32!BaseThreadInitThunk+0x10  (7ffd1a2855a0) [clientcore\base\win32\client\thread.c @ 75]
    ntdll!RtlUserThreadStart+0x2b  (7ffd1a8c485b) [minkernel\ntdll\rtlstrt.c @ 1152]
-------------------------
Callstack for hr=80070005 - Access is denied.

    Windows_UI_Xaml!DirectUI::StartDragAsyncOperation::StartIfNeededImpl+0xd9  (7ffcfda64be5) [onecoreuap\windows\dxaml\xcp\dxaml\lib\startdragasyncoperation.cpp @ 81]
    Windows_UI_Xaml!DirectUI::ListViewBase::OnDragGesture+0x4a0  (7ffcfde72b8c) [onecoreuap\windows\dxaml\xcp\dxaml\lib\listviewbase_partial_reorder.cpp @ 242]
    Windows_UI_Xaml!DirectUI::ListViewBaseItem::TryStartDrag+0x15c  (7ffcfde02b00) [onecoreuap\windows\dxaml\xcp\dxaml\lib\listviewbaseitem_partial.cpp @ 2914]
    Windows_UI_Xaml!DirectUI::ListViewBaseItem::OnPointerMoved+0x323  (7ffcfd662883) [onecoreuap\windows\dxaml\xcp\dxaml\lib\listviewbaseitem_partial.cpp @ 1332]
    Microsoft_UI_Xaml!winrt::impl::consume_Windows_UI_Xaml_Controls_IControlOverrides<winrt::Windows::UI::Xaml::Controls::IControlOverrides>::OnPointerMoved+0x17  (7ffc7075c367) [C:\a\_work\1\s\BuildOutput\Intermediates\x64\Microsoft.UI.Xaml\obj\Generated Files\winrt\Windows.UI.Xaml.Controls.h @ 5128]
    Microsoft_UI_Xaml!winrt::impl::produce<ColorPicker,winrt::Windows::UI::Xaml::Controls::IControlOverrides>::OnPointerMoved+0xa5  (7ffc708179b5) [C:\a\_work\1\s\BuildOutput\Intermediates\x64\Microsoft.UI.Xaml\obj\Generated Files\winrt\Windows.UI.Xaml.Controls.h @ 30979]
    Windows_UI_Xaml!DirectUI::ControlGenerated::OnPointerMovedProtected+0x1d5686  (7ffcfd7b833a) [onecoreuap\windows\dxaml\xcp\dxaml\lib\winrtgeneratedclasses\control.g.cpp @ 1438]
    Windows_UI_Xaml!DirectUI::Control::FireEvent+0x2d3  (7ffcfd386483) [onecoreuap\windows\dxaml\xcp\dxaml\lib\control_partial.cpp @ 251]
    Windows_UI_Xaml!CCoreServices::CLR_FireEvent+0x277  (7ffcfd386907) [onecoreuap\windows\dxaml\xcp\core\dll\xcpcore.cpp @ 3230]
    Windows_UI_Xaml!CommonBrowserHost::CLR_FireEvent+0x1d  (7ffcfd38666d) [onecoreuap\Windows\dxaml\xcp\control\common\shared\CommonBrowserHost.hpp @ 771]
    Windows_UI_Xaml!CControlBase::ScriptCallback+0x16c  (7ffcfd4c353c) [onecoreuap\windows\dxaml\xcp\control\common\shared\controlbase.cpp @ 267]
    Windows_UI_Xaml!CXcpDispatcher::OnScriptCallback+0x13a  (7ffcfd41d71a) [onecoreuap\windows\dxaml\xcp\win\shared\xcpwindow.cpp @ 1376]
    Windows_UI_Xaml!CXcpDispatcher::OnWindowMessage+0x3d  (7ffcfd41d44d) [onecoreuap\windows\dxaml\xcp\win\shared\xcpwindow.cpp @ 1218]
    Windows_UI_Xaml!CXcpDispatcher::ProcessMessage+0x72  (7ffcfd41d322) [onecoreuap\windows\dxaml\xcp\win\shared\xcpwindow.cpp @ 927]
    Windows_UI_Xaml!CXcpDispatcher::WindowProc+0x90  (7ffcfd41d220) [onecoreuap\windows\dxaml\xcp\win\shared\xcpwindow.cpp @ 841]
    user32!UserCallWinProcCheckWow+0x33c  (7ffd18b91cac) [clientcore\windows\core\ntuser\client\clmsg.cxx @ 282]
    user32!DispatchClientMessage+0x9c  (7ffd18b917fc) [clientcore\windows\core\ntuser\client\daytona\objfre\amd64\client.cxx @ 3435]
    user32!__fnDWORD+0x3d  (7ffd18ba4c6d) [onecoreuap\restricted\windows\inc\ntuser\inc\ntcb.h @ 1214]
    ntdll!KiUserCallbackDispatcherContinue  (7ffd1a967b84) [minkernel\ntos\rtl\amd64\trampoln.asm @ 607]
    win32u!ZwUserMessageCall+0x14  (7ffd17dd1434) [onecoreuap\windows\core\umode\moderncore\objfre\amd64\usrstubs.asm @ 197]
    user32!SendMessageWorker+0x2c4  (7ffd18b90ac4) [clientcore\windows\core\ntuser\client\clmsg.cxx @ 665]
    user32!SendMessageW+0x137  (7ffd18b90797) [onecoreuap\restricted\windows\inc\private\core\ntuser\client\cltxt.h @ 899]
    Windows_UI_Xaml!CXcpBrowserHost::SyncScriptCallbackRequest+0x146  (7ffcfd4baa76) [onecoreuap\windows\dxaml\xcp\host\win\browserdesktop\winbrowserhost.cpp @ 1048]
    Windows_UI_Xaml!CEventManager::Raise+0x513  (7ffcfd3f5203) [onecoreuap\windows\dxaml\xcp\core\dll\eventmgr.cpp @ 887]
    Windows_UI_Xaml!CEventManager::RaiseRoutedEventBubbling+0x197  (7ffcfd3f4bb7) [onecoreuap\windows\dxaml\xcp\core\dll\eventmgr.cpp @ 1334]
    Windows_UI_Xaml!ContentRootInput::PointerInputProcessor::ProcessPointerInput+0xd94  (7ffcfd5c89c0) [onecoreuap\windows\dxaml\xcp\components\contentroot\pointerinputprocessor.cpp @ 591]
    Windows_UI_Xaml!CInputServices::ProcessInput+0x1c2  (7ffcfd3cf572) [onecoreuap\windows\dxaml\xcp\core\input\inputservices.cpp @ 888]
    Windows_UI_Xaml!CCoreServices::ProcessInput+0x45  (7ffcfd3cf391) [onecoreuap\windows\dxaml\xcp\core\dll\xcpcore.cpp @ 992]
    Windows_UI_Xaml!CXcpBrowserHost::HandleInputMessage+0x136  (7ffcfd3cf206) [onecoreuap\windows\dxaml\xcp\host\win\browserdesktop\winbrowserhost.cpp @ 1411]
    Windows_UI_Xaml!CJupiterControl::HandlePointerMessage+0xfc  (7ffcfd5d8858) [onecoreuap\windows\dxaml\xcp\dxaml\lib\jupitercontrol.cpp @ 754]
    Windows_UI_Xaml!CJupiterWindow::OnIslandPointerMessage+0x108  (7ffcfd5d86cc) [onecoreuap\windows\dxaml\xcp\dxaml\lib\jupiterwindow.cpp @ 2367]
    Windows_UI_Xaml!CXamlIslandRoot::InjectPointerMessage+0x65  (7ffcfd5d857d) [onecoreuap\windows\dxaml\xcp\core\core\elements\xamlislandroot.cpp @ 634]
    Windows_UI_Xaml!Microsoft::WRL::Details::DelegateArgTraits<long  (7ffcfd5d83d9) [onecore\external\sdk\inc\wrl\event.h @ 354]
    InputHost!Microsoft::WRL::Details::DelegateArgTraits<long  (7ffcfaa41607) [onecore\external\sdk\inc\wrl\event.h @ 354]
    InputHost!Microsoft::WRL::InvokeTraits<-2>::InvokeDelegates<<lambda_f45aed66b5921ed661cdce4c5fc41fcc>,Windows::Foundation::ITypedEventHandler<Windows::UI::Internal::Input::PointerInputObserver *,Windows::UI::Core::PointerEventArgs *> >+0x72  (7ffcfaa4017a) [onecore\internal\sdk\inc\wrl\internalevent.h @ 121]
    InputHost!Microsoft::WRL::EventSource<Windows::Foundation::ITypedEventHandler<Windows::UI::Internal::Input::PointerInputObserver *,Windows::UI::Core::PointerEventArgs *>,Microsoft::WRL::InvokeModeOptions<-2> >::DoInvoke<<lambda_f45aed66b5921ed661cdce4c5fc41fcc> >+0x75  (7ffcfaa3ff4d) [onecore\external\sdk\inc\wrl\event.h @ 954]
    InputHost!Microsoft::WRL2::ContextSession::LeaveSession_Callback<<lambda_e3ec73fb4105148165e124077d5d30c6> >+0x77  (7ffcfaa40633) [onecore\private\sdk\inc\wrl2\Wrl2Agile.h @ 1140]
    InputHost!PointerInputObserverWinRT::InvokeEventDirectlyHelper_Callback<Microsoft::WRL2::ContextEventSource<Windows::Foundation::ITypedEventHandler<Windows::UI::Internal::Input::PointerInputObserver *,Windows::UI::Core::PointerEventArgs *>,Microsoft::WRL::InvokeModeOptions<-2> >,PointerInputObserverWinRT::Api>+0x2c  (7ffcfaa402c4) [onecoreuap\windows\moderncore\inputv2\components\attachableinputobject\system\windowsmessagedelivery\client\lib\PointerInputObserverWinRT.h @ 125]
    InputHost!PointerInputObserverWinRT::InvokeEventHelper_Callback<Microsoft::WRL2::ContextEventSource<Windows::Foundation::ITypedEventHandler<Windows::UI::Internal::Input::PointerInputObserver *,Windows::UI::Core::PointerEventArgs *>,Microsoft::WRL::InvokeModeOptions<-2> >,PointerInputObserverWinRT::Api>+0x59  (7ffcfaa4048d) [onecoreuap\windows\moderncore\inputv2\components\attachableinputobject\system\windowsmessagedelivery\client\lib\PointerInputObserverWinRT.h @ 182]
    InputHost!PointerInputObserverWinRT::OnWindowMessage_Callback+0xb3  (7ffcfaa41993) [onecoreuap\windows\moderncore\inputv2\components\attachableinputobject\system\windowsmessagedelivery\client\lib\pointerinputobserverwinrt.cpp @ 437]
    InputHost!<lambda_7ff7aeac0ddd8d862d847848f86f2968>::operator  (7ffcfaa1b70f) [onecoreuap\windows\moderncore\inputv2\components\inputsitemanager\client\lib\system\windowsmessagedeliveryinputsitewinrt.cpp @ 142]
    InputHost!InputSiteWinRT::ForEachAttachedObject+0xca  (7ffcfaa1ac66) [onecoreuap\windows\moderncore\inputv2\components\inputsitemanager\client\lib\system\inputsitewinrt.cpp @ 138]
    InputHost!WindowsMessageDeliveryInputSiteWinRT::OnWindowMessage_Callback+0x8d  (7ffcfaa1b9fd) [onecoreuap\windows\moderncore\inputv2\components\inputsitemanager\client\lib\system\windowsmessagedeliveryinputsitewinrt.cpp @ 137]
    InputHost!SystemIslandInputSiteWinRT::OnWindowMessage_Callback+0x58  (7ffcfaa1d148) [onecoreuap\windows\moderncore\inputv2\components\inputsitemanager\client\lib\system\islandinputsitewinrt.cpp @ 304]
    InputHost!WindowsMessageDeliveryInputSiteWinRT::Private::OnWindowMessage_Callback+0x96  (7ffcfaa1b8f6) [onecoreuap\windows\moderncore\inputv2\components\inputsitemanager\client\lib\system\windowsmessagedeliveryinputsitewinrt.cpp @ 262]
    InputHost!WindowsMessageDeliveryAdapter::ProcessWindowMessage_NoLock+0x10d  (7ffcfaa1dbd1) [onecoreuap\windows\moderncore\inputv2\components\inputsitemanager\client\lib\system\windowsmessagedeliveryadapter.cpp @ 320]
    InputHost!WindowsMessageDeliveryAdapter::StaticWndProc+0xcf  (7ffcfaa1decf) [onecoreuap\windows\moderncore\inputv2\components\inputsitemanager\client\lib\system\windowsmessagedeliveryadapter.cpp @ 262]
    user32!UserCallWinProcCheckWow+0x33c  (7ffd18b91cac) [clientcore\windows\core\ntuser\client\clmsg.cxx @ 282]
    user32!DispatchMessageWorker+0x2a6  (7ffd18b90f06) [clientcore\windows\core\ntuser\client\clmsg.cxx @ 3167]
    WindowsTerminal!wWinMain+0x194  (7ff7bef81404) [C:\a\_work\1\s\src\cascadia\WindowsTerminal\main.cpp @ 149]
    WindowsTerminal!__scrt_common_main_seh+0x106  (7ff7bef8f962) [D:\a\_work\1\s\src\vctools\crt\vcstartup\src\startup\exe_common.inl @ 288]
    kernel32!BaseThreadInitThunk+0x10  (7ffd1a2855a0) [clientcore\base\win32\client\thread.c @ 75]
    ntdll!RtlUserThreadStart+0x2b  (7ffd1a8c485b) [minkernel\ntdll\rtlstrt.c @ 1152]

    Nested Exception (XAML):
       dx ((Windows_UI_Xaml!ErrorContext*)0x2d37ee39130)

=========================
@$xamltriage()                 : Stowed exception
    ErrorCode        : 0xc000027b
    ErrorCodeString  : Stowed exception
    ErrorInfo        : 0x80070005 (Access is denied.) in Microsoft_UI_Xaml!winrt::hresult_error::originate+0x6f
    ErrorMessage     : Access is denied.
    OriginateError   : Access is denied. in Microsoft_UI_Xaml!winrt::hresult_error::originate+0x6f
    StowedExceptions : 2 StowedExceptions

.... ColorPicker::OnPointerMoved? what?

@zadjii-msft commented on GitHub (Aug 1, 2023): ``` 0:000> !xamltriage ------------------------- Callstack for hr=80070005 - Access is denied. Error message: "Access is denied." combase!RoOriginateLanguageException+0x57 (7ffd188f2de7) [onecore\com\combase\winrt\error\error.cpp @ 1517] Microsoft_UI_Xaml!winrt::hresult_error::originate+0x6f (7ffc707aae43) [C:\a\_work\1\s\BuildOutput\Intermediates\x64\Microsoft.UI.Xaml\obj\Generated Files\winrt\base.h @ 4697] Microsoft_UI_Xaml!winrt::hresult_error::hresult_error+0x19f (7ffc707a8b23) [C:\a\_work\1\s\BuildOutput\Intermediates\x64\Microsoft.UI.Xaml\obj\Generated Files\winrt\base.h @ 4630] Microsoft_UI_Xaml!winrt::throw_hresult+0x79 (7ffc707ab42d) [C:\a\_work\1\s\BuildOutput\Intermediates\x64\Microsoft.UI.Xaml\obj\Generated Files\winrt\base.h @ 4829] Microsoft_UI_Xaml!winrt::impl::consume_Windows_UI_Xaml_Controls_IControlOverrides<winrt::Windows::UI::Xaml::Controls::IControlOverrides>::OnPointerMoved+0x27 (7ffc7075c377) [C:\a\_work\1\s\BuildOutput\Intermediates\x64\Microsoft.UI.Xaml\obj\Generated Files\winrt\Windows.UI.Xaml.Controls.h @ 5128] Microsoft_UI_Xaml!winrt::impl::produce<ColorPicker,winrt::Windows::UI::Xaml::Controls::IControlOverrides>::OnPointerMoved+0xa5 (7ffc708179b5) [C:\a\_work\1\s\BuildOutput\Intermediates\x64\Microsoft.UI.Xaml\obj\Generated Files\winrt\Windows.UI.Xaml.Controls.h @ 30979] Windows_UI_Xaml!DirectUI::ControlGenerated::OnPointerMovedProtected+0x1d5686 (7ffcfd7b833a) [onecoreuap\windows\dxaml\xcp\dxaml\lib\winrtgeneratedclasses\control.g.cpp @ 1438] Windows_UI_Xaml!DirectUI::Control::FireEvent+0x2d3 (7ffcfd386483) [onecoreuap\windows\dxaml\xcp\dxaml\lib\control_partial.cpp @ 251] Windows_UI_Xaml!CCoreServices::CLR_FireEvent+0x277 (7ffcfd386907) [onecoreuap\windows\dxaml\xcp\core\dll\xcpcore.cpp @ 3230] Windows_UI_Xaml!CommonBrowserHost::CLR_FireEvent+0x1d (7ffcfd38666d) [onecoreuap\Windows\dxaml\xcp\control\common\shared\CommonBrowserHost.hpp @ 771] Windows_UI_Xaml!CControlBase::ScriptCallback+0x16c (7ffcfd4c353c) [onecoreuap\windows\dxaml\xcp\control\common\shared\controlbase.cpp @ 267] Windows_UI_Xaml!CXcpDispatcher::OnScriptCallback+0x13a (7ffcfd41d71a) [onecoreuap\windows\dxaml\xcp\win\shared\xcpwindow.cpp @ 1376] Windows_UI_Xaml!CXcpDispatcher::OnWindowMessage+0x3d (7ffcfd41d44d) [onecoreuap\windows\dxaml\xcp\win\shared\xcpwindow.cpp @ 1218] Windows_UI_Xaml!CXcpDispatcher::ProcessMessage+0x72 (7ffcfd41d322) [onecoreuap\windows\dxaml\xcp\win\shared\xcpwindow.cpp @ 927] Windows_UI_Xaml!CXcpDispatcher::WindowProc+0x90 (7ffcfd41d220) [onecoreuap\windows\dxaml\xcp\win\shared\xcpwindow.cpp @ 841] user32!UserCallWinProcCheckWow+0x33c (7ffd18b91cac) [clientcore\windows\core\ntuser\client\clmsg.cxx @ 282] user32!DispatchClientMessage+0x9c (7ffd18b917fc) [clientcore\windows\core\ntuser\client\daytona\objfre\amd64\client.cxx @ 3435] user32!__fnDWORD+0x3d (7ffd18ba4c6d) [onecoreuap\restricted\windows\inc\ntuser\inc\ntcb.h @ 1214] ntdll!KiUserCallbackDispatcherContinue (7ffd1a967b84) [minkernel\ntos\rtl\amd64\trampoln.asm @ 607] win32u!ZwUserMessageCall+0x14 (7ffd17dd1434) [onecoreuap\windows\core\umode\moderncore\objfre\amd64\usrstubs.asm @ 197] user32!SendMessageWorker+0x2c4 (7ffd18b90ac4) [clientcore\windows\core\ntuser\client\clmsg.cxx @ 665] user32!SendMessageW+0x137 (7ffd18b90797) [onecoreuap\restricted\windows\inc\private\core\ntuser\client\cltxt.h @ 899] Windows_UI_Xaml!CXcpBrowserHost::SyncScriptCallbackRequest+0x146 (7ffcfd4baa76) [onecoreuap\windows\dxaml\xcp\host\win\browserdesktop\winbrowserhost.cpp @ 1048] Windows_UI_Xaml!CEventManager::Raise+0x513 (7ffcfd3f5203) [onecoreuap\windows\dxaml\xcp\core\dll\eventmgr.cpp @ 887] Windows_UI_Xaml!CEventManager::RaiseRoutedEventBubbling+0x197 (7ffcfd3f4bb7) [onecoreuap\windows\dxaml\xcp\core\dll\eventmgr.cpp @ 1334] Windows_UI_Xaml!ContentRootInput::PointerInputProcessor::ProcessPointerInput+0xd94 (7ffcfd5c89c0) [onecoreuap\windows\dxaml\xcp\components\contentroot\pointerinputprocessor.cpp @ 591] Windows_UI_Xaml!CInputServices::ProcessInput+0x1c2 (7ffcfd3cf572) [onecoreuap\windows\dxaml\xcp\core\input\inputservices.cpp @ 888] Windows_UI_Xaml!CCoreServices::ProcessInput+0x45 (7ffcfd3cf391) [onecoreuap\windows\dxaml\xcp\core\dll\xcpcore.cpp @ 992] Windows_UI_Xaml!CXcpBrowserHost::HandleInputMessage+0x136 (7ffcfd3cf206) [onecoreuap\windows\dxaml\xcp\host\win\browserdesktop\winbrowserhost.cpp @ 1411] Windows_UI_Xaml!CJupiterControl::HandlePointerMessage+0xfc (7ffcfd5d8858) [onecoreuap\windows\dxaml\xcp\dxaml\lib\jupitercontrol.cpp @ 754] Windows_UI_Xaml!CJupiterWindow::OnIslandPointerMessage+0x108 (7ffcfd5d86cc) [onecoreuap\windows\dxaml\xcp\dxaml\lib\jupiterwindow.cpp @ 2367] Windows_UI_Xaml!CXamlIslandRoot::InjectPointerMessage+0x65 (7ffcfd5d857d) [onecoreuap\windows\dxaml\xcp\core\core\elements\xamlislandroot.cpp @ 634] Windows_UI_Xaml!Microsoft::WRL::Details::DelegateArgTraits<long (7ffcfd5d83d9) [onecore\external\sdk\inc\wrl\event.h @ 354] InputHost!Microsoft::WRL::Details::DelegateArgTraits<long (7ffcfaa41607) [onecore\external\sdk\inc\wrl\event.h @ 354] InputHost!Microsoft::WRL::InvokeTraits<-2>::InvokeDelegates<<lambda_f45aed66b5921ed661cdce4c5fc41fcc>,Windows::Foundation::ITypedEventHandler<Windows::UI::Internal::Input::PointerInputObserver *,Windows::UI::Core::PointerEventArgs *> >+0x72 (7ffcfaa4017a) [onecore\internal\sdk\inc\wrl\internalevent.h @ 121] InputHost!Microsoft::WRL::EventSource<Windows::Foundation::ITypedEventHandler<Windows::UI::Internal::Input::PointerInputObserver *,Windows::UI::Core::PointerEventArgs *>,Microsoft::WRL::InvokeModeOptions<-2> >::DoInvoke<<lambda_f45aed66b5921ed661cdce4c5fc41fcc> >+0x75 (7ffcfaa3ff4d) [onecore\external\sdk\inc\wrl\event.h @ 954] InputHost!Microsoft::WRL2::ContextSession::LeaveSession_Callback<<lambda_e3ec73fb4105148165e124077d5d30c6> >+0x77 (7ffcfaa40633) [onecore\private\sdk\inc\wrl2\Wrl2Agile.h @ 1140] InputHost!PointerInputObserverWinRT::InvokeEventDirectlyHelper_Callback<Microsoft::WRL2::ContextEventSource<Windows::Foundation::ITypedEventHandler<Windows::UI::Internal::Input::PointerInputObserver *,Windows::UI::Core::PointerEventArgs *>,Microsoft::WRL::InvokeModeOptions<-2> >,PointerInputObserverWinRT::Api>+0x2c (7ffcfaa402c4) [onecoreuap\windows\moderncore\inputv2\components\attachableinputobject\system\windowsmessagedelivery\client\lib\PointerInputObserverWinRT.h @ 125] InputHost!PointerInputObserverWinRT::InvokeEventHelper_Callback<Microsoft::WRL2::ContextEventSource<Windows::Foundation::ITypedEventHandler<Windows::UI::Internal::Input::PointerInputObserver *,Windows::UI::Core::PointerEventArgs *>,Microsoft::WRL::InvokeModeOptions<-2> >,PointerInputObserverWinRT::Api>+0x59 (7ffcfaa4048d) [onecoreuap\windows\moderncore\inputv2\components\attachableinputobject\system\windowsmessagedelivery\client\lib\PointerInputObserverWinRT.h @ 182] InputHost!PointerInputObserverWinRT::OnWindowMessage_Callback+0xb3 (7ffcfaa41993) [onecoreuap\windows\moderncore\inputv2\components\attachableinputobject\system\windowsmessagedelivery\client\lib\pointerinputobserverwinrt.cpp @ 437] InputHost!<lambda_7ff7aeac0ddd8d862d847848f86f2968>::operator (7ffcfaa1b70f) [onecoreuap\windows\moderncore\inputv2\components\inputsitemanager\client\lib\system\windowsmessagedeliveryinputsitewinrt.cpp @ 142] InputHost!InputSiteWinRT::ForEachAttachedObject+0xca (7ffcfaa1ac66) [onecoreuap\windows\moderncore\inputv2\components\inputsitemanager\client\lib\system\inputsitewinrt.cpp @ 138] InputHost!WindowsMessageDeliveryInputSiteWinRT::OnWindowMessage_Callback+0x8d (7ffcfaa1b9fd) [onecoreuap\windows\moderncore\inputv2\components\inputsitemanager\client\lib\system\windowsmessagedeliveryinputsitewinrt.cpp @ 137] InputHost!SystemIslandInputSiteWinRT::OnWindowMessage_Callback+0x58 (7ffcfaa1d148) [onecoreuap\windows\moderncore\inputv2\components\inputsitemanager\client\lib\system\islandinputsitewinrt.cpp @ 304] InputHost!WindowsMessageDeliveryInputSiteWinRT::Private::OnWindowMessage_Callback+0x96 (7ffcfaa1b8f6) [onecoreuap\windows\moderncore\inputv2\components\inputsitemanager\client\lib\system\windowsmessagedeliveryinputsitewinrt.cpp @ 262] InputHost!WindowsMessageDeliveryAdapter::ProcessWindowMessage_NoLock+0x10d (7ffcfaa1dbd1) [onecoreuap\windows\moderncore\inputv2\components\inputsitemanager\client\lib\system\windowsmessagedeliveryadapter.cpp @ 320] InputHost!WindowsMessageDeliveryAdapter::StaticWndProc+0xcf (7ffcfaa1decf) [onecoreuap\windows\moderncore\inputv2\components\inputsitemanager\client\lib\system\windowsmessagedeliveryadapter.cpp @ 262] user32!UserCallWinProcCheckWow+0x33c (7ffd18b91cac) [clientcore\windows\core\ntuser\client\clmsg.cxx @ 282] user32!DispatchMessageWorker+0x2a6 (7ffd18b90f06) [clientcore\windows\core\ntuser\client\clmsg.cxx @ 3167] WindowsTerminal!wWinMain+0x194 (7ff7bef81404) [C:\a\_work\1\s\src\cascadia\WindowsTerminal\main.cpp @ 149] WindowsTerminal!__scrt_common_main_seh+0x106 (7ff7bef8f962) [D:\a\_work\1\s\src\vctools\crt\vcstartup\src\startup\exe_common.inl @ 288] kernel32!BaseThreadInitThunk+0x10 (7ffd1a2855a0) [clientcore\base\win32\client\thread.c @ 75] ntdll!RtlUserThreadStart+0x2b (7ffd1a8c485b) [minkernel\ntdll\rtlstrt.c @ 1152] ------------------------- Callstack for hr=80070005 - Access is denied. Windows_UI_Xaml!DirectUI::StartDragAsyncOperation::StartIfNeededImpl+0xd9 (7ffcfda64be5) [onecoreuap\windows\dxaml\xcp\dxaml\lib\startdragasyncoperation.cpp @ 81] Windows_UI_Xaml!DirectUI::ListViewBase::OnDragGesture+0x4a0 (7ffcfde72b8c) [onecoreuap\windows\dxaml\xcp\dxaml\lib\listviewbase_partial_reorder.cpp @ 242] Windows_UI_Xaml!DirectUI::ListViewBaseItem::TryStartDrag+0x15c (7ffcfde02b00) [onecoreuap\windows\dxaml\xcp\dxaml\lib\listviewbaseitem_partial.cpp @ 2914] Windows_UI_Xaml!DirectUI::ListViewBaseItem::OnPointerMoved+0x323 (7ffcfd662883) [onecoreuap\windows\dxaml\xcp\dxaml\lib\listviewbaseitem_partial.cpp @ 1332] Microsoft_UI_Xaml!winrt::impl::consume_Windows_UI_Xaml_Controls_IControlOverrides<winrt::Windows::UI::Xaml::Controls::IControlOverrides>::OnPointerMoved+0x17 (7ffc7075c367) [C:\a\_work\1\s\BuildOutput\Intermediates\x64\Microsoft.UI.Xaml\obj\Generated Files\winrt\Windows.UI.Xaml.Controls.h @ 5128] Microsoft_UI_Xaml!winrt::impl::produce<ColorPicker,winrt::Windows::UI::Xaml::Controls::IControlOverrides>::OnPointerMoved+0xa5 (7ffc708179b5) [C:\a\_work\1\s\BuildOutput\Intermediates\x64\Microsoft.UI.Xaml\obj\Generated Files\winrt\Windows.UI.Xaml.Controls.h @ 30979] Windows_UI_Xaml!DirectUI::ControlGenerated::OnPointerMovedProtected+0x1d5686 (7ffcfd7b833a) [onecoreuap\windows\dxaml\xcp\dxaml\lib\winrtgeneratedclasses\control.g.cpp @ 1438] Windows_UI_Xaml!DirectUI::Control::FireEvent+0x2d3 (7ffcfd386483) [onecoreuap\windows\dxaml\xcp\dxaml\lib\control_partial.cpp @ 251] Windows_UI_Xaml!CCoreServices::CLR_FireEvent+0x277 (7ffcfd386907) [onecoreuap\windows\dxaml\xcp\core\dll\xcpcore.cpp @ 3230] Windows_UI_Xaml!CommonBrowserHost::CLR_FireEvent+0x1d (7ffcfd38666d) [onecoreuap\Windows\dxaml\xcp\control\common\shared\CommonBrowserHost.hpp @ 771] Windows_UI_Xaml!CControlBase::ScriptCallback+0x16c (7ffcfd4c353c) [onecoreuap\windows\dxaml\xcp\control\common\shared\controlbase.cpp @ 267] Windows_UI_Xaml!CXcpDispatcher::OnScriptCallback+0x13a (7ffcfd41d71a) [onecoreuap\windows\dxaml\xcp\win\shared\xcpwindow.cpp @ 1376] Windows_UI_Xaml!CXcpDispatcher::OnWindowMessage+0x3d (7ffcfd41d44d) [onecoreuap\windows\dxaml\xcp\win\shared\xcpwindow.cpp @ 1218] Windows_UI_Xaml!CXcpDispatcher::ProcessMessage+0x72 (7ffcfd41d322) [onecoreuap\windows\dxaml\xcp\win\shared\xcpwindow.cpp @ 927] Windows_UI_Xaml!CXcpDispatcher::WindowProc+0x90 (7ffcfd41d220) [onecoreuap\windows\dxaml\xcp\win\shared\xcpwindow.cpp @ 841] user32!UserCallWinProcCheckWow+0x33c (7ffd18b91cac) [clientcore\windows\core\ntuser\client\clmsg.cxx @ 282] user32!DispatchClientMessage+0x9c (7ffd18b917fc) [clientcore\windows\core\ntuser\client\daytona\objfre\amd64\client.cxx @ 3435] user32!__fnDWORD+0x3d (7ffd18ba4c6d) [onecoreuap\restricted\windows\inc\ntuser\inc\ntcb.h @ 1214] ntdll!KiUserCallbackDispatcherContinue (7ffd1a967b84) [minkernel\ntos\rtl\amd64\trampoln.asm @ 607] win32u!ZwUserMessageCall+0x14 (7ffd17dd1434) [onecoreuap\windows\core\umode\moderncore\objfre\amd64\usrstubs.asm @ 197] user32!SendMessageWorker+0x2c4 (7ffd18b90ac4) [clientcore\windows\core\ntuser\client\clmsg.cxx @ 665] user32!SendMessageW+0x137 (7ffd18b90797) [onecoreuap\restricted\windows\inc\private\core\ntuser\client\cltxt.h @ 899] Windows_UI_Xaml!CXcpBrowserHost::SyncScriptCallbackRequest+0x146 (7ffcfd4baa76) [onecoreuap\windows\dxaml\xcp\host\win\browserdesktop\winbrowserhost.cpp @ 1048] Windows_UI_Xaml!CEventManager::Raise+0x513 (7ffcfd3f5203) [onecoreuap\windows\dxaml\xcp\core\dll\eventmgr.cpp @ 887] Windows_UI_Xaml!CEventManager::RaiseRoutedEventBubbling+0x197 (7ffcfd3f4bb7) [onecoreuap\windows\dxaml\xcp\core\dll\eventmgr.cpp @ 1334] Windows_UI_Xaml!ContentRootInput::PointerInputProcessor::ProcessPointerInput+0xd94 (7ffcfd5c89c0) [onecoreuap\windows\dxaml\xcp\components\contentroot\pointerinputprocessor.cpp @ 591] Windows_UI_Xaml!CInputServices::ProcessInput+0x1c2 (7ffcfd3cf572) [onecoreuap\windows\dxaml\xcp\core\input\inputservices.cpp @ 888] Windows_UI_Xaml!CCoreServices::ProcessInput+0x45 (7ffcfd3cf391) [onecoreuap\windows\dxaml\xcp\core\dll\xcpcore.cpp @ 992] Windows_UI_Xaml!CXcpBrowserHost::HandleInputMessage+0x136 (7ffcfd3cf206) [onecoreuap\windows\dxaml\xcp\host\win\browserdesktop\winbrowserhost.cpp @ 1411] Windows_UI_Xaml!CJupiterControl::HandlePointerMessage+0xfc (7ffcfd5d8858) [onecoreuap\windows\dxaml\xcp\dxaml\lib\jupitercontrol.cpp @ 754] Windows_UI_Xaml!CJupiterWindow::OnIslandPointerMessage+0x108 (7ffcfd5d86cc) [onecoreuap\windows\dxaml\xcp\dxaml\lib\jupiterwindow.cpp @ 2367] Windows_UI_Xaml!CXamlIslandRoot::InjectPointerMessage+0x65 (7ffcfd5d857d) [onecoreuap\windows\dxaml\xcp\core\core\elements\xamlislandroot.cpp @ 634] Windows_UI_Xaml!Microsoft::WRL::Details::DelegateArgTraits<long (7ffcfd5d83d9) [onecore\external\sdk\inc\wrl\event.h @ 354] InputHost!Microsoft::WRL::Details::DelegateArgTraits<long (7ffcfaa41607) [onecore\external\sdk\inc\wrl\event.h @ 354] InputHost!Microsoft::WRL::InvokeTraits<-2>::InvokeDelegates<<lambda_f45aed66b5921ed661cdce4c5fc41fcc>,Windows::Foundation::ITypedEventHandler<Windows::UI::Internal::Input::PointerInputObserver *,Windows::UI::Core::PointerEventArgs *> >+0x72 (7ffcfaa4017a) [onecore\internal\sdk\inc\wrl\internalevent.h @ 121] InputHost!Microsoft::WRL::EventSource<Windows::Foundation::ITypedEventHandler<Windows::UI::Internal::Input::PointerInputObserver *,Windows::UI::Core::PointerEventArgs *>,Microsoft::WRL::InvokeModeOptions<-2> >::DoInvoke<<lambda_f45aed66b5921ed661cdce4c5fc41fcc> >+0x75 (7ffcfaa3ff4d) [onecore\external\sdk\inc\wrl\event.h @ 954] InputHost!Microsoft::WRL2::ContextSession::LeaveSession_Callback<<lambda_e3ec73fb4105148165e124077d5d30c6> >+0x77 (7ffcfaa40633) [onecore\private\sdk\inc\wrl2\Wrl2Agile.h @ 1140] InputHost!PointerInputObserverWinRT::InvokeEventDirectlyHelper_Callback<Microsoft::WRL2::ContextEventSource<Windows::Foundation::ITypedEventHandler<Windows::UI::Internal::Input::PointerInputObserver *,Windows::UI::Core::PointerEventArgs *>,Microsoft::WRL::InvokeModeOptions<-2> >,PointerInputObserverWinRT::Api>+0x2c (7ffcfaa402c4) [onecoreuap\windows\moderncore\inputv2\components\attachableinputobject\system\windowsmessagedelivery\client\lib\PointerInputObserverWinRT.h @ 125] InputHost!PointerInputObserverWinRT::InvokeEventHelper_Callback<Microsoft::WRL2::ContextEventSource<Windows::Foundation::ITypedEventHandler<Windows::UI::Internal::Input::PointerInputObserver *,Windows::UI::Core::PointerEventArgs *>,Microsoft::WRL::InvokeModeOptions<-2> >,PointerInputObserverWinRT::Api>+0x59 (7ffcfaa4048d) [onecoreuap\windows\moderncore\inputv2\components\attachableinputobject\system\windowsmessagedelivery\client\lib\PointerInputObserverWinRT.h @ 182] InputHost!PointerInputObserverWinRT::OnWindowMessage_Callback+0xb3 (7ffcfaa41993) [onecoreuap\windows\moderncore\inputv2\components\attachableinputobject\system\windowsmessagedelivery\client\lib\pointerinputobserverwinrt.cpp @ 437] InputHost!<lambda_7ff7aeac0ddd8d862d847848f86f2968>::operator (7ffcfaa1b70f) [onecoreuap\windows\moderncore\inputv2\components\inputsitemanager\client\lib\system\windowsmessagedeliveryinputsitewinrt.cpp @ 142] InputHost!InputSiteWinRT::ForEachAttachedObject+0xca (7ffcfaa1ac66) [onecoreuap\windows\moderncore\inputv2\components\inputsitemanager\client\lib\system\inputsitewinrt.cpp @ 138] InputHost!WindowsMessageDeliveryInputSiteWinRT::OnWindowMessage_Callback+0x8d (7ffcfaa1b9fd) [onecoreuap\windows\moderncore\inputv2\components\inputsitemanager\client\lib\system\windowsmessagedeliveryinputsitewinrt.cpp @ 137] InputHost!SystemIslandInputSiteWinRT::OnWindowMessage_Callback+0x58 (7ffcfaa1d148) [onecoreuap\windows\moderncore\inputv2\components\inputsitemanager\client\lib\system\islandinputsitewinrt.cpp @ 304] InputHost!WindowsMessageDeliveryInputSiteWinRT::Private::OnWindowMessage_Callback+0x96 (7ffcfaa1b8f6) [onecoreuap\windows\moderncore\inputv2\components\inputsitemanager\client\lib\system\windowsmessagedeliveryinputsitewinrt.cpp @ 262] InputHost!WindowsMessageDeliveryAdapter::ProcessWindowMessage_NoLock+0x10d (7ffcfaa1dbd1) [onecoreuap\windows\moderncore\inputv2\components\inputsitemanager\client\lib\system\windowsmessagedeliveryadapter.cpp @ 320] InputHost!WindowsMessageDeliveryAdapter::StaticWndProc+0xcf (7ffcfaa1decf) [onecoreuap\windows\moderncore\inputv2\components\inputsitemanager\client\lib\system\windowsmessagedeliveryadapter.cpp @ 262] user32!UserCallWinProcCheckWow+0x33c (7ffd18b91cac) [clientcore\windows\core\ntuser\client\clmsg.cxx @ 282] user32!DispatchMessageWorker+0x2a6 (7ffd18b90f06) [clientcore\windows\core\ntuser\client\clmsg.cxx @ 3167] WindowsTerminal!wWinMain+0x194 (7ff7bef81404) [C:\a\_work\1\s\src\cascadia\WindowsTerminal\main.cpp @ 149] WindowsTerminal!__scrt_common_main_seh+0x106 (7ff7bef8f962) [D:\a\_work\1\s\src\vctools\crt\vcstartup\src\startup\exe_common.inl @ 288] kernel32!BaseThreadInitThunk+0x10 (7ffd1a2855a0) [clientcore\base\win32\client\thread.c @ 75] ntdll!RtlUserThreadStart+0x2b (7ffd1a8c485b) [minkernel\ntdll\rtlstrt.c @ 1152] Nested Exception (XAML): dx ((Windows_UI_Xaml!ErrorContext*)0x2d37ee39130) ========================= @$xamltriage() : Stowed exception ErrorCode : 0xc000027b ErrorCodeString : Stowed exception ErrorInfo : 0x80070005 (Access is denied.) in Microsoft_UI_Xaml!winrt::hresult_error::originate+0x6f ErrorMessage : Access is denied. OriginateError : Access is denied. in Microsoft_UI_Xaml!winrt::hresult_error::originate+0x6f StowedExceptions : 2 StowedExceptions ``` .... `ColorPicker::OnPointerMoved`? what?
Author
Owner

@DHowett commented on GitHub (Aug 1, 2023):

That's probably the result of identical code folding. That specific produce adapter with that set of arguments is likely to be highly common between all C++/WinRT implementation types in Microsoft.UI.Xaml.dll.

This is almost certainly the DragExperienceHost/DataExchangeHost issue, we just need to figure out why (because we covered the common case where the user is running as a split-token admin.)

@DHowett commented on GitHub (Aug 1, 2023): That's probably the result of identical code folding. That specific `produce` adapter with that set of arguments is likely to be highly common between all C++/WinRT implementation types in `Microsoft.UI.Xaml.dll`. This is almost certainly the DragExperienceHost/DataExchangeHost issue, we just need to figure out _why_ (because we covered the common case where the user is running as a split-token admin.)
Author
Owner

@seamonstr commented on GitHub (Aug 8, 2023):

I have this issue too, and interestingly I'm also using BeyondTrust. Every time I drag a tab, kablooey.

I've emailed you a dump, @zadjii-msft .

@seamonstr commented on GitHub (Aug 8, 2023): I have this issue too, and interestingly I'm also using BeyondTrust. Every time I drag a tab, kablooey. I've emailed you a dump, @zadjii-msft .
Author
Owner

@zadjii-msft commented on GitHub (Sep 21, 2023):

msft:31242389 points at https://github.com/microsoft/microsoft-ui-xaml/issues/3871 and msft:31316551, but I don't think those look right. Especially if this works fine with the WinUI 2 Gallery. Hmm.

@zadjii-msft commented on GitHub (Sep 21, 2023): msft:31242389 points at https://github.com/microsoft/microsoft-ui-xaml/issues/3871 and msft:31316551, but I don't think those look right. Especially if this works fine with the [WinUI 2 Gallery](https://apps.microsoft.com/store/detail/winui-2-gallery/9MSVH128X2ZT). Hmm.
Author
Owner

@lhecker commented on GitHub (Sep 21, 2023):

But it also doesn't repro in the XAML controls gallery. We're not doing too much different than what they do, especially in 1.17. Hmm.

FWIW we do manipulate the tab vector directly, which the gallery probably doesn't do. If it's anything like the navigation view bug we had 1-2 years ago, then manipulating WinUI backing arrays is buggy if there are ongoing animations, etc.
Could that be the cause?

@lhecker commented on GitHub (Sep 21, 2023): > But it also doesn't repro in the XAML controls gallery. We're not doing too much different than what they do, especially in 1.17. Hmm. FWIW we do manipulate the tab vector directly, which the gallery probably doesn't do. If it's anything like the navigation view bug we had 1-2 years ago, then manipulating WinUI backing arrays is buggy if there are ongoing animations, etc. Could that be the cause?
Author
Owner

@zadjii-msft commented on GitHub (Sep 21, 2023):

I dunno - I suppose it depends on when the crash occurs. Does it happen:

  • When you click & hold on the tab?
  • Once you've started moving it (but still inside the tab row)?
  • Once you drag it out of the window?
  • At the moment you drop it (either inside or outside the tab row)?

We should almost certainly limit the investigation to 1.18, since drag/drop was pretty substantially changed in that release.

Just looking at the following blobs:

fc4a37ee91/src/cascadia/TerminalApp/TabManagement.cpp (L1064-L1070)
fc4a37ee91/src/cascadia/TerminalApp/TerminalPage.cpp (L4932-L4970)

Those don't look like they actually modify the underlying array when the drag is starting. So I'd guess the crash is happening later (if it's our fault)


However:
fc4a37ee91/src/cascadia/TerminalApp/TabManagement.cpp (L1072-L1085)

That GetAt isn't guarded, and can throw. If the crash is on the drop, then that might be it. Probably worth fixing, even without confirmation

@zadjii-msft commented on GitHub (Sep 21, 2023): I dunno - I suppose it depends on when the crash occurs. Does it happen: * When you click & hold on the tab? * Once you've started moving it (but still inside the tab row)? * Once you drag it out of the window? * At the moment you drop it (either inside or outside the tab row)? We should almost certainly limit the investigation to 1.18, since drag/drop was pretty substantially changed in that release. Just looking at the following blobs: https://github.com/microsoft/terminal/blob/fc4a37ee9189f2f7335ab942d50381a38a03acf2/src/cascadia/TerminalApp/TabManagement.cpp#L1064-L1070 https://github.com/microsoft/terminal/blob/fc4a37ee9189f2f7335ab942d50381a38a03acf2/src/cascadia/TerminalApp/TerminalPage.cpp#L4932-L4970 Those don't look like they actually modify the underlying array when the drag is starting. So I'd guess the crash is happening later (if it's our fault) ---- However: https://github.com/microsoft/terminal/blob/fc4a37ee9189f2f7335ab942d50381a38a03acf2/src/cascadia/TerminalApp/TabManagement.cpp#L1072-L1085 That `GetAt` isn't guarded, and can throw. If the crash is on the _drop_, then that might be it. Probably worth fixing, even without confirmation
Author
Owner

@mwaltersbmc commented on GitHub (Sep 21, 2023):

Using 1.18.1462.0
Single tab open
Click on tab, hold and release – no crash
Click on tab, move mouse slightly, remaining within tab limits - crash
Add a second tab and repeat using second tab and see the same behavior, crashes as soon as the mouse moves with button held.

@mwaltersbmc commented on GitHub (Sep 21, 2023): Using 1.18.1462.0 Single tab open Click on tab, hold and release – no crash Click on tab, move mouse slightly, remaining within tab limits - crash Add a second tab and repeat using second tab and see the same behavior, crashes as soon as the mouse moves with button held.
Author
Owner

@zadjii-msft commented on GitHub (Sep 21, 2023):

Okay interesting. That's not really the point where I'd expect any of our code to be running1 .

Here's another possibly dumb question - does this repro with the tabs in Notepad? (admittedly, I don't know which version of Windows includes the tabbed notepad.exe exactly, but I think you can get it from the Store)


  1. other than TerminalPage::_TabDragStarted, which doesn't really look possible to crash 🤔 ↩︎

@zadjii-msft commented on GitHub (Sep 21, 2023): Okay interesting. That's not really the point where I'd expect any of our code to be running[^1]. Here's another possibly dumb question - does this repro with the tabs in Notepad? (admittedly, I don't know which version of Windows includes the tabbed notepad.exe exactly, but I think you can get it from [the Store](https://www.microsoft.com/store/productid/9MSMLRH6LZF3?ocid=pdpshare)) [^1]: other than `TerminalPage::_TabDragStarted`, which doesn't really look possible to crash 🤔
Author
Owner

@mwaltersbmc commented on GitHub (Sep 21, 2023):

Windows Notepad 11.2306.15.0

Issue does not reproduce – able to drag and rearrange tabs without crashing.

@mwaltersbmc commented on GitHub (Sep 21, 2023): Windows Notepad 11.2306.15.0 Issue does not reproduce – able to drag and rearrange tabs without crashing.
Author
Owner

@lhecker commented on GitHub (Sep 21, 2023):

@zadjii-msft FYI What I meant is the manipulation of _tabView.TabItems() which is a vector owned by the WUX::Controls class.
It's similar to our previous use of SettingsNav().MenuItems() which resulted in random crashes.

@lhecker commented on GitHub (Sep 21, 2023): @zadjii-msft FYI What I meant is the manipulation of `_tabView.TabItems()` which is a vector owned by the `WUX::Controls` class. It's similar to our previous use of `SettingsNav().MenuItems()` which resulted in random crashes.
Author
Owner

@zadjii-msft commented on GitHub (Sep 21, 2023):

WELL that certainly would seem to point the finger at us.


CXamlIslandRoot::OnIslandPointerMoved ... _tabRow.PointerMoved({ get_weak(), &TerminalPage::_RestorePointerCursorHandler }); -

image

... Nah that seems like a dead end.

What I meant is the manipulation of _tabView.TabItems() which is a vector owned by the WUX::Controls class.

Oh I mean, that's certainly bound for pain. But at this point,

Single tab open ... Click on tab, move mouse slightly, remaining within tab limits - crash

we haven't done any tomfoolery with the TabItems yet, other than just add one.


Gonna keep picking through this dump but I can't find anything useful.

@zadjii-msft commented on GitHub (Sep 21, 2023): WELL that certainly would seem to point the finger at us. --- `CXamlIslandRoot::OnIslandPointerMoved` ... `_tabRow.PointerMoved({ get_weak(), &TerminalPage::_RestorePointerCursorHandler });` - ![image](https://github.com/microsoft/terminal/assets/18356694/a4101e40-2950-4e35-9f8e-9a4fefb6a593) ... Nah that seems like a dead end. > What I meant is the manipulation of `_tabView.TabItems()` which is a vector owned by the `WUX::Controls` class. Oh I mean, that's certainly bound for pain. But at this point, > Single tab open ... Click on tab, move mouse slightly, remaining within tab limits - crash we haven't done any tomfoolery with the TabItems yet, other than just add one. --- Gonna keep picking through this dump but I can't find _anything_ useful.
Author
Owner

@mwaltersbmc commented on GitHub (Oct 26, 2023):

I've just downloaded and tested Windows Terminal Preview v1.19.2831.0 and it fixes this issue. I can click on tabs and drag them to reorder or break out to a new window without crashing. Thank you!

Tested on the same Windows 11 system where Version: 1.19.2682.0 crashes attempting the same actions. I downloaded the new x64 release zip, unpacked to a new directory, created several SSH profiles that I frequently use and tested the actions that would fail on earlier versions. No crashes.

@mwaltersbmc commented on GitHub (Oct 26, 2023): I've just downloaded and tested Windows Terminal Preview v1.19.2831.0 and it fixes this issue. I can click on tabs and drag them to reorder or break out to a new window without crashing. Thank you! Tested on the same Windows 11 system where Version: 1.19.2682.0 crashes attempting the same actions. I downloaded the new x64 release zip, unpacked to a new directory, created several SSH profiles that I frequently use and tested the actions that would fail on earlier versions. No crashes.
Author
Owner

@zadjii-msft commented on GitHub (Oct 26, 2023):

I've just downloaded and tested Windows Terminal Preview v1.19.2831.0 and it fixes this issue

🙃

Well. That sure doesn't make any sense. Maybe this really was #16016 after all? @seamonstr you too?

@zadjii-msft commented on GitHub (Oct 26, 2023): > I've just downloaded and tested Windows Terminal Preview v1.19.2831.0 and it fixes this issue # 🙃 Well. That sure doesn't make any sense. Maybe this really was #16016 after all? @seamonstr you too?
Author
Owner

@Summerh15 commented on GitHub (Oct 26, 2023):

U kno I'm waiting on my new new software n devices so I can add all my
information it's alot at least 100 tb

On Thu., Oct. 26, 2023, 8:29 a.m. Mike Griese, @.***>
wrote:

I've just downloaded and tested Windows Terminal Preview v1.19.2831.0 and
it fixes this issue

🙃

Well. That sure doesn't make any sense. Maybe this really was #16016
https://github.com/microsoft/terminal/pull/16016 after all? @seamonstr
https://github.com/seamonstr you too?


Reply to this email directly, view it on GitHub
https://github.com/microsoft/terminal/issues/15689#issuecomment-1781243397,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AY7KJTBS25MWRQMCDSNEI4DYBJXT5AVCNFSM6AAAAAA2FTB4R6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOBRGI2DGMZZG4
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

@Summerh15 commented on GitHub (Oct 26, 2023): U kno I'm waiting on my new new software n devices so I can add all my information it's alot at least 100 tb On Thu., Oct. 26, 2023, 8:29 a.m. Mike Griese, ***@***.***> wrote: > I've just downloaded and tested Windows Terminal Preview v1.19.2831.0 and > it fixes this issue > > 🙃 > > Well. That sure doesn't make any sense. Maybe this really was #16016 > <https://github.com/microsoft/terminal/pull/16016> after all? @seamonstr > <https://github.com/seamonstr> you too? > > — > Reply to this email directly, view it on GitHub > <https://github.com/microsoft/terminal/issues/15689#issuecomment-1781243397>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AY7KJTBS25MWRQMCDSNEI4DYBJXT5AVCNFSM6AAAAAA2FTB4R6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOBRGI2DGMZZG4> > . > You are receiving this because you are subscribed to this thread.Message > ID: ***@***.***> >
Author
Owner

@seamonstr commented on GitHub (Oct 27, 2023):

That's exciting... I'm on holiday at the moment, so I don't have access to
the machine that shows the issue. I'll update on Monday!

S

On Thu, 26 Oct 2023 at 15:27, Mike Griese @.***> wrote:

I've just downloaded and tested Windows Terminal Preview v1.19.2831.0 and
it fixes this issue

🙃

Well. That sure doesn't make any sense. Maybe this really was #16016
https://github.com/microsoft/terminal/pull/16016 after all? @seamonstr
https://github.com/seamonstr you too?


Reply to this email directly, view it on GitHub
https://github.com/microsoft/terminal/issues/15689#issuecomment-1781243397,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA6SI6CKEIMV6BVXUDJ7N6DYBJXNTAVCNFSM6AAAAAA2FTB4R6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOBRGI2DGMZZG4
.
You are receiving this because you were mentioned.Message ID:
@.***>

@seamonstr commented on GitHub (Oct 27, 2023): That's exciting... I'm on holiday at the moment, so I don't have access to the machine that shows the issue. I'll update on Monday! S On Thu, 26 Oct 2023 at 15:27, Mike Griese ***@***.***> wrote: > I've just downloaded and tested Windows Terminal Preview v1.19.2831.0 and > it fixes this issue > > 🙃 > > Well. That sure doesn't make any sense. Maybe this really was #16016 > <https://github.com/microsoft/terminal/pull/16016> after all? @seamonstr > <https://github.com/seamonstr> you too? > > — > Reply to this email directly, view it on GitHub > <https://github.com/microsoft/terminal/issues/15689#issuecomment-1781243397>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AA6SI6CKEIMV6BVXUDJ7N6DYBJXNTAVCNFSM6AAAAAA2FTB4R6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOBRGI2DGMZZG4> > . > You are receiving this because you were mentioned.Message ID: > ***@***.***> >
Author
Owner

@seamonstr commented on GitHub (Oct 27, 2023):

Sorry, nope… 2831 still crashes after the teeniest little drag within a tab.

Happy to supply whatever info I can to debug…

On Fri, 27 Oct 2023 at 07:27, Simon Woodward @.***> wrote:

That's exciting... I'm on holiday at the moment, so I don't have access to
the machine that shows the issue. I'll update on Monday!

S

On Thu, 26 Oct 2023 at 15:27, Mike Griese @.***>
wrote:

I've just downloaded and tested Windows Terminal Preview v1.19.2831.0 and
it fixes this issue

🙃

Well. That sure doesn't make any sense. Maybe this really was #16016
https://github.com/microsoft/terminal/pull/16016 after all? @seamonstr
https://github.com/seamonstr you too?


Reply to this email directly, view it on GitHub
https://github.com/microsoft/terminal/issues/15689#issuecomment-1781243397,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA6SI6CKEIMV6BVXUDJ7N6DYBJXNTAVCNFSM6AAAAAA2FTB4R6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOBRGI2DGMZZG4
.
You are receiving this because you were mentioned.Message ID:
@.***>

@seamonstr commented on GitHub (Oct 27, 2023): Sorry, nope… 2831 still crashes after the teeniest little drag within a tab. Happy to supply whatever info I can to debug… On Fri, 27 Oct 2023 at 07:27, Simon Woodward ***@***.***> wrote: > That's exciting... I'm on holiday at the moment, so I don't have access to > the machine that shows the issue. I'll update on Monday! > > S > > On Thu, 26 Oct 2023 at 15:27, Mike Griese ***@***.***> > wrote: > >> I've just downloaded and tested Windows Terminal Preview v1.19.2831.0 and >> it fixes this issue >> >> 🙃 >> >> Well. That sure doesn't make any sense. Maybe this really was #16016 >> <https://github.com/microsoft/terminal/pull/16016> after all? @seamonstr >> <https://github.com/seamonstr> you too? >> >> — >> Reply to this email directly, view it on GitHub >> <https://github.com/microsoft/terminal/issues/15689#issuecomment-1781243397>, >> or unsubscribe >> <https://github.com/notifications/unsubscribe-auth/AA6SI6CKEIMV6BVXUDJ7N6DYBJXNTAVCNFSM6AAAAAA2FTB4R6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOBRGI2DGMZZG4> >> . >> You are receiving this because you were mentioned.Message ID: >> ***@***.***> >> >
Author
Owner

@mwaltersbmc commented on GitHub (Nov 12, 2023):

Some further testing shows something a bit odd - using the WindowsTerminal app from the release download Microsoft.WindowsTerminalPreview_1.19.2831.0_x64.zip file the problem does not happen. I just unzipped the archive and double clicked on the binary to start the app. Dragging tabs does not cause a crash.
Terminal (Unpackaged)
Version: 1.19.231010001-preview

However, having updated my already installed Terminal preview app using Microsoft.WindowsTerminalPreview_1.19.2831.0_8wekyb3d8bbwe.msixbundle, I do get a crash when dragging tabs!
Windows Terminal Preview
Version: 1.19.2831.0

@mwaltersbmc commented on GitHub (Nov 12, 2023): Some further testing shows something a bit odd - using the WindowsTerminal app from the release download Microsoft.WindowsTerminalPreview_1.19.2831.0_x64.zip file the problem does not happen. I just unzipped the archive and double clicked on the binary to start the app. Dragging tabs does not cause a crash. Terminal (Unpackaged) Version: 1.19.231010001-preview However, having updated my already installed Terminal preview app using Microsoft.WindowsTerminalPreview_1.19.2831.0_8wekyb3d8bbwe.msixbundle, I do get a crash when dragging tabs! Windows Terminal Preview Version: 1.19.2831.0
Author
Owner

@zadjii-msft commented on GitHub (Nov 13, 2023):

wat

that's insane. I have no idea why that would make a difference. The package identity itself? That's insane. Especially since the WinUI 2 Gallery would also have package identity...

@zadjii-msft commented on GitHub (Nov 13, 2023): wat that's insane. I have no idea why that would make a difference. The package identity itself? That's insane. Especially since the WinUI 2 Gallery would also have package identity...
Author
Owner

@mwaltersbmc commented on GitHub (Nov 13, 2023):

It may be related to permissions. I have the working wt.exe in c:\temp and if I open a DOS or PowerShell command prompt in that dir and run wt.exe then I can drag tabs without a crash. If I open the command prompt with "Run as administrator" launch wt.exe then dragging causes a crash.

@mwaltersbmc commented on GitHub (Nov 13, 2023): It may be related to permissions. I have the working wt.exe in c:\temp and if I open a DOS or PowerShell command prompt in that dir and run wt.exe then I can drag tabs without a crash. If I open the command prompt with "Run as administrator" launch wt.exe then dragging causes a crash.
Author
Owner

@zadjii-msft commented on GitHub (Nov 13, 2023):

If I open the command prompt with "Run as administrator" launch wt.exe then dragging causes a crash

Oh, elevated (as admin) vs unelevated might be a valuable data point here. There's literally endless issues with elevated drag/drop. I don't think you're supposed to be able to do that at all actually

@zadjii-msft commented on GitHub (Nov 13, 2023): > If I open the command prompt with "Run as administrator" launch wt.exe then dragging causes a crash Oh, elevated (as admin) vs unelevated might be a valuable data point here. There's literally endless issues with elevated drag/drop. I don't think you're supposed to be able to do that at all actually
Author
Owner

@mwaltersbmc commented on GitHub (Nov 13, 2023):

When I launch Terminal from the GUI it shows in Task Manager as running from C:\Program Files\WindowsApps\Microsoft.WindowsTerminalPreview_1.19.2831.0_x64__8wekyb3d8bbwe

However

cd "C:\Program Files\WindowsApps\Microsoft.WindowsTerminalPreview_1.19.2831.0_x64__8wekyb3d8bbwe"
Access is denied.

But I can dir the contents.

I've worked around the problem by creating a copy of the working set up in c:\apps\wt and running it from there and I can drag without issue - may be worth a shot @seamonstr

@mwaltersbmc commented on GitHub (Nov 13, 2023): When I launch Terminal from the GUI it shows in Task Manager as running from C:\Program Files\WindowsApps\Microsoft.WindowsTerminalPreview_1.19.2831.0_x64__8wekyb3d8bbwe However >cd "C:\Program Files\WindowsApps\Microsoft.WindowsTerminalPreview_1.19.2831.0_x64__8wekyb3d8bbwe" Access is denied. But I can dir the contents. I've worked around the problem by creating a copy of the working set up in c:\apps\wt and running it from there and I can drag without issue - may be worth a shot @seamonstr
Author
Owner

@mwaltersbmc commented on GitHub (Nov 15, 2023):

If I open the command prompt with "Run as administrator" launch wt.exe then dragging causes a crash

Oh, elevated (as admin) vs unelevated might be a valuable data point here. There's literally endless issues with elevated drag/drop. I don't think you're supposed to be able to do that at all actually

Tested on a Windows 10 system - run terminal as normal user and I can drag tabs without issue. Run elevated via right click Run As Admin and tab dragging doesn't work. No crash, dragging just doesn't do anything. Perhaps the BeyondTrust software is doing something odd with the way it handles elevated permissions.

The workaround of running the Terminal binary from the x64 release download rather than installed via the store is working for me so I'm happy to close this.

@mwaltersbmc commented on GitHub (Nov 15, 2023): > > If I open the command prompt with "Run as administrator" launch wt.exe then dragging causes a crash > > Oh, elevated (as admin) vs unelevated might be a valuable data point here. There's literally endless issues with elevated drag/drop. I don't think you're supposed to be able to do that at all actually Tested on a Windows 10 system - run terminal as normal user and I can drag tabs without issue. Run elevated via right click Run As Admin and tab dragging doesn't work. No crash, dragging just doesn't do anything. Perhaps the BeyondTrust software is doing something odd with the way it handles elevated permissions. The workaround of running the Terminal binary from the x64 release download rather than installed via the store is working for me so I'm happy to close this.
Author
Owner

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

Run elevated via right click Run As Admin and tab dragging doesn't work.

FWIW, that's unfortunately by design: #6661. The drag-drop service will CRASH YOUR APP if you run an app elevated and try to drag/drop tabs.

Perhaps that actually leads to the root cause here? Maybe BeyondTrust is getting up in the drag/drop service's business, and causing the drag/drop service to crash, bringing the Terminal down with it. We pre-emptively disable dragging if we know we're elevated (a known case that will crash us), but maybe there's something else unique going on here.

Then again, I dunno why it would act differently for the store package vs the unpackaged version 🤷

@zadjii-msft commented on GitHub (Nov 15, 2023): > Run elevated via right click Run As Admin and tab dragging doesn't work. FWIW, that's unfortunately by design: #6661. The drag-drop service will CRASH YOUR APP if you run an app elevated and try to drag/drop tabs. Perhaps that actually leads to the root cause here? Maybe BeyondTrust is getting up in the drag/drop service's business, and causing the drag/drop service to crash, bringing the Terminal down with it. We pre-emptively disable dragging if we know we're elevated (a known case that will crash us), but maybe there's something else unique going on here. Then again, I dunno why it would act differently for the store package vs the unpackaged version 🤷
Author
Owner

@korpx commented on GitHub (May 24, 2024):

The bug is still in v1.19.3172.0

@korpx commented on GitHub (May 24, 2024): The bug is still in v1.19.3172.0
Author
Owner

@korpx commented on GitHub (May 24, 2024):

The bug is still in v1.20.11271.0

@korpx commented on GitHub (May 24, 2024): The bug is still in v1.20.11271.0
Author
Owner

@SiMoStro commented on GitHub (Jun 3, 2024):

Always replicating with 1.20.11215.0
This happens only when starting the Terminal with "Run as Administrator".

WindowsTerminal.exe.25164.dmp.zip
WindowsTerminal.exe.25364.dmp.zip

@SiMoStro commented on GitHub (Jun 3, 2024): Always replicating with 1.20.11215.0 This happens only when starting the Terminal with "Run as Administrator". [WindowsTerminal.exe.25164.dmp.zip](https://github.com/user-attachments/files/15530431/WindowsTerminal.exe.25164.dmp.zip) [WindowsTerminal.exe.25364.dmp.zip](https://github.com/user-attachments/files/15530432/WindowsTerminal.exe.25364.dmp.zip)
Author
Owner

@zadjii-msft commented on GitHub (Jun 3, 2024):

This happens only when starting the Terminal with "Run as Administrator"

excuse me what? I was pretty confident that tab dragging is disabled entirely when running as Admin1 . If it's not, then yea - the Terminal will always crash if a tab is dragged in an admin window.

@zadjii-msft commented on GitHub (Jun 3, 2024): > This happens only when starting the Terminal with "Run as Administrator" excuse me _what_? I was pretty confident that tab dragging is _disabled entirely_ when running as Admin[^1]. If it's not, then yea - the Terminal will always crash if a tab is dragged in an admin window. [^1]: See: https://github.com/microsoft/terminal/blob/01e4df152e6e4d5156ef394412eb63025f7d743b/src/cascadia/TerminalApp/TerminalPage.cpp#L175-L176 -> https://github.com/microsoft/terminal/blob/01e4df152e6e4d5156ef394412eb63025f7d743b/src/cascadia/TerminalApp/AppLogic.cpp#L140 -> https://github.com/microsoft/terminal/blob/01e4df152e6e4d5156ef394412eb63025f7d743b/src/types/utils.cpp#L680
Author
Owner

@SiMoStro commented on GitHub (Jun 3, 2024):

Don't know what to say; in Admin mode tabs can be reordered, and it crashes 🤷
And no matter if it's the ZIP or the Store-installed version: it's the same for both.

@SiMoStro commented on GitHub (Jun 3, 2024): Don't know what to say; in Admin mode tabs **can** be reordered, and it crashes 🤷 And no matter if it's the ZIP or the Store-installed version: it's the same for both.
Author
Owner

@seamonstr commented on GitHub (Jun 3, 2024):

Indeed.

My long term battling of this issue was that terminal was ALWAYS running as
admin (I suspect something our corporate IT people set up), and I had to
super careful to not drag a tab instinctively because I’d lose all my
sessions in the ensuing crash!

On Mon, 3 Jun 2024 at 13:31, Simone Galleni @.***>
wrote:

Don't know what to say; in Admin mode tabs can be reordered, and it
crashes 🤷
And no matter if it's the ZIP or the Store-installed version: it's the
same for both.


Reply to this email directly, view it on GitHub
https://github.com/microsoft/terminal/issues/15689#issuecomment-2145085581,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA6SI6CEDZKZNJBCQ7BNCUDZFRO2HAVCNFSM6AAAAAA2FTB4R6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNBVGA4DKNJYGE
.
You are receiving this because you were mentioned.Message ID:
@.***>

@seamonstr commented on GitHub (Jun 3, 2024): Indeed. My long term battling of this issue was that terminal was ALWAYS running as admin (I suspect something our corporate IT people set up), and I had to super careful to not drag a tab instinctively because I’d lose all my sessions in the ensuing crash! On Mon, 3 Jun 2024 at 13:31, Simone Galleni ***@***.***> wrote: > Don't know what to say; in Admin mode tabs *can* be reordered, and it > crashes 🤷 > And no matter if it's the ZIP or the Store-installed version: it's the > same for both. > > — > Reply to this email directly, view it on GitHub > <https://github.com/microsoft/terminal/issues/15689#issuecomment-2145085581>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AA6SI6CEDZKZNJBCQ7BNCUDZFRO2HAVCNFSM6AAAAAA2FTB4R6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNBVGA4DKNJYGE> > . > You are receiving this because you were mentioned.Message ID: > ***@***.***> >
Author
Owner

@noheromen commented on GitHub (Dec 12, 2024):

Issue still persist even on latest release 1.21.3231.0. Seems like drag and drop is not disabled when run in Admin, or something is interferring with it. I do not have BeyondTrust.

Please fix it, I lost already a lot of sessions due to this bug.... really annoying. I know I can run it in normal mode instead of Admin, but I prefer Admin mode... Thanks

@noheromen commented on GitHub (Dec 12, 2024): Issue still persist even on latest release 1.21.3231.0. Seems like drag and drop is not disabled when run in Admin, or something is interferring with it. I do not have BeyondTrust. Please fix it, I lost already a lot of sessions due to this bug.... really annoying. I know I can run it in normal mode instead of Admin, but I prefer Admin mode... Thanks
Author
Owner

@GaoChX commented on GitHub (Dec 18, 2024):

I also encountered this issue in release 1.21.3231.0. Here is my crash file: WindowsTerminal.exe.18780.dmp

It is worth noting that when I try to reproduce the issue, it doesn't crash, but when I'm working, this problem often occurs unexpectedly.

@GaoChX commented on GitHub (Dec 18, 2024): I also encountered this issue in release 1.21.3231.0. Here is my crash file: [WindowsTerminal.exe.18780.dmp](https://github.com/user-attachments/files/18174472/WindowsTerminal.exe.18780.dmp) It is worth noting that when I try to reproduce the issue, it doesn't crash, but when I'm working, this problem often occurs unexpectedly.
Author
Owner

@vlomba0 commented on GitHub (Dec 18, 2024):

Happens to me all the time

@vlomba0 commented on GitHub (Dec 18, 2024): Happens to me all the time
Author
Owner

@nickdalt commented on GitHub (Mar 6, 2025):

I see this all the time, across many versions. Crash usually occurs a short time after the tab is re-attached to main window.

Doesn't appear to be related to the tab content, not associated with Admin

@nickdalt commented on GitHub (Mar 6, 2025): I see this all the time, across many versions. Crash usually occurs a short time after the tab is re-attached to main window. Doesn't appear to be related to the tab content, not associated with Admin
Author
Owner

@seamonstr commented on GitHub (Mar 7, 2025):

It’s a different bug, in that case. This was very clearly associated with
dragging a tab as admin, and the crash happens immediately on drag.

On Thu, 6 Mar 2025 at 22:09, nickdalt @.***> wrote:

I see this all the time, across many versions. Crash usually occurs a
short time after the tab is re-attached to main window.

Doesn't appear to be related to the tab content, not associated with Admin


Reply to this email directly, view it on GitHub
https://github.com/microsoft/terminal/issues/15689#issuecomment-2704835665,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA6SI6EZ73HXQ3RF7YVAFAD2TCTO3AVCNFSM6AAAAAA2FTB4R6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMBUHAZTKNRWGU
.
You are receiving this because you were mentioned.Message ID:
@.***>
[image: nickdalt]nickdalt left a comment (microsoft/terminal#15689)
https://github.com/microsoft/terminal/issues/15689#issuecomment-2704835665

I see this all the time, across many versions. Crash usually occurs a
short time after the tab is re-attached to main window.

Doesn't appear to be related to the tab content, not associated with Admin


Reply to this email directly, view it on GitHub
https://github.com/microsoft/terminal/issues/15689#issuecomment-2704835665,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA6SI6EZ73HXQ3RF7YVAFAD2TCTO3AVCNFSM6AAAAAA2FTB4R6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMBUHAZTKNRWGU
.
You are receiving this because you were mentioned.Message ID:
@.***>

@seamonstr commented on GitHub (Mar 7, 2025): It’s a different bug, in that case. This was very clearly associated with dragging a tab as admin, and the crash happens immediately on drag. On Thu, 6 Mar 2025 at 22:09, nickdalt ***@***.***> wrote: > I see this all the time, across many versions. Crash usually occurs a > short time after the tab is re-attached to main window. > > Doesn't appear to be related to the tab content, not associated with Admin > > — > Reply to this email directly, view it on GitHub > <https://github.com/microsoft/terminal/issues/15689#issuecomment-2704835665>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AA6SI6EZ73HXQ3RF7YVAFAD2TCTO3AVCNFSM6AAAAAA2FTB4R6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMBUHAZTKNRWGU> > . > You are receiving this because you were mentioned.Message ID: > ***@***.***> > [image: nickdalt]*nickdalt* left a comment (microsoft/terminal#15689) > <https://github.com/microsoft/terminal/issues/15689#issuecomment-2704835665> > > I see this all the time, across many versions. Crash usually occurs a > short time after the tab is re-attached to main window. > > Doesn't appear to be related to the tab content, not associated with Admin > > — > Reply to this email directly, view it on GitHub > <https://github.com/microsoft/terminal/issues/15689#issuecomment-2704835665>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AA6SI6EZ73HXQ3RF7YVAFAD2TCTO3AVCNFSM6AAAAAA2FTB4R6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMBUHAZTKNRWGU> > . > You are receiving this because you were mentioned.Message ID: > ***@***.***> >
Author
Owner

@0bbedCode commented on GitHub (Mar 14, 2025):

Each time I accidently drag a Tab its best to not drag it back, when I drag it back it crashes all the tabs.
So now I am in a state of "oops it was dragged out, exit it open a new tab on main tabs, etc"

Where can I get the logs this sht is pssing me off, my buddy forced me to get this sh*t (sorry for rage)

@0bbedCode commented on GitHub (Mar 14, 2025): Each time I accidently drag a Tab its best to not drag it back, when I drag it back it crashes all the tabs. So now I am in a state of "oops it was dragged out, exit it open a new tab on main tabs, etc" Where can I get the logs this sh*t is p*ssing me off, my buddy forced me to get this sh*t (sorry for rage)
Author
Owner

@zadjii-msft commented on GitHub (Apr 16, 2025):

WAIT HOLD ON

People who are hitting this - are you running Terminal as a different user?

@zadjii-msft commented on GitHub (Apr 16, 2025): WAIT HOLD ON People who are hitting this - are you running Terminal _as a different user_?
Author
Owner

@noheromen commented on GitHub (Apr 17, 2025):

No just running as admin

@noheromen commented on GitHub (Apr 17, 2025): No just running as admin
Author
Owner

@dean0123 commented on GitHub (Jun 13, 2025):

1.22.11141.0 on windows 10.0.19045 crash every time when drag the tab, every time

@dean0123 commented on GitHub (Jun 13, 2025): 1.22.11141.0 on windows 10.0.19045 crash every time when drag the tab, every time
Author
Owner

@jimmysadlek commented on GitHub (Jun 16, 2025):

1.22.11141.0:
This has been occurring for a very long time. It's a running joke at work, so many people experience this. This crashes every single time I drag a tab - even one pixel.

@jimmysadlek commented on GitHub (Jun 16, 2025): 1.22.11141.0: This has been occurring for a very long time. It's a running joke at work, so many people experience this. This crashes every single time I drag a tab - even one pixel.
Author
Owner

@lhecker commented on GitHub (Jun 16, 2025):

This has been occurring for a very long time. It's a running joke at work, so many people experience this.

FWIW, we've had crash reports before caused by AVs and similar software injecting themselves into Windows Terminal. If your entire organization has this issue, there's a decent change that's not an issue on our side.


I took a look at the last dump shared above, and at least that one points to an issue in the rendering code. #18632 is an attempt from me trying to fix issues like that. You can test it by installing Windows Terminal Canary here: https://aka.ms/terminal-canary-installer
(It cleanly uninstalls again once you stop needing it.)

@lhecker commented on GitHub (Jun 16, 2025): > This has been occurring for a very long time. It's a running joke at work, so many people experience this. FWIW, we've had crash reports before caused by AVs and similar software injecting themselves into Windows Terminal. If your entire organization has this issue, there's a decent change that's not an issue on our side. --- I took a look at the last dump shared above, and at least that one points to an issue in the rendering code. #18632 is an attempt from me trying to fix issues like that. You can test it by installing Windows Terminal Canary here: https://aka.ms/terminal-canary-installer (It cleanly uninstalls again once you stop needing it.)
Author
Owner

@seamonstr commented on GitHub (Jun 16, 2025):

Yes, that was our experience. There was something bizarre in our corporate
build that meant terminal always ran as admin.

I mean, is there no way to detect that the crash will happen and just
disable dragging?

On Mon, 16 Jun 2025 at 13:09, Leonard Hecker @.***>
wrote:

lhecker left a comment (microsoft/terminal#15689)
https://github.com/microsoft/terminal/issues/15689#issuecomment-2976376644

This has been occurring for a very long time. It's a running joke at work,
so many people experience this.

FWIW, we've had crash reports before caused by AVs and similar software
injecting themselves into Windows Terminal. If your entire organization has
this issue, there's a decent change that's not an issue on our side.

I took a look at the last dump shared above, and at least that one points
to an issue in the rendering code. #18632
https://github.com/microsoft/terminal/pull/18632 is an attempt from me
trying to fix issues like that. You can test it by installing Windows
Terminal Canary here: https://aka.ms/terminal-canary-installer
(It cleanly uninstalls again once you stop needing it.)


Reply to this email directly, view it on GitHub
https://github.com/microsoft/terminal/issues/15689#issuecomment-2976376644,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA6SI6AM2JHMENL6LF6JGEL3D2XYRAVCNFSM6AAAAAA2FTB4R6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSNZWGM3TMNRUGQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

@seamonstr commented on GitHub (Jun 16, 2025): Yes, that was our experience. There was something bizarre in our corporate build that meant terminal always ran as admin. I mean, is there no way to detect that the crash will happen and just disable dragging? On Mon, 16 Jun 2025 at 13:09, Leonard Hecker ***@***.***> wrote: > *lhecker* left a comment (microsoft/terminal#15689) > <https://github.com/microsoft/terminal/issues/15689#issuecomment-2976376644> > > This has been occurring for a very long time. It's a running joke at work, > so many people experience this. > > FWIW, we've had crash reports before caused by AVs and similar software > injecting themselves into Windows Terminal. If your entire organization has > this issue, there's a decent change that's not an issue on our side. > ------------------------------ > > I took a look at the last dump shared above, and at least that one points > to an issue in the rendering code. #18632 > <https://github.com/microsoft/terminal/pull/18632> is an attempt from me > trying to fix issues like that. You can test it by installing Windows > Terminal Canary here: https://aka.ms/terminal-canary-installer > (It cleanly uninstalls again once you stop needing it.) > > — > Reply to this email directly, view it on GitHub > <https://github.com/microsoft/terminal/issues/15689#issuecomment-2976376644>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AA6SI6AM2JHMENL6LF6JGEL3D2XYRAVCNFSM6AAAAAA2FTB4R6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSNZWGM3TMNRUGQ> > . > You are receiving this because you were mentioned.Message ID: > ***@***.***> >
Author
Owner

@lhecker commented on GitHub (Jun 16, 2025):

We already do that:
bd7e3179ff/src/cascadia/TerminalApp/TerminalPage.cpp (L171-L174)

bd7e3179ff/src/types/utils.cpp (L962-L998)

What's possible is that the CanUwpDragDrop logic is faulty. If you can figure out whether that's the case (and why that is), it would be more than welcome. 🙂

@lhecker commented on GitHub (Jun 16, 2025): We already do that: https://github.com/microsoft/terminal/blob/bd7e3179ff1c41e9147d99253a9ab150cf9e942a/src/cascadia/TerminalApp/TerminalPage.cpp#L171-L174 https://github.com/microsoft/terminal/blob/bd7e3179ff1c41e9147d99253a9ab150cf9e942a/src/types/utils.cpp#L962-L998 What's possible is that the `CanUwpDragDrop` logic is faulty. If you can figure out whether that's the case (and why that is), it would be more than welcome. 🙂
Author
Owner

@gastmaier commented on GitHub (Dec 5, 2025):

Still occur on 1.24.2682.0, I would say add an option to disable drag and drop.
This has not yet been fixed in 2 years, it is pretty atrocious UX and there is a Move tab > Move to new window as a fallback.
I always loose my work by accidentally dragging and dropping.

@gastmaier commented on GitHub (Dec 5, 2025): Still occur on 1.24.2682.0, I would say add an option to disable drag and drop. This has not yet been fixed in 2 years, it is pretty atrocious UX and there is a `Move tab > Move to new window` as a fallback. I always loose my work by accidentally dragging and dropping.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#20215