Files app permanently froze after launching it a few times from cmd
Description
I am using the non-microsoft store version of Files App, Installed it an hour ago.
All was working fine, a bit slow, but still working. Until I tried going to directories from the CMD.
I read from a previous issue that there was a cmd command to use Files app https://github.com/files-community/Files/pull/6558#issuecomment-947072067
Now the app is unresponsive and loads nothing except the default tags Re-starting the app also does not fix the issue.
Steps To Reproduce
- Have Files open
- Try out the following cmd commands (don't know which is actually the faulty one)
2.1.
files.exe2.2.files.exe -Directory "..."(replace...with a directory) 2.3.files.exe -select "..."(replace...with a directory) - re-open files
Requirements
I expect one of the above commands to work, as I believe this was implemented from a previous issue. I expect Files to load correctly.
Files Version
3.4.0.0
Windows Version
Windows 10 22H2 19045.4291
Log File
No log file available
Thanks for the feedback.
What happens if you close Files from the system tray and open normally from the Start menu > All apps.
What happens if you close Files from the system tray and open normally from the Start menu > All apps.
(sorry it took a while to answer) Nothing changes then, it remains in this broken state
It looks like InnerNavToolBar doesn’t know what the page is shown in the active shell page, and AddressToolbar looks like its ViewModel is not loaded because SidebarView.PaneHolder property is null. This seems sometimes to happen first TabBar item is not added and loaded before anywhere else starts to load. As almost all function is in AddressToolBar, the buttons, such as Back, Forward and Up don't load its icon, but somehow Refresh icon is loaded because it references CommandManager in code-behind. This proves that DI is loaded correctly.
Is this still an issue in the preview version? https://files.community/download/
If it is, please upload the log file so we can investigate further.
Is this still an issue in 3.7.11?