WinFX Posted September 5, 2019 Posted September 5, 2019 I open the winver in my windows vista and I get the compilation 6003 instead of 6002, as if it were Microsoft that launched an unofficial service pack 3 as an update rollup or something
NojusK Posted September 5, 2019 Posted September 5, 2019 Microsoft made an update to bump the build number 1 digit higher
Vistapocalypse Posted September 5, 2019 Posted September 5, 2019 Yes, that has been observed since April 2019. This change broke Avast/AVG, but Avast later issued a micro-update that resolved the issue (not bad for a company that no longer supports Windows 6.0). One member reported an issue with VMware services in April (not sure which version). I wonder if any other legacy software was broken. Windows Update apparently does not recognize "Vista build 6003" at all. "Microsoft strongly recommends you install the latest servicing stack update (SSU) for your operating system [KB4493730] before installing the latest Rollup" beginning with April's KB4493471. Even those who do not regularly install Server 2008 updates will end up running build 6003 if they install the recommended BlueKeep patch KB4499180 (May 2019 security-only update).
Jaguarek62 Posted September 6, 2019 Posted September 6, 2019 14 hours ago, Vistapocalypse said: Yes, that has been observed since April 2019. This change broke Avast/AVG, but Avast later issued a micro-update that resolved the issue (not bad for a company that no longer supports Windows 6.0). One member reported an issue with VMware services in April (not sure which version). I wonder if any other legacy software was broken. Windows Update apparently does not recognize "Vista build 6003" at all. "Microsoft strongly recommends you install the latest servicing stack update (SSU) for your operating system [KB4493730] before installing the latest Rollup" beginning with April's KB4493471. Even those who do not regularly install Server 2008 updates will end up running build 6003 if they install the recommended BlueKeep patch KB4499180 (May 2019 security-only update). vmware workstation 12 is not affected by this at all. i'm super happy. However vmware workstation 10 has some unexpected behavior when running under vista 6003. Sometimes it runs, but the services keep crashing and bsoding the os.
erpdude8 Posted September 20, 2019 Posted September 20, 2019 On 9/5/2019 at 11:38 AM, Vistapocalypse said: "Microsoft strongly recommends you install the latest servicing stack update (SSU) for your operating system [KB4493730] before installing the latest Rollup" beginning with April's KB4493471. there is a newer servicing stack update (SSU) for Server 2008 - KB4517134. MS support article 4517134 says that this new update supersedes/replaces KB4493730. 1
erpdude8 Posted October 29, 2019 Posted October 29, 2019 (edited) On 9/19/2019 at 5:57 PM, erpdude8 said: there is a newer servicing stack update (SSU) for Server 2008 - KB4517134. MS support article 4517134 says that this new update supersedes/replaces KB4493730. gosh damn it Microsoft. it seems that KB4517134 fails to install if the KB4493730 update is not installed first as I had tested this myself this past weekend (and KB4474419 is also not installed). so that MS article 4517134 is wrong but on the other hand the MS Update Catalog site about the KB4517134 update is correct that it does not replace KB4493730 [friggin inconsistent info by MS on patch supersedence] I also found that installing the KB4474419 update alone (without installing any other updates from April 2019 & later) changes the build number from 6002 to 6003 and prevents Windows Update from looking for any Vista updates Edited October 29, 2019 by erpdude8 1
Vistapocalypse Posted October 29, 2019 Posted October 29, 2019 (edited) On 10/29/2019 at 4:49 AM, erpdude8 said: it seems that KB4517134 fails to install if the KB4493730 update is not installed first... No surprise. The reason occurred to me a month ago. On 10/29/2019 at 4:49 AM, erpdude8 said: I also found that installing the KB4474419 update alone (without installing any other updates from April 2019 & later) changes the build number from 6002 to 6003 and prevents Windows Update from looking for any Vista updates No surprise either. I am not aware of any advantage in installing KB4474419 on Vista. The update may be necessary for Server 2008 users who want to use Windows Update until January, but Windows Update clearly knows the difference between Server 2008 and Vista. Edit: VistaLover has recently found that KB4474419 v4 makes it possible to install Windows Defender definitions. Edited November 1, 2019 by Vistapocalypse 1
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now