[tex-live] [NSIS-devel] Fwd: Unable to use install-tl-windows.exe: "Windows XP earliest supported version; aborting..."
Jon Hood
squinky86 at gmail.com
Mon Jun 6 19:07:05 CEST 2016
This is occurring on the Army Gold Master image for Windows 7, and
thanks to your input, I've been able to track it down:
* Force XP compatbility mode in the installers Properties->Compatbility
* Rename the installer
* Move the installer to C:\
* Use another user (preferably with only English letters in its name)
* Try on a different Windows 7 computer
Same result on all systems with this image.
* Disable your AV
* Run the version test suite on your --
https://github.com/kichik/nsis/blob/51e74df6c950cd8176ded182d09fc2553481f1ba/Source/Tests/winver.nsi
Bingo - that got it. The issue is with McAfee Host Intrusion
Prevention and McAfee VirusScan. Winver copies dll files to %TEMP%
including a system.dll file. It then begins executing within a new
folder in %TEMP%. McAfee configuration information is available here:
https://kc.mcafee.com/resources/sites/MCAFEE/content/live/PRODUCT_DOCUMENTATION/22000/PD22818/en_US/Access_Protection_Rules.pdf
p. 6 starting with the section “Prevent all programs from running
files from the Temp folder”
And the STIG rule for the fully unclassified side is available at:
https://www.stigviewer.com/stig/mcafee_virusscan_8.8_managed_client/2015-06-18/finding/V-59363
So, the moral of the story: NSIS version checking does not work on a
DoD-STIG'd system using McAfee VirusScan or HIP.
I'm cross-posting this on the texlive list so that their developers
know that the issue has been tracked down, and it's an issue with the
U.S. DoD + McAfee, not with NSIS.
Thanks again,
Jon
On Mon, Jun 6, 2016 at 11:37 AM, Amir Szekely <kichik at gmail.com> wrote:
> We use relative version comparison to avoid issues like the one you're
> describing. There is no list where Windows 7 SP1 is missing. I have
> developed this feature on Windows SP1 and have worked with it for the past 3
> years without seeing this issue. Yours is also the first report of such an
> issue. I am therefore under the working assumption that this is a local
> issue with your computer or that specific installer.
>
> Here is a list of a few things you can try to pinpoint the issue:
>
> * Force XP compatbility mode in the installers Properties->Compatbility
> * Rename the installer
> * Move the installer to C:\
> * Disable your AV
> * Use another user (preferably with only English letters in its name)
> * Try on a different Windows 7 computer
> * Run the version test suite on your --
> https://github.com/kichik/nsis/blob/51e74df6c950cd8176ded182d09fc2553481f1ba/Source/Tests/winver.nsi
>
> On Mon, Jun 6, 2016 at 7:43 AM, Jon Hood <squinky86 at gmail.com> wrote:
>>
>> I can confirm that the installer is not being run in compatibility mode.
>>
>> C:\>ver
>> Microsoft Windows [Version 6.1.7601]
>>
>> On Sat, Jun 4, 2016 at 4:10 PM, Amir Szekely <kichik at gmail.com> wrote:
>> > Sounds like you're running your installer in Windows 2000 compatibility
>> > mode. Right click the executable, go to the Compatibility tab and make
>> > sure
>> > everything is unchecked.
>> >
>> > On Fri, Jun 3, 2016 at 12:14 PM, Jon Hood <squinky86 at gmail.com> wrote:
>> >>
>> >> I had the following exchange with the texlive people who use nsis and
>> >> downloaded the latest nsis subversion trunk. The Windows 7 Enterprise
>> >> w/ SP 1 version appears to be missing from Include/WinVer.nsh:
>> >>
>> >> Mine: "Microsoft Windows NT 6.1.7601 Service Pack 1"
>> >>
>> >> Can you please make sure Windows 7 with Service Pack 1 (version
>> >> 6.1.7601) is supported with nsis so that ${AtMostWin2000} evaluates
>> >> that I'm using at least Windows XP? (line 72 of
>> >>
>> >>
>> >> http://www.tug.org/svn/texlive/trunk/Master/tlpkg/libexec/install-tl.nsi?revision=33535&view=markup
>> >> begins the block that I'm tripping up on).
>> >>
>> >> Additional reference for Windows 7 version:
>> >> http://www.jrsoftware.org/ishelp/index.php?topic=winvernotes
>> >>
>> >> Thanks!
>> >> Jon
>> >>
>> >> ---------- Forwarded message ----------
>> >> From: Siep Kroonenberg <siepo at cybercomm.nl>
>> >> Date: Thu, Jun 2, 2016 at 9:05 AM
>> >> Subject: Re: [tex-live] Unable to use install-tl-windows.exe: "Windows
>> >> XP earliest supported version; aborting..."
>> >> To: Jon Hood <squinky86 at gmail.com>
>> >> Cc: tex-live at tug.org
>> >>
>> >>
>> >> On Tue, May 31, 2016 at 02:06:52PM -0500, Jon Hood wrote:
>> >> > When trying to run install-tl-windows.exe from
>> >> > https://www.tug.org/texlive/acquire-netinstall.html I receive an
>> >> > immediate pop-up stating, "Windows XP earliest supported version;
>> >> > aborting..."
>> >> >
>> >> > My platform: Windows 7 Enterprise Service Pack 1 64-bit
>> >> >
>> >> > Current workaround: open install-tl-windows.exe in 7zip and extract
>> >> > the install-tl-20160405 folder. Run install-tl-windows.bat from the
>> >> > extracted folder
>> >> >
>> >> > Thanks,
>> >> > Jon
>> >>
>> >> I cannot reproduce this with a freshly-downloaded
>> >> install-tl-windows.exe on Windows 10 64-bit, and have no idea what
>> >> may have caused this.
>> >>
>> >> --
>> >> Siep Kroonenberg
>> >>
>> >>
>> >>
>> >> ------------------------------------------------------------------------------
>> >> What NetFlow Analyzer can do for you? Monitors network bandwidth and
>> >> traffic
>> >> patterns at an interface-level. Reveals which users, apps, and
>> >> protocols
>> >> are
>> >> consuming the most bandwidth. Provides multi-vendor support for
>> >> NetFlow,
>> >> J-Flow, sFlow and other flows. Make informed decisions using capacity
>> >> planning reports.
>> >> https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
>> >> _______________________________________________
>> >> Nsis-devel mailing list
>> >> Nsis-devel at lists.sourceforge.net
>> >> https://lists.sourceforge.net/lists/listinfo/nsis-devel
>> >
>> >
>
>
More information about the tex-live
mailing list