Announcement

Collapse
No announcement yet.

WigiDash cannot connect to localhost servers, unable to register with DCOM

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • WigiDash cannot connect to localhost servers, unable to register with DCOM

    I upgraded my Windows 11 to 26100.6899 yesterday and WigiDash suddenly throw these 2 errors. (Upload image threw database error in this forum.)

    There were multiple updates, KB5066835, KB5066131, KB5068331 and Visual Studio 2022 so I'm not sure which one caused this and I can't uninstall them. (Also tried to go back to a Restore Point, which failed.)

    Errors were for HWinfo & AIDA64.
    Failed to initialize AIDA64. The Sensor Panel function will not be available.
    An error occurred while receiving the HTTP response to http://
    localhost:8733/WigiDashService/WigiDashWcf/. This could be due to the
    service endpoint binding not using the HTTP protocol. This could also be
    due to an HTTP request context being aborted by the server (possibly due
    to the service shutting down). See server logs for more details.

    There were also tons of DCOM error related to Interactive user in Event manager and software like Armoury Crate and Razer Synapse were also affected and most point to HWinfo failing to load at some stage. However, those software still worked while the Wigidash stopped working altogether. It seems to be related to RGB.

    I have not tried opening ports in Windows Firewall for these programs like what you would do for Ollama, etc.

    Have uninstalled standalone HWinfo64, rebooted, Reinstalled WigiDash.

    I can provide logs. Just let me know where to upload the LOG file.

    The GUID (for the sensors) seem to correspond to the failed registration to DCOM and points to a non-existent folder "C:\Users\JonSandstr?m\Source\..." but I don't know enough about HWinfo to know what's wrong. (Good to see the face behind HWinfo!)

  • #2
    Same problem

    Comment


    • #3
      UPDATE: Looks like MSFT pushed another update, and now it works. I just installed KB5066128.

      It looks like KB5066131 broke most localhost applications.

      -------------

      It appears to be related to .NET. My .NET runtime log in event viewer is filled with these:

      Application: WigiDashManager.exe
      Framework Version: v4.0.30319
      Description: The process was terminated due to an unhandled exception.
      Exception Info: System.Net.Sockets.SocketException
      at System.Net.Sockets.NetworkStream.Read(Byte[], Int32, Int32)

      Exception Info: System.IO.IOException
      at System.Net.Sockets.NetworkStream.Read(Byte[], Int32, Int32)
      at System.Net.PooledStream.Read(Byte[], Int32, Int32)
      at System.Net.Connection.SyncRead(System.Net.HttpWebR equest, Boolean, Boolean)

      Exception Info: System.Net.WebException
      at System.Net.HttpWebRequest.GetResponse()
      at System.ServiceModel.Channels.HttpChannelFactory`1+ HttpRequestChannel+HttpChannelRequest[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].WaitForReply(System.TimeSpan)

      Exception Info: System.ServiceModel.CommunicationException

      Server stack trace:
      at System.ServiceModel.Channels.HttpChannelUtilities. ProcessGetResponseWebException(WebException webException, HttpWebRequest request, HttpAbortReason abortReason)
      at System.ServiceModel.Channels.HttpChannelFactory`1. HttpRequestChannel.HttpChannelRequest.WaitForReply (TimeSpan timeout)
      at System.ServiceModel.Channels.RequestChannel.Reques t(Message message, TimeSpan timeout)
      at System.ServiceModel.Dispatcher.RequestChannelBinde r.Request(Message message, TimeSpan timeout)
      at System.ServiceModel.Channels.ServiceChannel.Call(S tring action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
      at System.ServiceModel.Channels.ServiceChannelProxy.I nvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
      at System.ServiceModel.Channels.ServiceChannelProxy.I nvoke(IMessage message)
      at System.Runtime.Remoting.Proxies.RealProxy.HandleRe turnMessage(System.Runtime.Remoting.Messaging.IMes sage, System.Runtime.Remoting.Messaging.IMessage)
      at System.Runtime.Remoting.Proxies.RealProxy.PrivateI nvoke(System.Runtime.Remoting.Proxies.MessageData ByRef, Int32)
      at WigiDashServiceLibrary.WigiDashWcfReference.IWigiD ashWcf.GetHwinfoSdkVersion()
      at ServiceLibrary.ServiceBridge.GetHwinfoSdkVersion()
      at WigiDashManager.Views.ConfigPanel.OnLoaded(System. Object, System.Windows.RoutedEventArgs)
      at System.Windows.EventRoute.InvokeHandlersImpl(Syste m.Object, System.Windows.RoutedEventArgs, Boolean)
      at System.Windows.UIElement.RaiseEventImpl(System.Win dows.DependencyObject, System.Windows.RoutedEventArgs)
      at System.Windows.BroadcastEventHelper.BroadcastEvent (System.Windows.DependencyObject, System.Windows.RoutedEvent)
      at System.Windows.BroadcastEventHelper.BroadcastLoade dEvent(System.Object)
      at MS.Internal.LoadedOrUnloadedOperation.DoWork()
      at System.Windows.Media.MediaContext.FireLoadedPendin gCallbacks()
      at System.Windows.Media.MediaContext.FireInvokeOnRend erCallbacks()
      at System.Windows.Media.MediaContext.RenderMessageHan dlerCore(System.Object)
      at System.Windows.Media.MediaContext.RenderMessageHan dler(System.Object)
      at System.Windows.Threading.ExceptionWrapper.Internal RealCall(System.Delegate, System.Object, Int32)
      at System.Windows.Threading.ExceptionWrapper.TryCatch When(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
      at System.Windows.Threading.DispatcherOperation.Invok eImpl()
      at MS.Internal.CulturePreservingExecutionContext.Call backWrapper(System.Object)
      at System.Threading.ExecutionContext.RunInternal(Syst em.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
      at System.Threading.ExecutionContext.Run(System.Threa ding.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
      at System.Threading.ExecutionContext.Run(System.Threa ding.ExecutionContext, System.Threading.ContextCallback, System.Object)
      at MS.Internal.CulturePreservingExecutionContext.Run( MS.Internal.CulturePreservingExecutionContext, System.Threading.ContextCallback, System.Object)
      at System.Windows.Threading.DispatcherOperation.Invok e()
      at System.Windows.Threading.Dispatcher.ProcessQueue()
      at System.Windows.Threading.Dispatcher.WndProcHook(In tPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
      at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
      at MS.Win32.HwndSubclass.DispatcherCallbackOperation( System.Object)
      at System.Windows.Threading.ExceptionWrapper.Internal RealCall(System.Delegate, System.Object, Int32)
      at System.Windows.Threading.ExceptionWrapper.TryCatch When(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
      at System.Windows.Threading.Dispatcher.LegacyInvokeIm pl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
      at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
      at MS.Win32.UnsafeNativeMethods.DispatchMessage(Syste m.Windows.Interop.MSG ByRef)
      at System.Windows.Threading.Dispatcher.PushFrameImpl( System.Windows.Threading.DispatcherFrame)
      at System.Windows.Application.RunDispatcher(System.Ob ject)
      at System.Windows.Application.RunInternal(System.Wind ows.Window)
      at WigiDashManager.App.Main()
      Last edited by eckertt001; 10-16-2025, 02:04 AM.

      Comment


      • #4
        Not working

        Comment


        • #5
          The difference I see with my installation is you do not have KB5066131. Did you uninstall that?

          Click image for larger version

Name:	update.png
Views:	24
Size:	168.1 KB
ID:	170504

          Comment


          • #6
            no

            Comment


            • #7
              Originally posted by eckertt001 View Post
              UPDATE: Looks like MSFT pushed another update, and now it works. I just installed KB5066128.

              It looks like KB5066131 broke most localhost applications.

              -------------

              It appears to be related to .NET. My .NET runtime log in event viewer is filled with these:

              Application: WigiDashManager.exe
              Framework Version: v4.0.30319
              Description: The process was terminated due to an unhandled exception.
              Exception Info: System.Net.Sockets.SocketException
              at System.Net.Sockets.NetworkStream.Read(Byte[], Int32, Int32)

              <snip>
              Thanks mate! It worked! I went to Update Catalog to download KB5066128 to overwrite KB5066131. Wigidash is now working.

              Those 2 are for the same CVE-2025-55248 vulnerability. Did Windows Update served the wrong update to certain configuration?

              I will update my feedback with Microsoft.
              Last edited by EricTay; 10-16-2025, 06:16 PM.

              Comment


              • #8
                Originally posted by NIGHT View Post
                Not working
                I assume you have already restarted Windows.

                Try to download KB5066131 from Update Catalog.

                Microsoft Update Catalog

                Download the correct version and install it to overwrite KB5066128. See if that works.

                Comment


                • #9
                  KB5066131 for version 24H2

                  Comment


                  • #10
                    Originally posted by NIGHT View Post
                    KB5066131 for version 24H2
                    This is too weird. All I can suggest now is to try to reinstall KB5066128 and restart.

                    Comment


                    • #11
                      Originally posted by EricTay View Post

                      Thanks mate! It worked! I went to Update Catalog to download KB5066128 to overwrite KB5066131. Wigidash is now working.

                      Those 2 are for the same CVE-2025-55248 vulnerability. Did Windows Update served the wrong update to certain configuration?

                      I will update my feedback with Microsoft.
                      I think I figured out why Windows Update installed the wrong patch.

                      I installed the 25H2 enablement package last week but winver.exe still showed 24H2 for some reason. (Might be region block.) All the binaries for 25H2 are already installed, only the OS still report itself as 24H2. So when KB5066131 (this is for 24H2) was installed, I guess OS internal checks might have blocked .Net runtime from executing code due to incorrect version.

                      When I first use Windows Update to install KB5066131, it actually failed, even after reboot. I downloaded it from Update Catalog to do a force install, which led to Wigidash's underlying HWinfo dll to not run.

                      This morning, I got the 25H2 update in Windows Update officially and after install, there was no problem with Wigidash, so I guess there's no problem with this PC anymore.

                      Comment

                      Working...
                      X