sdfox7

Beta channel has been updated to 26.0.0.115, and is confirmed working with Google Chrome on Windows XP. https://fpdownload.macromedia.com/pub/labs/flashruntimes/flashplayer/install_flash_player_ppapi.exe

I just noticed a "nuance" with K-Meleon 76: the installer complains about needing XP SP2: but the portable version works just fine on Windows 2000 without Extended Core: Installer version: here or alternate Portable version: here or alternate (requires 7Zip or WinRAR to unpack)

I ran Windows Update today out of curiosity, and noticed that the Windows 2000 Security Rollup Package (SRP) is being offered, even though it is clearly installed in the Control Panel. What gives?

Yes. I understand that websites may not want to officially support old browsers and operating systems. That being said, intentionally blocking them is silly. Block= lost advertising revenue. I support the concept of graceful degradation: W3C: Graceful degradation versus progressive enhancement

Beta channel has been updated to 26.0.0.110, and is confirmed working with Google Chrome on Windows XP. https://fpdownload.macromedia.com/pub/labs/flashruntimes/flashplayer/install_flash_player_ppapi.exe

NOTE: I originally posted this in the 2000 forum, but it would also be useful duplicated here since XP has such a large user base. As we know, most websites have artificial browser requirements for using their website. Firefox can be spoofed easily on Windows 2000 and XP. I don't recommend Chrome for spoofing, because 1) Chrome does not really work well on 2000, and 2) Chrome can only store user agent changes temporarily, while the Developer Console is open. By visiting Citibank's website with Firefox 48 (last working on Windows 2000), it says the browser is out of date and not supported. So, we go into about:config , create a string value called general.useragent.override , and make the value Mozilla/5.0 (Windows NT 5.1; rv:53.0) Gecko/20100101 Firefox/53.0 This tells the browser to report Windows XP, and Firefox 53.0. Again, we know that XP cannot really support Firefox 53. After saving, reopen Firefox and go back to Citibank's website. The outdated browser warning is gone. This proves an artificial browser warning. Also, if you visit a website to check the browser, it reports that it is Firefox 53 on XP, even though we know we are running Firefox 48 on Windows 2000. This trick will also be useful on XP, since Firefox will not be updated past version 51 going forward.

As we know, most websites have artificial browser requirements for using their website. Firefox can be spoofed easily on Windows 2000 and XP. I don't recommend Chrome for spoofing, because 1) Chrome does not really work well on 2000, and 2) Chrome can only store user agent changes temporarily, while the Developer Console is open. By visiting Citibank's website with Firefox 48 (last working on Windows 2000), it says the browser is out of date and not supported. So, we go into about:config , create a string value called general.useragent.override , and make the value Mozilla/5.0 (Windows NT 5.1; rv:53.0) Gecko/20100101 Firefox/53.0 This tells the browser to report Windows XP, and Firefox 53.0. Again, we know that XP cannot really support Firefox 53. After saving, reopen Firefox and go back to Citibank's website. The outdated browser warning is gone. This proves an artificial browser warning. Also, if you visit a website to check the browser, it reports that it is Firefox 53 on XP, even though we know we are running Firefox 48 on Windows 2000. This trick will also be useful on XP, since Firefox will not be updated past version 51 going forward.

I'd love to know why this KB4012598 update hasn't been pushed out to Automatic Updates. It seems like that would be a good idea given the scale of the infections. Back in May 2014, you will recall KB2964358 was pushed out via Automatic Updates, to patch the zero-day exploit on Internet Explorer.

Heinoganda I'd like to see this patch working on Windows 2000. Is editing the update_SP3QFE.inf all that is necessary? I would just have to figure out what entries need to be changed.

I was able to easily extract the KB4012598 using WinRAR. Only problem is, I don't know how to "read" the files.

Without delving too far into politics, this reminds me of the incident last year where the FBI reopened Clinton's email case in order to "help" her. In fact, it probably hurt her, because the email debacle had died down somewhat, and reopening the case just brought back bad memories. Similarly, it seems clear to me that Microsoft has not issued this as a goodwill patch to "help" XP users. XP remains popular, so Microsoft is just trying to make XP appear more vulnerable and discourage its use, and by issuing a new patch, it brings XP back into the news.

RVKROOTS.EXE: KB2917500 https://support.microsoft.com/en-us/help/2917500/microsoft-security-advisory-improperly-issued-digital-certificates-could-allow-spoofing or the Internet Archive if the above link ever goes down or gets deleted: https://web.archive.org/web/20131215073232/https://support.microsoft.com/kb/2917500 (direct download: https://web.archive.org/web/20131216214109/http://download.microsoft.com/download/0/E/6/0E60F1EB-4E0A-4D3A-B4D1-20D9D405499A/rvkroots.exe) IMAPI_XP_SRV2003_x86.EXE: KB952011 The original page is dead, so you'll have to use the Internet Archive: https://web.archive.org/web/20121111064508/http://www.microsoft.com/en-us/download/details.aspx?id=19622 (direct download: https://web.archive.org/web/20121111064508/http://download.microsoft.com/download/4/D/C/4DC0907E-38FF-4CF6-A155-B45C4EF39C35/IMAPI_XP_SRV2003_x86.exe)

Due to a change in the backend of Windows Update, the Windows Update functionality built-in Internet Explorer no longer works. I don't know if this is temporary or permanent, but discovered it this morning on Windows XP. I have confirmed the situation is the same with Windows 2000. http://windowsupdate.microsoft.com no longer works: You must now use the legacy v6 site, which does and always has worked: http://www.update.microsoft.com/windowsupdate/v6/default.aspx?ln=en-us

JodyT The built-in http://windowsupdate.microsoft.com/ functionality in Internet Explorer is currently not working (and may never again, only Microsoft knows this!) I wonder if that got turned off last month, along with the end of Vista support. To regain access to Windows Update, use the legacy v6 version of the site, it still works flawlessly, just as it always has! http://www.update.microsoft.com/windowsupdate/v6/default.aspx?ln=en-us

JodyT I'm not sure what is causing your Firefox issues. I'm not having any issues with Firefox ESR 52.1.1. The update is also available manually from the Windows Update Catalog, using Google Chrome 49.0.2623.112. I have to admit, the catalog is slower than molasses! http://www.catalog.update.microsoft.com/Search.aspx?q=kb4012598

I went to Windows Update to see if this update was available, and actually can't access Windows Update. Can anyone confirm if WU still works? I disabled SSL 3.0 because most sites don't work with it due to POODLE.

"The code to support the Adobe Primetime CDM was removed from gecko in bug 1329543 in Firefox 53." --> Stop serving Adobe CDM to Firefox 52 and higher: https://bugzilla.mozilla.org/show_bug.cgi?id=1337121#c1 If PrimeTime CDM is still working in Firefox 52, it probably won't be working in Firefox 53. Which is [probably] fine, since XP can't officially run Firefox 53 anyway. --> Remove Adobe Primetime supporting code: https://bugzilla.mozilla.org/show_bug.cgi?id=1329543

Hi all, I just got a reply over at Adobe, and we are back in business with the Google Chrome PepperFlash PPAPI on Windows XP. The latest stable is version 25.0.0.171, and the latest beta is 26.0.0.102. Both work on XP. Sometimes you just have to ask nicely, and people will be willing to help you out. https://forums.adobe.com/message/9507336#9507336

The latest update a few minutes ago re: PepperFlash 26.x (https://forums.adobe.com/message/9498543#9498543):

Heinoganda Beta 26.0.0.94 was posted yesterday, but was digitally signed April 29, well before I discovered the issue. I am almost certain that the issue will be fixed in the final shipping version.

Today, at 2:56 PST, our bug has an official number: FP-4187926. Now we patiently wait until Adobe fixes the issue in a new revision. My goal would be by the time the non-beta final release hits Patch Tuesday, May 9. https://forums.adobe.com/message/9494097#9494097

Send me the exact model number, I bet I can find those drivers for you. I am very resourceful! Usually there is a specific model identifier. As I said above, I own an generic "HP 15", but my model identifier is X7T78UA / 15-BA009DX: https://support.hp.com/us-en/product/HP-15-Notebook-PC-series/10862317/model/13386205/document/c05281438/. (Again, as I said above) I used a workaround to get the Windows 7 drivers since HP only provides Windows 10 drivers.

Adobe employee M Vargas was able to reproduce our issue today, and has opened an internal bug report to get this bug fixed. Hopefully this issue will be resolved. Response 22: 22. Re: "Couldn't Load Plugin": New Beta 26.0.0.89 PPAPI does not work in Chrome, Windows XP

Heinoganda I can see you've been tracking the discussion over on the Adobe forums. Yes, I discovered that later in the discussion. However, simply renaming the beta 26 file to pepflashplayer.dll is not allowing the plugin to function. It normally does, and always has. One of the Adobe staff will access to an XP machine tomorrow, according to his reply.

Also does not work with SlimJet, just tested. It's clearly a PepperFlash problem, AKA an Adobe problem, not limited to just Chrome. It doesn't work on any Chromium-based browser.