I don't blame Apple or Microsoft, for my part, the recent Apple Devices software has always worked well since its release, because I systematically do the "big" updates from the PC.
But there it turns out that following the installation of Windows 11 24H2... it's a disaster
A compatibility problem surely, but I'm sure that in 2025 this will be resolved.
On the other hand, I am surprised because if I understood correctly you managed to update your iPad Pro 10.5" from 17.7.2 to .3, it's surprising...
For my part, on Apple Devices 1.5.2.58, I did not have a specific error code, I monitor from the Windows task manager the different processes linked to the Apple Devices application (during the update), and some processes (I can't say which ones exactly) start to disappear and then the update freezes on my iDevice, consequently the processor usage as well as the disk usage drops to zero.
For information, I had the error code 06b4 0000 on Apple Devices 1.5.0.160 (iDevice frozen etc...) BUT by resetting the software and unplugging and replugging the cable, I was then able to restart the update
I also noticed like you that on Apple Devices 1.5.2.58, following a crash of the update, the Restore button does not work, you click and nothing happens, and the Update button is grayed out too, incredible!
Like you, I will continue to do my tests, to monitor the updates of the Apple Devices software and stay on the 24H2, at worst I have a virtual machine under Windows 10 which allows me to get out of trouble in case of problem.
Indeed, the use of old versions of Windows is to be avoided for security reasons. In any case as soon as Microsoft judges your PC ready to switch to version 24H2, it downloads and installs the update, unless you have done like me for a few weeks, to suspend the updates, but this is not a good thing to do.
As soon as the days are better between Apple Devices & Windows, I will not hesitate to let it be known here