He dismisses the tools because they are useless. The fact that you seem to think they are OK is only because you've never come across a bad problem in Windows.
Let's pretend for a minute that there's a new kernel level security patch on Windows that makes the system BSOD constantly on a system reboot. Let's pretend that it doesn't do this on any of your test systems or other equipment, and for whatever reason only affects a particular piece of hardware, despite not being a driver update. The computer never comes up again. Can't try safe mode, because on new windows the only way to get to safe mode is to reboot from a running system.
Let's check the log! Wait, it's in event viewer, and the system won't boot. Ok. Let's use DART to access the log!
It's not there. There's nothing there, because whatever "CRITICAL_PROCESS_DIED" happened before the event viewer log actually engaged. The last entry in the event log was the first reboot yesterday and it has nothing else there since then, despite attempting to boot 30 times.
Or worse, DART can't seem to find the damn log at all. It also doesn't show any patches in the last 15 days, despite installing a patch 5 days ago, one 3 days ago, and one yesterday. Removing the offending hotfix doesn't work if it's not in the list. Oh, and system restore won't work, because the problem is caused by file permission on some file that you can't find because NONE OF THE SYSTEM LOGS ARE WORTH ANYTHING.
Boot time diagnostics for NTBOOT.txt? NO! YOU HAVE TO HAVE A RUNNING SYSTEM TO ENABLE THIS NOW! YOUR SYSTEM DOESN'T RUN, NO LOGGING FOR YOU! Oh, did you think you could enable that using bcdedit from a boot disc? NO! It will save the safeboot option, but bootlogging is thrown away because FUCK YOU. Safeboot won't work anyway, because the system is denying itself access to some unknown file.
In this situation, Linux has some sort of log, or has an obvious error on the screen itself. In windows, you don't get to find the error. You get to wipe the system and start over, and hope that your client has a recent backup because Microsoft decided that the repair install function was just toooooo complicated for them to maintain.