This update resets the base time to UTC+01:00." Instead, the system clock shows an incorrect base time of UTC+02:00.
Go up to July 2019 update - it's KB4507704 with note "This update was revised on August 13, 2019, to apply to Windows Embedded POSReady 2009" and explanation about fix for Morocco: "The base time for the "Morocco Standard Time" time zone in Windows did not update correctly to UTC+01:00 as expected in the Windows DST update that was installed on (KB 4501226). Go to May 2019 update - it's KB4501226 described here: As you should know, there was an update for Windows XP Embedded, but now it's removed. You should just read list of updates here: in reverse order:ġ. It's an update by downgrade described using corporate newspeak -) Well, finally I understood what MS did to KB4507704 for Windows XP Embedded. Since those 3 files are not used by IE8 they're not updated by IE8 cumulative updates, but other XP SP3 modules do use them, so it's relatively easy not to have the last browsewm.dll & shdocvw.dll in one's installation, because the updates they are in require IE6 to install, and most users had already moved on to IE8 when they were released.
It won't install on a system already having IE8 installed, but may be replaced by hand on a non-booted XP using, say, a linux-live CD to boot the machine, first in %windir%/system32/dllcache, then in %windir%/system32. The much older 2014 KB2962872-IE6 for x86 POSReady 2009 does, however, contain *non superseded* browsewm.dll v.6576, which is the last version of it ever released. As for browseui.dll, the last version ever released of it (v.7288) is in KB4025497, from 2017. The important files there are browseui.dll & shdocvw.dll (both v.6985), and the latter is the last shdocvw.dll ever released. KB3124275 IE6 *is not superseded* by later updates. The important files there are browseui.dll & shdocvw.dll (both v.6740). Well, since you asked me, here are my 2¢: KB2898785 *is superseded* by later updates. No, you can't, due to board rules and Microsoft redistributable license, but you might do a script that downloads them all from Microsoft catalog or, if worried it will die, from Wayback machine. Should work no matter if you install reg tweak first or the last, but personally I always updated registry as a late step (when all XP updates were installed, and I needed POSReady ones), so that's the only way I swear onĥ. If you're still worried, we might compare file checksums, or you might throw it to virustotal or jotti for scan.Ĥ. Microsoft might have used different certificates, it's a beeeg corpo start from running heinoganda's cert updater and if installer will not throw prompt that certificate looks invalid, you are safe. Install for sake of completeness if neededģ. I do not know if NDP20SP2-KB2932079-x86.exe was included in later cumulative updates or not, but chances that you are really vulnerable for this are near zero in home reality. You need to remove nothing, although patches 7 to 14 are not mandatory to make WU work.īTW I realised, that both my VMs installed in 2019 go away without KB2898785 - is this something included in KB3124275 IE6 Cumulative Update? also, I remember I've been starting with IE8, so that might also did the trick.Ģ.