Bug: Microsoft.UI.Input.dll crash

[Fixerup]

Description

Files keeps dying on me, sometimes more than once per hour. This seems to happen when I have several tabs open on various folders and then I double-click on a Microsoft Word file in one of these folders. I've been using Files for a while, but this particular problem only showed up in the last month or two.
Here's what the Event Viewer had to say about it. This is just ONE of the many crashes:

Faulting application name: Files.exe, version: 1.0.0.0, time stamp: 0x666b0000
Faulting module name: Microsoft.UI.Input.dll, version: 10.0.26105.1010, time stamp: 0x5e0e88e0
Exception code: 0xc0000409
Fault offset: 0x00000000000c6572
Faulting process id: 0x0xDB2C
Faulting application start time: 0x0x1DB2494945806C4
Faulting application path: C:\Program Files\WindowsApps\49306atecsolution.FilesUWP_3.7.11.0_x64__et10x9a9vyk8t\Files.App\Files.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.WindowsAppRuntime.1.5_5001.275.500.0_x64__8wekyb3d8bbwe\Microsoft.UI.Input.dll
Report Id: a1f82e54-6b72-43c4-9344-97e07f3fe2c2
Faulting package full name: 49306atecsolution.FilesUWP_3.7.11.0_x64__et10x9a9vyk8t
Faulting package-relative application ID: App

Fault bucket 1980408209663435559, type 5
Event Name: MoBEX
Response: Not available
Cab Id: 0

Problem signature:
P1: 49306atecsolution.FilesUWP_3.7.11.0_x64__et10x9a9vyk8t
P2: praid:App
P3: 1.0.0.0
P4: 666b0000
P5: Microsoft.UI.Input.dll
P6: 10.0.26105.1010
P7: 5e0e88e0
P8: 00000000000c6572
P9: c0000409
P10: 0000000000000007

Attached files:
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.4cd503be-6cce-4597-9a74-f6e2c421a711.tmp.mdmp
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.a96dd111-081a-49a2-bd9b-840d7779895d.tmp.WERInternalMetadata.xml
WPR_initiated_DiagTrackMiniLogger_OneTrace_User_Logger_20240808_1_EC_0_inject.etl
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.22eb3f03-d106-4498-9b34-4bf5e838b1fa.tmp.etl
WPR_initiated_DiagTrackMiniLogger_WPR System Collector_inject.etl
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.1d6e6b6f-fffd-484c-b1d8-1e29e6930e2f.tmp.etl
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.6eeab71e-af55-4ab1-b696-67678a777bd2.tmp.csv
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.4cd28aa8-70ee-4dae-a1e2-85541bb43cba.tmp.txt
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.283c9a1d-ca3f-4348-846a-8b26a6a6f30d.tmp.xml

These files may be available here:
\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_49306atecsolutio_bd5659e266e8567d28bdb8fd395e76d3d9131a_2f4cc691_ad82b1bc-a40f-432b-bd7e-d14c9a71c6b3

Analysis symbol:
Rechecking for solution: 0
Report Id: a1f82e54-6b72-43c4-9344-97e07f3fe2c2
Report Status: 268435456
Hashed bucket: e95f507f9e79bb4abb7bd2c62741a327
Cab Guid: 0

Steps To Reproduce

This seems to happen when I have several tabs open on various folders and then I double-click on a Microsoft Word file in one of these folders.

Requirements

• e.g. Fix crash that occurs when...

Files Version

3.7.11.0

Windows Version

10.0.22631.4317

User ID

77daf46a-22bc-4e4c-92bb-5a668ed15f5a

Log File

debug.log

[0x5bfa]

Thank you for the report.

Can you try:

• Restart Windows
• Reinstall Files

Looks similar to #16161.

[Fixerup]

#16161 does sound similar to my problem.

Except I've been using Files with OneDrive folders, not Google Drive.

This problem started just in the last month or two.

Uninstalling/reinstalling Files does not prevent this bug.
Neither does rebooting Windows.

Are there any other files I can send you to help pinpoint this bug? Event Viewer mentioned several files.

[yaira2]

I don't see any reports in Sentry for your user id. Are the repro steps you mentioned consistent?

[gustassou]

My files also crashes with both google drive and dropbox... Very annoying

[dany23K]

Same problem here

Faulting application name: Files.exe, version: 1.0.0.0, time stamp: 0x666b0000
Faulting module name: Microsoft.UI.Input.dll, version: 10.0.26105.1011, time stamp: 0x4f04f05e
Exception code: 0xc0000409
Fault offset: 0x00000000000c6572
Faulting process id: 0x0x75C0
Faulting application start time: 0x0x1DB4B7409769AB3
Faulting application path: C:\Program Files\WindowsApps\Files_3.8.0.0_x64__1y0xx7n9077q4\Files.App\Files.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.WindowsAppRuntime.1.5_5001.311.2039.0_x64__8wekyb3d8bbwe\Microsoft.UI.Input.dll
Report Id: 89eb7a47-e94b-4185-9fd9-79067cc2e57e
Faulting package full name: Files_3.8.0.0_x64__1y0xx7n9077q4
Faulting package-relative application ID: App

Steps To Reproduce
I was proving this app for my first time. When I open it, it crashes 10-15 min later every time even if its only open without any task to do. Also I have a synolgy drive as my own cloud.

[Fixerup]

Since others have mentioned the cloud:
With me, these exact same crashes seem to happen when I'm viewing a folder stored in OneDrive. I don't have to be interacting with Files at all. It just crashes spontaneously even when I'm working with other programs or none at all.

I thought I had fixed the problem by completely uninstalling Files and then reinstalling it. That seemed to work for a while. But then the same problem started happening again.

[Hawksprey420]

This had been happening to me in both Files (3.8) stable and Files-Preview (latest is 3.8.10.0) as well.

I don't know if this is a result of unreasonable use and even expected to happen, or maybe not haha.

Steps on how I did it on my end (applies to both Files versions):

1. Open Files.

2. Open a new tab, then click or select a file (replicated with PDFs, Word, PowerPoint files)

3. Open the preview pane.

In step 3, it goes two ways:

• If you click the details' part, and then go another tab, it would be stable and not crash itself.
• If you click the preview part, then select another tab to go to, then go back after some time, or manipulate with the previewed file in the preview pane, it would insta-crash the app and provide the error log in the Event Viewer.

It also can be reproduced when:

• Switching the preview pane from details to preview too quickly. (based on my observation)
  Event Viewer logs:
  --

For Files Stable:
Faulting application name: Files.exe, version: 1.0.0.0, time stamp: 0x666b0000
Faulting module name: Microsoft.UI.Input.dll, version: 10.0.26105.1011, time stamp: 0x4f04f05e
Exception code: 0xc0000409
Fault offset: 0x00000000000c6572
Faulting process id: 0x5084
Faulting application start time: 0x1DB5BC874AB8466
Faulting application path: C:\Program Files\WindowsApps\Files_3.8.0.0_x64__1y0xx7n9077q4\Files.App\Files.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.WindowsAppRuntime.1.5_5001.311.2039.0_x64__8wekyb3d8bbwe\Microsoft.UI.Input.dll
Report Id: 72a0e57d-433a-4b90-a191-ba91c8ad69ea
Faulting package full name: Files_3.8.0.0_x64__1y0xx7n9077q4
Faulting package-relative application ID: App

For Files Preview:
Faulting application name: Files.exe, version: 1.0.0.0, time stamp: 0x666b0000
Faulting module name: Microsoft.UI.Input.dll, version: 10.0.26105.1011, time stamp: 0x4f04f05e
Exception code: 0xc0000409
Fault offset: 0x00000000000c6572
Faulting process id: 0x5CFC
Faulting application start time: 0x1DB5BC8DEE017C6
Faulting application path: C:\Program Files\WindowsApps\FilesPreview_3.8.10.0_x64__1y0xx7n9077q4\Files.App\Files.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.WindowsAppRuntime.1.5_5001.311.2039.0_x64__8wekyb3d8bbwe\Microsoft.UI.Input.dll
Report Id: 1e01f8a7-190c-43d8-ba4f-6d7546efd9bb
Faulting package full name: FilesPreview_3.8.10.0_x64__1y0xx7n9077q4
Faulting package-relative application ID: App

Files-Stable debug.log:
debug.log

Files-Preview debug log:
debug.log