InSSIDer closes/crashes while loading

Oscium Products inSSIDer
1

I installed a fresh copy of Windows (25H2, build 26200.7462) from a USB generated with the Creation tool downloaded directly from Microsoft yesterday. InSSIDer installed fine, including allowing me to log in and walking me through the features and icons. However, today, I tried to open the app and it would not respond at all. I tried to uninstall from the Installed Apps section, and it too would not do anything. I then ran the installer again which offered a repair option. After the repair, it would open the “Initializing” screen, but then promptly crash/close. I was then able to uninstall the app and then reinstalled, but it is still crashing after displaying “Initializing”. It is possible a Windows update has broken things, or does it sound like my 18-hour old Windows installation is already corrupt?

EDIT: I reinstalled Windows from scratch once again and updated everything. I installed InSSIDer and… same issue. There are errors in the Windows Application Logs. Here is the .NET runtime error:
”Application: MetaGeek.InssiderPro.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.DllNotFoundException
at MetaGeek.WiPry.LibUsb.NativeMethods.Init(IntPtr ByRef)
at MetaGeek.WiPry.Services.WiPryDeviceMonitor+d__24.MoveNext()
at System.Runtime.CompilerServices.AsyncMethodBuilderCore+<>c.b__6_1(System.Object)
at System.Threading.QueueUserWorkItemCallback.WaitCallback_Context(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
at System.Threading.ThreadPoolWorkQueue.Dispatch()
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()”

Here is the Application Error:
”Faulting application name: MetaGeek.InssiderPro.exe, version: 5.6.1.8, time stamp: 0x695819f1
Faulting module name: KERNELBASE.dll, version: 10.0.26100.7462, time stamp: 0x832e17c6
Exception code: 0xe0434352
Fault offset: 0x00161e54
Faulting process id: 0x1CC4
Faulting application start time: 0x1DC82BB90BFD782
Faulting application path: C:\Users\richa\AppData\Local\inSSIDer\current\MetaGeek.InssiderPro.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: 13081474-3c2e-4603-aebc-cb2de59c7675
Faulting package full name:
Faulting package-relative application ID:”

2

I was having a similar problem after running inSSIDer for the first time in a while. It worked fine that one time, but after that it would nothing at all - the UI never even came up. Even trying to uninstall did the same thing - nothing! Rebooting or running Windows in Safe Mode made no difference.

I discovered that running the downloaded installer would get it to start, and when it did, there was a brief error message in the top-right corner that indicated some sort of problem with “version 5.6.1” even though the installed version is 5.5.0.

Further investigation led me to the app’s data folder at
C:\Users\[mylogin]\AppData\Local\inSSIDer, where I found both an app-5.5.0 and an app-5.6.1 folder.

After removing the app-5.6.1 folder, everything started working again! My guess is that this was some sort of failed auto-update, that left broken remnants behind.

Hope that helps anyone else that’s having the same problem.