Muppet Hunter

Hello all I just found this topic after doing a bit of catch-up reading. Here's a few points which should answer everyone's questions. I took over the list from TommyP back in about August and about 3 months ago there was a bit of a mix-up with my sending a new list to fdv for hosting. To cut a long story short, I had gone on a trip to Holland and it was thought that I'd abandoned it when fdv and tp tried to message me. I was a bit busy for a couple of the lists and my last one was about a week late, so I could see how it looked. Mimo answered the call to do the XP list and I subsequently contacted fdv and tp just to say what happened after I saw that fdv had uploaded my list after Mimo had taken over. It was eventually decided that two lists were better than one and I think this has worked out well. Mimo has developed a nice update checker and sparked more interest to the extent that there's more discussion about what the best/latest updates are. My list could probably be considered a stable, minimal version to satisfy WU and when I took over I just tried to improve it without radically altering things. It just does the base stuff and fits with my own way of working - to just install anything that isn't slipstreamable (eg dotnetfx) after Windows gets installed. Like a lot of others who use hfslip, I tend to cut a lot of stuff out (although I normally use nLite for this), so I'm not into getting the latest updates for quite a few things. Mimo's list is more detailed with extra stuff that a lot of people seem to want, but which I probably wouldn't have included. It's very good, very neat and more people seem to be interested in hfslip as a result, which is a good thing imo. Mimo obviously puts in a lot of work into putting together and supporting his list. I find it very hard to keep track of and categorise everything and I've learned to be careful about including stuff which might not work for everyone. There's no absolutely consistent way to categorise everything which would suit everyone, but with two lists (and others elsewhere) there should be enough info to help everyone keep updated. I'm currently trying to see if there's a good way in which to make it easier to check the list against what's in the hotfix folder on one's harddrive. It's easier for me to maintain the list in date order and easier to see what's new each month. However, mistakes get made and it's maybe harder to account for each and every update unless they're in name order. There's still lots I'm doing with my list and I'm currently sorting through my own hotfixes. This basically means that I'll be taking a look at some of the latest beta hotfixes (this info can be useful later on if a stable fix gets released), looking at the WMP stuff and trying to get some kind of record of all the individual files within all the fixes. That last bit might take a while, but it should stop unnecessary fixes from being included. I don't really use WMP, WU, Office so any comments/corrections are welcome - just post in the Updates thread to which I'm now subscribed. MH

The following is just in case anyone reads this via google and wants an easy life - all these msxml fixes are confusing and can cause a bad headache KB973686 and KB973687 are listed together on their kb pages and imo the different version numbers of msxml6.dll are probably so that they can easily be distinguished (eg by MS support), rather than one being newer/better than the other. The two updates fix exactly the same issue and you can safely leave out KB973686 which is intended for SP2; KB973687 is intended for SP3 and fixes msxml3 too.

The MDAC update kb952287 is superseded by kb961451 which is available by contacting Microsoft, ie it's being beta-tested. The ENU version is called WindowsXP-KB961451-v2-x86-ENU.exe and msadce.dll gets upgraded from 2.81.3002.0 to 2.81.3010.0. A more stable update will probably get released eventually, but there are English, Greek, Czech and Russian versions of the new fix available via a certain other hotfix sharing site. Personally, I'd just stay with kb952287 for the time being. http://support.microsoft.com/?kbid=952287 Note The hotfix that was described in the "Resolution" section in the earlier version of this article is superseded by the hotfix that is described in 961451.

msxml4-KB973685-enu.exe superseeds the original MSXML 4.0 SP3 release.

Just a quick note - IMAPI_XP_SRV2003_x86.exe which is part of KB952011 contains an old version of cdrom.sys.

Since you don't have an entry for SuppressExtendedProtection then you need to apply the regfile if you want to enable Extended Protection for Authentication; your LmCompatibilityLevel should be 3 anyway from a security perspective, regardless of whether you enable Extended Protection.This update looks like it was backported from Windows 7 and to me looks like it's worth installing as it's strongly recommended. http://blogs.technet.com/msrc/pages/monthl...ugust-2009.aspx Q: KB968389 was listed as a critical update from within Windows Server Update Service (WSUS). However, the article states that it is a "security update". Just wondering if there are any vulnerabilities if this update is NOT applied? A: This is a non-security update which does not directly address any vulnerabilities. Not installing this update does not leave your system unprotected against a specific vulnerability. However, this update will allow applications to make use of Extended Protection for Authentication, which is a new functionality that offers more robust protection of authentication credentials. While there is no immediate difference after installing the update, we strongly recommend installing this update so third party applications and Windows components will be able to make use of this strengthened authentication technology. To learn more about Extended Protection for Authentication, we recommend reviewing Security Advisory 973811 for more information on this technology.

Sorry for the delay, see the attachment for the October changes until fdv puts up the new page. Oct_hotfixes.txt

TommyP - I'll add a note to the MSI entry pointing out the new beta and remove the link to that regfile.

*** Edit - WMP9 will be included for now for those wanting a vanilla install of XP *** If there are no objections I'm going to remove the reference to WMP9 hotfixes to make things simpler. The line will be changed to :- If you do not slipstream the WMP11 installer, you do not need the WMP11 hotfixes

@ Tomalak Thanks, I'll get the wu link changed. Good work on solving the MSI 4.5 issue, I'll update the info on that too @ fdv It looks like I picked the wrong day to quit smoking

@ Tomalak Does putting MSI 4.5 in HF with Lions' regfile not work for you?

@ Tomalak Thanks for that, I'll include it when the next patch Tuesday comes around. @ willydejoe1234 I think your link is probably the same file that is directly linked to on the hfslip updates page (which contains files from 24 August 2009).

I'd like to clear up the situation with the different versions of WMP. At the top of the XP hotfix list there are references to WMP9 hotfixes for which there are no links. WMP10 isn't covered at all and I'm not even sure if HFSLIP supports it. I'm thinking that either the references to WMP9 should be removed entirely or that I should add links to WMP9 hotfixes for people that want to stick with the vanilla XP install. The latter option would make the list a bit more consistent since it would follow the scheme used for Internet Explorer where links for IE6 and IE8 are supplied. Any views appreciated.

Just when I thought the list was fully up to date I noticed that the August critical update for WMP 11 seems to replace one of the bugfix updates in the WMP section :- Dec 2008 (??) bugfix update WindowsMedia11-KB959772-x86-ENU.exe Wmp.dll 11.0.5721.5260 Replaced by :- Aug 2009 critical update WindowsXP-WindowsMedia-KB973540-x86-ENU.exe Wmp.dll 11.0.5721.5268

A junk update if ever there was one I suppose The only other update possibly worth including in the future is the exFAT update, but by that time we'll all probably be using Windows 7 or 8

@willydejoe1234 I'm not sure what you mean by the DX redist or WU being important for Microsoft's browser, but the Junk Email Filter is probably something that's considered non-core. I'm open to ideas on the latter if anyone thinks it's worth including. Thanks for the links though, quite a few of which I'll include @everyone Don't worry about posting MS Security Bulletin updates (ie the Patch Tuesday security fixes) as I have these covered. Virtually anything else is welcome though

Attached is a reg file for KB967715 which is included in my update list for those who either want to disable autorun completely, or want to change the default behaviour. The regfile disables autorun on all drives by default. Refer to the KB article (the link above) if you want to edit it. Although some people don't think it's necessary, I'd recommend using this reg file to be on the safe side even if you need to edit it for your situation. There's some more info here (under the green text) and some info on possible values for NoDriveTypeAutorun here. WindowsXP-KB967715-x86-xxx.reg Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\policies\Explorer] "HonorAutorunSetting"=dword:00000001 "NoDriveTypeAutoRun"=dword:000000ff ; Default is to disable Autorun for all drive types ; ; For more possible values for NoDriveTypeAutoRun for different types of drives ; go here - http://www.msfn.org/board/topic/75640-what-are-all-the-different-settings-for-nodrivetypeautorun/page__view__findpost__p__514721 ; Per-user setting (don’t uncomment this if you don’t know what you are doing) ;[HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Explorer] ;"NoDriveTypeAutoRun"=dword:000000ff

Thanks for all the pointers to the updates, there's a few there that I'd have probably missed. I don't use IE, Office or Windows Update so posting these links would be much appreciated I'll be sending the new revised list to fdv as soon as I've finished updating it.

@fdv I was thinking that you could host the main list and I could re-edit the first post of the new thread with anything issued after patch Tuesday. I'll keep the same kind of format where deletions are listed. I'm ready for the dreaded IM's @Crash&Burn Thanks, I'll take a look at hfnetchk.

I would do the XP list if it got it's own sticky thread to make the admin a bit easier.

Seeing as it's patch Tuesday soon please make sure WindowsXP-KB942288-v3-x86.exe gets labelled correctly. It's Windows Installer 4.5, not Windows Search 4.5 and probably shouldn't be labelled as junk either. Cheers

WindowsXP-KB942288-v3-x86.exe should go into the HF folder, but you have it in HFGUIRUNONCE. To ensure the Windows Installer service installs correctly, a regfile needs to go into HFGUIRUNONCE (it's posted somewhere on this board).

If an ntfs partition appears automagically then I would think it's something to do with the unattended settings, probably autopartition. If you remove format capability then this never happens of course For the benefit of others, if the GParted Live CD doesn't work then give the Parted Magic one a try. Super Grub Disk might be worth a look for Linux users wishing to backup, restore their bootsectors.

Parted Magic is worth a look too and is also based around Gparted. Clonezilla is quite handy for backing up the Windows partition before doing a new install. These linux live CD's have come on leaps and bounds in the last couple of years, effectively making Ghost and Partition Magic unnecessary for most users.

I used to use Smart BootManager on an old 1995 era PC which had a buggy bios and couldn't boot from CD. Installing via dos is messy, it's to do with dos using fat and having to convert to ntfs. It's possible to use SBM and avoid the hassle of having to boot from floppy every time you reinstall - but it's a fairly complicated process.