Jump to content

The File-Checker (HFSLIPFC) for HFSLIP


Mim0

Recommended Posts


Where would would one locate the following file?

--> WindowsXP-KB968389-x86.reg

--> http://www.google.com/#q="WindowsXP-K...9-x86.reg"

Seem to be getting this error:

--> missing (S): HFSVCPACK\WindowsXP-KB968389-x86.reg (Enable Extended Protection for Authentication)

Hi, links are on my update-list (see signature).

For WindowsXP-KB968389-x86.reg take this.

Mimo

Link to comment
Share on other sites

Yes, it's a secret! :D

Not any more!

You can also read the KB-Article what to do in the registry.

Read? That takes too much work.

It's just for convenience to offer a file to download. :)

I figgured that it would be even more convenient to post

it right here. That way, you wouldn't have to go look

for it even--just cut and paste.

Link to comment
Share on other sites

2010-01-12

- Removed: KB968930

- Fixed: For KB968930 only a reduced language-set is available

- Fixed: For KB973686 a reduced language-set is available (not only ENU)

- Added: KB972270, MS10-001 Embedded OpenType Font Engine

- Removed: KB961371, MS09-029 OpenType Font Engine

- Added: Malicious Software Removal Tool 3.3 (windows-kb890830-v3.3.exe) to WIN

- Removed: Malicious Software Removal Tool 3.2 (windows-kb890830-v3.2.exe) from WU

- Fixed (again): KB971276-v3 back to ENU only (DL-page shows lang-selection but file stays in ENU)

- Added: Information about obsolete/wrong updates

- Fixed: A reduced language-set for KB973686 is available.

You can also read the KB-Article what to do in the registry.

Read? That takes too much work.

rofl

Bye, Mimo

Link to comment
Share on other sites

hi Mim0! hope you don't mind if i compared Table 5: Optional updates for Media Player with that of Boooggy and n7Epsilon's WMP11 Hotfix List. by this, there are 2 KBs listed that is not in table 5, namely: KB954067 & KB973442 ... just thought you might like to add these. cheers!

KB954067: Wmvcore.dll 11.0.5721.5250 and Wmvdecod.dll 11.0.5721.5250

KB973442: Wmvdecod.dll 11.0.5721.5268

KB954067 is not to be installed because the Wmvdecod.dll of KB973442 is newer and Wmvcore.dll is replaced by critical security update MS09-047/KB968816.

KB973442 will be checked deeper later... :) But on the first view it seems it's worth to be listed. THX :)

---- EDIT ----

KB973442 was really a new update. I've added it to the list and also that KB954067 was replaced.

Thx@Kiki :D

Edited by Mim0
Link to comment
Share on other sites

2010-01-14

- Fixed: Speeding up the process dramatically (now just a few seconds)

- Removed: KB960225 (Schannel.dll 5.1.2600.5721) because it's replaced

by KB968389 (Schannel.dll 5.1.2600.5834)

- Added: Options to move unknown, wrong and/or obsolete Updates.

For each type there is a INI-setting. The destination-folder

can be defined also in then INI.

-------------------------------------------------

! Move wrong (updates of a component which is not

! belonging to a selected component), obsolete or

! unknown updates to a new folder.

!

! MOVEWRONG: Setting for wrong updates

! MOVEOBSOLETE: Setting for obsolete updates

! MOVEUNKNOWN: Setting for unknown updates

!

! Possible values:

! 0 - Don't move the file (default)

! 1 - move the updates to "MOVETO"

!

! MOVETO the destination-folder. Default:

! HFSLIPFC.MOV

-------------------------------------------------

MOVEWRONG=

MOVEOBSOLETE=

MOVEUNKNOWN=

MOVETO=

Regarding the new INI-settings it's the easiest way to let hfslipfc create a new INI and see whats new.

Mimo

---EDIT---

A small bug comes into this version. Plz use this download temporarily here (attachement).

2010-01-15

- Fixed: When creating a new INI the sections are now better sorted.

- Fixed: When an unknown file was found, no filename was displayed

(comes with 2010-01-14).

Edited by Mim0
Link to comment
Share on other sites

2010-01-14

- Fixed: Speeding up the process dramatically (now just a few seconds)

- Removed: KB960225 (Schannel.dll 5.1.2600.5721) because it's replaced

by KB968389 (Schannel.dll 5.1.2600.5834)

You are still faster then your script .. just wanna report that msxml4 is optional (line 1152 of hfslipfc.cmd) and it's stating to be build 2010/01/13

But I found another one regarding KB968389 and the [recommended] optional updates KB970430 and KB971737:

Your list calls KB968389 Advisory.

You say you removed 'KB960225 (Schannel.dll 5.1.2600.5721) because it's replaced by KB968389 (Schannel.dll 5.1.2600.5834)'.

Then you should also remove KB960803 cause it's superseeded by KB971737 - if KB971737 is inside HF (the File-Checker already checks dependencies).

Maybe you should also mention that Advisory 968389 is handled like a security update by the File-Checker, although it is still optional.

ps: Muppet Hunter's list and Freudi agree with me - or better said: I agree with them ;-)

pps: keep on the good work - very much appreciated!

Edited by mukke
Link to comment
Share on other sites

Hi mukke,

thx for that. It's already a discussion in the update-thread. But I had thought about that how to integrate it in the file-checker and in the list and I have a solution in mind which is not online yet. see here (post #374) :)

CU, Mimo

Edited by Mim0
Link to comment
Share on other sites

is easy enough, the few times I've run the tool I've usually forgotten and had to run it again or cut and paste from the command window. It might be nice for there to be a Log - Yes or No line in hfslipfc.ini perhaps. Your thoughts?
It's implemented now! To create a log-file can be activated in the INI with the next release of the file-checker :)
Link to comment
Share on other sites

hi Mim0! just wanted to report results of trying out hfslipfc_100115b ... i had the following settings:

[font="Courier New"]-------------------------------------------------
! Move wrong (updates of a component which is not
! belonging to a selected component), obsolete or
! unknown updates to a new folder.
!
! MOVEWRONG: Setting for wrong updates
! MOVEOBSOLETE: Setting for obsolete updates
! MOVEUNKNOWN: Setting for unknown updates
!
! Possible values:
! 0 - Don't move the file (default)
! 1 - move the updates to "MOVETO"
!
! MOVETO the destination-folder. Default:
! HFSLIPFC.MOV
-------------------------------------------------
MOVEWRONG=[color="#0000FF"]1[/color]
MOVEOBSOLETE=[color="#0000FF"]1[/color]
MOVEUNKNOWN=[color="#0000FF"]1[/color]
MOVETO=[/font]

& somewhere below:

[font="Courier New"]-------------------------------------------------
! hfslip-folders to check for obsolete, wrong and
! unknown updates (not missing!). When using more
! than one folder, separate them by semicolon.
! Default:
! HF\*.*;HFGUIRUNONCE\*.*;HFCABS\*.*;HFSVCPACK_SW1\*.*
-------------------------------------------------
FOLDERSET=[color="#0000FF"]HF\*.*;HFGUIRUNONCE\*.*;HFCABS\*.*;HFSVCPACK\*.*;HFSVCPACK_SW1\*.*;HFSVCPACK_SW2\*.*[/color][/font]

& as result in \HFSLIP\HFSLIPFC.MOV\move.txt were these only:

[font="Courier New"]unknown: 
unknown:
unknown:
unknown:
unknown:
unknown:
unknown:
unknown:
unknown:
unknown:
unknown:
unknown:
unknown:
unknown:
unknown:
unknown:
unknown:
unknown:
unknown:
unknown:
unknown:
unknown:
unknown:
unknown:
unknown:
unknown:
unknown:
unknown:
unknown: [/font]

no other file could be found (except for move.txt)... was expecting these wrong, obsolete & unknown hotfixes be moved based on this:

- Fixed: When an unknown file was found, no filename was displayed

(comes with 2010-01-14).

but were not ... was there something amiss in my settings for these to be the result? btw, please correct me if i was mistaken but running it the 2nd time (with HFSLIPFC.MOV dir retained as well as move.txt file inside (while leaving FOLDERSET= to default setting this time) only resulted to appending the current number of "unknown" items (making it twice the number of "unknown" instances in the 1st run: i.e., from what used to be 25 to 50) ... wouldn't it be better for this entire dir be deleted & recreated every run of hfslipfc? (i understand there shouldn't be a need to answer my last inquiry as this wouldn't have happened if identified files were moved to the designated directory & parsing it the 2nd time would certainly not produce the results i encountered.) just my thoughts ... cheers! ;) Edited by Kiki Burgh
Link to comment
Share on other sites

@Mim0

Maybe you could add a component-selection in the INI for MS-XML also, so that we e.g. don't get prompted for the mising MS-XML4 update, when using only default XP XP3 included MS-XML(v3+v6).

Somethings are listed twice in the output.

There's a line stating that i don't have rootsupd.exe in HF, but i have disabled reporting of optional updates.

Thanks again for your great work on list and tool! :)

PS: Your update-clasifying terminology has grown on me, and i now also prefer it over the msft 'High-priority' and 'Optional' :)


Checking existing updates for wrong, obsolete or unknown:
---------------------------------------------------------

Check missing updates for Windows XP SP3:
-----------------------------------------
missing (S): HF\msxml4-KB973685-ENU.exe (XML Core Services 4.0 (MSXML4) SP3 Buil
d 2107)

Check missing updates for IE6:
------------------------------

Check missing updates for WMP9:
--------------------------------

Check missing updates for RDC6:
--------------------------------

Check missing updates for DX9:
--------------------------------

Check missing updates for Windows XP SP3:
-----------------------------------------

Check missing updates for IE6:
------------------------------

Check missing updates for WMP9:
--------------------------------

Check missing updates for RDC6:
--------------------------------

Checking the version of Adobe Flash Player
------------------------------------------
Expected version 10.0.42.34 (file=Flash10d.ocx, size=3982240)
OK
HF\rootsupd.exe does not exist.

Finished
Press any key to continue . . .

Link to comment
Share on other sites

hi Mim0! just wanted to report results of trying out hfslipfc_100115b ... i had the following settings:
[font="Courier New"]-------------------------------------------------
! Move wrong (updates of a component which is not
! belonging to a selected component), obsolete or
! unknown updates to a new folder.
!
! MOVEWRONG: Setting for wrong updates
! MOVEOBSOLETE: Setting for obsolete updates
! MOVEUNKNOWN: Setting for unknown updates
!
! Possible values:
! 0 - Don't move the file (default)
! 1 - move the updates to "MOVETO"
!
! MOVETO the destination-folder. Default:
! HFSLIPFC.MOV
-------------------------------------------------
MOVEWRONG=[color="#0000ff"]1[/color]
MOVEOBSOLETE=[color="#0000ff"]1[/color]
MOVEUNKNOWN=[color="#0000ff"]1[/color]
MOVETO=[/font]

& somewhere below:

[font="Courier New"]-------------------------------------------------
! hfslip-folders to check for obsolete, wrong and
! unknown updates (not missing!). When using more
! than one folder, separate them by semicolon.
! Default:
! HF\*.*;HFGUIRUNONCE\*.*;HFCABS\*.*;HFSVCPACK_SW1\*.*
-------------------------------------------------
FOLDERSET=[color="#0000ff"]HF\*.*;HFGUIRUNONCE\*.*;HFCABS\*.*;HFSVCPACK\*.*;HFSVCPACK_SW1\*.*;HFSVCPACK_SW2\*.*[/color][/font]

& as result in \HFSLIP\HFSLIPFC.MOV\move.txt were these only:

[font="Courier New"]unknown: 
unknown:
unknown:
unknown:
unknown:
unknown:
unknown:
unknown:
unknown:
unknown:
unknown:
unknown:
unknown:
unknown:
unknown:
unknown:
unknown:
unknown:
unknown:
unknown:
unknown:
unknown:
unknown:
unknown:
unknown:
unknown:
unknown:
unknown:
unknown: [/font]

no other file could be found (except for move.txt)... was expecting these wrong, obsolete & unknown hotfixes be moved based on this:

- Fixed: When an unknown file was found, no filename was displayed

(comes with 2010-01-14).

but were not ... was there something amiss in my settings for these to be the result? btw, please correct me if i was mistaken but running it the 2nd time (with HFSLIPFC.MOV dir retained as well as move.txt file inside (while leaving FOLDERSET= to default setting this time) only resulted to appending the current number of "unknown" items (making it twice the number of "unknown" instances in the 1st run: i.e., from what used to be 25 to 50) ... wouldn't it be better for this entire dir be deleted & recreated every run of hfslipfc? (i understand there shouldn't be a need to answer my last inquiry as this wouldn't have happened if identified files were moved to the designated directory & parsing it the 2nd time would certainly not produce the results i encountered.) just my thoughts ... cheers! ;)

ups... the problem was not for console-output only but also for the move.log. And also the file was not moved. FIXED & THX :D

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...