Yeah, I was afraid of that. It’s taking the client so long to traverse through all of the folders that the inspector is timing out.
I recommend you use the method suggested on one of your other threads, to use an action to retrieve a directory listed through PowerShell or the output of dir /s /b c:\users\*.pst and then loop through the text file’s results in your analysis. Ref Get Outlook PST size and location or Outlook PST Size
Also more generic methods for scanning the whole drive are linked on your other thread at Search hard drive for partial name of a file and get it's location
There’s also a very similar scan at Get Java, version and java build details