Installation errors

I use AVAST and get the same.

Bruce -- the sandbox is because the file "reputation is low". Basically, not many people use it and AVAST doesn't know if it should be trusted. So it asks if you want to run it in the visualised sandbox environment. I always choose "Run Normally".

However, I DO get the "This program might have not installed correctly" after installing.
 
Unfortunately, this is due to the new 7-zip based installation package. The 7zS file for doing the extract and install routine is from 2005, well before 7 or 8 were around, which is what results in the second message. The first message is due to the 7-zip installation package being unknown to avast! as a trusted installer.

I will see about getting a new 7zS version (or similar) from the 7-zip site. I have not had time to look into this yet.


Update:

I found an updated version, but it still results in the second message. If I run Setup.exe alone, I do not get the message, so I am pretty sure it is something within the 7-Zip installer's manifest. I could build my own, but that would involved learning how 7-zip works with their source code which looks pretty involved. There are two options here until I find time to build a self-extracting installer from scratch:

  1. Continue with the old method of running Setup.exe from the folder it is extracted to and not being able to move Setup.exe to any place on the drive without also moving the SysnativeBSODApps sub-directory that comes with it.

  2. Continue with the contained installer that can install from anywhere and ignore these annoying messages.

What would people prefer?​
 
Last edited:
 
Thanks Stephen. Looks like I can use the resource editing software I installed to add the icon to also add the manifest file. I'll look into it.
 
Attached is an updated version of the installer. The apps have not changed, only the installer has. Please let me know if any further problems occur.

PCA errors should be fixed. The updated version of the extractor may fix the problem with avast!, but I cannot say one way or another since I do not use avast!
 

Attachments

AVAST! still pops up with a warning, but it's nothing to worry about.

PCA errors are now fixed! Nice work Mike, nice work
 
Hello Mike :)

The official documentation is here: Application Manifest (Windows)

There are two main solutions. Firstly, using the manifest is fine, but will disable all Program Compatibility Assistant (PCA) Mitigation.

Alternatively, you could not be detected by PCA at all. Using the 32bit Compatibility Administrator from Microsoft Application Compatibility Toolkit, you are being picked up on two shims, 'Install' (*instal* in file name) and 'Setup' (*setup* in file description).

So, you could rename the application & change the file description. But then you completely lose all PCA as well, so you may as well have used the manifest.

So yeah, probably using mt.exe to set the manifest in some sort of hopefully automated post build script in 7-Zip is the way forward.

Richard
 
Thanks Stephen. Sorry I could not fixe the avast! issue. I'll submit a report to them about it and maybe their support team can look into 7-zip based installers.
 
niemiro said:
Hello Mike :)

The official documentation is here: Application Manifest (Windows)

There are two main solutions. Firstly, using the manifest is fine, but will disable all Program Compatibility Assistant (PCA) Mitigation.

Alternatively, you could not be detected by PCA at all. Using the 32bit Compatibility Administrator from Microsoft Application Compatibility Toolkit, you are being picked up on two shims, 'Install' (*instal* in file name) and 'Setup' (*setup* in file description).

So, you could rename the application & change the file description. But then you completely lose all PCA as well, so you may as well have used the manifest.

So yeah, probably using mt.exe to set the manifest in some sort of hopefully automated post build script in 7-Zip is the way forward.

Richard
Click to expand...

Yeah, I'd rather not touch how PCA itself works on people's systems. Not everyone is as safe about installers as we are, so the more layers of warning they have the better, in my opinion.

I simply placed the manifest into the 7zS.sfx file as such:
Code: 
<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
  <compatibility xmlns="urn:schemas-microsoft-com:compatibility.v1">
    <application>
      <!--The ID below indicates application support for Windows Vista -->
      <supportedOS Id="{e2011457-1546-43c5-a5fe-008deee3d3f0}" />
      <!--The ID below indicates application support for Windows 7 -->
      <supportedOS Id="{35138b9a-5d96-4fbd-8e2d-a2440225f93a}" />
      <!--The ID below indicates application support for Windows 8 -->
      <supportedOS Id="{4a2f28e3-53b9-4441-ba9c-d69d4a4a6e38}" />
    </application>
  </compatibility>
</assembly>

That should help with compatibility for Vista/7/8 and prevent the PCA warnings. The problem, as I understand it, is that the apps are not installed to the programs registry to be removed through Uninstall a Program or the Start button.
 
The Avast issue is not a major concern, I just wanted you to be aware of it.
The installer runs now without the Windows error and even installs it in the directory selected instead of creating a new directory inside the directory selected :)
So bottom line good work :)
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top