⚠️ 3 verified solutions available for Error 1789 — Last updated 2026-03-13
Error 1789 📋

Fix ERROR_TRUSTED_RELATIONSHIP_FAILURE — Windows Error Code 1789

Error 1789 (ERROR_TRUSTED_RELATIONSHIP_FAILURE) is a Windows RPC & Network error that occurs when the trust relationship between this workstation and the primary domain failed.. This guide provides step-by-step solutions to resolve this issue.

🏷️ Code: 1789 📛 ERROR_TRUSTED_RELATIONSHIP_FAILURE 📅 Updated: 2026-03-13 ⏱️ 3 Solutions

🎮 Common Scenario: Are you experiencing Error 1789 while launching or installing Valorant? The solutions below directly address the system interactions specific to this application.

⚡ Quick Fix

Update Root Certificates: Open Command Prompt as Administrator

👇 See all 3 solutions below

The Ultimate Auto-Fix Script

Download our advanced, custom-built Smart Diagnostic Script (.bat). It safely creates a System Restore Point, applies targeted fixes based on advanced diagnostics for Error 1789, and generates a detailed HTML repair report.

✓ Safe & Verified ✓ Restore Point Protected ✓ HTML Report Included
⚠️
CRITICAL INSTRUCTION: Once downloaded, you MUST right-click the file and select "Run as Administrator". If opened normally, it will not function.
📑 Table of Contents
What is Error 1789? Common Causes Step-by-Step Solutions Prevention Tips Related Errors

💡 What is Error 1789?

Windows System Error Code 1789, known as ERROR_TRUSTED_RELATIONSHIP_FAILURE, is a RPC & Network error that occurs during Remote Procedure Call (RPC) and network communication. The error indicates that: The trust relationship between this workstation and the primary domain failed. When this error is encountered, the Windows operating system was unable to complete the requested operation within the network services subsystem. The error code 1789 is returned by the GetLastError() function and provides developers with a specific identifier to diagnose the root cause of the failure. The symbolic name ERROR_TRUSTED_RELATIONSHIP_FAILURE maps directly to this numeric code and is commonly referenced in Microsoft documentation, developer forums, and system logs. Understanding this error and its context within Remote Procedure Call (RPC) and network communication is essential for effective troubleshooting.

⚠️ Common Causes

  • System date/time is incorrect, causing certificate validation to fail
  • Root certification authorities are outdated or missing
  • TLS protocol mismatch between client and server
  • Antivirus or proxy is intercepting SSL traffic with an untrusted certificate
📚 Comprehensive Guide

Resolving Device Driver Failures: Code 43, PnP Watchdog, and DDU

An encyclopedia on mastering Windows Device Manager, resolving generic Code 43 GPU faults, and executing flawless driver sweeps with DDU.

Read the full guide →

✅ Step-by-Step Solutions

1 Update Root Certificates
  1. Open Command Prompt as Administrator
  2. Run: certutil -generateSSTFromWU roots.sst
  3. This downloads the latest root certificates from Microsoft
  4. Open certmgr.msc → Trusted Root Certification Authorities → import roots.sst
  5. Restart your browser and applications
Advertisement
[AdSense In-Article Ad Generator]
Show Advanced Solutions (2 more)
2 Fix System Date and Time
  1. Incorrect system time is the #1 cause of SSL/TLS errors
  2. Right-click the clock in the taskbar → Adjust date/time
  3. Enable 'Set time automatically' and 'Set time zone automatically'
  4. Click 'Sync now' under 'Synchronize your clock'
  5. If time is significantly off, manually set it first, then enable auto-sync
3 Clear SSL State and Cache
  1. Press Win+R, type inetcpl.cpl, press Enter
  2. Go to the Content tab → click 'Clear SSL State'
  3. Go to the Advanced tab → ensure TLS 1.2 and TLS 1.3 are checked
  4. Uncheck SSL 3.0 and TLS 1.0 (outdated and insecure)
  5. Click Apply → OK and restart your browser

🎬 Video Tutorials

▶️ Watch Video Tutorials
How To Fix Rpc Network Error Windows
Open on YouTube →

💻 Diagnostic Command

Run this PowerShell command to find related events in your system log:

Get-EventLog -LogName System -Newest 20 | Where-Object {$_.Message -like "*1789*" -or $_.Message -like "*ERROR_TRUSTED_RELATIONSHIP_FAILURE*"} | Format-List

💡 Open PowerShell as Administrator, paste the command above, and press Enter.

🛡️ Prevention Tips

  • Keep your system clock synchronized (Settings → Time & Language → Sync now)
  • Install Windows Updates regularly to keep root certificates current
  • Disable SSL inspection in antivirus software if it causes certificate errors
Was this helpful?
Last updated: 2026-03-13
📖
Based on Official Microsoft Documentation
Solutions Tested on Windows 10 & 11
Error codes sourced from Microsoft Win32 SDK. Updated 2026-03-13.
🔧 Diagnose Your Error