@Vadimk
A "bricked" device which boots only as far as the logo splash screen due to an unloadable file (or files) needed to boot, may not be detected by WebUdater but should always be detected by Updater (that's in preboot only for modern devices, as the very old 'region-only' devices are in a perpetual state where Updater.exe can be used regardless to re-flash its regions as required).

Modern devices normally have a visible file system accessible in Mass Storage Mode which isn't available if the device is soft-bricked, however usually in such cases preboot is still available. To remove corrupt files or re-format the file system, it's necessary to load a modified "cure" firmware so that MSM is re-enabled. After removal of corrupt files or formatting, original firmware is then loaded back to the device.

So you can now understand that if the boot process doesn't complete far enough for WebUpdater to be used, Updater.exe can be be essential to repair a device by software means.