Yea like @acid1996 said. No matter what version of XP your running you need to have IE8 installed to begin with to even hope to get updates easily. That may be why your getting long scans also.
Well there is something wrong there. (I guess you know that LOL) Are you running a modified version of XP or a clean version?
is clean/official/original Windows XP SP3. EDIT: I've tested several hours in a virtual machine doing clean installs of XP SP3 to check what thing is causing the bug, and I can say that the bug is caused by IE8, if IE8 is installed Windows Update hangs with process svchost.exe at 99% CPU usage, and Windows Update can't find any update, but if you uninstall IE8, Windows Update starts to works fine again.
There were 7 updates released on teusday . 6 for XP and 1 for internet exploder . 1 is dated january . 5 in february and one in march . The last one in march was the internet eroder fix .
303 updates seems like a lot. My XP with the Pos2009 reg hack has only 202 updates as of this month. If I add in Net and office 2003 updates my total is only 261. You sure some of those updates are not superseded?
Note: Updates are extracted directly from WindowsUpdate.log and do not use the POSRead update channel switch, which is updated from the original version of XP SP3, prior to the time of the upgraded Microsoft system update new api platform Note: I must manually update the KB958644, KB957097, KB958687 packages that through Windows Update can not receive, while I detect in the network infected Net-worm and firewalls always alerted to the attack. Private office 2003 with extension 2007 format up to 110 updates and after the end of support for WinXP/Office2003, after day 8/4/2014, next month is still releasing updates for extension 2007 The new system updates completely after Microsoft stopped supporting XP / Office 2003 updates are no longer as full as before. The XP / Office support paths are being removed by Microsoft from the system. Very well, unfortunately I deleted all .NET 1.0 - 4.0 update backups, since I do not intend to use the IIS ASP.NET platform so those updates are not required for me. Although POSReady 2009 was developed from the Windows XP platform, I do not recommend applying "WEPOS", "POSReady" updates to the Win XP Pro
FWIW, "XDOT TK" last one before MS stopped all support was May 1, 2014, then July 27, 2014. I was a tester and have all of the updates archived. Be aware that it only include what MS considered "needed" excluding non-XP updates (dotNet, etc). 143 Updates in all. He was very meticulous about replacing superseded, moreso than MS (that failed over and over). You'll note that many of the updates won't download via his script but can still be found on the Catalog. Run it, look at the output, go to MS Catalog and get the failed ones, integrate, then flip the POSReady bits. Be aware that MS also fails miserably at superseded POSReady updates and you'll get more than what you really want. Ryan-VM and Win Cert will help you clear the redundancies just by viewing their topics. All of the above posts are pretty accurate as to other places to get the updates. Trust me, you will be getting older updates via MS Updates in your "lists" that MS won't exclude. If you use WSUS Offline (get the last version supporting XP), they use MS' very own "superseded" listings and you'll get WAY more than you really need. HTH
WSU Offline v9.21 is the last version for downloading official update for WinXP (2014) , After (2016-2017..) you could still have XP security update via MsWindowsUpdate after converting your WinXP to Win PosReady via this XP_PosReady.reg file : Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\WPA\PosReady] "Installed"=dword:00000001