One Last Update For Internet Explorer 8.0 on XP

Microsoft decided to release One Last Update For Internet Explorer 8.0 for Windows XP on the 30th April 2014 after officially pulling the plug on the 8th of April 2014.

The browser update was released right across the board for XP including the embedded IE6  built into XP and also for the IE7 and IE8 updated browsers on both x86 and x64 Xp systems.

Although oddly the KB search on the update catalogue site  provides No results, the files where still on the microsoft download site.

They where named as follows

WindowsXP-KB2964358-x86-custom-ENU.exe (for the onboard IE 6)
IE7-WindowsXP-KB2964358-x86-custom-ENU.exe
IE8-WindowsXP-KB2964358-x86-custom-ENU.exe

WindowsServer2003-KB2964358-x64-ENU.exe (for the onboard IE 6)
IE7-WindowsServer2003-KB2964358-x64-ENU.exe
IE8-WindowsServer2003.WindowsXP-2964358-x64-ENU.exe


Updated 17th January 2017:

WARNING:

For the genuine none PosReady users i hate to say it but "Windows Update" along with "Microsoft Update" and the windows "Auto Update" no longer offer users the KB2964358 update.

Also the most modern Cumulative Security Update for Internet Explorer 8 Windows XP   they now offer users is KB2879017, which is oddly dated 23rd September 2013.

That's a far cry from even KB2909210 released on the 10th February 2014, one could say "yeah but you also get KB2632503 and KB2510531" but lets take a closer look at what they both really are and remind our selves just.. what they where.

KB2632503
IE8-WindowsXP-KB2632503-x86-ENU.exe, well this thing replaced KB976662 which in turn was also replaced by KB2510531... bah humbug... All confusion aside if i was to just name something people would remember and suddenly you realise its been missing a while.

What if i renamed IE8-WindowsXP-KB2632503-x86-ENU.exe
                         Into      WindowsXP-KB2632503-JS58-x86-ENU.exe

see that JS58? and suddenly its gone from kinda like this...

Description: Install this update to improve Internet Explorer 8's JSON interoperability in conformance with the new ECMAScript, fifth edition standard. After you install this item, you may have to restart your computer. (even that lacks the old term JScript)

Into

Description: Install this update to resolve issues in Windows. For a complete listing of the issues that are included in this update, see the associated Microsoft Knowledge Base article for more information. After you install this item, you may have to restart your computer. 

 

So what about this one ?

KB2510531
IE8-WindowsXP-KB2510531-x86-ENU.exe
Just what's under the hood of this one ?
Well do you remember getting another update every month along with JScript?  Only this one was for ActiveX Killbits?  well that's what it is. (and this things dated March 2011)

Doesn't it make you wonder what ever happened to the CAPICOM-KB931906

Description: This update resolves a security vulnerability in the redistributable component CAPICOM (versions prior to 2.1.0.2) which could result in remote code execution.

So if your updating a bog standard XP online then your missing at the very least, KB2909210, KB931906, KB931906 and KB2964358. Its no wonder KB2925418 got pulled by what people are describing but that's just the last one (that's the March 2014 Cumulative Security Update for Internet Explorer 8, 9 & 10)

If we where to talk "Conspiracies" and say (just for imaginative example) That between October 2013 and April 2014.. a company leased the telemetry code and fed it into users machines to gather stats for windows 10 and also this idea of users essentially "Torrenting Updates with windows 10" to save a company a load of bandwidth...

Then the lease runs out, so in turn, any updates featuring that code get pulled. Kinda looks like that  MS good deed of.. "here people you can have IE8-WindowsXP-KB2964358-x86-custom-ENU.exe"  but then  "advising us" its best to install it right after a roll up.. conveniently being IE8-WindowsXP-KB2925418-x86-ENU.exe seems more like a slap in our face than a good deed.

So users formatting, partition restoring and updating

Your using a JScript from the 4th of March 2011
Your using ActiveX Killabits from 28th October 2011
and a IE Cumulative Security Update from the 23rd of October 2013

and yet support ended 8th April 2014? and one assumes your fully updated to that 8th of April? because it lets you get the downloads...?

False sense of security is even more false than one can imagine...
i get the moaning that some updates were telemetry fixes.. but theirs no way from March 2011, Oct 2013 to April 2014 their wasn't major security or other bugs fixed.

When i set up an XP x64 SP2 (with IE 8) I get offered the same set of KB Numbers.

So remember, although support ended in April 2014, the browsers patch rate is October 2013, one runtimes from March 2011 and the others from October 2011... Hell... does this mean they've been officially data mining info since march 2011, escalated it in october 2011 and went in for the kill in 2013?... April 30th 2014 looked like someone was scooping up the dregs before pulling the plug.

And people wonder why i maintain this blog...

So if it has been safe using just these 3
IE8-WindowsXP-KB2510531-x86-ENU.exe
IE8-WindowsXP-KB2632503-x86-ENU.exe
IE8-WindowsXP-KB2879017-x86-ENU.exe
Since october, then just wtf was with the next 5 cumulative updates....

The strange thing is the April 2014 Update ISO listed here points to a dead page here and yet the file listed here that link currently works. Notice how when searching on the DL site it has the word FREE next to it here, one wonders when a BASKET is going to appear with a £ or $ sign ?  
Meanwhile everyone with Windows 10 is Seeding Updates by default on users own bandwidth... just like wtf...



Updated April 2017:

WARNING:

Microsoft have released another out of life cycle patch for Windows XP users, however it only appears available for XP-SP3 with IE 8

The file names are
IE8-WindowsXP-KB4018271-x86-custom-ENU.exe
IE8-WindowsXP-KB4018271-x64-custom-ENU.exe

They didn't release one for the IE6 or IE7.  Nor will KB4018271-x86  Install on Windows Fundamentals for Legacy PC's.  Do NOT post ini file hacks in the comments for installing KB4018271.  Keep the blog Clean and LEGAL!

Windows XP Service Pack 4

These are my random thoughts on what I would essentially call a Fan Made Service Pack 4 for Windows XP. Some hail it as epic, some slant it as untrustworthy... Let me know what you think of it in the comments and i shall give you my opinions on it as follows....

First off, it's a great idea and im sure it took a lot of work but it lacks a lot of legalities, the permission to use the reg tweaks is great but the implementation of them and the PosReady fix along with microsoft stuff released After April 2014 makes the pack illegal.

It would of been nice to have a semi legal release that just caps off the official life cycle of the OS. The removal of the need to validate media player 11 also causes legal issues with using it.

The reg tweaks should be a Folder under Admin tools with a Reg key for ON and OFF regarding each feature. The packs not sterile because it wont suit all users or network environments unless the user is pc savi to change these settings.

The fact its had the PosReady patch slipped in & yet it hasn't had the Download ActiveX stuff put in for "Microsoft Update" seams also really stupid to only have Windows Update included. If your going to try and integrate .Net 3.5 then clearly windows should be using Microsoft Update (update windows AND OTHER microsoft products) Such as Microsoft .NET

.Net 3.5 included but yet no PowerToys Included ?
why no TweakUI or even AutoRuns placed within the Program Files dir?
IE 8 and yet no Silverlight ?

I see 37 updates on windows update as of today (for PosReady) You realise a system will automatically break the law if auto updates are enabled. It's such a shame because this pack could of truly been an SP4 and then an optional version. Its a lot easier to End a Pack than make one that still essentially needs more. It also should of blocked out MSE and hid it on windows update to avoid offering users to install an AV that actually no longer works.. (win update offers the newer MSE which is clearly dead and an older version is needed) It doesn't even hide the update for the End of support notice, were was the imagination once this pack began?

Microsoft .NET 4.0 is offered on windows update (not .NET 4.5.2) this in turn (after installing 4.0) will bring an unleash a mass of 40+ updates relating to .Net 1.1, 2.0, 3.0, 3.5 and 4.0 when a merged reg key for 4.0 could of had it offer 4.5.2 and cut down on a stack of the follow on updates.

I have tested the SP4 on Xp Home OEM, XP Professional (Corporate VLK) both harddrive tower based and i have tested it on a Windows 7 Professional running the Virtual XP-MODE with the XP Professional OEM, same results on all 3, it works. XPS Viewer, yet no taskkill.exe added to home. I clocked qefcheck is in and yet no permanent copy of qchain.

I mean if a packs going to break laws and step over the line, step off the kerb to do that bit more, why just tip toe, why that iddy didy bit after what must of been masses of work? to overlook the small easy tasks ? DirectX isn't anywhere near what it should be neither.  What about the patched UX theme dll, why was it not included?

This SP4.. It's such a cool idea and yet a waste of time using it. Even for offline gamers, the Dx Online updater tool is going to offer more DX components (once certain games are installed) at some stage it wont be safe at all to hook XP to the web to download something. Things change over the years.

It just leaves a lot to be desired really in what it could have been capable of. I will be sticking to my own BAT scripts to update a pre-installed XP environment offline and my own bat scripts when slipstreaming separate updates into a custom OEM replacement image for servicing systems.

A fantastic idea with to many ideas above its station and not enough imagination.
frankly this comes across more like a "Roll Up" than a XP farewell finale, frankly he fkd this up.

You can download it from MajorGeeks, just google search  WindowsXP-USP4-v3.1b-x86-ENU.exe

If your looking to keep your XP legal (but having problems browsing microsoft servers with IE 8.0) the check  out the little archive were making here
ber in mind that Microsoft Update and Windows Update (the ActiveX Control certificate is Signed & Dated) that Root Certificate will expire one day.. so the page here will be important one day im sure.

Microsoft Security Essentials 4.5.216.0 Windows XP Red Box Solution

Ok ive been asked this over and over again so i figured id share a little info on this
so your still using xp as PosReady but the MSE pop up is driving you mad?

So.. how about this...

1) you have  4.5.216.0 installed and its Red and the pop up box is driving you mad
Solution, download the one thats on the MS site here OR from filehippo  here then right click the exe and extract it (7zip or winrar will let you do that)  then go into the   x86   folder  and  right click on the file called  epp.msi   and select extract to here,    now open the folder to microsoft security essentials (so its ready to access, normally C:\Program files\Microsoft security client)  now go back in the folder you extracted to, look for a file called    msseces.exe    and right click on it and select CUT   now right click on your task bar and select task manager.. end task on the process called    msseces.exe  then right click on the program files version of the folder & paste (replacing the file) and then re-open MSE from your start menu.
Notice when you go to the little drop down you still have the latest scan engine, malware engine and program version (so windows update WONT downgrade you)  ;)


2) you have the version thats green or red, but is older than 4.5.216.0
Solution, first (if your outdated MSE is still green ut an older scan engine) Make a copy of the file called  msseces.exe because you know that works :)   If its not green, follow the steps above to get access to a clean & green  msseces.exe
 then download Microsoft Security Essentials 4.5.216.0 (if you google good enough you'll find it)
Once you have installed  4.5.216.0, do the end task and put the  older  msseces.exe in the folder (as descriptive in the 1st option above.  And again as above, check the about to see its the new version and scan engine.. yet green..

Last but not least.. the REF database AKA viral Pattern file update link is Here 

also note...
even with the red box, you are still protected if it says its "ON" and its "Up To Date" but i know the green monopoly house is more soothing

remove pop up from MSE

October 2006 Update Rollup for Windows XP Media Center Edition 2005 (KB925766)

Original Page Graphics

October 2006 Update Rollup for Windows XP Media Center Edition 2005 (KB925766)

Download: Here
Mirror Link: Here

Overview

---

Microsoft has released Update Rollup KB925766. This update is intended for systems running Update Rollup 2 for Microsoft Windows XP Media Center Edition 2005.

This update rollup is cumulative and supersedes the following updates:
 (supersedes means you don't need the 4 updates below as KB925766 replaces them)

• KB908250 - October 2005 Update Rollup for Windows XP Media Center Edition 2005
• KB912067 - January 2006 Update Rollup for Windows XP Media Center Edition 2005
• KB914548 - April 2006 Update Rollup for Windows XP Media Center Edition 2005
• KB919803 - July 2006 Update Rollup for Windows XP Media Center Edition 2005

For more information about this update, read Microsoft Knowledge Base Article 925766. (This site may be in English.)

System Requirements!

---

• Supported Operating Systems:Windows XP Media Center Edition with

• Update Rollup 2 for Microsoft Windows XP Media Center Edition 2005
  (KB900325)

How Can You Tell What Your Windows XP CD Really Is?

I'm often asked this question of

i have a windows xp cd but how do i tell what the disk is?
or, I know its xp professional or xp home but what service pack is it?

Maybe your looking to Slipstream it, or just Identify the right type of product key or oem for it and here are some clues to Identify a Windows XP Product Source (by hand & eyes)

To Identify The Windows XP Service Pack Level?
-------------------------------------------------------------------------------
Sadly the readme doesn't give any information regarding the disks "Service Pack Level"
But you can Browse the disk root and look for the .SP? file.

Windows XP Home (with NO service pack) Example

Note This Lacks An SP File

 Windows XP Home (with service pack 1) Example

This Contains An SP File

 Windows XP Home (with service pack 2) Example

This Contains An SP File

As you can see, the disks with a service pack built in contain an SP file as its extension and the number marks its SP level.

It is rumoured that if you have ALL the SP files in the root of the install disk that an SP3 disk can be used to recover an SP0, SP1, SP1a, SP2 and SP3 machines initial installation. I have yet to have to test this theory as i fix them without having to wipe them, but i would assume its in relation to the setup.exe having access to ALL those files.

So your disk will either have a file Ending in .SP1, .SP2 .SP3 or it wont have any file with a .SP*

Note you probably wont have ALL the files our images show, but you hopefully will have at least 1 specific one we circle in at least 1 image (if not, go to control panel, folder options, view) and turn On show hidden files and turn Off hide extensions for known file types and then  re-browse the Root of the Disc again to make sure your seeing all the files.

How Do I Define Between Xp Home and Xp Professional ?
-------------------------------------------------------------------------------

This will require browsing a little deeper into the disks i386 folder and looking for 2 specific files right next to each other
(Windows XP Home) doesn't come with taskkill.exe OR tasklist.exe

Remember though, as we are browsing an UN-installed source!
we are looking for   taskkill.ex_  and  tasklist.ex_
Until setup expands files, their extensions often end in an underscore _


How Do I Define Between OEM or VLK ?
-------------------------------------------------------------------------------

If you have taskkill.ex_ then your certainly running a version of Professional at its core, But the dressing around this could not simply just be XP Professional or XP Corporate, It could also be Windows XP Media Centre 2002 or Windows XP Media Centre 2005, often known as MCE Edition IF it consists of 2 CD's or a Single DVD.

If you have located both taskkill.ex_ and tasklist.ex_   in the disc/iso  i386 folder
CD PATH :\i386\TASKKILL.EX_
CD PATH :\i386\TASKLIST.EX_

 then the next thing to look for is to see if it has OEM information here
CD PATH :\i386\SETUPP.INI

Open that  .INI file  "with notepad" and you'll see something similar to this PID

Pid=55277OEM

 If it says OEM, then Corporate comes off the list (as that is VLK, not OEM)
In turn this source also contains the four OEM files and possibly branding information & decals.

How Do I No If My XP Professional OEM Is Really Just MCE
-------------------------------------------------------------------------------

If its a Single CD, then its actually just windows XP Professional (oem)
What happens is, if you install XP Professional "using a media centre product key" then after windows is installed it asks you for CD 2 which features the MCE content.

SO, if you only have one CD, you'd have to use a Pro OEM or Pro Retail / Sticker key
IF its a DVD (and you know the source is clean) as in, its to big for a CD but clean, then its the full MCE.    by clean.. I mean.. no NFO files, driver packs, no links to sites, no WAG cracks and serial text files. Just an xp source that is two big for a single  700MB CD and you have a DVD or ISO over 800mb of data.


Now you should be able to work out just what a back up x86 XP Disc really is under the hood

How to tell what version an x64 Windows XP Disk Is?
pretty much the same only your looking in the AMD64 folder rather than the i386, also remember x64 XP had NO service pack 3... Nor can you get an SP0 disk, x64 First Release was SP1a really

Be it x86 or x64, if its an OEM disc it'll also contain these files 4 OEM files regardless of any other branding OEM's folders...

the FOUR files within the i386 folder (on OEM discs) you can change these 4 files for the specific OEM machine it'll be installed on.

OEMBIOS.CA_
OEMBIOS.SI_
OEMBIOS.DA_
OEMBIOS.BI_

when Expanded (not renamed, must be expanded by a command prompt)
they are  .cat   .sig  .bin and .dat
which can be scanned by various bios and oem tools to even identify the manufacture.

expand example (AKA Decompress)

expand d:\i386\OEMBIOS.CA_ c:\BiosTest\SetOne /y

expand d:\i386\OEMBIOS.SI_ c:\BiosTest\SetOne /y

expand d:\i386\OEMBIOS.DA_ c:\BiosTest\SetOne /y

expand d:\i386\OEMBIOS.BI_ c:\BiosTest\SetOne /y  

 

Some Random DISC ID's
-------------------------------------------------------------------------------
Some of these are the ISO name and Disc Label

x86 {32bit Versions}
x14-92386.iso = GRTMHKFPP_EN Home K (SP3) x86 EN-US Retail / OEM Pid=76477000
x14-92388.iso = GRTMHKNFPP_EN Home KN (SP3) x86 EN-US Retail / OEM Pid=76477000
x14-92393.iso = GRTMHRMFPP_EN Home N (SP3) x86 EN-US Retail / OEM Pid=76477000
x14-_OEM_.iso = GRTMHOEM_EN Home (SP3) x86 EN-US OEM Pid=76477OEM
x14-92413.iso = GRTMHFPP_EN Home (SP3) x86 EN-US Retail / OEM Pid=76477000
x14-92430.iso = GRTMPKFPP_EN PRO K (SP3) x86 EN-US Retail / OEM Pid=76487000
x14-92432.iso = GRTMPKNFPP_EN PRO KN SP3) x86 EN-US Retail / OEM Pid=76487000
x14-78118.iso = GRTMPRMVOL_EN PRO N (SP3) x86 EN-US VLK Pid=76487270
x14-92445.iso = GRTMPRMFPP_EN PRO N (SP3) x86 EN-US Retail / OEM Pid=76487000
x14-73974.iso = GRTMPVOL_EN PRO (SP3) x86 EN-US VLK Pid=76487270
x14-_OEM.iso = GRTMPOEM_EN PRO (SP3) x86 EN-US OEM Pid=76487OEM
x14-80428.iso = GRTMPFPP_EN PRO (SP3) x86 EN-US Retail / OEM Pid=76487000
x14-74003.iso = GRTMPVOL_PL PRO (SP3) x86 PL-PL  VLK Pid=????
DELL_XP_HOME_SP3_20080911.iso x86 EN-US OEM / Branded Pid=76477OEM
DELL_XP_HOME_SP3_20090829.iso x86 EN-US OEM / Branded Pid=76477OEM
DELL_XP_PRO_SP3_20080819.iso x86 EN-US OEM / Branded Pid=76487OEM
DELL_XP_PRO_SP3_20090819.iso EN-US OEM / Branded Pid=76487OEM
MRMPFPP_EN.iso Media Center Edition 2005 and XP Tablet CD1 EN-US Retail Pid=76487000
MRMSD2_EN.iso Media Center Edition 2005 and XP Tablet CD2 EN-US Retail
MRMPINT_EN.iso MCE 2005 and XP Tablet CD1 and 2  EN-US Retail Pid=76487000
XPSP2.9IN1.EN.iso = Home, PRO, CORP, MCE EN-US Retail / OEM / VLK Pid=???????
XPSP3.9IN1.EN.iso = Home, PRO, CORP, MCE EN-US Retail / OEM / VLK Pid=???????


x64 {64bit Versions}
ARMPXVOL_EN.iso = XP PRO x64 (no service pack)  EN-US VLK Pid=76588270
CRMPXVOL_EN.iso = XP PPRO x64 (SP2)  EN-US VLK Pid=76588270
CRMPXFPP_EN.iso = XP PRO x64 (SP2) EN-US Retail / OEM Pid=76588000
CRMPXOEM_EN.iso = XP PPRO x64 (SP2)  EN-US OEM Pid=76588OEM
DELL_X64_X64_SP2.iso XP PRO x64 (SP2)  EN-US OEM / Branded Pid=76588OEM
 
Windows XP Serial Number Basics
------------------------------------------------------------------------------- 

Will x86 (32bit) Serial Numbers / Product Keys work on x64 (64bit) = NO
 only vista, 7, 8, 8.1 & 10 product keys span across architectures

Will a basic SP0 serial work on an SP2 Disk?, Normally NO, you see SP0 was entitled to SP1 and SP1a,  but  SP2 brought many new features (although an SP0 Install can often upgrade to SP2 and sometimes SP3 via windows update) Some actual SP0 keys wont allow SP3 or MP11.  An SP2 key seams the most useful because it'll work on SP2 & SP3 discs and some folks prefer SP2 for DRM manipulation.

Will my SP0, SP1, SP1a, SP2 or SP3 key work on a disk if i slip stream it?
If your source disk is what your key is for then yes, IE, You can slip an SP0 all the way to SP3 and use your SP0 key.. you Can Not use an SP2 or SP3 key just because you turned an sp0, sp1 or sp1a cd into sp2 or sp3..

Post Last Updated April 8th 2014