I obtained the latest version 10 of Mathematica however, when I start the installation the process aborts and a pop up window explains that "The program requires Windows NT version 6.0 or later". As far as I know, this means that version 10 is compatible only with Vista and all later versions of windows, am I right? In my PC I still have Windows XP SP3. So, is there a way to install version 10 in this OS? Currently, I have version 9 and runs like a charm. I refuse to believe that Wolfram made in purpose version 10 incompatible with XP.

  • 1
    $\begingroup$ Why do you think they will support unsupported (even extended support) version of OS? $\endgroup$
    – m0nhawk
    Jul 16, 2014 at 8:41
  • 6
    $\begingroup$ @m0nhawk Why not? There are still millions of XP users around the world. $\endgroup$
    – Vaggelis_Z
    Jul 16, 2014 at 8:45
  • 4
    $\begingroup$ Microsoft itself no longer supports Windows XP, so why expect new Wolfram products work with it? $\endgroup$
    – murray
    Jul 16, 2014 at 20:28
  • 6
    $\begingroup$ yet somehow Wolfram supports linux which isn't "supported" by anyone. $\endgroup$
    – george2079
    Jul 17, 2014 at 18:11
  • 1
    $\begingroup$ @george2079 linux is supported by several companies: e.g. RedHat, Canonical, SUSE, each with their own version schedule and EOL times. $\endgroup$
    – Ruslan
    Jan 25, 2019 at 9:45

2 Answers 2


I have contacted the Wolfram support ([CASE:1292216]):

Dear Andrew,

Thank you for contacting Wolfram Customer Service. We simply ended our support of XP shortly after Microsoft had announced they would no longer support XP themselves. XP is going to become to difficult to handle without any kind of support from Microsoft as many of the issues we would run into would be from the OS interaction with Mathematica and without updates for the OS each machine could almost be running its own version of XP. Please let us know if we may help further.

Regards, Wolfram Research, Inc.

The only solution: find an installed version and copy, but there is no guarantee it will work (mine worked on Windows XP on Hyper-V VM) and work correctly.

  • $\begingroup$ If I understand correctly your sayings you suggest me to install v10 in Win 8 for example and then copy the entire installation folder from Program Files to my XP PC. Am I right? Another idea the came by to me: Since I have the setup .exe file, can I produce a portable version of it? Few months ago, I found a torrent with a portable v9 that runs in any PC without installation just from a USB stick. $\endgroup$
    – Vaggelis_Z
    Jul 17, 2014 at 20:22
  • $\begingroup$ Yes, or ask someone with installed to share it. But take in account that you will need x86 version, so you need x86 version of Win8. About portable... I didn't have any experience with creating portable software, so can't advice anything. I think someone would definitely make it, and it would work seamlessly. $\endgroup$
    – m0nhawk
    Jul 17, 2014 at 20:25
  • $\begingroup$ @m0nhawk I have not tried that yet but what about registry entries that V10 would create? $\endgroup$
    – bobbym
    Jul 18, 2014 at 15:11
  • $\begingroup$ @bobbym there is nothing necessary for computations, only some system information, like version or file association (can be added manually). $\endgroup$
    – m0nhawk
    Jul 18, 2014 at 15:14
  • $\begingroup$ Okay, sounds reasonable +1 $\endgroup$
    – bobbym
    Jul 18, 2014 at 15:17

One can use Microsoft Application Verifier to cheat the Windows version.

  • $\begingroup$ Like so? I'm not sure if HighVersionLie also works for cheating on lower version numbers; can anyone confirm that this works? $\endgroup$ Sep 7, 2014 at 9:12
  • $\begingroup$ @Teake Nutma yes, it works. $\endgroup$
    – Anixx
    Sep 7, 2014 at 9:31
  • 6
    $\begingroup$ Can you then amend your answer with a step-by-step procedure of how to get it working? At the very least, include the command line to wrap the installer in MAV. $\endgroup$ Sep 7, 2014 at 9:33
  • $\begingroup$ This one does not help $\endgroup$
    – Kattern
    Jun 28, 2015 at 15:02
  • 2
    $\begingroup$ @Anixx Yea, shit. Checked the module name. If the installer executable file is m.exe, then the module name when it's started is somehow m.tmp. Works perfectly, upvoting, thanks! $\endgroup$
    – dbanet
    Jul 10, 2015 at 1:25

Not the answer you're looking for? Browse other questions tagged or ask your own question.