Tomalak

Just remove the corresponding entry from "sysoc.inf".HTH, Tomalak

Okay, had a chance to try this today (used test version 60523a), but it did not work. After installation I still found MSXML3 SP5 instead of MSXML3 SP7 though I had put the newest msxml3.msi in the HF folder.I used another computer I have no access to now and I'm very busy for the rest of the week so I will try to give more detailled information (logfile etc.) next weekend. Just for your information in case you want to have a look on that issue before... Regards, Tomalak

I found it using the following Google search: "legitcheckcontrol.cab site:microsoft.com" (to prevent all of the MSFN links to show up), but only to discover a few minutes later that it is the same link as fdv has on its pages. So all kudos to him!Regards, Tomalak

I think it is http://go.microsoft.com/fwlink/?linkid=39204Regards, Tomalak

Thanks, that was quick! I'll test it next time I install Windows...

Hello, just noticed that WinXP Pro SP2 comes with MSXML 3 SP5. Is it possible to slipstream SP7 (current german version is 8.70.1104 from 2005/08/19, named "msxml3.msi") with hfslip? I know it supports integration of MSXML 4 and MSXML 6, so what about MSXML 3? Thanks! Regards, Commander Tomalak

It has been replaced by KB911567 (MS06-016).

That's strange, PSA works perfectly for me (Win XP SP2 though, not Win 2000). Does the tool really say "missing" or just "note"? I've some of those as well, the helpfile tells about the status "note": This is a special status. It means that PSA was not able to determine whether the patch is installed or not. This is not due to PSA error, but because the mssecure.xml file contains no information about affected files and/or registry keys for this bulletin.So you may indeed have all patches installed and there is no discrepancy between WU/MU, MBSA and PSA.

Hi, just wanted to inform you about a fine small utility I discovered that might be a good GUI alternative to hfnetchk: http://www.elcomsoft.com/psa.htmlIts output is not as concise as the .txt file output of hfnetchk (PSA allows exporting its results to a HTML file), but it offers IMHO a really nice overview. Have fun with it!

Sorry, this was clearly my fault - but as there is now a HFNetChk Pro version 5 and the free version still is 3.86 I believed it to be rather abandoned (it is in fact quite old, its date is 2002/11/20). And I can remember reading something about HFNetChk and especially its data (the mssecure.cab / mssecure.xml available for the free version) not any longer being updated, this was over one or two years ago (I think it was linked to something that had to do with the introduction of SP2)? But I can't find the source of this claims now or any online article backing this, so this is apparently a mistake on my side - it could of course still be working (and using for example Microsofts mssecure.cab; HFNetChk is a part of MBSA, if I'm informed correctly). I'll set up a virtual machine during the weekend and try out the new hfslip release from 2006/01/22 there. If the errors are gone - fine, otherwise I'll install hfnetchk as you wanted and give you its results directly after the installation of Windows (when the mentioned updates still are missing). Thanks!

Fine, thanks! Okay, no problem, the error_report file is attached. But I do not use hfnetchk (it's old, not any longer supported and updated, and if WindowsUpdate is happy I'm satisfied too), so I can't give you its results. I'm not even sure whether this would help because I installed the patches afterwards and so no missing updates would be reported now. And I need my system during the next days so I will start another installation not before mid of February... Sorry for not being able to help more - but something fundamentally must have changed during one of the updates in the last two weeks. Any others here experiencing the same difficulties (some updates apparently not slipstreamed, maybe just non-US patches)? Oh, I almost forgot, I saved a part of the hfslip script where one the patches was processed. I'm not sure if the "file not copied" problem is normal as I saw it happen before with other files and patches and without any problems afterwards, but here it might be the reason for the missing KB898461 update: === Expanding 69_WindowsXP-KB898461-x86-DEU.exe 1 Datei(en) kopiert. 1 Datei(en) kopiert. 1 Datei(en) kopiert. 1 Datei(en) kopiert. 1 Datei(en) kopiert. 1 Datei(en) kopiert. Datei nicht gefunden [file not found] 1 Datei(en) kopiert. D:\CustomXP\HFSLIP\TEMP\UPDATE\KB898461.CAT Integrating 69_WindowsXP-KB898461-x86-DEU.exe 0 Datei(en) kopiert [huh?] 241 COMPLETE Processing Windows Update Completed 69_WindowsXP-KB898461-x86-DEU.exe === ERROR_REPORT.TXT

Hello (I'm new here), just wanted to confirm that there are some problems with the newest releases of hfslip. I wanted to do a fresh Windows installation during the weekend (german version of XP Professional SP2) and discovered the following glitches: 1. The HFEXPERT\WIN folders where not correctly dealed with. After installation I had a "system32" directory as well as a "SYSTEM32 " directory (notice the extra space). This extra directory contained only the files I gave to hfslip. I could move them to correct "system32" directory but was unable to delete the apparently empty remaining "SYSTEM32 " directory. Windows always complained that it could not remove something like "$...$" (can't remember which letters were there), which seemed to be a file or a structure of the NTFS file system. After a reboot I got a bluescreen and could not recover the whole installation... The same phenomenon holds true for the "drivers" subdirectory - I saw an extra "DRIVERS " (the space again) directory which was empty except the few files I expected to be there. So I went back to an older version of hfslip, from 2006/01/17, which I fortunately still had on disk. The problem mentioned above was not there (I have no idea whether this is one of the "several small bugfixes" in the newest hfslip version from 2006/01/22, had no time to try it out yet), but I experienced another difficulty. It was also present in the 2006/01/21-version, by the way: 2. Some hotfixes are not correctly slipstreamed and not recognized the Windows Update. I had to manually install them (or let WindowsUpdate do this) after the installation of Windows. I can remember of KB898461 (the new installer), KB885836 (the Wordpad patch), KB905915 (the newest IE update), the Windows Update Agent and the WGA files in 'LegitCheckControl.cab'. I know their use is allegedly not possible at the moment, deprecated according to fdv's documentation and not mentioned on his XP pages any more, but slipstreaming them nethertheless always worked fine for me. I never had to do any additional steps when visiting Windows Update after a new Windows installation - my 'patch level' was absolutely perfect from the beginning. I'm sure this worked until one or two weeks ago - my last installation that integrated these components successfully was with hfslip version 2006/01/07, I guess. Maybe one version later, maybe one earlier, I don't know exactly. Hope this helps? Thanks for your support, for ironing out further bugs and for providing such a great tool - it's really appreciated!