Windows 10: Failed to install MSI package

When we install networker tools in windows server 2016 thare some error from MSI Package

:)

 

Failed to install MSI package

Hello,

Got that error at installation of GrassVally Edius Trail version:

Failed to install MSI package.

Installtiob quit on error,who can help solving this problem?

Can attach full log file but here are some lines from that log file:

[245C:03BC][2017-05-01T11:22:06]i000: Registry key not found. Key = 'SOFTWARE\Grass Valley\EDIUS\8.00\Installation'

[245C:03BC][2017-05-01T11:22:06]i000: Registry key not found. Key = 'SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{5A6D1DC6-25AE-4CBC-883F-8A5737E438E0}'

[245C:03BC][2017-05-01T11:22:06]i000: Registry key not found. Key = 'SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{B91A1230-C199-421e-8F63-7235731D925E}'

[245C:03BC][2017-05-01T11:22:06]i000: Registry key not found. Key = 'SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{3F77A9DD-DEEB-479F-A3A6-23D3B9F292EA}'

[245C:03BC][2017-05-01T11:22:06]i101: Detected package: MSI.GVLicenseManager, state: Absent, cached: Complete

[245C:03BC][2017-05-01T11:22:06]i000: Running detect complete BA function

[1EA4:14C0][2017-05-01T11:23:10]i323: Registering package dependency provider: {0F76163F-73DE-483F-B86F-9FB85704FC98}, version: 8.3.2.1697, package: MSI.Edius

[1EA4:14C0][2017-05-01T11:23:10]i301: Applying execute package: MSI.Edius, action: Install, path: C:\ProgramData\Package Cache\{0F76163F-73DE-483F-B86F-9FB85704FC98}v8.3.2.1697\EdiusPackage.msi, arguments: ' ARPSYSTEMCOMPONENT="1" MSIFASTINSTALL="7" TELEMETRY="1"'

[1EA4:14C0][2017-05-01T11:25:45]e000: Error 0x80070643: Failed to install MSI package.

[1EA4:14C0][2017-05-01T11:25:45]e000: Error 0x80070643: Failed to execute MSI package.

[245C:03BC][2017-05-01T11:25:45]e000: Error 0x80070643: Failed to configure per-machine MSI package.

[245C:03BC][2017-05-01T11:25:45]i319: Applied execute package: MSI.Edius, result: 0x80070643, restart: None

[245C:03BC][2017-05-01T11:25:45]e000: Error 0x80070643: Failed to execute MSI package.

[1EA4:14C0][2017-05-01T11:25:45]i318: Skipped rollback of package: MSI.Edius, action: Uninstall, already: Absent

[245C:03BC][2017-05-01T11:25:45]i319: Applied rollback package: MSI.Edius, result: 0x0, restart: None

thanks,

Srool...

 

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