Mim0

New High-Priority Update (at least for EU-contries):

After some discussions with others I tried to suit everybody with INI-options what shall be listed. If you set ADVISORIES=1 (or empty because 1 is default) then KB968389 will be listed as missing if it not present in HF. Independend from INI-settings:- KB960225 will be reported as obsolete when both (KB960225 and KB968389) are present. - KB960225 will not reported as missing if KB968389 is present

What ist the new one?As far as I know KB960225 can be replaced by KB968389. If KB968389 is existing in HF the file-checker will not report KB960225 as missing. THX for the list. Mimo

For my understanding (what is not very big for WU/MU because I don't use the WU/MU-files) the legitcheckcontrol.cab is a replacement for KB892130.But if this is not correct, I need the info what is correct. Is this worth to open a new thread for this? Problably users with more experience with WU/MU can explain that...

On my system I have Bthport.sys 5.1.2600.5620 which is coming with KB951376-v2.

Hi Lilla,thx for this idea. I've thought about it and I come to the conclusion to leave it as it is, because I want to recommend the latest beta. If I add links on th top of the page, a user will probably use the final instead of the latest beta (betas often have the touch of 'unstable'). But I've modified the line with the download-links for HFSLIP in table 6. Until now the final was more in the foreground than the current beta (which is to prefer). I changed it now in that way, that the latest beta stands more in the foreground. What do you think? Interesting! Yes, I would like to see your list. : I've just quick looked at this side. Many hotfixes!!!

Done! You can use regular expressions now in the sense in FINDSTR (see FINDSTR /? for details). But regarding yours: You can place a dot (.) as the wildcard for a single character in the filename: H|HF\windows-kb890830-v3...exeBut because the backslash is the escape-character you have to replace it also by the dot: H|HF.windows-kb890830-v3...exeBut you can it make it now more simple: just write KB... H|kb890830 Yes, if it will be more clear I will do it. I don't know these file and I think the better info comes from users who are using it THX It's included now! 2010-03-01 - Changed: The description of LegitCheckControl.cab - Added: Regular expressions allowed in IGNORE-list. How to use RegEx will be described in the INI now. - Added: Hint for RAR-packed AddOn(s) (*.rar) found in HFAAO - Added: When using hints for multiple files (by using wildcards), all matching files will now be listed (instead of only one like before) Mimo

THX for giving the info. Mimo

it's described in KB938720.

Regarding problems with WU/MU updates please ask in the forum. I don't use it. If something has to be changed I will do it. When you look at the security-bulletins for WIN-XP3 you will see that this is also not perfect. Yes Sir! 2010-02-24 - Added: IE8 JSON interoperability (KB976662) (can replace KB971961/MS09-045) - Added: Cumulative Time Zone Update (KB979306) (replaces KB976098 v2) - Removed: Cumulative Time Zone Update (KB976098 v2)

2010-02-23: - Changed: DX9-Redist will now be reported as "obsolete" instead of "wrong" when also the manual extracted CABs are found (this is conform to WMP11). - Added: Hint to LegitCheckControl.cab - Fixed: KB979099 doesn't have the standard language-schema but a really new individual schema what is now implemented.

THX! Not a typo. KB979099 is using a new (very strange) language schema which I have implemented now (next release). THX for reporting it!!!

Not a typo. KB979099 is using a new (very strange) language schema which I have implemented now (next release). THX for reporting it!!! Yes, nice. Next rel. --- Youre right, it's not consistent. It' comes from the internal handling of them (DX is a seperate component internally, WMP11 not). I'll see to change it.But the "(O)" is not possible in combination with "obsolete" now. For that I have to change to much I think it's not worth. Or? I check also the unneccesary manually extracted DX9-files in HFCABS. Regarding this thread I report unneeded DX9-files as "wrong". But for people who are not using the file-checker it's worth to add this link in the list. THX for reporting this. Fixed in next rel. Hmmm. I don't use MU/WU-files. I have no knowledge about that and also no interest for that. What I can do is to make a hint for the legit-cab to be sure to get the newest one!!! Would this be helpful?THX @ all, Mimo

Thx for reporting this. I've made the same experience... 2010-02-22 - Added: INI-setting HINTS=0/1 (default=1) to disable/enable the output of hints for specific updates. - Added: PAUSE after creating INI - Added: cmdow.exe will checked against HFTOOLS\cwnd.exe. If cwnd.exe exists cmdow.exe will not be reported as missing. Also changed the msg for cmdow ("...could be deleted by virus-scanner"). - Fixed: Using other wording for "missing files". "missing" will now used only for security-updates (MS...). All other will reported as "not found" to avoid missunderstandings. The user has to decide (and think about it) which MS...-update shall be used. - Fixed: KB979099 was expected always in English instead of the correct language.

2010-02-19 - Fixed: Obsolete updates were not moved when MOVEOBSOLETE=1 (came with the previous version) - Added: Check of (optional) cmdow.exe in HFTOOLS. - Fixed: After clarification with TommyP I've corrected the List of extracted DX9-CABs (if someone will extract it manually) and added information of DX9-Files which are not to be used. @Lilla I'm just in a hurry. Let's talk later about an HFSLIP-section! Mimo

Yes... I hope they can make it faster...Thx for clarification regarding the DX9-CABs!!! Wish you a nice weekend!

I do this checks because some users here extract the cabs manually to HFCABS. And the file-cheker does the follwing things:- If both (the dx9-redist-exe AND the manually extracted CABs) are found, than the dx9-redist-exe will be reported as wrong. - the file-checker checks each file in HFCABs and report it as unknown, wrong or obsolete. And for that each file must be known by the file-checker to prevent that files are reported as unknown. These CABs are inside of the dx9-redist-exe which are not copied by HFSLIP to HFCABS: 1. Apr2006_MDX1_x86.cab 2. Apr2006_MDX1_x86_Archive.cab 3. BDANT.cab 4. BDAXP.cab 5. dxdllreg_x86.cab 6. dxnt.cab 7. dxupdate.cab My information after reading hfslip.cmd: Files 1 and 2: I saw in hfslip that you filter out *MDX* and so I will remove these files from the filechecker. File 3: it's for Win 2000 - I don't put it in th file-checker Files 4 and 6: Not used for XP with SP3 - I don't put it in the file-checker File 5: ??? (used under specific circumstances. Needed?) File 7: ??? (not used?) Can you tell me something about the usage of dxdllreg_x86.cab and dxupdate.cab in HFSLIP? Regards, Mimo

Hmm... I've just downloaded the file and i got no probs. Maybe the webserver had temp problems. Can you try again? Observation, Microsoft Security Essentials (MSE) identifies cmdow.exe as a threat and recommends removal.SUGGESTION: Include HFTOOLS in the default FOLDER SET for HFSLIPFC.ini. Then, in the event cmdow.exe was deleted by your anti-virus this would be caught by HFSLIPFC. Good idea! But I will do a "special-check" for this file instead of checking the whole HFTOOLS because then the file-checker will report too many unknown or missing files I think!Bye, Mimo

But why does HFSLIP not put all of these CABs to the HFCABS-folder? I think the only one with this knowledge ist TommyP!

@Lilla THX!!! I've changed the list regarding our hints. 2010-02-18 - Info: INI-setting PREFIX has leaved it's beta-state but it will not be "official" in the INI. - Fixed: Prefixes are handled now also in the dependency-check of KB970430 and KB971737 against KB968389. - Fixed: If KB970430 doesn't exists, KB971737 was not checked against KB968389. - Changed: Reduced console output - Changed: Renamed the INI-setting "DOWNLOAD-SCRIPT" to "DOWNLOAD-COMMAND" (still beta state) - Added: KB979099 to WIN (replaces KB917275) - Removed: KB917275 from WU - Added: Support of giving hints for each used (known) update So far hints was given for WMP11-installer, Windows Messenger 5.1, KB975254 (MS09-053) and KB977377 (Advisory 977377). With this extension, the special-code for printing a hint for KB975254 (MS09-053) was deleted. - Added: Windows Messenger 5.1 (optional, can replace KB946648/MS08-050)

THX!!!

Hi Kiki,do you mean you extract these files (above) manually? Or does HFSLIP extract these files on your system??? Yes, I found and read it befor starting this topic. But I didn't found my answer there! CU, Mimo

Regarding the comment from ricktendo64 (msi based installers inside): You put this file in the HF-folder to make it work correctly?Mimo

For the file-checker I added support for the manually extracted x86-CABs of the DirectX-redistributable. For the previous version I got a list of CAB-files from a user which I put in the file-checker. Now I thought I've updated it to the feb2010-version but during a HFSLIP-run wich the directx_feb2010_redist.exe (I don't extract the CABs manually) I noticed that not all x86-CABs are extracted temporarely in HFCABS by HFSLIP. Missing x86-CABs: - Apr2006_MDX1_x86.cab - Apr2006_MDX1_x86_Archive.cab - and some other files which names are not beginning with <month><year>, but I think they are not to use (if I'm wrong please tell it) Now my question: What's the correct way to find out which x86-CABs are needed to be in HFCABS when the DirectX-redistributable is extracted manually? Thx, Mimo

Thx for the Info. Does it replace 917275?PS: I've testet WU also but kb979099 is not listed there. Yes. I've thought about it how to check if messenger.msi the latest one. But I think I will make just a Remark the the user has tu ensure that.Another thing: Can you confirm that HFGUIRUNONCE is the correct folder? Regards, Mimo