Skip to main content

Patching against the Conficker worm

The Win32Conficker worm takes advantage of a vulnerability in the Server service of pretty much all versions of Windows and allows a remote attacker to take control of the infected computer.

According to Microsoft "Most anti-virus software could detect and block the Conficker worm, so if you have updated anti-virus software on your computer, you are at a much lower risk of being infected by the Conficker worm."

However, it is also recommended to ensure your Windows OS is patched so that you are not vulnerable to the threat.  In order to ensure you are patched against this nasty piece of work please follow the steps below...

1. Find out what version of Windows you are running

  • Hold down the Winlogo button (looks like the Windows icon) and tap once on R
  • Type "winver" and hit Enter
  • You will be able to read off what version of Windows you have, e.g. in the image below I can tell that I have Windows XP Professional with Service Pack 3.

image

2. Download the correct patch for your Windows version

3. Apply the patch

  • Navigate to where you saved the patch and double-click it
  • Follow any on-screen prompts that appear

To find out more about Conficker have a look here:

http://www.microsoft.com/protect/computer/viruses/worms/conficker.mspx

Comments

Popular posts from this blog

Resolve WSUS Server issue that gives "Cannot save configuration because the server is still processing"

This is a pretty infuriating error and can sometimes crop up as a result of running a "wsusutil reset" command. First of all, give the server some time, and then a bit more...  but you've probably already done this. These steps may help to resolve the situation: - Install Microsoft SQL Management Studio (free download) - Run SQL Management Studio and start to connect to the WSUS database - Enter this in the "Server Name" box:  \\.\pipe\MICROSOFT##WID\tsql\query - Expand the "Databases" tree - Right-click on "SUSDB" and choose "New Query" - Paste this query in:     UPDATE tbSingletonData     SET ResetStateMachineNeeded = 0 - You should see a message like "1 row affected", which is good - Quit SQL Management Studio - Open "Services" and restart the "WSUS Service" - Now, open WSUS

Logon Scripts in Group Policy not running

Problem  Was having difficulty with a logon script I had created and was deploying to users via Group Policy. The script was to customise printer settings for certain users. But it just wasn't running when the users would logon to their PCs. The GPO was applying properly, and I could run the script manually without issue. Cause It turns out that it was happening because, by default, logon scripts don't run for 5 mins after logon occurs on a Windows client PC. Solution This can be adjusted by setting the "Configure Logon Script Delay policy" to "Enabled" and then configuring a better delay. Note: if this policy is set to disabled or not configured, the default delay of 5 mins will apply. I initially set this delay to "0" but found that wasn't successful.  Perhaps the script needed a small delay. So I set it to "1" (1 minute) and it worked nicely. I must also note that during the troubleshooting process, I read many recommendations to e...

Convert Ruckus AP from Unleashed to ZoneDirector-managed

Here is the method to convert a Ruckus Unleashed AP to one which can be managed by a Ruckus ZoneDirector controller: - Login to https://support.ruckuswireless.com/ - Click "Downloads" - Choose the correct product, e.g. Ruckus R550 - Choose a "standalone" version along the lines of 118.2.0.0.875.bl7 or something similar - Agree to terms and download the software - Connect to the AP's IP address - It should open the setup wizard, showing "Unleashed Installation" - Click "Local Upgrade" - Choose the firmware image file you just downloaded - It will upload, process, and then be ready for upgrade when you click "Yes" - After this, the ZD should detect the new AP - The new AP will then need to be approved - The new AP will then be upgraded to the correct software by the ZD - The new AP will then reboot and should be ready to use - Don't forget that, for the ZD to even detect, let alone manage the new AP, it must have enough licenses