You wish to understand the reasoning behind why the Windows 10 Cumulative Update packages have been split into two packages – one for 32-bit machines and another for 64-bit machines. (Starting July 10, 2018)
This is will impact any current auto-download packages and schedules that are targeting 32-bit machines. Please change your schedules and download new packages as needed.
You asked, we wavered, and said, "No, you're wrong." BUT, we are happy to announce the Windows 10 cumulative update packages are getting an amicable divorce. (Yeah, you were right.)
Starting over the next few days, we will be uploading separate packages for the Windows 10 cumulative update packages. We are doing this because of the ever growing size of the .msu files contained in the packages. A lot of people do not need the 32-bit updates, and our single package causes unneeded bandwidth consumption leading to longer-than-needed patch times.
What this means for you:
1. Your current Windows 10 Cumulative update packages starting next patch Tuesday (July 10, 2018) will auto-download to 64-bit ONLY. You will need to change how you are targeting this package to deploy to 64-bit machines ONLY.
2. If you are patching 32-bit machines as well, you can pre-stage for next week by downloading June's cumulative updates (32-bit only) from the package library and target your 32-bit machines. On July 10, 2018 those packages will be updated to July's 32-bit updates and continue in that fashion in the future.
What if you don't want to create a new schedule for 32-bit machines, and you liked the combined package? No worries! Download the 32-bit package and then create a nested package that contains both the 64-bit and 32-bit auto-download packages, then use the nested package in your schedule.
Additionally, we will be adding new 32-bit and 64-bit collections into the Collection Library to reflect this change.