Rem0o
The app will never bootup if a usb floppy drive with no floppy exist
Describe the bug
I have a TEAC USB to floppy adapter connected to my PC. After upgrading from version 242(ish?) to the latest version, the app won't boot anymore.
The adapter malfunctions when there is no floppy inserted in the drive. Windows freezes after a certain amount of time when it tries to access the contents of the floppy, and eventually times out and displays a 'please insert floppy' dialog. The freeze only affects partitions-related software.
But after the update, the app won't boot anymore with no crash,no log evidence, just a thread in the background. It won't time out or fix itself.
Sometimes it can't even be killed by taskkill.
The only solution is to eject the floppy adaptor, but to do so, it cannot be used by any software. And Windows thinks that FanControl is using it. :(
Relevant hardware specs and setup
Please try latest release from here: https://github.com/Blacktempel/DiskInfoToolkit and see if the error occurs. (Start DiskInfoViewer)
Would also be great if you could upload the generated log from ConsoleOutputTest in same release.
Please try latest release from here: https://github.com/Blacktempel/DiskInfoToolkit and see if the error occurs. (Start DiskInfoViewer)
Would also be great if you could upload the generated log from ConsoleOutputTest in same release.
they just... freeze here forever with no error or so
Does something change if you let one run / load for 1-2 minutes per drive you have connected ? Seems weird, but I certainly did not expect a floppy disk to still be used - when using FanControl. I can try compiling a small program and let you test something else. Maybe that will work and can "ignore" floppy disks. May need a little while for that.
Does something change if you let one run / load for 1-2 minutes per drive you have connected ? Seems weird, but I certainly did not expect a floppy disk to still be used - when using FanControl. I can try compiling a small program and let you test something else. Maybe that will work and can "ignore" floppy disks. May need a little while for that.
nope, they won't.
For other software, I usually let it run while I do something else. By the time I remember it again, it's usually done.
but the app won't run even pass a night
Does something change if you let one run / load for 1-2 minutes per drive you have connected ? Seems weird, but I certainly did not expect a floppy disk to still be used - when using FanControl. I can try compiling a small program and let you test something else. Maybe that will work and can "ignore" floppy disks. May need a little while for that.
I got one log by run it and forget about it
Floppy_Log.txt (SN Blurred)
Please test this version and upload the log.
https://drive.google.com/file/d/1224tW5kR1-9rNH7JUeufVWDWvPn5oH4s/view?usp=sharing
OpenHashTab
20251215_1615_FC_3759_Debug.7z MD5 EF8A30F33CCB3C6835572D45976116A4
20251215_1615_FC_3759_Debug.7z SHA-1 DF8ED9F8E59386904B7F30D4FFF4AF7CA07678F8
20251215_1615_FC_3759_Debug.7z SHA-256 221B57306740055A560995B5237BDB17D74EBD90B68F5A4A4B18CC26AA7DEB82
20251215_1615_FC_3759_Debug.7z SHA-512 ACB32CAE59B340D283AED92FB258E9AC4B0B3D07C6F1F9581447338D1033AD388E331D267E592F8F2413B781375E6F7CF17AD5C7F0D7000F355198E857517353
20251215_1615_FC_3759_Debug.7z SHA3-512 05DBE45CD55A4F81D9CCB9DD9242924BA91ABDFA04F2F4730D2AF72897E998F822F7901BFF9199B22F242DAAC8454A193F38B9C02F167FC85A33469C960739BB
The floppy seems to be detected and filtered out
[15/12/2025 23:23:03.930] [TRACE] Adding '\\?\usbstor#sfloppy&ven_teac&prod_usb_uf000x&rev_0.00#6&32068f35&0#{53f56311-b6bf-11d0-94f2-00a0c91efb8b}' to exclusion list (is floppy).
Though I believe it was not even considered a storage device in previous logic as it does not show up again. So the issue is not the floppy but it appears to be the Samsung 970. That one takes almost 2 minutes:
[15/12/2025 23:23:03.936] [TRACE] PhysicalPath = '\\?\scsi#disk&ven_nvme&prod_samsung_ssd_970#5&3a98cff4&0&000000#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}'.
[15/12/2025 23:25:01.236] [DEBUG] Initialization of Storage took 00:01:57.2987440.
Same for previous log:
[10/12/2025 23:47:49.204] [TRACE] PhysicalPath = '\\?\scsi#disk&ven_nvme&prod_samsung_ssd_970#5&3a98cff4&0&000000#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}'.
[10/12/2025 23:51:08.434] [TRACE] Adding device with PhysicalPath = '\\?\scsi#disk&ven_nvme&prod_samsung_mz1lv960#5&4b26363&0&000000#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}'.
Can you check if CrystalDiskInfo is working as expected or does it hang too ?
Another test (expect same delay) for a bit more log information: https://drive.google.com/file/d/1nO3O8UGeKaB3QKWh-m4o6k4RJFSBWiwR/view?usp=sharing
OpenHashTab
20251215_1700_GithubTest_FC_3759_Debug.7z MD5 370B2A335A8D8B32B6DC1BCA8F02B3D6
20251215_1700_GithubTest_FC_3759_Debug.7z SHA-1 CB07B3EB2050C6B540A4E8A338AC00B7B6340798
20251215_1700_GithubTest_FC_3759_Debug.7z SHA-256 3800C477BC51C3AA9E62754400E31C52AF1246C0DB9A15F47D219B9400F7DB78
20251215_1700_GithubTest_FC_3759_Debug.7z SHA-512 6940087FFCB196439D0C749503E41F0793EC5D976CA00917E40C021D769075A25EA3F235E28C30BDAE800AA4EB32C8DC19EB81A4A454906B352DF5A38BDA49AE
20251215_1700_GithubTest_FC_3759_Debug.7z SHA3-512 41A445E41FFE84AEF135AA67DA087F3C36DC8190504819ECC9B3427206717831DC5E369D6B6DBBE126AEA26E6EF84E4D6C9E45C033771DC0B2B2FDCDD0074FB5
Can you check if CrystalDiskInfo is working as expected or does it hang too ?
Nope, it wont.
and the new version pops out immediately :(
Can you check if CrystalDiskInfo is working as expected or does it hang too ?
Nope, it wont.
So CrystalDiskInfo is working good ? Could be due to them also using WMI.
The new log seems to have finished properly and fast enough (~1 second). What has changed ?