<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - Deinstall of LO 7.0.0.3 on Win7Pro also deletes "VCRUNTIME140.dll"" href="https://bugs.documentfoundation.org/show_bug.cgi?id=135579#c3">Comment # 3</a> on <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - Deinstall of LO 7.0.0.3 on Win7Pro also deletes "VCRUNTIME140.dll"" href="https://bugs.documentfoundation.org/show_bug.cgi?id=135579">bug 135579</a> from <a class="email" href="mailto:mikekaganski@hotmail.com" title="Mike Kaganski <mikekaganski@hotmail.com>"> Mike Kaganski</a> <pre>(In reply to V Stuart Foote from <a href="show_bug.cgi?id=135579#c1">comment #1</a>) > Meanwhile MS has moved VC++ support to the consolidated "Windows 10 > Universal CRT" multi-release replacing individual VC++ runtimes (2015, 2017, > 2019) as "latest supported"[1], and as delivered via MS update mechanisms. > > @Mike, should/could we start to bundle the Universal CRT for the Windows > builds, or would that affect build infra? FTR: this was attempted in v.6.0 (if I recall correctly the version). The package by MS is an .exe that bundles MSUs and *MSIs*, which makes it impossible to install it with our MSI; the only way is to hack it to run outside of the main installation, and require another authentication request, and impossibility to be installed administratively. See also <a href="https://developercommunity.visualstudio.com/idea/412198/detect-a-windows-version-from-msi.html">https://developercommunity.visualstudio.com/idea/412198/detect-a-windows-version-from-msi.html</a> , which describes current situation in detail.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>