Windows 10: How to mark my MSI package safe for Windows Systems?

Hi!We are building an .NET application as an MSI package which should go to the Internet and update itself from time to time. Also, the app sends metrics to the dedicated server.We sign that MSI with a trusted digital certificate.The problem is Windows Defender detects it as TrojanClicker:Win32/Doplik!ml and blocks. The error message says that the app goes to the Internet as a background task. It's correct! It's what exactly we want.So, how can I tell Windows operations systems probably with strict security settings that my MSI is actually safe?

:)

 

Windows Installer Error: This installation package cannot be opened.

Hi AJ,

Thank you for posting in Community.

We are glad to provide the assistance required to help you answer your query.

The above error can occur if the locally cached Windows Installer package (*.msi) file is damaged or corrupted.

To rectify the above, I suggest that you try the steps mentioned below and check if you are able to install the software successfully.

• Open the \Windows\Installer folder on your computer's hard disk.
• Right-click any file with an .msi extension.
• Click Properties on the shortcut menu. The
  Subject box on the Summary tab contains the name of the product that installed the .msi file.
• Repeat steps 2 and 3 for each .msi file in the \Installer folder, and delete the .msi file for the software that you are trying to install.

Hope this helps

 

msi package cannot be installed

When I try to install any msi-based program (in my case VirtualBox but also 7zip) I get following error messages: "the system could not open the specified device or file." and then "the installer has encountered an unexpected error installing this package.
This may indicate a problem with this package. The error code is 2755." when I hit the "install" button.

I have captured the most verbose log I could get and posted it here:
https://pastebin.com/PZSRQgwy

It seems that the installer is unable to read the msi file.

What I have already tried:

• rebooting
• re-registering msiexec with msiexec /unreg and msiexec /regserv
• sfc /scannow
• this troubleshooter: MicrosoftProgram_Install_and_Uninstall.meta.diagcab
• give everyone full r/w permission to the msi file and parent folder

I run win 10 home build 1809 with all available updates

my av is avast

I have no clue what could have coused this error because a month ago it did work

 

AMD FX OC'ers Club

That's what the auto setting will do since you're over the 1333 mark it jumps to the next step which isn't listed or officially supported I assume by that ram.

At this point though I would suggest dropping the multi one step or .5 so that we can get something stable and possibly take the heat issue out of the picture for now.