Tested Windows 10 only. We could support both 10, 8 . I’ll have to get an 8 image. Would be good to test on different releases anyways. Support for Windows 7 for a little while since it reaches EOL in a few months.
Microsoft recently announced that it will officially begin the Windows 7 end of life phase on Jan. 14, 2020. On that day, the company will stop supporting Windows 7 on laptops and desktops, and will no longer patch it with security updates.
First time extracting had an error. My guess would be Norton antivirus or Windows defender interrupted the process which cause the issue? Started the extraction over and everything went fine. Repeated the Download/installation a few more time with no issues.
When installing from Whonix.org, Windows automatically restarts (to finish installation?) This only happened after build when:
Norton quarantined Whonix.exe at the start of build and the installer obviously wouldn’t work. But a file is created .\Output\InstallWhonix.exe that works to install Whonix when executed. However, when run this also restarted Windows the same as above. The whonix-installer.exe did not do this.(Windows restart)
You appear to execute this program from a folder which doesn’t contain the necessary files for it to operate properly. Please try reinstalling this program via the Whonix-Installer. If the program persists, please contact the developer at:
https://forums.whonix.org
I’ve had this same issue when running the Whonix Installer.
To recap. This happened when:
(after building from source) I ran the wrong executable (InstallWhonix.exe) which is built along side the Whonix Installer and can be found in \current_working_directory\InstallWhonix.exe
This is one of the reasons for changing the installer name from Install Whonix.exe to whonix-installer.exe . (to prevent confusion)
Not sure of the purpose of this executable?
When Norton anti-virus qaurantines a needed file when the whonix-installer.exe is run. This has happen to me more than a few times…
Obviously there could be other reasons for this issue.
This is a common fix for Windows users. But I think we can do better…
When I start working on development again I plan on trying to resolve this issue and work on better error handling for the installer.
If anyone is having issues with the Whonix installer you will likely receive a faster response by asking your question on the Whonix forum as opposed to emailing myself or Whonix developers directly.
I don’t mind answering questions via email, but when questions are asked in the Whonix public forums, all community members can benefit from the answers provided by the Whonix team and greater community.
I personally usually refuse to help by e-mail, unless professional (paid) support requests. And link to Free Support for Whonix ™ (Unless something minor.)
(Needless to say: everyone is free to e-mail anyone of course.)
gpg4win website nowdays has a valid, CA signed TLS certificate / functional https. Therefore chapter for manual TLS certificate installation remove.d
Is there still any point of downloading SignTools from microsoft.com to use it to verify gpg4win? Connecting to microsoft.com over TLS only vs connecting to gpg4win.org over TLS only seems to be equally dangerous. There seems to be a bootstrapping problem of securely obtaining gpg4win on the Windows platform anyhow.
Or is initially downloading SignTools (which then will be used to verify gpg4win) from microsoft.com more secure because microsoft.com is on the TLS Static Public Key Pinning list?
TLS Public Key Pinning (HPKP) was deprecated but does TLS Static Public Key Pinning still exist?
It’s not just about the connection. It’d be much more unlikely for a massive company like Microsoft to be compromised and serve malicious software than gpg4win.
curl --head https://www.microsoft.com/en-us/ does though which is weird.