Tag Info

New answers tagged


This is the event you are looking for, down the keyword it triggers. I believe it is safe to assume it will be identical on all Windows systems at least as old as Windows 7 or newer. PS:I hope this answer doesn't get downvoted because the screenshot is from a Windows 7 machine, as opposed to a server product.


Apparently this is an intermittent issue with some 2008/2008 R2 environments after a heavy round of updates [insert favourite windows update débâcle anecdote here]. Try this solution on one of your 'less critical' servers, but it is relatively non-aggressive and shouldn't cause any more harm in the event that it doesn't help your particular issue. let the ...


I know mfinni beat me to the punch, but I'm just going to +1 for WSUS. Specifically: Let's assume that you have multiple servers, including test and production. Let's also assume that test has similar hardware to production (which isn't a safe assumption, I know, but let's go with it--it's nice but not necessary). You could set up the following scenario ...


In my experience, one of two things occurs: These updates were found to be no longer necessary, so they failed and don't come back. After a reboot or running a Windows update check again, they come back. You can check the failure of the update and lookup the error code. You can get the error code in the History view. Double-click the failed update to get ...


This is entirely up to your business and the policy that you have set out for updating your servers. At the very least you should install security updates and perform any other patches like .NET framework updates in a testing environment first before updating production servers.


The generic answer is it is a good practice to keep your servers updated. But pay attention to a few things: Updates may cause the server to be sluggish during installation, or even cause some downtime if they require reboot(s). You should plan to do them out of office work hours. Updates have some risk associated. They might break your server, or cause ...


Short answer - yes. Most of the Windows Updates are security related. Not having the patches means you're vulnerable. Longer answer - you need a procedure that covers this sort of thing. It's more rare these days, but sometimes a patch can break things, or change behavior in such a way that it's broken as far as your company is concerned. You should be ...


In powershell you can do that : Get-WmiObject -Class "win32_quickfixengineering" easy and fast .


You can refer to the last successful update install time: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\Results\Install REG_SZ: LastSuccessTime This is a datetime value formatted as yyyy-MM-dd HH:mm:ss.

Top 50 recent answers are included