Leolo

Thanks, it's a sane recommendation, I've proposed something along those lines to the customer. I hope they'll accept it!

Many thanks for the links! (By the way, I've double checked the spam folder, there's nothing there from Microsoft. I think there's either a problem with my mail servers, or their mail servers) This old PC is important for the customer because it's running an old Citect 5.01 SCADA program, connected via Profibus to a machine in a bottle factory. It would cost tens of thousands of euros to replace the entire machine that produces the bottles, and the SCADA part is absolutely critical for its operation. Do you know if the hotfix can be installed without upgrading NT4 to SP4 ? I'm very nervous about upgrading the Operating System in this PC, because I'm not sure about possible compatibility problems with Citect 5.01 My main reason to apply the hotfix would be to avoid these kind of problems if they accidentally happen again in the future

I tried. I swear I tried. I searched for that fix for almost two hours, but came up empty handed By the way, I also tried filling up those forms with my email details in Microsoft's page. I submitted my request but they don't even reply, they simply ignore you!

Yes, I wouldn't do that either, it's too risky for my taste. But in my case this procedure was needed to fix a dumb mistake one of our technicians made. We had a computer with Win NT 4.0 that wasn't booting, and he suspected it could be a problem with the hard disk. He took the HDD from the old PC, and used an IDE-to-USB adapter to check it in a new computer running Windows 10. As soon as the disk was connected, BAM! the NTFS version was upgraded. He simply browsed the volume with Explorer, but didn't write anything to it. It turned out that the real problem with the old computer was a faulty cable. We replaced the cable, but now it still wouldn't boot because of the changed NTFS version (the old PC only had NT4 SP3 installed, so we got a Blue Screen of Death at startup) We finally managed to fix the drive by installing NT4 in another (very old) machine, and plugging it in that box to be able to run DiskProbe and change those damned bytes related to the NTFS version When the failing machine booted again at last, we ran chkdsk just to be sure and it only found a few metadata errors, that were quickly corrected. There was no data loss, and the PC runs fine, thankfully. Regards.

I've tested the Mark4NTFS tool in a PC with WinNT 4.0 SP6a installed, but unfortunately it doesn't work with volumes formatted using NTFS version 3.1 (commonly called version 5.1). Michael Tartsch's utility gets confused and gives an error saying that it cannot detect the NTFS version :( I had to manually fix the drive using DiskProbe from WinNT 4.0 Resource Kit (found it googling its filename "sp4rk_i386.exe") I followed these instructions: http://web.archive.org/web/20160505164434/http://www.nthelp.com/NT6/NTFS_version.htm And changed the NTFS version bytes from "03 01" to "01 02". Then I unchecked the Read-Only option in DiskProbe, and closed the tool, answering "yes" to flush the changes to disk. After doing that, chkdsk.exe will happily run again in the drive!