16 votesMarcus Gormsen commented
You cannot though Don,
That release date is based on the Vendor's release date. If Kace takes a few days to receive the patch, then uses the Vendor's release date, it could bridge the gap of what your test PCs received, but then still make it to production. We just had this happen last month. Our release date on our patch label was set to 7/16/2019. We patched our test group that night. Well Google Chrome had an update come out on 7/15/2019 that didn't reach Kace until 7/17/2019, but since the Vendor Release Date was prior to 7/16/2019, all of our production PCs received the untested patch a week later.
Thank you for your request. We are publishing information in a Knowledge Base article as Microsoft’s updates/patching practices evolve:
Thank you for your input. Offering both 32 and 64 bit clients would double our Windows agent QA testing time and we are sensitive to the impact of extending test times as it impacts our ability to release full-featured updates at our desired pace. A surprisingly large amount of our customers still need 32bit support today. We are going to continue monitoring this closely to determine the best time to drop 32 bit support (of course older versions of the agent would still be available once we moved to 64 bit). In the meantime, it would be helpful to know specifically what difficulties a 32bit client is causing so we might consider work-arounds in parallel with the 64bit only decision.
We are investigating this and encourage others to voteMarcus Gormsen commented
I agree with Jeff, we need a way to upgrade the Windows 10 Versions.