Perhaps its time for Xojo to use newer C++ runtime on windows ?
As I am not sure Xojo users want to be shipping security holes to their customers.
As far as I know Xojo is still using 140 on all windows Platforms except Arm where its 142 I think ?
Xojo uses the Windows Universal Runtime which gets updated through Windows Update continually.
Universal runtime 2015 (140) is out of support, and will not get more security patches. Which is exactly what this thread is about.
4 Likes
Where did you get that information from?
Microsoft lists an end of support date of Jan. 13 2032 for the redistributable version 14.44.35211
Xojo ships with v14.40.33816 (2025 r2.1) which is listed with an end of support date Jan 13. 2026
Even Windows 11 still uses that version of the runtime. Newer version are binary compatible, so I guess. Microsoft will update those to a newer version? Or don’t they?
According to the screenshot on the original post, Xojo uses 14.00 which ended July 2017 or October 2025 per your link.
1 Like
No the screenshot is from Visual Studio.
I think what Stefan is saying is that all the kits are packaged into the 14.44 bundle.
Which probably means I can safely compile against 142, 143 or 144.