-
Notifications
You must be signed in to change notification settings - Fork 775
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stuck at extracting if the executable is located at the root of a network share/drive #608
Comments
I tried placing the file in the root of a network share, but it still updated successfully. Can you provide the ZipExtractor.log file that is created in "%temp%" folder? It will give better info about the issue. |
I got stucked too, but I was put app in driver root like D:\ instead of \network_share. 2023-04-26 20:01:19 ZipExtractor started with following command line arguments. 2023-04-26 20:03:02 ZipExtractor started with following command line arguments. 2023-04-26 20:05:11 ZipExtractor started with following command line arguments. |
I created a PR to fix this problem #616 |
@ravibpatel I can confirm the issue is resolved. Thank you for the fix! |
@ravibpatel could you please also update the NuGet package to 1.8.1 Thanks in advance! |
I tagged the new release. It should be available on NuGet soon. |
@ravibpatel Thank you, Im going to update the new release |
For example if the executable is located at \network_share, the updater will stuck at the extracting sequence.
If the executable is located at \network_share\any folder, the updater can extract and and update the exe successfully.
The text was updated successfully, but these errors were encountered: