Updates were installed:  Date different

I have a odd issue, I think.    My updates are getting applied.  but, it shows in the history correctly.  but, the "Updates were installed"  is different.   I have other users that show the same thing.   The "Updates were installed"  can be like a month or so later. 

In this example: it says my updates were installed  6/27/2013,  but my history shown below, shows the correct date  7/15/2013 which is correct.  

July 19th, 2013 8:24am

Yes, I know this is an old post, Im clean them up.

Did you figure this out, if so how?

Free Windows Admin Tool Kit Click here and download it now
July 27th, 2013 12:36pm

Yes, I know this is an old post, just trying to clean up old posts. Did you figure this out, if so how did you solve it?

Since no else has replied, I recommend that you contact Microsoft Support (CSS), they should be able to help you out.

August 10th, 2013 8:22am

no, no ever replied.  
Free Windows Admin Tool Kit Click here and download it now
August 10th, 2013 8:25am

no, no ever replied.  

Ok, I recommend that you contact CSS for support.
August 10th, 2013 10:14am

I am experiencing the same issue with System Center 2012. Did you ever find a solution?

Any help would be appreciated.

Thank you

Free Windows Admin Tool Kit Click here and download it now
November 29th, 2013 7:50pm

Hello,   I never did find a solution.   The behavior is still the same..  

thanks 

November 29th, 2013 7:54pm

Old post indeed, yet I've hit the same thing recently. I'm using a Powershell script to install updates against a batch of servers, and I've seen that even if all is installed successfully, the "Updates were installed" never gets updated.

I went ahead and contacted Microsoft Premier Support and the technician there and - after checking with someone who is actually involved with developing the Windows Updates component - he told me that this is by design. What happens is that the date will be updated only by Automatic Updates or during an interactive session, and updates processed through other means, such as scripts, don't get to trigger this. The reasoning behind this eludes me (a user can select to install one update only and leave the system exposed vs. a script/SCCM patching 100% - the first would be "good" and second "bad" according to this logic).

I agree that taking a look inside Control Panel and seeing 2012 as the year when "Updates were installed" is a big red flag - especially for an auditor (not to mention the explanations one has to give them for reassurance), but there's always the Powershell one liner which will yield when the last update was installed:

(Get-HotFix | Sort-Object InstalledOn -Descending)[0]

Free Windows Admin Tool Kit Click here and download it now
March 27th, 2015 2:51pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics