Facing Issues while installing gateway (1603 Error)

[Niket_Srivastav]

While installation of the gateway on my client VM, I am facing the below error that says machine thread returning 1603

MSI (s) (5C:38) [14:32:18:893]: Product: GatewayComponents -- Installation failed.

MSI (s) (5C:38) [14:32:18:894]: Windows Installer installed the product. Product Name: GatewayComponents. Product Version: 16.42.7. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status: 1603.

MSI (s) (5C:38) [14:32:18:961]: Deferring clean up of packages/files, if any exist
MSI (s) (5C:38) [14:32:18:962]: MainEngineThread is returning 1603
MSI (s) (5C:68) [14:32:18:966]: RESTART MANAGER: Session closed.
MSI (s) (5C:68) [14:32:18:966]: No System Restore sequence number for this installation.
=== Logging stopped: 12/22/2025 14:32:18 ===
MSI (s) (5C:68) [14:32:18:974]: User policy value 'DisableRollback' is 0
MSI (s) (5C:68) [14:32:18:974]: Machine policy value 'DisableRollback' is 0
MSI (s) (5C:68) [14:32:18:974]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (5C:68) [14:32:18:974]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (5C:68) [14:32:18:975]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (5C:68) [14:32:18:992]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (s) (5C:68) [14:32:18:993]: Destroying RemoteAPI object.
MSI (s) (5C:CC) [14:32:18:993]: Custom Action Manager thread ending.
MSI (c) (EC:8C) [14:32:18:996]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (EC:8C) [14:32:18:997]: MainEngineThread is returning 1603
=== Verbose logging stopped: 12/22/2025 14:32:18 ===

I have tried the following things -
1) Running the setup file using run as administrator mode.

2) Contacted the IT team and tried the setup with the elevated admin access on VM.

Still the issue persist what should I check or configure to be able to install gateway on my client VM

[v-karpurapud]

Hi @Niket_Srivastav 

We have not received a response from you regarding the query and were following up to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions.

Thank You.

[v-karpurapud]

Hi @Niket_Srivastav 

I wanted to check if you’ve had a chance to review the information provided. If you have any further questions, please let us know. Has your issue been resolved? If not, please share more details so we can assist you further.

Thank You.

[v-karpurapud · Accepted solution]

Hi @Niket_Srivastav 
Thank you for contacting the Microsoft Fabric community forum.

The 1603 error here is due to a corrupted or incomplete “GatewayComponents” package from a previous installation. Even with .NET 4.8, TLS 1.2, updates, and admin rights set up correctly, MSI will still return 1603 if a hidden Gateway component can't be fixed or replaced. To resolve this, use the Microsoft Program Install/Uninstall Troubleshooter to remove the leftover GatewayComponents MSI entry, clear the Package Cache, and reinstall the gateway from scratch.

I hope this information is helpful. If you have any further questions, please let us know. we can assist you further.

Best Regards.
Microsoft Fabric Community Support Team.

[tayloramy]

Hi @Niket_Srivastav, 

Do you have full admin rights on the VM? Is there any group policy in place to prevent installations? 

If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution. 

[AntoineW]

Is it any firewall or policy that block the installation ? 

[rohit1991]

Hii @Niket_Srivastav 

Error 1603 during Power BI Gateway installation is a generic Windows Installer failure, usually caused by blocked prerequisites or system restrictions on the VM, not by the gateway setup itself. Common causes include missing or corrupted .NET Framework, TLS 1.2 disabled, pending Windows updates / reboot, antivirus or endpoint protection blocking MSI execution, or an existing broken gateway component already installed. Ensure the VM has .NET 4.8+, TLS 1.2 enabled, latest Windows updates applied, no pending reboot, uninstall any old gateway versions, temporarily disable antivirus, and install using a local admin account. In most cases, fixing prerequisites or cleaning old GatewayComponents resolves error 1603.

[Niket_Srivastav]

My .NET version is

9.0.102
I have TLS 1.2 enabled
Windows is upto date
Gateway is not installed
still facing the same issue?