Files
Files copied to clipboard
Application Won't Start
Description
I tried latest from the store and the preview version, same result. Installed the app and attempted to run, nothing happens. Tried terminating and clearing data which didn't change anything. I did locate crash dumps in the CrashDumps folder which I have attached below.
Steps To Reproduce
- Install the application
- Attempt to run
Requirements
Application should run.
Files Version
2.5.10.0
Windows Version
22621.1848
Log File
@jwhipp thank you for the report, do you have the log file from the app data folder?
You can find the debug.log file by typing %localappdata%\Packages\FilesPreview_wvne1zexy08sa\LocalState
in Windows File Explorer path bar
I have one folder written today with "Files" in the name under %localappdata%\Packages called "49306atecsolution.FilesUWP_et10x9a9vyk8t", however, LocalState under that dir is empty.
Are other apps like Phone Link working? Phone Link is a good example because it uses the same framework as Files.
I ran that app specifically and it does fire up.
After you attempt to open Files, are there any "error" entries in Event View under Application Logs? https://www.windowscentral.com/how-use-event-viewer-windows-10
Good call, that got us something to work with.
Faulting application name: Files.exe, version: 1.0.0.0, time stamp: 0x648f9b5c Faulting module name: KERNELBASE.dll, version: 10.0.22621.1928, time stamp: 0xe9af6ed4 Exception code: 0xc00000fd Fault offset: 0x000000000000ca5d Faulting process id: 0x0x4D30 Faulting application start time: 0x0x1D9B3A1A7B34160 Faulting application path: C:\Program Files\WindowsApps\49306atecsolution.FilesUWP_2.5.10.0_x64__et10x9a9vyk8t\Files.App\Files.exe Faulting module path: C:\Windows\System32\KERNELBASE.dll Report Id: b09e466f-0e7d-4335-a3c3-de93ea8ef353 Faulting package full name: 49306atecsolution.FilesUWP_2.5.10.0_x64__et10x9a9vyk8t Faulting package-relative application ID: App
Probably this exception (stack overflow) was causing when loading kernelbase.dll and is OS side problem.
That error code is for a stack overflow exception. This may be an issue with WASDK's bootstrapper..
@jwhipp can you check if this is an issue in the latest preview build? The preview build is using an updated version of WinAppSdk so I'm curious if the issue was resolved. https://files.community/download
We're now launching, looks like whatever changed fixed the issue.
Excellent! Thanks for the update.