That's not an unreasonable expectation these days, but for Windows applications targeting a variety of Windows Operating Systems it is not trivial, especially for such a complicated product. We're moving that direction, but it'll take time, careful planning, and tradeoffs.
In the meantime, as issues are identified they are triaged and business folks make ROI type decisions in regards to whether something is released as a hotfix out of the already planned release cycle. That's where constructive feedback and engagement in the community, to communicate impact, is often helpful. In this case, we became aware of the issue just a couple of days ago. We solved it yesterday, and need to test it over the next few days on various environments and setups. We could get it out before Jan 6th, but the tradeoff would probably be delaying that release.. which contains dozens of other fixes and features. But again, that's a business decision spread across multiple people, not just me - hence why I usually give an approximate date.