Open Ealfardan opened 4 days ago
Thanks for the report, the log doesn't show any error message, Can you type Event Viewer
into the Windows start menu search > Click Windows logs > Click Application > Screenshot any errors that have Files.exe shown on the first line
Error details:
Log Name: Application
Source: Application Error
Date: 2024-11-13 5:07:32 PM
Event ID: 1000
Task Category: Application Crashing Events
Level: Error
Keywords:
User: EMKF-LENOVO\emkfa
Computer: EMKF-Lenovo
Description:
Faulting application name: Files.exe, version: 1.0.0.0, time stamp: 0x666b0000
Faulting module name: Microsoft.UI.Xaml.dll, version: 3.1.5.0, time stamp: 0xc7b159d6
Exception code: 0xc0000005
Fault offset: 0x0000000000072c5a
Faulting process id: 0x0x3ED0
Faulting application start time: 0x0x1DB35D50E9F31A2
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.Xaml.dll
Report Id: 237b0398-9fb5-4d99-b4b6-7c0e8d620dd7
Faulting package full name: 49306atecsolution.FilesUWP_3.7.11.0_x64__et10x9a9vyk8t
Faulting package-relative application ID: App
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" Guid="{a0e9b465-b939-57d7-b27d-95d8e925ff57}" />
<EventID>1000</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>100</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2024-11-13T14:07:32.8292519Z" />
<EventRecordID>23695</EventRecordID>
<Correlation />
<Execution ProcessID="14412" ThreadID="23556" />
<Channel>Application</Channel>
<Computer>EMKF-Lenovo</Computer>
<Security UserID="S-1-5-21-3368623369-3077475623-2865081394-1001" />
</System>
<EventData>
<Data Name="AppName">Files.exe</Data>
<Data Name="AppVersion">1.0.0.0</Data>
<Data Name="AppTimeStamp">666b0000</Data>
<Data Name="ModuleName">Microsoft.UI.Xaml.dll</Data>
<Data Name="ModuleVersion">3.1.5.0</Data>
<Data Name="ModuleTimeStamp">c7b159d6</Data>
<Data Name="ExceptionCode">c0000005</Data>
<Data Name="FaultingOffset">0000000000072c5a</Data>
<Data Name="ProcessId">0x3ed0</Data>
<Data Name="ProcessCreationTime">0x1db35d50e9f31a2</Data>
<Data Name="AppPath">C:\Program Files\WindowsApps\49306atecsolution.FilesUWP_3.7.11.0_x64__et10x9a9vyk8t\Files.App\Files.exe</Data>
<Data Name="ModulePath">C:\Program Files\WindowsApps\Microsoft.WindowsAppRuntime.1.5_5001.275.500.0_x64__8wekyb3d8bbwe\Microsoft.UI.Xaml.dll</Data>
<Data Name="IntegratorReportId">237b0398-9fb5-4d99-b4b6-7c0e8d620dd7</Data>
<Data Name="PackageFullName">49306atecsolution.FilesUWP_3.7.11.0_x64__et10x9a9vyk8t</Data>
<Data Name="PackageRelativeAppId">App</Data>
</EventData>
</Event>
Description
It happens when opening a file from within a zipped folder, whenever the file closes, Files closes with it. Even after the zip is extracted, the behavior persists within the same session.
Steps To Reproduce
Another way:
Files Version
3.7.11.0
Windows Version
10.0.22631.4317
User ID
854f6bbd-70be-4a0f-84e1-4747a9e7a84b
Log File
debug_server.log debug.log