We routinely delayed requirements and only turned on "Windows Update optional" for a few days just so users can all get the proper updates first. We enforce it after couple days. It reduces a lot of user calls, frustration and also the Microsoft update hiccups.
From: Cisco Clean Access Users and Administrators [mailto:[email protected]] On Behalf Of Karla Borecky Sent: Thursday, October 15, 2009 10:04 AM To: [email protected] Subject: Re: KB971961 - Another Windows Update 'file check' failure Hello all, In what must be a miraculous occurrence, Microsoft seems to have released a 'fixed' version of KB971961 because 99%* of the folks who were failing the check suddenly were PASSING it. (If you look at the info page for the check, it says "Updated September 20, 2009.) I *did* bring it up to an MS support person shortly after writing to this list abt the problem, but I wouldn't dare presume this was at all related! The weird thing about this situation was that the correct version was put on the machine - but not in the system32 directory. SO. My question to all of you is: Do you delay the requirement of new Windows updates (say, for a week or so), and if so, how did you do it? thanks, Karla B * For the other odd person or so, our tech guys put a copy of the correct jscript.dll on the desktop, and then booted with BART (or similar program) so they could copy it into system32. They had to use the latest version of the boot-OS program to get this to work. Karla Borecky Novell Systems Administrator Information Technology Services Smith College Northampton, MA 01063 Hi, This seems to happen every once in a while, and we have yet to find a solution except reinstalling Windows Vista. A Windows Update that Clean Access (v4.1.10 Agent) checks based on the file information instead of the registry is failing, even though the file is showing up with the correct information in Vista. I found a few posts about this for past problems, and have posted here about similar incidents with different KBs and different PCs, but never got any kind of reasonable (ie, not reinstalling Windows) resolution. Reinstalling Windows due to one pesky file is a pretty unreasonable thing to ask of a student. The update this time is KB971961, on file C:\Windows\System32\Jscript.dll. Clean Access fails the file check (see the log below), but according to the computer, the file in this location is version 5.8.6001.18795, with a creation date of 6/6/09, which should pass the check. The version of Vista is US, and the date format is MM/dd/yy (the only suggested fix that's been posted on here). We've uninstalled and reinstalled the update, uninstalled and reinstalled Clean Access, but it still fails. If anyone has run into this before, please let me know what you're experience has been. Thanks, Doug Chudzik, [email protected]<mailto:[email protected]> Student Computing Manager Wellesley College 781.283.2124, LIB 214 User: ----- Operating System: Windows Vista Business Agent Version: 4.1.10.0 Agent Type: Windows Agent System Name: ---- System Domain: n/a System User: ---- User Domain: ---- ________________________________ 1. Windows Critical Updates (Mandatory) Passed Checks: 1. pc_Windows-Vista-SP2 2. Failed Checks: 3. pc_vista64, Registry Check [\HKEY_CURRENT_USER\Software\Wow6432Node\ exists ] 4. pc_Windows-Vista-SP1, Registry Check [\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\CSDVersion contains Service Pack 1] 5. pc_Vista_KB971961_MS09-045, File Check [$SYSTEM_32\Jscript.dll later than [M]06/03/2009 00:00:00] 6. pc_Windows-Vista-SP1-int, Registry Check [\HKEY_LOCAL_MACHINE\system\CurrentControlSet\control\windows\CSDVersion equals 256] 7. Not executed Checks: 8. pc_KB929123_2_MS07-034_Vista 9. pc_KB929123_1_MS07-034_Vista 10. pc_Windows_ehkeyctl 11. pc_Vista_KB971557_MS09-038 12. pc_KB930178_2_MS07-021_Vista 13. pc_KB946026_2_MS08-007_Vista 14. pc_KB946026_1_MS08-007_Vista 15. pc_KB930178_1_MS07-021_Vista 16. pc_Vista_KB967723_MS09-048 17. pc_KB925902_2_MS07-017_Vista 18. pc_KB925902_1_MS07-017_Vista 19. pc_Vista_KB973768_MS09-037 20. pc_Vista_KB973507_MS09-037 21. pc_IE8_0 22. pc_KB956802_MS08-071_Vista 23. pc_Windows-Vista-SP2-int 24. pc_MSXML3r_MS08-069_Vista 25. pc_Vista_KB972260_MS09-034_IE8 26. pc_IE7_0 27. pc_KB938127_MS07-050_Vista 28. pc_Vista_KB972260_MS09-034_IE7 29. pc_KB943055_MS08-008_Vista 30. pc_Vista64_KB951698_MS08-033 31. pc_KB960803_MS09-013_Vista 32. pc_KB959349_MS08-075_Vista 33. pc_MSXML3_MS08-069_Vista 34. pc_KB954593_MS08-052_Vista 35. pc_KB961371_MS09-029_Vista 36. pc_Vista_KB970710_MS09-049 37. pc_KB929916_2_MS07-040_Vista 38. pc_KB929916_1_MS07-040_Vista 39. Description: 1. Windows Automatic Update Misconfigured (Mandatory) Passed Checks: 1. au_install_option 2. WinVista_pc_AutoUpdateCheck 3. Failed Checks: 4. Not executed Checks: 5. Description: 1. Anti-virus installed (Mandatory) Passed Checks: 1. av_inst_ANY_of_McAfeeAV 2. Failed Checks: 3. Not executed Checks: 4. av_inst_ANY_of_TrendMicroAV 5. av_inst_ANY_of_NortonAV 6. av_inst_ANY_of_F-ProtAV 7. av_inst_AVG7_5_7_x 8. Description: 1. Anti-virus definitions updated (Mandatory) Passed Checks: * Failed Checks: * av_def_McAfeeAV, Antivirus Check [Any supported McAfeeAV AV software up to date] see Client AV Info<https://cam.wellesley.edu/admin/agent/reports/display_report.jsp?CCA_TOKEN=U60eEFr8uBpjYyC88YNrEihbk2ClQ88FvFqxXBnFVP8.&id=1026/#avinfo> for details * av_inst_AVG7_5_7_x, Antivirus Check [AVG 7.5 7.x installed] see Client AV Info<https://cam.wellesley.edu/admin/agent/reports/display_report.jsp?CCA_TOKEN=U60eEFr8uBpjYyC88YNrEihbk2ClQ88FvFqxXBnFVP8.&id=1026/#avinfo> for details * av_def_NortonAV, Antivirus Check [Any supported NortonAV AV software up to date] see Client AV Info<https://cam.wellesley.edu/admin/agent/reports/display_report.jsp?CCA_TOKEN=U60eEFr8uBpjYyC88YNrEihbk2ClQ88FvFqxXBnFVP8.&id=1026/#avinfo> for details * av_def_TrendMicroAV, Antivirus Check [Any supported TrendMicroAV AV software up to date] see Client AV Info<https://cam.wellesley.edu/admin/agent/reports/display_report.jsp?CCA_TOKEN=U60eEFr8uBpjYyC88YNrEihbk2ClQ88FvFqxXBnFVP8.&id=1026/#avinfo> for details * av_def_F-ProtAV, Antivirus Check [Any supported F-ProtAV AV software up to date] see Client AV Info<https://cam.wellesley.edu/admin/agent/reports/display_report.jsp?CCA_TOKEN=U60eEFr8uBpjYyC88YNrEihbk2ClQ88FvFqxXBnFVP8.&id=1026/#avinfo> for details 1. Not executed Checks: 2. av_defn_AVG7_5_7_x 3. Description: 1. Anti-malware installed (Mandatory) Passed Checks: * Failed Checks: * pc_as_inst_MalwarebytesAnti-Malware_MalwarebytesAnti-Malware_1_x, Anti-Spyware Check [Malwarebytes Anti-Malware 1.x installed] see Client AS Info<https://cam.wellesley.edu/admin/agent/reports/display_report.jsp?CCA_TOKEN=U60eEFr8uBpjYyC88YNrEihbk2ClQ88FvFqxXBnFVP8.&id=1026/#asinfo> for details Not executed Checks: Description: ________________________________ Client AV Info Product ID: McAfeeAV Product Name: McAfee VirusScan Enterprise Product Version: 8.5.0.781 Virus Definition File Version: 5769 Virus Definition File Date: 10/12/2009 Client AS Info Product ID: Malwarebytes Anti-Malware Product Name: Malwarebytes Anti-Malware Product Version: 1.41.0 Spyware Definition File Version: Spyware Definition File Date: Product ID: MicrosoftAS Product Name: Windows Defender Vista Product Version: 1.1.1600.0 Spyware Definition File Version: 1.67.698.0 Spyware Definition File Date: 10/12/2009 2:46:41 AM Doug Chudzik Student Computing Manager Wellesley College 781.283.2124, LIB 214
