FanControl.Releases Update from V24x to V247 leads to continous USB mass storage unmount/remount

Like the title says, since I updated from an earlier version (V245 or V246 I guess), the startup of FanControl causes unmount and remount of one USB mass storage device (Chieftec internal card reader) every some seconds. As soon as FanControl is closes, the device works normally again.

This is NOT uniquely connected to FanControl, I had the same issue with WD Dashboard (now Sandisk Dashboard). But maybe they are using similar libraries. I would highly appreciate finding out what excactly causes this, it seems to have been integrated/changed in FanControl in the latest version.

Thanks!

Nov 16 '25 11:11 Hymenochirus32

This seems weird. Does this also happen when you use CrystalDiskInfo ?

Please provide "Log.txt" which is being created by "ConsoleOutputTest" in latest release from here: https://github.com/Blacktempel/DiskInfoToolkit/releases

Nov 16 '25 12:11 Blacktempel

Does this also happen when you use CrystalDiskInfo ?

No.

Please provide "Log.txt" which is being created by "ConsoleOutputTest" in latest release from here: https://github.com/Blacktempel/DiskInfoToolkit/releases

While executing the console tool, it happened also. Log.txt

Nov 16 '25 13:11 Hymenochirus32

Thank you for the log. I will check it and see what I can do.

Nov 16 '25 18:11 Blacktempel

That is a bit weird. There is not a single drive letter in the log, yet it said device with drive letter 'S' was removed. Was the log modified ?

Nov 16 '25 18:11 Blacktempel

No, the log was not changed. The HDD and the two SSD cannot have just one drive letter, because they have multiple partitions. The card reader has multiple drives (one for each slot), but because I am only using the SD slot only one of them has a drive letter ('S').

Nov 16 '25 19:11 Hymenochirus32

All partitions of all drives are also in the log file and usually contain the drive letter, if one was set for the partition. Just weird that no partition seems to have one in the log, that's a first.

I will try to get a test version ready.

Nov 16 '25 19:11 Blacktempel

I may have found a solution. This seems to work fine for my card reader devices. Please try this, upload the log file and let me know if it solves your problem.

https://drive.google.com/file/d/1Wp96bqJQ6tQhXDj7xh-GM-KYX1PDQrfg/view?usp=sharing

OpenHashTab

20251117_1420_GithubTest_FC_3697_Debug.7z	MD5	95D6476700B8D95B56620A0695307254
20251117_1420_GithubTest_FC_3697_Debug.7z	SHA-1	F4769F7FB26E783744734E75A3576F665CE7889C
20251117_1420_GithubTest_FC_3697_Debug.7z	SHA-256	3A6721509B1180E38A2A99466C83CF8709A9F29123DE42234002B2A0D0DB502F
20251117_1420_GithubTest_FC_3697_Debug.7z	SHA-512	A12D0F47609EA0AE0ABF5F6FFDC6C916A327B59456137DF0675A93C8E2043139C11E02C4510864DD588846B7CD21A6F2B426F115C6C93788BDEFF58CDACB8D24
20251117_1420_GithubTest_FC_3697_Debug.7z	SHA3-512	A8B7AF103279A2B1B74299B0520C3D1165A87C22A41AB8FE2320E8881645AAF3B3CB31A498A6180966C4DE0F5A323213CBA2D396AD6E818182BB4A54C35A754B

Nov 17 '25 13:11 Blacktempel

Thanks for your effort! Here you are: Log.txt

Nov 17 '25 21:11 Hymenochirus32

Same problem for me (and my card reader), i reverted to v243. That seems to work.

Nov 19 '25 10:11 MrMcFlyy

@MrMcFlyy Please upload a log file from most recent release here: https://github.com/Blacktempel/DiskInfoToolkit/releases/tag/1.0.6

and from that specific version:

I may have found a solution. This seems to work fine for my card reader devices. Please try this, upload the log file and let me know if it solves your problem.

https://drive.google.com/file/d/1Wp96bqJQ6tQhXDj7xh-GM-KYX1PDQrfg/view?usp=sharing

OpenHashTab

20251117_1420_GithubTest_FC_3697_Debug.7z	MD5	95D6476700B8D95B56620A0695307254
20251117_1420_GithubTest_FC_3697_Debug.7z	SHA-1	F4769F7FB26E783744734E75A3576F665CE7889C
20251117_1420_GithubTest_FC_3697_Debug.7z	SHA-256	3A6721509B1180E38A2A99466C83CF8709A9F29123DE42234002B2A0D0DB502F
20251117_1420_GithubTest_FC_3697_Debug.7z	SHA-512	A12D0F47609EA0AE0ABF5F6FFDC6C916A327B59456137DF0675A93C8E2043139C11E02C4510864DD588846B7CD21A6F2B426F115C6C93788BDEFF58CDACB8D24
20251117_1420_GithubTest_FC_3697_Debug.7z	SHA3-512	A8B7AF103279A2B1B74299B0520C3D1165A87C22A41AB8FE2320E8881645AAF3B3CB31A498A6180966C4DE0F5A323213CBA2D396AD6E818182BB4A54C35A754B

Nov 19 '25 10:11 Blacktempel

I have the same issue with (https://github.com/Blacktempel/DiskInfoToolkit/releases/tag/1.0.6) but https://drive.google.com/file/d/1Wp96bqJQ6tQhXDj7xh-GM-KYX1PDQrfg/view?usp=sharing Seem to work with no problem.

Debug-Log.txt

1.0.6-Log.txt

Nov 21 '25 10:11 cdegut

I've got the same issue with any version higher than 247. It keeps connecting and disconnecting USB devices forever. I've also got a card reader that is recognized as multiple USB devices. Actually version 247 is affected too but contrary to later versions the connect/ disconnect loop stops at some point. I've tried versions up to 250. Let me know if I can do something to help troubleshoot the issue.

Nov 28 '25 09:11 altae7

@altae7 Please upload a log file from most recent release here (by running "ConsoleOutputTest"): https://github.com/Blacktempel/DiskInfoToolkit/releases/

Also check if it still keeps happening as some edge cases were fixed.

Nov 28 '25 09:11 Blacktempel

Here is the requested log file. I ran ConsoleOutputTest.exe while version 250 was installed.

Log.txt

Nov 28 '25 10:11 altae7

Does it still happen with that version ? I cannot see an issue in your log.

Nov 28 '25 12:11 Blacktempel

Yes it still happens with Version 250. In fact it's worse than version 247. When running version 247 the USB connect/ disconnect loop eventually stops and Fan Control runs without issues. With version 250 the loop never stops and Fan Control eventually crashes.

Nov 28 '25 13:11 altae7

Ah no, I was talking about the version of DiskInfoToolkit. Does the issue still happen when executing ConsoleOutputTest or DiskInfoViewer ? Please check this. That includes some fixes as mentioned.

Nov 28 '25 13:11 Blacktempel

OK, now it's clear. I can run both without getting into a USB connect/ disconnect loop.

Nov 28 '25 20:11 altae7

I encountered the same problem, which persists in version v251. Even with the sensor temperature acquisition interval set, the USB mass storage device still disconnects. A temporary workaround is to uncheck the "Storage" option in the "Sensor Settings".

我也遇到了同样的问题，这个问题在 v251 版本中仍然存在。即使设置了传感器温度采集间隔，USB 大容量存储设备仍然会断开连接。一个临时的解决方法是在“传感器设置”中取消勾选“存储”选项。

Dec 08 '25 06:12 YukinoRikka

@YukinoRikka Please check this:

Does the issue still happen when executing ConsoleOutputTest or DiskInfoViewer ? Please check this. That includes some fixes as mentioned.

And provide a log from ConsoleOutputTest. Take latest release from here: https://github.com/Blacktempel/DiskInfoToolkit/releases

Dec 08 '25 08:12 Blacktempel

@Blacktempel I tested two USB devices, Lexar and Netac: When running ConsoleOutputTest, the Lexar worked fine, but the Netac disconnected.

Lexar log (working fine): Log-lexar.txt Netac log (error occurred): Log-netac.txt

Dec 08 '25 09:12 YukinoRikka