Questions

Windows 7 install problem

Tags: Windows, Operating Systems, Software
+
0 Votes

Windows 7 install problem

admin
I have a HP Z400 workstation (xeon W3565 processor, 12GB RAM, 929GB HD) running Windows 7 SP1. I am trying to install software, but after opening the setup .exe, I keep getting the error message "This Program Must Be Run on Windows 7". The program author has made some changes, but so far to no success. Also, when trying to run a manual scan of my anti-malware software, the application quits after about 15-20 seconds, with no error message. I have been told that this is an issue when the software is loaded on old Windows XP operating systems. Because of this common thread, I think that Windows 7 is not correctly reporting the OS version to applications. Where do applications get the information regarding the operating system they are running on? (System properties show Windows 7 SP1).

Member Answers

    • +
      0 Votes
      WinOutreach2

      The version number is reported in System Information under the entry Version under the System Summary, i.e. 6.1.7601 for Windows 7. There are various variables used to determine system version, including VersionNT, WindowsBuild, and ServicePackLevel. See Operating System Property Values under the Windows Installer Guide:
      http://msdn.microsoft.com/library/aa370556

      If your application is installing from an EXE, you may be able to use the compatibility modes built into Windows to mimic the target operating system. For example, in Windows 7 SP1 you can run in compatibility mode for Windows 7. See:
      http://windows.microsoft.com/en-us/windows7/make-older-programs-run-in-this-version-of-windows

      If the built in compatibility modes do not resolve the issue, you can get much more advanced with the Application Compatibility Toolkit (ACT). ACT provides granular control over the vast array of shims which can be used to present compatible behavior to the incompatible application to allow it to run. For example, you can mimic the version of the operating system. You can also redirect queries from the application to resources which have been relocated in the newer operating system to their targets. You can find out more about ACT and other application compatibility solutions at the Application Compatibility Center at the Springboard Series on TechNet:
      http://technet.microsoft.com/windows/aa905066


      If the installer is MSI rather than EXE, you may need to be a bit more creative. You can use Orca to edit the package and remove or modify the LaunchCondition which restricts the package to a particular version of the operating system. Orca is available through the Windows Software Development Kit (SDK) which is available for Windows 8.1, Windows 8, and Windows 7 here on MSDN:
      http://msdn.microsoft.com/windows/desktop/aa904949
      More on Orca:
      http://msdn.microsoft.com/library/aa370557

      Brandon
      Windows Outreach Team- IT Pro
      The Springboard Series on TechNet
      http://technet.com/windows

    • +
      0 Votes
      WinOutreach2

      The version number is reported in System Information under the entry Version under the System Summary, i.e. 6.1.7601 for Windows 7. There are various variables used to determine system version, including VersionNT, WindowsBuild, and ServicePackLevel. See Operating System Property Values under the Windows Installer Guide:
      http://msdn.microsoft.com/library/aa370556

      If your application is installing from an EXE, you may be able to use the compatibility modes built into Windows to mimic the target operating system. For example, in Windows 7 SP1 you can run in compatibility mode for Windows 7. See:
      http://windows.microsoft.com/en-us/windows7/make-older-programs-run-in-this-version-of-windows

      If the built in compatibility modes do not resolve the issue, you can get much more advanced with the Application Compatibility Toolkit (ACT). ACT provides granular control over the vast array of shims which can be used to present compatible behavior to the incompatible application to allow it to run. For example, you can mimic the version of the operating system. You can also redirect queries from the application to resources which have been relocated in the newer operating system to their targets. You can find out more about ACT and other application compatibility solutions at the Application Compatibility Center at the Springboard Series on TechNet:
      http://technet.microsoft.com/windows/aa905066


      If the installer is MSI rather than EXE, you may need to be a bit more creative. You can use Orca to edit the package and remove or modify the LaunchCondition which restricts the package to a particular version of the operating system. Orca is available through the Windows Software Development Kit (SDK) which is available for Windows 8.1, Windows 8, and Windows 7 here on MSDN:
      http://msdn.microsoft.com/windows/desktop/aa904949
      More on Orca:
      http://msdn.microsoft.com/library/aa370557

      Brandon
      Windows Outreach Team- IT Pro
      The Springboard Series on TechNet
      http://technet.com/windows