Why does symantec quarantine the latest version of Doxygen? - doxygen

I was able to download doxygen 1.8.13-setup.exe for windows. However when I download the latest version, Symantec states that there is strong evidence that doxygen-1.8.14-setup.exe is untrustworthy. First, is anyone else having problems with the latest installer that was produced in December of 2017? Something is different about it that causes the antivirus program to quarantine it. I've never had any problems like that with previous versions of doxygen.
Here is the link where I found the setup program. I also tried downloading directly from the doxygen website, and the result was the same.
https://sourceforge.net/projects/doxygen/files/
http://www.doxygen.nl/download.html

Related

How to convert PS1 to EXE [duplicate]

I'm looking to convert a PS1 file to an .exe file so I can roll it out to less technical users.
I believe it'll be much easier for them if all they need to do is double-click it vs explaining how to run through PowerShell.
How can I achieve this?
Use PS2EXE instead of this online tool that forces you to upload your script and creates a security breach if you have confidential information inside your script.
There is a GUI mode available; to learn more, see the GitHub repository.
You have a few paid and unpaid solutions. I agree with last answer, do not use online tools unless you are sure they are not keeping your code and you trust them.
There are two free ones that come to mind:
PS2EXE-GUI
PS1 To EXE by F2KO (Make sure t it is the local install command line interface, not the web one)
The Paid ones are:
PowerShell Studio
ISE Steroids 2.0 Enterprise
Noted: I think the free ones should be fine for most uses. I do like PowerShell Studio though.
An update to PS2EXE tool (all versions are open-source):
The original script comes from Ingo Karstein, but the development seems to have halted in 2017. You can find his blog here, and his contribution on Microsoft Technet's forums here.
Markus Scholtes has continued the script's development, adding some useful features. You can find his post on Microsoft Technet here, and github repository here.
Powershelling's answer point you to a fork of Markus' project by Stuart Dootson (here and here), which is less maintained. The obvious difference would be the "Added support for scripts that require elevation. This inserts a suitable manifest into the executable produced by the tool. that .exe files built with his version of the script require elevation".
I'd recommend checking out Markus Scholtes' version, but beware (!) (README.md on 3rd Nov 2020):
Attention: Incorrect virus detection of PS2EXE
Some stupid idiot seems to have abused PS2EXE to compile his computer virus script. As a result, a rapidly growing number of virus scanners recognize programs created with PS2EXE as malicious programs and delete them.
There is only one hope to save the PS2EXE project: Please send your (harmless) programs created with PS2EXE via the web forms from the virus scanners' vendors for reporting false positives (I've already done it with some of them, please use only the false positive page)!
If this is not successful, then I will have to quit PS2EXE as nobody can use it anymore.
Thank you for your support

Where we can get older versions of VSCode (like 1.25) in ZIP format?

First of all, I have to make clear that I need the zip version because I will use it on Win 64 in the business and there we have no admin privileges on notebook.
I looked out over web but I wasn't able to find where I can get the VSCode v1.25(.1). I only found .EXE versions or source code archive.
Why I need this? VSCode 1.26 and greater (and many others electron based applications) are very slow in Win 64. Thank God I use Linux at home! Please, see this issue: https://github.com/microsoft/vscode-docs/issues/4609
Ok, after report it as an issue on github vscode repository, somebody gave me the provisory link and previous archives (zip) versions will be put available asap issue come to be solved.
VSCode 1.25.1 archive (zip) Win64 link: https://vscode-update.azurewebsites.net/1.25.1/win32-x64-archive/stable
Go to https://code.visualstudio.com/docs/supporting/faq#_previous-release-versions.
The URLs to each download are provided there.

Convert PowerShell script to exe

I'm looking to convert a PS1 file to an .exe file so I can roll it out to less technical users.
I believe it'll be much easier for them if all they need to do is double-click it vs explaining how to run through PowerShell.
How can I achieve this?
Use PS2EXE instead of this online tool that forces you to upload your script and creates a security breach if you have confidential information inside your script.
There is a GUI mode available; to learn more, see the GitHub repository.
You have a few paid and unpaid solutions. I agree with last answer, do not use online tools unless you are sure they are not keeping your code and you trust them.
There are two free ones that come to mind:
PS2EXE-GUI
PS1 To EXE by F2KO (Make sure t it is the local install command line interface, not the web one)
The Paid ones are:
PowerShell Studio
ISE Steroids 2.0 Enterprise
Noted: I think the free ones should be fine for most uses. I do like PowerShell Studio though.
An update to PS2EXE tool (all versions are open-source):
The original script comes from Ingo Karstein, but the development seems to have halted in 2017. You can find his blog here, and his contribution on Microsoft Technet's forums here.
Markus Scholtes has continued the script's development, adding some useful features. You can find his post on Microsoft Technet here, and github repository here.
Powershelling's answer point you to a fork of Markus' project by Stuart Dootson (here and here), which is less maintained. The obvious difference would be the "Added support for scripts that require elevation. This inserts a suitable manifest into the executable produced by the tool. that .exe files built with his version of the script require elevation".
I'd recommend checking out Markus Scholtes' version, but beware (!) (README.md on 3rd Nov 2020):
Attention: Incorrect virus detection of PS2EXE
Some stupid idiot seems to have abused PS2EXE to compile his computer virus script. As a result, a rapidly growing number of virus scanners recognize programs created with PS2EXE as malicious programs and delete them.
There is only one hope to save the PS2EXE project: Please send your (harmless) programs created with PS2EXE via the web forms from the virus scanners' vendors for reporting false positives (I've already done it with some of them, please use only the false positive page)!
If this is not successful, then I will have to quit PS2EXE as nobody can use it anymore.
Thank you for your support

Error "end of central directory record signature not found" while installing ionide-fsharp in vscode

I have installed VS Code version 1.8.1. Machine is Windows 7, 64 bit. While installing ionide-fsharp extension, I am getting error "end of central directory record signature not found". It seems version 1.7.2 of VS Code works, however this issue probably seems fixed for version 1.8.0 see this git link. Any idea on how to get the extn installed?
Thanks
Found a workaround for this. Downloaded '.vsix' file of ionide-fs from this link. In VS Code Extensions tab, there is an option 'Install from VSIX'. That worked. So in case anyone is unable to install from vscode extensions tab directly(i.e. from Marketplace), they may try this way of installing an extension.
Just for information, I was getting the same error for version 1.7.2 of vscode as well while trying to install from Marketplace.
Seems there were bugs that exist in past versions, due to the embedded browser and other reasons; these have since been fixed.
The above solution seems a common way to install a troublesome plugin.
However, there is a long standing reason for this error, running out of disk space.
As of v1.54.1 (2021/03) and it turns out this can happen if your disk/home folder can run out of space during download OR install.
https://github.com/microsoft/vscode/issues/118711

How can I get rid of a "zombie" MSI entry in "Programs and Features"?

In Win7, an old version of Acrobat XI is still showing, but there is no matching MSI file for it to execute, so it can't "uninstall" and I can't delete the entry because MS makes it intentionally difficult.
Normally such things just pile up over time. But Acrobat insists on uninstalling the previous version and will not install until the old one is gone.
How can I remove the entry from the database that "Programs and Features" uses?
The cached MSI file that is supposed to run the uninstall might be missing from the super-hidden MSI cache folder normally found at C:\windows\installer (formally at %SystemRoot%\Installer), or there is a crash in the uninstall sequence. Creating an uninstall log file could help (replace the truncated paths):
msiexec.exe /X "C:\Test.msi" /L*V! "C:\msilog.log"
Uninstall by product code (sample guid):
msiexec.exe /x {11111111-1111-1111-1111-11111111111X} /L*V! "C:\msilog.log"
Please see sections 3, 4 and 12 here for details on how MSI's uninstall works: Uninstalling an MSI file from the command line without using msiexec. This will also tell you how to find the product GUID for Adobe Acrobat XI Pro (use the Powershell command found in section 3, or find the same information and a screenshot here: How can I find the product GUID of an installed MSI setup?).
Before trying anything else, I suppose you can try this uninstall fix tool (fixed broken link, September 2017). It would be interesting with feedback on whether it actually works.
I had similar issues in the past and used ccleaner to clean up entires from "Programs and Features" after an uninstall went wrong. Hope it works for you.
This question is technically off topic as you are a user of the product not a developer of the product setup. Your cached MSI is missing and that's blocking their uninstall (bad design on their part) which occurs during upgrade to the new version. There are several things you can try:
1) Reinstall / Repair the old version and then try to uninstall it.
2) Contact the vendor for support.
3) Reinstall Windows.
4) Use the Windows Installer Cleanup Utility (no longer supported but can be found online ) to whack MSI's knowledge of the product. Note this doesn't actually uninstall the product and can cause all sorts of difficulties that may lead you to back to option 3.