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
Can't install new version (4.3.4) ? #14603
Comments
I usually get this error if I try to launch the installer from a networked disk (or VM shared disk). Try launching it from a local disk. |
Scratch that. I now see the path at the top of the dialog. Supposedly it is launched from the local disk. Does the v4.3.3 installer show the same error? |
What I say might sound silly, but when an AV program quarantines the file silently I've seen this error message. It is worth checking if the setup file still exists in the download location. |
What do you mean "exists" ? It is still there. I can check "properties" on it. I can delete it. I can restore it... |
The issue seems to appear for some other installers, but not for some others. |
@showstoppre I think you are right. I think it's because of these settings on MS defender: Why does it occur? What is the setting here that caused it (I disabled all and now it installs fine) ? |
@AndroidDeveloperLB Windows defender decided to not play nice with qBittorrent recently: #14489 |
qBittorrent version and Operating System
Windows.
qbittorrent_4.3.4_x64_setup.exe
What is the problem
I try to install the app as it told me there is a new version.
What is the expected behavior
Should work fine like it always.
Steps to reproduce
Extra info(if any)
This is what I get, even if I run as admin:
"Windows cannot access the specific device, path or file. You may not have the appropriate permission to access the item".
Just to check that it's not some weird web browser issue, I tried to open an installer of Android Studio (an exe file, just like in this case) :
https://developer.android.com/studio
Worked fine (meaning it started the installer and didn't have this error).
The text was updated successfully, but these errors were encountered: