StableBit Troubleshooter - Revision history

Alex at 00:18, 15 February 2026

2026-02-15T00:18:29Z

2026-02-15T00:18:15Z

2026-02-15T00:17:09Z

2020-03-14T23:20:46Z

2020-03-14T23:20:13Z

2019-02-14T00:42:57Z

2019-02-14T00:41:04Z

2018-12-20T04:42:26Z

2018-12-13T22:35:47Z

2017-11-09T17:12:07Z

@@ Line 4: / Line 4: @@
 * [https://dl.covecube.com/Troubleshooter/StableBit.Troubleshooter.exe Download the latest version]
-** This tool requires .NET Framework 4.8
+** This tool requires .NET Framework 4.8+
 The StableBit Troubleshooter program is a stand alone EXE (requires no installation). It's sole purpose is to grab logs and other information about the system that is used for troubleshooting (and for nothing else).

@@ Line 4: / Line 4: @@
 * [https://dl.covecube.com/Troubleshooter/StableBit.Troubleshooter.exe Download the latest version]
-** This tool requires .NET Framework 4.5.1
+** This tool requires .NET Framework 4.8
 The StableBit Troubleshooter program is a stand alone EXE (requires no installation). It's sole purpose is to grab logs and other information about the system that is used for troubleshooting (and for nothing else).

← Older revision		Revision as of 00:17, 15 February 2026
Line 1:		Line 1:
−	[[File:StableBitTroubleshooter.png\|border\|StableBit Troubleshooter]]	+	[[File:StableBitTroubleshooter.png\|border\|StableBit Apps Troubleshooter]]

← Older revision		Revision as of 23:20, 14 March 2020
Line 3:		Line 3:


−	* [~~http~~://dl.covecube.com/Troubleshooter/StableBit.Troubleshooter.exe Download the latest version]	+	* [https://dl.covecube.com/Troubleshooter/StableBit.Troubleshooter.exe Download the latest version]
	** This tool requires .NET Framework 4.5.1		** This tool requires .NET Framework 4.5.1

@@ Line 4: / Line 4: @@
 * [http://dl.covecube.com/Troubleshooter/StableBit.Troubleshooter.exe Download the latest version]
-** This tool requires .NET Framework 4.5
+** This tool requires .NET Framework 4.5.1
 The StableBit Troubleshooter program is a stand alone EXE (requires no installation). It's sole purpose is to grab logs and other information about the system that is used for troubleshooting (and for nothing else).

@@ Line 35: / Line 35: @@
 #*:*Event Viewer logs
 #*:*Minidumps from the system (crash dumps), and the the NT OS Kernel EXE (in case there are issues reading the dump, this allows us to be able to).
-#*:*VDS output from the system, which enumerates a bunch of disk information
+#*:*VDS output from the system, which enumerates a bunch of disk information.
-#*:*"mountvol" output, which allows us to see the specific mount points, and some additional info
+#*:*"mountvol" output, which allows us to see the specific mount points, and some additional info.
 #*:*FLTMC output, as this lists file system filters and other disk info. This is useful, as it lets us know if any antivirus or disk tools are installed, as they are usually installed as "filters".
 #*:*MSINFO32 output, as this gets a lot of additional system information.

@@ Line 30: / Line 30: @@
 #*: This will create a tracing of the GUI, and log the crash that occurs.  It will then compress and upload the memory dump. This is useful if the UI is crashing, especially due to specific actions or just over time.
 # '''Additional (System) Information'''
-#: There is some additional system information that we may need, that isn't directly related to our software. And it may take a while to completely collect this information.  Because of these reasons, they are optional, and may be disabled.
+#: There is some additional system information that we may need that isn't directly related to our software, and it may take a while to completely collect this information. Because of these reasons, they are optional, and may be disabled.
 #* '''Include system information'''
 #*:  This collects additional system information, that may be very useful for diagnostics.  We do highly recommend leaving it enabled, as it grabs information that is very, very helpful.  Specifically, it captures:

@@ Line 39: / Line 39: @@
 #*:*FLTMC output, as this lists file system filters and other disk info. This is useful, as it lets us know if any antivirus or disk tools are installed, as they are usually installed as "filters".
 #*:*MSINFO32 output, as this gets a lot of additional system information.
-#* '''Include disk details (Direct I/O)```
+#* '''Include disk details (Direct I/O)'''
 #*: This collects information about the disks, include S.M.A.R.T. information.
 #*:* This may hang on some systems, so it is disabled by default.

@@ Line 24: / Line 24: @@
 #*: This will generate a process memory dump of the system service for the product you've selected. It will compress it, and then upload it.  This is the same as opening up the task manager, right clicking on the process and selecting "Create dump file". However, there are some caveats to doing this, especially with StableBit Scanner, and this handles that issue seamlessly.
 #* '''Submit a user interface memory dump'''
-#*: This will generate a process memory dump of the use interface process for the product you've selected. It will compress it, and then upload it.  This is the same as opening up the task manager, right clicking on the process and selecting "Create dump file". However, there are some caveats to doing this, especially with StableBit Scanner, and this handles that issue seamlessly
+#*: This will generate a process memory dump of the user interface process for the product you've selected. It will compress it, and then upload it.  This is the same as opening up the task manager, right clicking on the process and selecting "Create dump file". However, there are some caveats to doing this, especially with StableBit Scanner, and this handles that issue seamlessly
 #* '''Submit a service crash (manual)'''
 #*: This will create a tracing of the service, and log the crash that occurs.  It will then compress and upload the memory dump. This is useful if the service is crashing, especially due to specific actions or just over time.