Service pack 1 error on window 7

[bahman jafari]

Hi all,

I was working with iIno Setup old version (5.6) to create installer for my programs without any problem,  but after downloading and installing new version of inno setup (6.1.2), installer is giving  this error on windows 7 (64 bit) :

"This program requires windows service pack 1 or later"

While new service pack (4.5.2) is installed on the windows and it does not have this problem with old version's (5.6) installer.

Do you think new version has a bug or I should update my functions?

[Eivind Bakkestuen]

Are you saying that the Win7 machine you are testing on does have service pack 1 or later installed?

--
You received this message because you are subscribed to the Google Groups "innosetup" group.
To unsubscribe from this group and stop receiving emails from it, send an email to innosetup+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/innosetup/27b67085-c7f6-479f-8f0c-aee3c59cd85dn%40googlegroups.com.

[bahman jafari]

Yes, I have installed service pack version 4.5.2 on win7, and also I've installed some software successfully that need to higher version framework like Autocad.

as I said win7 has no problem with old version of inno setup, this problem only happen with the newer version of inno setup.

[Martijn Laan]

Hi,

> Op 7 mrt. 2021 om 12:30 heeft bahman jafari <bahman...@gmail.com> het volgende geschreven:
>
> I have installed service pack version 4.5.2 on win7, and also I've installed some software successfully that need to higher version framework

Windows 7 version 4.5.2 doesn't exist. I think you're confusing Windows and .NET Framework versions?

Greetings,
Martijn

[bahman jafari]

https://www.microsoft.com/en-us/download/details.aspx?id=42642

[Martijn Laan]

That's a .NET Framework download which is not related to your error message in any way.

Op 7 mrt. 2021 om 13:55 heeft bahman jafari <bahman...@gmail.com> het volgende geschreven:

https://www.microsoft.com/en-us/download/details.aspx?id=42642

--

You received this message because you are subscribed to the Google Groups "innosetup" group.
To unsubscribe from this group and stop receiving emails from it, send an email to innosetup+...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/innosetup/778f975a-e7b0-4d93-b5ca-fb3279042ba3n%40googlegroups.com.

[Marcelo Lauxen]

Hello everyone,

We're facing a similar problem, we've upgraded InnoSetup to 6.1.2 and now a lot of our customers are seeing this error when installing our app, for the customers who are with Windows 7 we're recommending upgrading to 8.1/10, but today another customer contacted us regarding this problem and different from the other customers this one is running Windows 10 in a machine which he upgraded from Windows 7, has someone seen something similar? 

For now, we're downgrading InnoSetup but this problem was new to us, at least we weren't expecting such a message to be shown on Windows 10.

Regards,

[Eivind Bakkestuen]

Did the customer send a screenshot proving they are without doubt running windows 10?

Could Win 7 "Compability mode" have been turned on for the installer exe?

To view this discussion on the web visit https://groups.google.com/d/msgid/innosetup/571c982f-1038-48bf-922e-2c6aff29913bn%40googlegroups.com.

[Gavin Lambert]

On 8/03/2021 4:01 am, Martijn Laan wrote:
> That's a .NET Framework download which is not related to your error
> message in any way.

Information on checking whether Win7 SP1 is installed (and how to
install it, if not) can be found here:


https://support.microsoft.com/en-us/windows/install-windows-7-service-pack-1-sp1-b3da2c0f-cdb6-0572-8596-bab972897f61

As Martijn said, there are other things that also have service packs
(including the .NET Framework), but that is not the same thing as the OS
service pack itself.

[Marcelo Lauxen]

The problem was what Eivind pointed out. Our customer had the Win 7 "Compatibility mode" turned on for the installer, he didn't know to explain why it was on, but after disabling it the problem didn't happen anymore.

Thanks, Eivind and Gavin!