[Tomcat76]

This is an advanced feature and no active support will be provided for it. My dynamic hotfix lists won't be updated for it either.


Using HFSLIP 1.6.0 or newer, you can reduce the amount of HFSLPxxx.INF files for Type 1 hotfixes in the new source as well as the amount of registry additions. There are two new folders for this: HF\BASIC and HF\NOREG.

The main difference between them is that one identifier key is added into the registry for the hotfixes in HF\BASIC while no identifier key is added into the registry for hotfixes in HF\NOREG. However, for some hotfixes requiring more registry edits, hardcoded support has been added into HFSLIP if they are placed in either HF\BASIC or in HF\NOREG; this includes hotfixes with updates for shell32.dll (Win2K/XP), p2p*.dll (WinXP), usb*.sys (WinXP), msxml3.dll (Win2K/XP), kerberos.dll (Win2K), localspl.dll (Win2K), ipsec.sys (Win2K) and the Package Installer for WinXP. Also, an often recurring setting for "BufferPolicyReads" is added for Win2K.

Note 1: only Type 1 hotfixes are supported in HF\BASIC and HF\NOREG.
Note 2: this was only tested with Win2K+IE6+WMP9+MDAC281, WinXP SP2 and Win2K3 SP2, so the list below may need to be updated for other OS's and configurations.
Note 3: the hotfix names in HF\BASIC are expected to be in this format: "<word>-KBxxxxxx-<word>*.exe" or "<word>-<word>-KBxxxxxx-*.exe". If the KB article number is not in the 2nd or 3rd position and is not preceded and followed by a hyphen, the identifying registry key will fail to be created.

Here is some info that could be useful if you want to keep Windows Update happy. Most hotfixes don't require any identifier key(s), so everything goes in HF\NOREG except...

To be placed in HF\BASIC (Windows Update wants the one registry key):
Windows2000-KB926121-x86-ENU.EXE
WindowsXP-KB885836-x86-ENU.exe

To be placed in HF (requiring too much registry edits or containing post-setup commands):
IE cumulative update (currently KB933566)
IE7-WindowsXP-x86-enu.exe
MDAC*.exe
OE5.5*.exe
OE6*.exe
WindowsInstaller-KB893803-v2-x86.exe
Windows-KB909520-v1.000-x86-ENU.exe
Windows2000-KB842773-x86-ENU.EXE
Windows2000-KB891861-v2-x86-ENU.EXE
Windows2000-KB896358-x86-ENU.EXE
Windows2000-KB900725-x86-ENU.EXE
Windows2000-KB922582-x86-ENU.EXE
Windows2000-KB928843-x86-ENU.EXE
WindowsServer2003-KB923845-x86-ENU.exe
WindowsServer2003-KB925876-v2-x86-ENU.exe
WindowsServer2003-KB932716-x86-ENU.exe
WindowsXP-KB896358-x86-ENU.exe
WindowsXP-KB897338-v3-x86-ENU.exe
WindowsXP-KB905474-ENU-x86-Standalone.exe
WindowsXP-KB912817-v2-x86-ENU.exe
WindowsXP-KB913580-x86-ENU.exe
WindowsXP-KB914440-v12-x86-ENU.exe
WindowsXP-KB922120-v5-x86-ENU.exe
WindowsXP-KB922668-x86-ENU.exe (COM+ Rollup 14)
WindowsXP-KB923845-x86-ENU.exe
WindowsXP-KB925876-x86-ENU.exe
WindowsXP-KB932716-x86-ENU.exe
WindowsXP-KB933684-v2-x86-ENU.exe
WindowsXP-KB935448-x86-ENU.exe

Also to be placed in HF (not supported in HF\BASIC or HF\NOREG at all):
Service Pack installers
msxml*
WindowsRightsManagement*.exe
WindowsUpdateAgent30-x86.exe
WMP9/10/11 installers and other Type 2 updates

This post has been edited by Tomcat76: 07 August 2007 - 03:46 AM

[Oleg_II]

Interesting feature
Too many updates by now...

[tain]

This feature seems perfect for you, Oleg

[Oleg_II]

Yeah

Ideally I'd prefer only one HFSLIP.INF file Just jocking It needs some manual work.

[Tomcat76]

I actually experimented with that a couple of months ago and talked about it with TommyP. This never made it into a public release because it would "overcomplexify" () the code to add support for those security registry entries. To convert strings, whatever comes after a semi-colon needs to be ignored but those security keys actually contain lots of semi-colons and those should not be ignored. Still with me?

[Oleg_II]

I agree that is difficult to implement automatically

Some time ago I tried to collect regestry settings from hot-fixes and place them all in one INF file... But I never had time to make this work on constant basis And now when there are A LOT of hot-fixes I'm just affraid to approach this metter Maybe some time in future

[Tomcat76]

Added WindowsXP-KB912817-v2 (COM+ Rollup Package 13) to the list. I am using Rollup 14 so forgot about this one...

[johndoe74]

it would be nice if we had a static list of which hotfixes are recommended to be placed in HF\BASIC or HF\NOREG. so far there's only one each for win2k and xpsp2 going from the first post

[tain]

More lists? I'm sure that would be handy, but it seems like we already have folks spending lots of time just keeping various lists updated.

[Tomcat76]

johndoe74, on Aug 7 2007, 08:24 PM, said:

it would be nice if we had a static list of which hotfixes are recommended to be placed in HF\BASIC or HF\NOREG.

The title post shows everything you need to know. The statement "everything goes in HF\NOREG except..." is accurate. I'm even listing updates that don't appear on Windows Update, on the_guy's list and on my dynamic list.

johndoe74, on Aug 7 2007, 08:24 PM, said:

so far there's only one each for win2k and xpsp2 going from the first post

That's right. Only those two need to be placed in that folder if you want to keep Windows Update happy.