locked
"Windows 10 in S mode doesn't support this version of Office" using ODT setup of PerpetualVL2019 with config.xml RRS feed

  • Question

  • I used the 12325-20288 version of the Office Deployment Tool available here to do a setup.exe /download config.xml to a folder, then made an install.xml, put it in the same folder as the resulting output "Office" folder with the C2R files in it, and ran setup.exe /configure install.xml

    This is for our computer labs, so I'm getting the 2019 Perpetual.

    <Add SourcePath="e:\2019\2019perpetual" OfficeClientEdition="64" Channel="PerpetualVL2019">
        <Product ID="ProPlus2019Volume">

    Immediately, I get an error dialogue with the following text

    "Can't install this version of Office"
    Windows 10 in S mode doesn't support this version of Office.
    Use Office Version 1902 or later, or switch out of S mode.

    No computers in our entire company use S mode.

    This is 2019 Perpetual, which is still on 1808 anyway, 1902 isn't even an option for anyone (source).

    So, is this a bug? A double bug, since it's apparently detecting our totally normal installs of Windows 10 Education as being in S mode, and then telling us we need a build of Office that doesn't exist for the 2019 perpetual customers?

    Strangely enough, Office 365 installs fine to the Semi-Annual channel (which is also 1808) using the exact same build of setup.exe. I'm only having this problem with PerpetualVL2019.


    • Edited by MD5Hash Thursday, February 20, 2020 6:19 PM fix url
    Thursday, February 20, 2020 6:16 PM

All replies

  • My office install log file has the following line in it:

    02/20/2020 12:05:32.365    SETUP_~1 (0x164)    0x2d0        Click-To-Run General Telemetry    dek45    Medium    C2R::CatalogFiles::DetermineSMode {"MachineId": "d9e4debe90c36a4ebf11639100f64cd1", "SessionID": "96f2673d-be2e-4e28-8468-0207b0d3ab1a", "GeoID": 244, "Ver": "16.0.10354.20022", "C2RClientVer": "0.0", "ContextData": "{\"message\":\"S Mode check succeeded\",\"PolicyValue\":\"2147483663\",\"ModeValue\":\"0\"}"}   

    Then a few milliseconds later:

    02/20/2020 12:05:32.381    SETUP_~1 (0x164)    0x2d0        Click-To-Run General Telemetry    c2s7d    Medium    WindowsSModeMinimumVersionValidator::CheckPreReq {"MachineId": "d9e4debe90c36a4ebf11639100f64cd1", "SessionID": "96f2673d-be2e-4e28-8468-0207b0d3ab1a", "GeoID": 244, "Ver": "16.0.10354.20022", "C2RClientVer": "0.0", "ContextData": "{\"message\":\"Version too low to be supported for Windows 10 S Mode installation.\",\"version\":\"16.0.10354.20022\"}"}   

    Thursday, February 20, 2020 6:25 PM
  • Hi MD5Hash,

    To check Windows 10 S Mode, you may go to Start > Settings > System > About, scroll down to check "Windows specifications".


    As far as I know, Windows 10 S Mode only allows for installing Microsoft verified apps from the Microsoft Store and requires Microsoft Edge for safe browsing.  Did Office 365 (Version 1808) could be installed smoothly on your PCs?

    If yes, would you please create a new configuration file for Office 2019 on Office Customization Tool site for a test? You may set configurations, such as the version, Source path like the pictures below.

    After settings are completed, please export the <configuration file> to the same folder with Office Deployment Tool.

    Then you may run "setup.exe /download <configuration file>" to download installation files to the specific path. When finish the download, you may run "setup.exe /configure <configuration file>" to install Office 2019 from the specific path.

    If you have any updates, please feel free to let me know.

    Best Regards,

    Emily


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Office 2019.


    Friday, February 21, 2020 4:42 AM
  • Hi Emily, no - none of these computers we tested on, including our own office workstations or some test VMs, are in Windows S mode. They are all Windows 10 for Education SKU.

    Yes, I also tried making a brand new config file via the website you linked to already. The exact same result happens. This is while I am using the setup.exe version 16.0.12325.20276 that is included in the most recent ODT installer.

    I had a version of the ODT from 2018 which I also tried using the setup.exe from as a test, and that failed with a different error code. However, I'd like to try with the October 2019 version listed here.

    Is there someone who can provide me with a download link for the 2nd-to-last released copy of the ODT (that would be October 31, 2019, Version 16.0.12130.20272) from an official Microsoft source, so I can see if the same problem happens with that one?


    • Edited by MD5Hash Friday, February 21, 2020 3:59 PM fixed url, clarified version
    Friday, February 21, 2020 3:15 PM
  • Hi,

    Thanks for your response.

    What's the version number of your Windows OS? I created a test environment of Windows 10 Education (Version 1903), but I cannot reproduce your problem when I install Office ProPlus 2019.

    I download the ODT (Version 16.0.12325.20288) into C:\ODT, there is also a Config2019.xml (configuration file) I created as below in ODT folder:

    <Configuration>
      <Add SourcePath="C:\Users\admin\Desktop\Test" OfficeClientEdition="64" Channel="PerpetualVL2019">
        <Product ID="ProPlus2019Volume">
          <Language ID="en-us" />
        </Product>
      </Add>
    </Configuration>

    Then I download the installation file via the following commands:

    • cd C:\ODT
    • setup.exe /download Config2019.xml

    After download, I run following command to install Office 2019, it works without any issue.

    • setup.exe /configure Config2019.xml

    >> ... do a setup.exe /download config.xml to a folder, then made an install.xml, put it in the same folder as the resulting output "Office" folder with the C2R files in it, and ran setup.exe /configure install.xml

    << Have you tried to create one configuration file? The configuration file with "Add Source" attribution could work for download and installation. Besides, could you please share your configuration file with us? I will use it for a test...

    >> Is there someone who can provide me with a download link for the 2nd-to-last released copy of the ODT (that would be October 31, 2019, Version 16.0.12130.20272) from an official Microsoft source...

    << ODT tool in Microsoft Download Center is only shown the latest version, so I could not find the tool of Version 16.0.12130.20272 for you. Thanks for your understanding.

    Best Regards,

    Emily


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Office 2019.

    Friday, February 28, 2020 2:19 AM
  • Hi Emily, here is a compressed .7zip file of the following files - the .log file generated, the newest setup.exe (renamed to setup_new.exe) and two .xml files - one is technet.xml which is the exact configuration you provided in your previous post, and one is office2019_Emeritus.xml which is the one that I originally had problems with, that I deploy to the professors I support.

    Both xml files have the same S-Mode error.

    https://ssc.wisc.edu/~heise/s_mode/s_mode.7z



    • Edited by MD5Hash Friday, February 28, 2020 4:37 PM fix URL
    Friday, February 28, 2020 4:37 PM
  • Hi,

    I install Office 2019 on my test environment via your office2019_Emeritus.xml and the newest ODT, I could not reproduce your problem.

    Besides, in official Microsoft Download Center, the ODT Version 16.0.12130.20272 has been replaced via the newest one, it could not be available any more.

    In the log, the system is indeed identified as S mode, in my opinion, your issue seems to be more related your Windows 10. To help you troubleshoot this problem, it would be best to open a paid support ticket with Microsoft Support to help review your problem and help you test remotely.  Paid Support Information: https://support.microsoft.com/en-us/contactus/.

    Thanks for you understanding.

    Best Regards,

    Emily


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Office 2019.

    Thursday, March 5, 2020 9:48 AM
  • Hi Emily, in your testing, what SKU of windows 10 were you using - Home, Pro, Enterprise, or Education? All of my testing has been done with Education.
    Thursday, March 5, 2020 3:24 PM
  • Hi,

    It is Windows 10 Education, version 1903 (OS Build 18362.657) as the picture I showed in previous post. The follow picture shows the Office Product Information and the Windows information about running "winver".

    Best Regards,

    Emily


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Office 2019.

    Monday, March 9, 2020 10:08 AM
  • Just as an update, I saw the new April 2020 ODT came out, officedeploymenttool_12624-20320.exe this week. I repeated my testing, downloading the fresh copy of ProPlus2019 files with the Volume License channel.

      <Add SourcePath="e:\2019\2019perpetual_2020-4_labs" OfficeClientEdition="64" Channel="PerpetualVL2019">
        <Product ID="ProPlus2019Volume">
        <ExcludeApp ID="Lync" />
        <ExcludeApp ID="Groove" />
        <ExcludeApp ID="OneDrive" />
        <ExcludeApp ID="Outlook" />
        <ExcludeApp ID="Teams" />
        <ExcludeApp ID="Bing" />
          <Language ID="en-us" />
        </Product>
      </Add>

    Exact same problem occurred on my test VM - "windows 10 in s mode doesn't support this version of office"

    So far, the only workaround I've found is to use a pre-2020 version of setup.exe. This continues to work with even the current 'freshest' files using the /download flag with the April 2020 setup.exe. So my new workflow is download everything with the latest setup.exe, but do a /configure with a mid-2019 version of setup.exe

    I feel like this is a very 'brittle' method of doing things. Using old versions of setup.exe with new install files is probably a bad idea. But what else can I do? And I really wish I knew why setup.exe is incorrectly identifying my VM, and all my physical test machines, as being in S mode when they are 100% not in S mode.

    Friday, April 17, 2020 5:31 PM
  • Problem continues with June version of the ODT. I have found a second thread with a user having the same, or at least a similar problem here: https://social.technet.microsoft.com/Forums/office/en-US/099442de-0be4-4580-9888-f414de242b31/office-2019-standard-install-error-windows-10-s-mode?forum=Office2016ITPro
    Wednesday, July 22, 2020 8:40 PM