Leaderboard

Well, it's that time of the month again, and only a year away from Vista's true EoL (or EoS, as @dencorso has said about XP, though not sure if it applies to Vista as well)... And as usual, I recommend waiting at least a week before any of these, because we never know, if Microsoft won't pull any of these updates and upload it (or even more than one of them) again in a couple days. So, without further ado, let's finally get to what you all have come here for: KB4480968 - Security Monthly Quality Rollup for Windows Server 2008 - 32-bit | 64-bit KB4480957 - Security Only Quality Update for Windows Server 2008 - 32-bit | 64-bit KB4480965 - Cumulative Security Update for Internet Explorer 9 for Windows Server 2008 SP2 - 32-bit | 64-bit KB4481486 - Security and Quality Rollup for .NET Framework 2.0, 3.0, 4.5.2, 4.6/4.6.1 for Windows Server 2008 SP2 - 32-bit and 64-bit update catalog link KB4480062 - Security and Quality Rollup for .NET Framework 2.0, 3.0 for Windows Server 2008 SP2 - 32-bit | 64-bit KB4480059 - Security and Quality Rollup for .NET Framework 4.5.2 for Windows Server 2008 SP2 - 32-bit | 64-bit KB4480055 - Security and Quality Rollup for .NET Framework 4.6/4.6.1 for Windows Server 2008 SP2 - 32-bit | 64-bit KB4481487 - Security Only Update for .NET Framework 2.0, 3.0, 4.5.2, 4.6/4.6.1 for Windows Server 2008 SP2 - 32-bit and 64-bit MS update catalog link KB4480084 - Security Only Update for .NET Framework 2.0, 3.0 for Windows Server 2008 - 32-bit | 64-bit KB4480076 - Security Only Update for .NET Framework 4.5.2 for Windows Server 2008 SP2 - 32-bit | 64-bit KB4480072 - Security Only Update for .NET Framework 4.6/4.6.1 for Windows Server 2008 SP2 - 32-bit | 64-bit Extra/optional update: KB4487354 - Update for Windows Server 2008 SP2 for x84/x64 based Systems - 32-bit | 64-bit I think that's all for this month (for now at least), except 2 updates for Itanium based systems only, but I don't think it's necessary to post them here. I also hope you all will like this new way of posting lists of updates which are available for Vista, and which I will try to use from now on. I also apologize for no direct links to bigger .net rollups but direct downloads of those are sadly unavailable. Added KB4487354, thanks to @mike_shupp for finding it.

Direct links for January 2019 updates: WES09/POSReady 2009 update (English only), IE8 cumulative security update (English), .NET Framework 2.0 SP2 and .NET Framework 4.0 updates (international), Office 2003 SP3 security update http://download.windowsupdate.com/c/msdownload/update/software/secu/2018/12/windowsxp-kb4481275-x86-embedded-enu_5160cf8226e525f266f39e7279ce39e6176cece9.exe http://download.windowsupdate.com/d/msdownload/update/software/secu/2019/01/ie8-windowsxp-kb4480965-x86-embedded-enu_469b647b191dac942734a9a64e05bc27321e79a5.exe http://download.windowsupdate.com/d/csa/csa/secu/2019/01/NDP20SP2-KB4480087-x86_010990466ABCF053D7164DFFE1BC0812B5A86B96.exe http://download.windowsupdate.com/d/msdownload/update/software/secu/2019/01/NDP40-KB4480077-x86_05E61336A238A90796BCDA78D13F0982075F2A2E.exe http://download.microsoft.com/download/0/5/5/055B2A2C-2102-40D1-B0C7-A0BF29DEA79B/office2003-KB4461635-FullFile-ENU.exe P.S. Windows Embedded Standard 2009 (WES09) support has ended. WES registry keys should be removed. There should be only POSReady key left from now on.

Release channel of Adobe Flash Player has been updated today: 32.0.0.114 (tested/working on Windows XP SP3 and XP x64 SP2) Internet Explorer ActiveX: http://fpdownload.adobe.com/get/flashplayer/pdc/32.0.0.114/install_flash_player_ax.exe Mozilla Firefox NPAPI (also for Opera Presto/Google Chrome 44 and earlier): http://fpdownload.adobe.com/get/flashplayer/pdc/32.0.0.114/install_flash_player.exe Google Chrome 45 through 49 PPAPI: http://fpdownload.adobe.com/get/flashplayer/pdc/32.0.0.114/install_flash_player_ppapi.exe

If your time and date is fine (check that first) It's likely that IE is too old to have proper security ciphers to connect to the mozilla website, try downloading the installer directly. (EN-US) http://ftp.mozilla.org/pub/firefox/releases/52.9.0esr/win32/en-US/Firefox Setup 52.9.0esr.exe for other countries/languages, go here: http://ftp.mozilla.org/pub/firefox/releases/52.9.0esr/win32/ and select your language-country code and download the appropriate installer inside. You can either do this directly from the XP system or you can save the installer to a flash drive from another PC

Well, Bill told me it's all part of his master plan. By the way, he's coming back. He, like all of us, has finally had enough of the current administration's ridiculousness. He told me all of this in the strictest confidence, (he was a little drunk at the time), but I can trust you guys, right? Cheers and Regards

I'm using (hand-installed) 192 quite happily, ATM. Why shouldn't I?

Hmmm. Let me see. Under Windows everyone uses Chrome or Chorome/Chromium engine based browser. (exception made for those insisting on using Mozilla Firefox, all in all a small amount of people [1]). Noone uses Edge. Whatever undocumented features of Edge (if any ) *somehow* facilitating MS operations is lost. The whole plan on world domination and stuff through the Windows 10 pushing is likely failing (besides the total defeat on phones) because even those that for one reason or the other are using Windows 10 ar not using Edge and nowadays a large part of the time spent on a computer is through its browser. Idea , let's make a new browser similar to or nearly identical to Chrome (possibly while keeping the same *whatever* undocumented features we like to have). Wait, this would mean actually writing lots of code, why not using the actual same engine as Chrome? jaclaz [1] and with the exception of a few old dinosaurs like yours truly that still use good ol' browsers (with some limitations).

What is Microsoft's reasoning for this? Better yet, why does the chromium engine have to be used for everything? Do people not remember what happened the last time a certain browser had too much market share?

@Tamris It's totally fine , I never implied you should have frequented the rest of the XP forums; I just posted that piece of info to let people here (in the Vista subforum) know how "I" was informed of the existence of the unofficial 2.49.5 builds; I hope it's clear now...

Windows 10: How to burn CDs and DVDs And if you install OpenShell, you get a replacement start menu, which presents "This PC" option right after you open it (well, actually, the very first time you try to open it, its Settings window opens). But still, the fastest way to open File Explorer is using the yellow folder icon in the taskbar (assuming it wasn't removed for any reason). Traditionally, File Explorer used to be called just Explorer in the old days. Then at one point it was renamed to File Explorer. The confusion stems from the fact that the most common way to open it is not through the shortcut that just points to the File Explorer program, but through the special shortcut (that's my own term for simplicity sake), that opens the specific location in the File Explorer. This special shortcut had different names throughout history, such as "My Computer", "Computer" and "This PC". But it always pointed to the same location where you can access all storage media connected to the computer. The only difference besides the name, they added some commonly used folders in newer Windows versions in the same place where you see all storage media. BTW, I don't know how good it is, but there's this book called Windows 10 for Dummies. Perhaps it has some useful answers.

Skype seems dropping out v7 support. I hex-edited Russian's unpacked skype.exe 6.16 and changed version to 8.34 and it is able to login again.

New build of basilisk/UXP for XP! Test binary: Win32 https://o.rths.cf/basilisk/basilisk52-g4.1.win32-git-20190105-7fcb7f544-xpmod.7z Win64 https://o.rths.cf/basilisk/basilisk52-g4.1.win64-git-20190105-7fcb7f544-xpmod.7z diff: https://o.rths.cf/basilisk/UXP-xp-gitdiff-20181110.7z PM28XP build: Win32 https://o.rths.cf/palemoon/palemoon-28.3.0a1.win32-git-20190105-7fcb7f544-xpmod.7z Win64 https://o.rths.cf/palemoon/palemoon-28.3.0a1.win64-git-20190105-7fcb7f544-xpmod.7z Official repo changes since my last build: - [PALEMOON] Bug 1115369 - Use notifications instead of getViewItem for DownloadsView (a970e88a1) - [PALEMOON] Bug 1115971 - Don't fall back to the Places title for downloads without the target file name annotation (1b414c2b9) - [PALEMOON] Bug 1115972 - Don't fall back to the Places icon for downloads without the target file name annotation (8bd13f3a2) - [PALEMOON] Bug 1120429 - Remove unused code handling nodeAnnotationChanged (1eab01b24) - [PALEMOON] Bug 1115421 - Simplify download annotations handling in the Library (81265fae3) - [PALEMOON] Bug 1115983 - Keep only minimal state information in the DataItem (e666c9a8e) - [PALEMOON] Bug 1116176 - Create DownloadsHistoryDataItem and HistoryDownload objects (ac3159f02) - [PALEMOON] Bug 1115379 - Streamline DownloadsViewItemController construction and remove now unneeded identifiers (927853bde) - [PALEMOON] Bug 1117139 - Move code controlling the "download.xml" binding to a common place (f2f700514) - [PALEMOON] Bug 1117139 - Move code controlling the "download.xml" binding to a common place (downloadsViewCommon.js) (df852eca4) - [PALEMOON] Bug 1117141 - Part 1 of 2 - Bypass all the DownloadsDataItem properties (462332eee) - [PALEMOON] Bug 1117141 - Part 2 of 2 - Refactor notifications and remove the DownloadsDataItem object (d6c976bf6) - Fix typos (761b6eb25) - [PALEMOON] Bug 1127867 - Use the new back-end property to get the size of downloads asynchronously (beeede618) - [PALEMOON] Bug 1195279 - Fix typo in allDownloadsViewOverlay.js following landing of bug 1127867 (8cc3f3616) - [PALEMOON] Bug 1129896 - Part 1 of 2 - Keep cached metadata for history downloads indefinitely (0b15a2b89) - [PALEMOON] Bug 1129896 - Part 2 of 2 - Convert the shared front-end code to a JavaScript code module (551c6ff04) - [PALEMOON] Bug 1135348 - Fix about:downloads by adding missing XPCOMUtils imports (909c3ee13) - [PALEMOON] Initialize the search service asynchronously when calling 'BrowserSearch.addEngine()' (accd61429) - [FFmpeg] Use new decode API with recent FFmpeg version. (515e0794f) - [FFmpeg] Don't define AV_CODEC_ID_VPx with libavcodec 58 (68acfbb14) - Merge pull request #921 from trav90/media-work (5920c1dc6) - Avoid redefined macro warning in MediaFormatReader (7a39cd52e) - Merge pull request #922 from trav90/media-work (626d40774) - Merge pull request #920 from JustOff/PR_nsIBrowserSearchService_async_init_2 (bcf3df362) - Merge pull request #917 from janekptacijarabaci/_testBranch_pm_downloads_rewrite (78ad9498a) - Dont rely on 'this' staying alive long enough for getting favicons. (8a10092b5) - Add Comodo IS < 6.3 64-bit to the dll blocklist (517f50298) - Update UXP Coding Style guideline document (WIP) (eec3d00bb) - Update UXP Coding Style guideline document (WIP) (7a22921c2) - Update UXP Coding Style guideline document (WIP) (da0d462d6) - Use getElementBoundingRect and element.ownerGlobal in FormSubmitObserver (f543892e4) - Update HSTS preload list (483267ba9) - Make MAX_CSS_VAR_LENGTH unsigned to avoid warnings. (dfce7fa7b) - Remove proprietary constructor on AudioContext. (7fcb7f544) My changes since my last build: - update libaom to git rev c07e9d6ccf340843e8899e7da6b15a0893007bd5

v191 has several security updates -> see https://www.oracle.com/technetwork/java/javase/8u191-relnotes-5032181.html v192 has a extra new feature -> see https://www.oracle.com/technetwork/java/javase/8u192-relnotes-4479409.html With v191 you are as safe as possible, v192 is not needed. In the past there where alsways two versions, one with security updates ans one with new features. Recommended was always the lower v number to avoid problems with the new features. Only if you need the new feature go to the higher v number.

It would have been good, not just for eventual new features, but also because when a service pack is released, support is extended. Can you imagine Windows XP Service Pack 4 with official support to UEFI, GPT, USB 3.0/3.1, IE11, a new crypto.dll, many more functions in the kernel, proper DXVA2 support, official DX10 and DX11 and many other things...? It would have been a completely different story... :')