[PowerShell][Data Gateway] DataGateway Module not installing latest version

[loganmzz]

Hi,

We have automated Microsoft Data Gateway provisionning relying on the PowerShell DataGateway Module. However, it seems the Install-DataGateway isn't installing latest version.

As next commands ends with given error message:

```

Add-DataGatewayClusterMember: Upgrade the gateway version to continue

```

How to solve this?

[v-hashadapu]

Hi @loganmzz , hope you are doing well.

Just wanted to know if your issue has been resolved through your support ticket with Microsoft? If so, we would greatly appreciate it if you could share the insights here, as they may benefit others with similar issues.

If you have any other queries, please feel free to raise a new post in the community. We are always happy to help. Thank you.

[v-hashadapu]

Hi @loganmzz , The best course is to raise a Microsoft Support ticket, Provide them with all the required details. They will check the issue and help you with the solution.

Below is the link to help create Microsoft Support ticket:
How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn

[v-hashadapu]

Hi @loganmzz , Thank you for reaching out to the Microsoft Community Forum.

The error indicates that the gateway binaries installed on the VM are below the minimum version required by the Power BI service. In practice, this happens when the PowerShell module pulls an older installer or when a previously cached gateway installer is reused during automation.

Ensure the automation installs the latest supported Standard mode gateway. Run Install-DataGateway -AcceptConditions without specifying -InstallerLocation. When this parameter is omitted, the cmdlet downloads and installs the newest gateway version it can access, which usually resolves version mismatches.

If the issue persists, explicitly control the installer version. Download the On premises data gateway (Standard mode) from the Microsoft Download Center or select a November 2025 or later Standard mode build from the currently supported monthly updates page. Save the installer locally and run Install-DataGateway -AcceptConditions -InstallerLocation "C:\BuildAssets\GatewayInstall.exe".

Finally, verify the environment is not contributing to the problem. Use PowerShell 7.0.6 or later (7.4.x preferred), ensure the latest DataGateway module is installed with Install-Module DataGateway -Force and run the script in an elevated session. Before reinstalling, remove any existing GatewayInstall.exe files from temp or build artifact folders to avoid reusing an outdated binary.

Update an on-premises data gateway | Microsoft Learn

PowerShell Cmdlets for On-premises data gateway management | Microsoft Learn

[loganmzz]

As automation process, installation & registration is done on new fresh VM on every run. So neither cache, neither oldre version for Gateway installer/binaries or PowerShell module exists.

[lbendlin]

That's a good thing, actually.  The latest version is broken, as only the Personal version was supplied.

Never ever install the latest version on a production cluster.

[loganmzz]

---

@lbendlin wrote:

That's a good thing, actually.  The latest version is broken, as only the Personal version was supplied.

Never ever install the latest version on a production cluster.

---

As they don't left us choice, it doesn't really matter ^^

[lbendlin]

You have choices

[loganmzz]

I may try to automate installer download. Unfortunately, not enough time available before holiday. But a new thing to try for a new year 🙂

I will get back there for the result!

[Zanqueta]

Hi @loganmzz 

This error indicates that the PowerShell DataGateway module is installing an outdated version of the gateway. When you attempt to add the cluster, the service requires a more recent version.

The Install-DataGateway cmdlet does not always retrieve the latest version automatically. Instead, it installs the version associated with the module package. This typically occurs when:

• The MicrosoftPowerBIDeployment or DataGateway module has not been updated.
• The parameter -AcceptEula or -DownloadLatest has not been used (depending on the module version).
• There is a local cache containing an older installer.

---

How to resolve this

Force update of the module and gateway

# Update the module to ensure you have the latest cmdlets
Update-Module -Name DataGateway

# Install the latest version of the gateway
Install-DataGateway -AcceptEula -DownloadLatest
``

Official reference:

Install an on-premises data gateway | Microsoft Learn

If this response was helpful in any way, I’d gladly accept a 👍much like the joy of seeing a DAX measure work first time without needing another FILTER.

Please mark it as the correct solution. It helps other community members find their way faster (and saves them from another endless loop 🌀.

[loganmzz]

---

@Zanqueta wrote:

This error indicates that the PowerShell DataGateway module is installing an outdated version of the gateway. When you attempt to add the cluster, the service requires a more recent version.

---

Sounds obvious 😄 

---

@Zanqueta wrote:

The Install-DataGateway cmdlet does not always retrieve the latest version automatically. Instead, it installs the version associated with the module package. This typically occurs when:

• The MicrosoftPowerBIDeployment or DataGateway module has not been updated.
• The parameter -AcceptEula or -DownloadLatest has not been used (depending on the module version).
• There is a local cache containing an older installer.

---

We are using a fresh VM on every build. So, I assume we use latest module versions.

---

@Zanqueta wrote:

---

How to resolve this

Force update of the module 

# Update the module to ensure you have the latest cmdlets
Update-Module -Name DataGateway
``

Tried, but as expected we already have latest one.

---

@Zanqueta wrote:

---

How to resolve this

Force update of the gateway

# Install the latest version of the gateway
Install-DataGateway -AcceptEula -DownloadLatest
``

Neither `-AcceptEula` neither `-DownloadLatest` parameter exist. As I assume `-AcceptEula` might be replaced with `-AcceptConditions`. I see no corresponding parameter for the later.

Sounds like an AI generated answer 😄