From 6f00b1b916e0f29749c47e86c0f2b85180e312c5 Mon Sep 17 00:00:00 2001
From: Elinor Fung <elfung@microsoft.com>
Date: Tue, 21 Apr 2026 13:22:34 -0700
Subject: [PATCH] Fix logical condition in
 ComWrappers.TryGetComInterfaceDispatch

---
 .../src/System/Runtime/InteropServices/ComWrappers.cs           | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/libraries/System.Private.CoreLib/src/System/Runtime/InteropServices/ComWrappers.cs b/src/libraries/System.Private.CoreLib/src/System/Runtime/InteropServices/ComWrappers.cs
index a5a5a3d7195e87..e91e7f755607d1 100644
--- a/src/libraries/System.Private.CoreLib/src/System/Runtime/InteropServices/ComWrappers.cs
+++ b/src/libraries/System.Private.CoreLib/src/System/Runtime/InteropServices/ComWrappers.cs
@@ -998,7 +998,7 @@ public object GetOrRegisterObjectForComInstance(IntPtr externalComObject, Create
             // we know how to interpret the IUnknown.
             IntPtr knownQI = ((IntPtr*)((IntPtr*)comObject)[0])[0];
             if (knownQI != ((IntPtr*)DefaultIUnknownVftblPtr)[0]
-                || knownQI != ((IntPtr*)DefaultIReferenceTrackerTargetVftblPtr)[0])
+                && knownQI != ((IntPtr*)DefaultIReferenceTrackerTargetVftblPtr)[0])
             {
                 // It is possible the user has defined their own IUnknown impl so
                 // we fallback to the tagged interface approach to be sure.