Occasionally, you might discover a client that isn’t automatically installing updates correctly. Such clients are typically identified during software update audits. To identify the source of the problem, follow these steps:
1. Determine the last time the client was updated. This can be done in two different ways—by checking the client’s registry (the most reliable technique) or, if you use Windows Server Update Services (WSUS), by checking the Reports page on the WSUS Web site.
* To check the client’s registry, open the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\Results registry key. In each of the Detect, Download, and Install subkeys, examine the LastSuccessTime entry to determine when updates were last detected, downloaded, and installed. More »
Windows 7 RC, as well as its precursor, Windows Vista, and the R2 and RTM/SP1 releases of Windows Server 2008 are immune to a zero-day vulnerability affecting DirectX on older versions of Windows. The security hole makes Windows 2000 Service Pack 4, Windows XP (including SP2 and SP3), and Windows Server 2003 vulnerable to exploits but not the later versions of the Windows client and server operating systems, since the code containing the flaw was removed in Vista.
Christopher Budd, security response communications lead for Microsoft, confirmed that the company was “aware of limited, active attacks that exploit this vulnerability.” Budd explained that the vulnerable code was contained in the QuickTime parser in Microsoft DirectShow. DirectX 7.0, DirectX 8.1 and DirectX 9.0 are impacted.
“An attacker would try and exploit the vulnerability by crafting a specially formed video file and then posting it on a website or sending it as an attachment in e-mail. While this isn’t a browser vulnerability, because the vulnerability is in DirectShow, a browser-based vector is potentially accessible through any browser using media plug-ins that use DirectShow. Also, we’ve verified that it is possible to direct calls to DirectShow specifically, even if Apple’s QuickTime (which is not vulnerable) is installed,” Budd stated. More »
We all use windows run prompt to launch various windows utilities like command prompt, msconfig but whenever we type a command in run prompt it gets saved in Windows as Run History as Run MRU (Most Recently Used) List.
Many of my friends gets annoyed to see recently typed commands in windows run as they do not want others to see what they had typed in run.
Today, we will tell you all the ways to clear run prompt history in Windows XP and Vista.
There two methods to clear the windows run history, the first method is via windows registry to clear windows run and second method involves a free utility MRU Blaster which lets you clear windows run history
Let’s discuss both of these methods to clear the recently typed commands in run. More »
Have you ever clicked on the Shutdown or Restart button in Windows and have absolutely nothing happen? Sometimes Windows gets stuck because of some process that has become hung, meaning it is running, but can’t be ended in the normal way.
Hence, you try to shutdown or restart your computer, nothing happens at all. If you’re lucky, after a minute or two, you might see a message pop up saying that a process is hung and you can either let Windows try to end it or you can press End Now. I always prefer End Now!
Unfortunately, sometimes Windows simply refuses to shutdown and it won’t give you any kind of message. Don’t worry, the underlying cause of this is still a hung process, so all you need to do is kill the non-critical Windows processes one by one or modify the registry so that a hung process is automatically ended without manual intervention. I’ll explain both methods. More »
Registry tweaks can fix problems, boost performance and improve Windows features, and the risks are minimal as long as you follow our advice.
There are many ways to change your settings and your applications within Windows. You might click Edit > Preferences or Tools > Options, right-click on a system tray icon, or just poke around in your Control Panel. But the end result is almost always the same. When you’ve tweaked an option and clicked OK, the new setting will be stored in a central database called the registry.
Normally you don’t have to worry about low-level technical details of individual registry settings. But occasionally they can come in useful. If a program won’t start or can’t be reinstalled, for instance, it could be down to a corrupt registry setting: change it and you might fix the problem. Other applications have useful settings that can only be accessed from the registry, too.
There is a potential down side, though. If you delete the wrong registry setting you could corrupt an application, and even prevent Windows from loading on your next reboot. But then Windows Explorer can be dangerous, too, if you start randomly deleting things from the Windows or Program Files folders. Don’t worry though, as long as you’re cautious and sensible – registry editing actually poses very little risk. More »