-
Notifications
You must be signed in to change notification settings - Fork 907
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
Strange behavior when running behind the "Hotspot Shield" VPN app. #1291
Comments
There is some detection going on Normally we'd say this was a packaging issue, but this looks like a possible issue with Chocolatey. Can you provide the contents of |
@ferventcoder Thank you for the follow up. This is the ".registry" file in the mentioned directory:
|
@BehzadV and this was just due to running the program, not installing/upgrading it at the same time (or letting it auto-upgrade)? |
Well, |
I'm talking about the Hotspot VPN, not Elixir. The registry snapshot is taken prior to install and after install. The before and after are compared to produce this Since this publisher notes a log location for uninstall, it is likely they have one on your system for any installs they do as well. You may want to look around and review to see if the timing for the package install in |
Actually, now that I look in
|
Also, apparently Hotspot doesn't keep a file log of its happenings ( |
Now this is making me wonder - some packages have queried WMI I wonder if either of these packages were doing something similar. Without the full log, I have no idea what version of Chocolatey you have installed nor the environment it is installed in. Please provide that full output log so we can get an awareness of those aspects. Thanks! |
Hey,
So i had chocolatey install elixir (choco install elixir) on my windows, when I noticed this in the logs:
I was running the Hotspot Shield VPN application during installation.
Also, the Hotspot Shield directory (C:\Program Files (x86)\Hotspot Shield) is void of any elixir related files.
Here is the last parts of the log:
Maybe an issue only related to logging?
The text was updated successfully, but these errors were encountered: