Bug: Microsoft.UI.Input.dll cause crash

[wuyilingwei]

Description

It seems to be an error originating from Microsoft.UI.Input.dll

Faulting application name: Files.exe, version: 1.0.0.0, time stamp: 0x666b0000
Faulting module name: Microsoft.UI.Input.dll, version: 10.0.26105.1013, time stamp: 0xee9442fe
Exception code: 0xc0000409
Fault offset: 0x00000000000c6572
Faulting process ID: 0x0x88D8
Faulting application start time: 0x0x1DBACB1FBF24BFD
Faulting application path: C:\Program Files\WindowsApps\49306atecsolution.FilesUWP_3.9.1.0_x64__et10x9a9vyk8t\Files.App\Files.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.WindowsAppRuntime.1.5_5001.373.1736.0_x64__8wekyb3d8bbwe\Microsoft.UI.Input.dll
Report ID: d7be8c97-5ce0-4b65-8405-bee583f8a2a7
Faulting package full name: 49306atecsolution.FilesUWP_3.9.1.0_x64__et10x9a9vyk8t
Faulting package relative application ID: App

I tried reinstall runtime from https://download.microsoft.com/download/cac5c52a-4b8b-4036-8616-3ef102badaed/WindowsAppRuntimeInstall-x86.exe , but not any help.

Steps To Reproduce

Open a OneDrive folder (not sure if it is associated)

After a while/try to open/right-click to create a file, there is a chance that the entire program will crash

Files Version

3.9.1.0

Windows Version

10.0.22631.5189

User ID

9a9d7334-3ac0-4870-a4ae-9503d5f3c117

Log File

There is no relevant log entry at the time when the error occurred

[Josh65-2201]

Thanks for the report, can you see if this is an issue in the preview version. https://files.community/download

[wuyilingwei]

It seems not, and the crash of the official version of files also stopped after the system restart. I can't reproduce the previous reason now. There are two possibilities:
One is that in certain circumstances, files will still crash after files restart, but the system restart will solve the unknown problem;
The second is that the WindowsAppRuntime library repair needs a system restart, but I think it is unlikely unless it is cached in memory. After I performed the SDK repair, I was not prompted to restart to apply the changes, so I think this is unlikely, but MS's recent code is a piece of shit, it's possible that they forgot to add a hint.
I will continue to pay attention to this problem, but I have not been able to successfully reproduce it for the time being, so I will close the issue first.

[wuyilingwei]

I found that it appeared again, still indicating that it was a problem with \Microsoft.UI.Input.dll and there was no error log