
Mim0
MemberContent Type
Profiles
Forums
Events
Everything posted by Mim0
-
Sorry for that! I also found this error when I tested it in my HFSLIP-environment. But - shame on me - I''ve forgotten to copy the fixed script back to my development environment from which I publish the file-checker. I upload it asap!
-
Yeah, that's a really great thing! Thx to Parseus!!! You can download it from here: File-Checker downlads
-
Yes, that's right. I'll add it to the list...
-
Thx, Parseus. I've forgotten to refresh also this posting...
-
Yes First, the message "replaced by kb2616310" was an old text. Correctly it should be "AD is not part of a standard Windows XP", If forgotton to change the texts. Also for further/older updates (see below). I have to change it. KB2616310 (MS11-086) -> KB982000 (MS10-068) -> KB973039 (MS09-066) -> MS09-018...all of them are regarding AD. And no one of them are needed if AD (ADAM) is not installed. The info, that update xxx is not needed is given now, but the reason could confuse... (see above).
-
Thx!! New file-checker extension for XP: 2011-11-12 - Added: KB2641690 (Security Advisory 2641690: Certificate Revocation) - Removed: KB2616676-v2 (Security Advisory KB2616676: Certificate Revocation, replaced by KB2641690)
-
Thx you both! new file-checker-extension for XP: 2011-11-11 - Added: Adobe Flash Player 11.0.1.152 - Removed: Adobe Flash Player 11.0.1.152 - Removed: KB2616310 (MS11-086: Active Directory, not part of a standard Windows XP) HFSLIPFC v.2011/05/10 with XP-update-list v.2011/11/11
-
Yes, Acitve Directory-Updates are on my list since 2009. It's correct that these updates are not needed. What should I do? Remove also the last current AD update from the update-list (and also file-checker)? Anybody any idea?
-
Hi jvidal, Yes, but Parseus noticed that it fixes audio problems (and it's just a hotfix which will not be listed by default by the file-checker) I frequently look into the download-center (new downloads) and there I found it.And MSRT... I didn't forgot it but yesterday evening - when I updated the XP-list and file-checker - the new MSRT was not released.
-
new file-checker extension for Windows XP: 2011-11-08 - Added: KB2544893 (v2) (MS11-037: MHTML) - Added: KB2616310 (MS11-086: Active Directory) - Removed: KB2544893 (MS11-037: MHTML, replaced by KB2544893-v2) - Removed: KB982000 (MS10-068: Local Security Authority Subsystem Service, replaced by KB2616310) HFSLIPFC v.2011/05/10 with XP-update-list v.2011/11/08
-
and MS11-037 was re-released: KB2544893 (v2)
-
fixed file-checker extension for XP: 2011-10-31 - Fixed: Changed the folder of KB961742 (v3) from HF to HFSVCPACK_SW1 Thx for kooky for the solution and Parseus for remembering me and confirming that information.
-
new update-list for XP: 2011-10-28 - Added: KB887606 (MSXML uses cached credentials incorrectly) - Added: KB888111 (High Definition Audio class driver 1.0a) I was really surprised that MSXML2 was on XP SP3. KB887606 sets the version a little bit higher. KB888111 could avoid some audio problems. Thx to Parseus for both.
-
User who are downloading the current KB2564958-update will have the new name. But after I released the script - later in the evening - I thought that I forgot that WindowsXP-KB2564958-X86-XXX.exe could be ignored if Windows-XX-XX-KB2564958.exe is present.Thx for remembering me...
-
new file-checker for XP 2011-10-25 - Added: Roots Certificates Update October 2011 (31.0.2195.0) - Added: KB2598845 (Internet Explorer 8 Compatibility View List) - Removed: Roots Certificates Update June 2011 (28.0.2195.0) - Removed: KB2447568 (Internet Explorer 8 Compatibility View List) - Changed: Filename of KB2564958 (MS11-075: Active Accessibility) - Changed: Folder of UPHClean from HFGUIRUNONCE to HFSVCPACK_SW1 (Thx to Parseus) HFSLIPFC v.2011/05/10 with XP-update-list v.2011/10/25
-
some new updates for XP: - Roots Certificates Update October 2011 (31.0.2195.0) - KB2598845 (Internet Explorer 8 Compatibility View List) and KB2564958 (MS11-075: Active Accessibility) was re-released with the correct filename
-
Of course. Bus as I written it I thought the local one couln't never be newer....
-
I don't know this. I don't integrate MSRT into my CDs and I don't us Window/Mocrosoft Update.Sorry... In case iof online-udapte I download an info-file with informatin about the current filechecker on the webspace. Inside of this info-file there is the version. I extract the version (=date) and comüpare it with the local. But I just compare if they are equal or not, because normally the web-version is newer than the local. But in this case you had a newer local version because I couldn't upload a newer one --> the result was: the versins are different and the online-update-routine thought there was a newer one on the web.
-
Oh yes... I didn't considered that - reason was the file on the webserver was not the current ones.Now I could upload all files and the auto-update problem is gone.
-
new file-checker for XP: 2011-10-12 - Added: KB2564958 (MS11-075: Active Accessibility) - Added: KB2567053 (MS11-077: Windows Kernel-Mode Drivers) - Added: KB2592799 (MS11-080: Ancillary Function Driver) - Added: KB2586448 (MS11-081: Internet Explorer) - Added: Malicious Software Removal Tool 4.1.5503.0 - Added: KB943232 (An application that uses the Sxs.dll file crashes on Windows XP) - Removed: KB971513 (Automation API Update, replaced by KB2564958) - Removed: KB2555917 (MS11-054: Windows Kernel-Mode Drivers, replaced by KB2567053) - Removed: KB2503665 (MS11-046: Ancillary Function Driver, replaced by KB2592799) - Removed: KB2559049 (MS11-057: Internet Explorer, replaced by KB2586448 - Removed: Malicious Software Removal Tool 4.0.5400.0 due to problems with the ftp-access to my site I offer the download here: hfslipfc-110510-xp111012.zip
-
yes, of course that's not the first update with a non-standard filename-scheme. The file-checker will respect this Thx, but NET-Framework-updates are not handled on my site . Should it?
-
Yes, october-patches are released, tomorrow is a good time to make it. :-)
-
The new reg-setting (in the inf of the new SWFLASH.cab) takes the correct path (not fix WINDOWS)