Microsoft Office Ltsc 2024 Professional Plus Standard Visio Project 1601793220130 May 2026

The number sequence you provided does not match any known Microsoft product key format (e.g., XXXXX-XXXXX-XXXXX-XXXXX-XXXXX). Instead:

If you encountered this code during installation or activation, it is likely a transaction reference or a support ticket ID – not a functional part of the software itself. Microsoft does not use numeric-only codes of that length for product identification.


  • Use Cases: This suite seems targeted at professional environments, likely within medium to large organizations that require comprehensive office productivity tools along with specialized applications like Visio and Project. It's suitable for environments needing stability and predictability in their software.

  • Organizations deploying Office LTSC 2024 typically use: The number sequence you provided does not match

    System Requirements:


    Let’s address the elephant in the room: Why does your search include the number 1601793220130?

    Target Audience: Diagramming professionals, process engineers, IT architects. If you encountered this code during installation or

    Editions Available:

    What’s New in Visio 2024:

    Important Note: Visio LTSC 2024 is not included in any Office LTSC suite (Professional Plus or Standard). It must be licensed separately via volume licensing. Use Cases : This suite seems targeted at


    The numeric suffix might appear in VLSC as a Product ID for a specific bundle. You would use it like this in a configuration.xml:

    <Configuration>
      <Product ID="ProPlus2024Volume" PIDKEY="XXXXX-XXXXX-XXXXX-XXXXX-XXXXX">
        <Language ID="en-us" />
        <ExcludeApp ID="Access" />
      </Product>
      <Product ID="VisioStd2024Volume">
      </Product>
      <Product ID="ProjectStd2024Volume">
      </Product>
    </Configuration>
    

    The string 1601793220130 might map internally to that triple-product combination.


    You must install Visio and Project after or simultaneously using the same ODT but with separate <Product ID> lines:

    <Product ID="VisioPro2024Volume" PIDKEY="VISIO-MAK-KEY">
    <Product ID="ProjectPro2024Volume" PIDKEY="PROJECT-MAK-KEY">
    

    Note: The same 1601793220130-style key will never appear in a genuine configuration.xml file.


    Send this to a friend