Just getting the above update now as I type. It's another dual installer; it went pretty fast 1st time round, but stuck around on 100% installed for a while. It's now at 73% second time round. Yet more confusion for new users.
Yeah... A 64bit operating system that shutsdown with a 32bit program. My sister's laptop had 32bit Windows 7 on it, but upgraded itself to the 64bit version of Win10. During the 5 hours it took to get the 1903 update on it, I switched it off when specifically told not to as I fancied some sleep. The details of this experience are elsewhere, but during the 5 hours it took, there could have been a power cut resulting in the same thing. Since it was a free download, no compensation for lost data.
The update below makes interesting reading (it fixes broken 32bit stuff) regarding the comment I made above, why isn't Windows 64bit just a straight 64bit version with only 64bit programs? I realise that it would cost money to re-compile 32bit to 64bit, but if stuff is developed on a 64bit system, how come 64bit versions don't exist; such as W32time for example. Maybe I'm missing something, just curious.
My guess is that there are so many 32-bit programs that it would be a big job to make the changes to 64-bit. Microsoft has, however, created this problem as they've been releasing both 64-bit and 32-bit versions of Windows since Vista in 2007, so plenty of time to migrate to 64-bit.
Just got this, now. It's a bit shouty and fixes the same stuff the last update did, along with a fix for Internet Explorer 11 (I thought they were firing this off, along with dll files and active x; something that hasn't happened). I've also noticed that it no longer updates if you initiate a power off "event" (i.e. pressing the off button) and you need to go on the Start Menu>Power>Update and restart/shutdown otherwise it just "parks" the update.