Microsoft Official patch for WMF flaw released

User Comments: 18

1. January 5, 2006 3:09 PM
   phantasm66 said:
   Excellent! Heading there now.
   Reply
2. January 5, 2006 3:18 PM
   phantasm66 said:
   OK I just installed it. You need to reboot. After rebooting, I re-registered the dll with this command:regsvr32 %windir%system32shimgvw.dll...and turned Google Desktop back on.
   Reply
3. January 5, 2006 4:18 PM
   Crofty74 said:
   Thanks for the heads up, popping over now.
   Reply
4. January 5, 2006 4:59 PM
   luismigilbert said:
   great work from microsoft...took a while but finally here...
   Reply
5. January 5, 2006 5:07 PM
   PanicX said:
   8 days after the first report of the exploit in the wild. Thats pretty good given Microsofts track record. I'm especially impressed that they didn't wait on the patch release cycle.
   Reply
6. January 5, 2006 5:09 PM
   nathanskywalker said:
   Pheww, was holding my breath there, well not really. Good that they got the update out, but Microsoft really should make windows update compatible with firefox...
   Reply
7. January 5, 2006 5:27 PM
   krugger said:
   [b]Originally posted by nathanskywalker:[/b][quote]Pheww, was holding my breath there, well not really. Good that they got the update out, but Microsoft really should make windows update compatible with firefox...[/quote][url]http://windowsupdate.62nds.com/[/url]
   rd party site, works for me though.
   Reply
8. January 5, 2006 6:04 PM
   Masque said:
   I was surprised when I logged in this evening to see that sitting in my tray ready to run. Glad they pushed it out. I'm sure it wouldn't have been long before something came out to exploit this.
   Reply
9. January 5, 2006 8:04 PM
   MonkeyMan said:
   Its great that they came out with this new patch, and it should be useful to everyone that downloads it. I know I will be downloading it for sure.
   Reply
10. January 6, 2006 2:18 AM
    brownpaper said:
    [quote][b]Are Windows 98, Windows 98 Second Edition, or Windows Millennium Edition critically affected by one or more of the vulnerabilities that are addressed in this security bulletin?[/b]No. Although Windows 98, Windows 98 Second Edition, and Windows Millennium Edition do contain the affected component, the vulnerability is not critical because an exploitable attack vector has not been identified that would yield a Critical severity rating for these versions. For more information about severity ratings, visit the following Web site.[/quote]So, are the older versions of Windows vulnerable or not vulnerable? There is a vulnerabilty, but there is no way to attack this vulnerability? Huh? Wtf?
    Reply
11. January 6, 2006 4:13 AM
    zachig said:
    FINALLY. Thanks Microsoft.
    Reply
12. January 6, 2006 6:25 AM
    Per Hansson said:
    brownpaper; I think that if you have a third party app that uses the vulnerable dll's in Windows 98, heck, even 95 and 3.0 is vulnerable... But Microsoft does not want to fix them, as they do not include an application that can view wmf files on those OS'es... That's my take on it anyway...
    Reply
13. January 6, 2006 6:35 AM
    Rage_3K_Moiz said:
    A rare bout of good work from Microsoft's part.
    Reply
14. January 6, 2006 7:09 AM
    asphix said:
    Thanks for the info techspot! Going to push it out to our cleint PC's later this morning!This was much sooner than expected. A nice surprise from Microsoft for sure.
    Reply
15. January 6, 2006 7:50 AM
    vnf4ultra said:
    [b]Originally posted by phantasm66:[/b][quote]OK I just installed it. You need to reboot. After rebooting, I re-registered the dll with this command:regsvr32 %windir%system32shimgvw.dll...and turned Google Desktop back on.[/quote]I just did the same, except the page I read said to execute "regsvr32 shimgvw.dll", instead of "regsvr32 %windir%system32shimgvw.dll", what's the difference? It seemed to work when I did it.
    Reply
16. January 6, 2006 8:42 AM
    asphix said:
    Its the same command, just one is a short hand way of doing it. The first way is the method you would take if wanted more control over the exact .dll to install. The first way basically says "register this .dll in this folder" where the other one just says "register this .dll"For example, if you wanted to register a .dll that is in the "program filesapplication" directory you would type regsvr32 c:program filesapplicationthedll.dllregsvr32 = command to register a .dll with the OS%windir% = command for the windows Directory (sometimes Windows, sometimes winNT)
    Reply
17. January 6, 2006 3:37 PM
    mentaljedi said:
    I'm sure everyone is thinking "FINALLY!". And so am i. THank goodness. Microsoft... you took your time you really did.
    Reply
18. January 8, 2006 7:23 PM
    Race said:
    Just a reminder.......you need to re-register the related 'shimgvw.dll' file BEFORE installing the patch.
    Reply

Recently commented stories