A standard installation shouldn't result in them being laid out in the wrong order. (I thought they stopped doing it that way during install a long time ago.) If they're in the wrong order, you modified it. So if you've already futzed around with your system in a way that isn't supported by Microsoft, they're not going to bother trying to give you instructions to fix the problem when they don't have any way of knowing every possible way that people may have modified their systems and then testing out instructions for them all. The reason they can't fix it within the update is because they can't go making such drastic changes to partitions within an update.
For me, I moved my recovery partition towards the beginning of the drive, in front of C, because I got tired of Microsoft automatically changing around my partitions when I was trying to leave space unprovisioned (for SSD overprovisioning). Trying to fix this recovery partition issue involved using partitioning programs to resize things. And of course, that didn't actually resolve the problem and eliminate the error code, so them blaming the partition size for the failure of the update is false.
They need to do one of two things (or both): One is to make the update simply check for the recovery partition being an issue, and if it is, then mark the update as "uninstallable" and never list it or try to install it again without the user going in and unflagging it (in case they follow the instructions to resize). They'd have to have some way to still indicate to the user that it failed, but having it fail and display an obscure error code EVERY SINGLE TIME UPDATES ARE INSTALLED is stupid. It should return a message like "an option update didn't install correctly, here are instructions if you want to try to fix it, but it's not a big deal since you're not using BitLocker". At the very least, actual information should be given instead of an error code that users may not even see and probably won't understand or know how to research.
The other option is to eliminate the partition entirely, since the recovery environment doesn't entirely depend on it. The update and just set it up to run without the partition. The only thing that is possibly lost is the ability to "reset" Windows, and they can add instructions into the Reset process for dealing with that if it becomes necessary (click here to create a USB installer). If the Recovery partition is broken or can't be properly serviced, what good is it doing anyway?
Of course, the real fix is to make the update not require a larger recovery partition in the first place. Work within what the standard install of a current version of the OS will have available.