Closed suntong closed 4 years ago
Not familiar with choco installation, I'd guess you should have admin privilege to run the installation. Or try to install the original installer of this project to check please.
I am running every installation with admin privilege
will report to the choco installation author and try scoop instead.
Holly smoke, when I said "This is a corporate PC with excessive restrictions", I wasn't joking at all -- when I tried to install the original installer of this project, the downloaded .exe disappeared right after I launched it:
Talking about excessive restrictions! My lord!
If wsltty installer, choco and scoop all fail, there's still the option to install cygwin, download the wsltty archive from here and run make install
. A small number of additional cygwin packages would be needed for which there is currently no overview, gcc, make and unzip at least.
Alternatively, the wsltty installer can be extracted in a folder with 7ZIP like tools but it will not generate the shortcuts.
If you run the install.bat
script, all configuration should be done. If, on the other hand, the installer gets deleted by some anti-virus policy before you can unpack it, you're out of luck. For that case, I may provide an additional zip archive if needed.
Thanks you all for chipping in offering help.
Currently I'm contacting the choco installer author for help, as it seems our anti-virus watches over browser download only, and not over the cinst scripts yet (touch woods).
Failing that, I can try ask for exceptions from my IT department, although the chance is slim, I'd like to exhaust all my options before coming back asking for more help.
will let you know...
Is this still an issue or can we close it?
Sorry for the delay. The thing is, I decided to go through IT to white-list it, albeit it'll take a long time, but it will be the least hassle way of doing things. However, three months passed but I haven't heard from IT yet.
I'll give cinst scripts another go tomorrow. If all failed, then, yes, we may need an additional zip archive...
You mean an archive of the binary distribution, instead of an installer?
Yeah, exactly, but hold on,as I said,
I'd like to exhaust all my options before coming back asking for more help.
Hmm... I'm closing this, as I don't think there is anything you can do at your end to make things work for the situation like this.
This is what I've just tried:
iwr 'https://aelius.keybase.pub/wsltty.portable.3.3.0.nupkg' -OutFile wsltty.portable.3.3.0.nupkg
iwr :
D01We found a security threat.
Website blocked
You tried to visit: https://aelius.keybase.pub/wsltty.portable.3.3.0.nupkg
Threat found: Virus
See our internet use policy.
Need help? Contact our support team at ...
Your organization has selected Zscaler to protect you from internet threats.
At line:1 char:1
+ iwr 'https://aelius.keybase.pub/wsltty.portable.3.3.0.nupkg' -OutFile ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (System.Net.HttpWebRequest:HttpWebRequest) [Invoke-WebRequest], WebExcept
ion
+ FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeWebRequestCommand
I have made a zip file manually as a test case. Can you install wsltty with this? wsltty-3.4.2-x86_64.zip
Instruction: unzip the archive, go into the folder and invoke its install.bat
script.
Oh, YES! this works for me!
Thank you very much @mintty for going the extra miles helping people like me. Really appreciate it!
I'm so happy. Thanks again!
Try this. Download the wsltty installer in a WSL2 installation. Then extract all the files from it with p7zip. The installer is a self extracting file, so 7zip can extract it. The anti-virus may not scan into WSL2 VHDX file.
Ah, so that could save me from adding a zip file to the build and distribution. But where do Windows users get 7zip from?
I think I'll make it a "cabinet" file, to save all complications.
Released 3.4.3 with build of cab file. Adding instruction to project page.
Thanks, that's the best option, as I'm still using WSL, not WSL2. I.e., the files in WSL are not hiding within WSL2 VHDX file, but reside in plain sight, albeit a bit hard to find.
You would normally download and unpack the archive file at Windows level, so it doesn't matter what WSL you use.
Released 3.4.4.
I got:
This is a corporate PC with excessive restrictions. I checked the log and it turns out to be:
Since I have tons of chocolatey packages installed, I'm sure there is a way to overcome such restriction (of calling
Get-OSArchitectureWidth
).