title | layout | filename |
---|---|---|
Frequently Asked Questions |
default |
faq |
Many versions of Windows 11 and Windows 10 operating systems exists, and they run on a wide range of hardware. Sometimes a specific operating system and/or specific hardware might crash the app. If the app is crashing, please email the log.txt, config.json, device information (such as device model and screen resolution) to the developer ([email protected]) with steps to reproduce the crash.
By default, the config.json file should be located in the folder location similar to the one shown below. Replace with the actual user name.
C:\Users\<UserName>\AppData\Local\Packages\43158JPTGamesandApps.ShresthaFiles-AModernDualPane_pnxmbr0ydfejr\LocalState
Alternately, you can click the
Open Application Folder
icon on the top right side of the
Log Viewer
to load the folder.
Log file (log.txt) is stored in
C:\Users\<UserName>\AppData\Local\Packages\43158JPTGamesandApps.ShresthaFiles-AModernDualPane_pnxmbr0ydfejr\TempState
Alternately, click on the Log Viewer
-> Open Full Log
to open log file in a text viewer (such as the Notepad).
The tabs, bookmarks, and other settings are stored in config.json file. Sometimes newer version of config file is not compatible with older version of config. When newer versions are installed, the app attempts to update the config file. Sometimes this process might fail, and the config file may be reset. In such cases, you can try to recover tabs, bookmarks, and other settings from backed up config file(s). The LocalState folder will may have other versions of config file such as config.failed.json that was saved when the app failed to read the previous config.json the last time. Similary, config.prior.json should have the version from the last version of the app. config.successful.json stores the last config file that was read successfully. More back ups are stored in the temporary location C:\Users\<UserName>\AppData\Local\Packages\43158JPTGamesandApps.ShresthaFiles-AModernDualPane_pnxmbr0ydfejr\LocalCache\ConfigBackups
folder. The contents in this temporary location may be deleted by Windows automatically over time.
Sometimes the config file (that stores the settings for the app) changes in the newer version. While attempts are made to upgrade the config files automatically, sometimes such process fails and can crash the app. In such case, you might need to rename the config.json and its versions in the LocalState folder or move them to other locations. Launch the app again and save settings (Ctrl+S) and a new config.json will be created. You can manually import desired previus settings from the existing config files that you just moved or renamed.
Make sure the app was not running when you edited and saved the config.json file. The application saves the config.json while closing the app. If you edited the config.json when the application was running, it will be overridden by the values in the memory. Thus, make sure the app is closed while editing the config.json. Then save the config.json, and launch the app afterwards.
If the config.json is edited improperly, the app will fail to read the config.json. In such case, the app will try to read previous version of config.json. If that fails as well, it will rest the settings. The app attempts to back up config files that it failed to read and it should be stored in the App folder.
There are two potential methods to ease accessing network locations.
- Type the location (e.g. "\share\foldername") in the path and navigate to the folder. Now bookmark the path (Ctrl + D) or right click and Pin to Navigation Bar.
- Map the location as a drive from Windows File Explorer. The path will now show up in the list of drives in Shrestha Files!
The Pro X version is updated more often than the Free version. Some features are available only in the Pro X version. The free version shows a prompt requesting to consider purchasing the Pro X version every time it is launched. Users' support is essential to continue improving the app further. This includes sharing the apps to others, providing feedback, sending bug information, requesting new features, and purchasing the Pro X version. While all feature requests cannot be fulfilled, the developer will attempt to fulfill features that are requested by more users which requires less effort to implement.