Discussion in 'Application Software' started by abbodi1406, Mar 9, 2018.
2022 not a typo? So it went from "2015-2019" to "2015-2022"?
You mean it should be 2021?
Bit strange ........ 2019 is now renamed to 2022 ? ........ Its still xxx140.dll and 14.30.30401.0
2022 is upgrade for 2019 which is upgrade for 2017 that is upgrade for 2015
Hey, don't you bring logic and crap into this! (guess it's normal on how they do things...)
Hello, will you be updating addons?
Thank you . That is self evident . What i was trying to point out is ---- >
2010 is xxx100.dll
2012 is xxx110.dll
2013 is xxx120.dll
2019 is xxx140.dll ....... and so is 2022
You need to login to view this posts content.
What I never understood is why MS refuses integrate those (small by today standards) components straight in the ISO images (and CUs), given they are needed by 95% of the users.
Do you have a reasonable explanation for that?
They are afraid of being accused to monopolize their MSVC compiler
maybe Raymond Chen (oldnewthing) explained it some time ago
So they are not ashamed to bundle .net things, Hyper-V, Defender, Edge and so on to fight Oracle, VMware, Symantec, Mcafee, Google, Mozilla, Opera...
But are too timid to include a few stupid dlls ?
Incredible, very likely the right explanation, but still incredible
Please answer, will you update your add-ons on the wincert website?
In few hours
Compare for what? 30040 has more fixes?
I want to ask which version is better. In terms of version 14.29.30130.2 is larger sequence number. But about the release date it is after 14.29.30040.0. And the size is also smaller than 14.29.30040.0. What I'm asking is which version is better.