Friday, January 06, 2006

Update on Windows Flaw

Two days ago, I told you about the very dangerous Windows Meta File flaw that was being exploited by some of the scum that stalk the Internet on search and destroy missions. After returning from my 2 day wedding shoot in Yakima late last night, I logged onto my desktop computer this morning to discover that Microsoft had automatically installed an urgent fix on my system.

It didn't say what it was, but I suspected that it might be the fix that Microsoft said it was working on to fix the meta file flaw. After doing some research, I found that Microsoft had indeed rushed the patch out for downloading, roughly 10 days ahead of schedule. Good job, Microsoft!

The patches are available for Windows 2000 SP4, Windows XP SP1 and SP2, and Windows Server 2003 SP1. There are no fixes for Windows 98 (any version) or Windows ME. According the Microsoft, the security vulnerability does not affect these operating systems. Originally, Microsoft said it did, but now they have backtracked on that statement.

If you have Windows XP, and you are not sure you have received it, you can go to your control panel and access the "Security Center." On the left side of the screen, you will see a menu selection called, "Check for the latest updates from Windows Update." This will take you to a special section of the Microsoft website. Follow the instructions on the screen to see if you already have this latest patch. Microsoft will scan your computer and tell you if you need to download it or if it has already been done. You can also check and see if you computer automatically downloads the latest updates. If it isn't set up that way, you should probably set it so you don't have to worry about getting these patches in the future.

If you have Windows 2000, you may have to manually check on the Microsoft website to see if you can download the patch. Whatever operating system your computer uses, if your computer has not installed this latest patch, do so immediately!! It is a very critical fix.

Again, cudos to Microsoft for fixing this problem so fast.

No comments: