I am using WUA (Windows Update Agent API) to check for the installed updates on my computer.
What I found interesting is the Date property value (http://msdn.microsoft.com/en-us/library/windows/desktop/aa386400(v=vs.85).aspx) is hugely different from the real installation time, i.e local time. For example, for one patch "Security Update for Microsoft .NET Framework 3.5.1 on Windows 7 and Windows Server 2008 R2 SP1 for x64-based Systems (KB2789645) ", using WUA API, I see the Date value = '2/21/2013 11:04:30 PM', while on my computer, I found in the EventLog, it is logged as "2/21/2013 4:51:58 PM". I initially thought the WUA API is using UTC time, but if I change the UTC time to local time (I am at Pacific time zone), then '2/21/2013 11:04:30 PM' (UTC) will be equal to '2/21/2013 3:04:30 PM' (local), still far away from the eventlog's "2/21/2013 4:51:58 PM".
Does anyone know what this Date property of IUpdateHistoryEntry really means? According to MS in the above msdn link, the Date property is
Property AccessType Description
Date Read-only Gets the date and the time an update was applied.
Thanks in advance for your help. I am puzzled by this difference.
Kind regards,
JYao
Related
I have been using WMI to retrieve the antivirus/antispyware/firewall products registered in the Windows Security Center. Since last month duplicate entries for ESET Internet Security started showing up (since v12.2.29). Somebody else said it also happened with McAfee.
ESET said that since Windows 8, WMI should not be used to check this as there is new API made specifically for this. Apparently this is IWscProduct, which indeed does not seem to report the duplicates.
But I want to know if WMI can still be used as well, as this is required for pre-Win8 and I have not seen any reports that it shouldn't be used in Win8+ anymore.
To test, use this command line to check the installed antivirus products:
WMIC /Node:localhost /Namespace:\\root\SecurityCenter2 Path AntiVirusProduct Get /Format:List
And this is what it outputs on my computer:
displayName=Windows Defender
instanceGuid={D68DDC3A-831F-4fae-9E44-DA132C1ACF46}
pathToSignedProductExe=windowsdefender://
pathToSignedReportingExe=%ProgramFiles%\Windows Defender\MsMpeng.exe
productState=393472
timestamp=Fri, 11 Oct 2019 16:09:34 GMT
displayName=ESET Security
instanceGuid={885D845F-AF19-0124-FECE-FFF49D00F440}
pathToSignedProductExe=C:\Program Files\ESET\ESET Security\ecmds.exe
pathToSignedReportingExe=C:\Program Files\ESET\ESET Security\ekrn.exe
productState=266240
timestamp=Mon, 11 Nov 2019 08:20:20 GMT
displayName=ESET Security
instanceGuid={EC1D6F37-E411-475A-DF50-12FF7FE4AC70}
pathToSignedProductExe=C:\Program Files\ESET\ESET Security\ecmds.exe
pathToSignedReportingExe=C:\Program Files\ESET\ESET Security\ekrn.exe
productState=266240
timestamp=Wed, 02 Oct 2019 07:08:22 GMT
Windows Defender is disabled and as you can see, the second ESET entry has not been touched for over a month now.
Now my questions are:
Can WMI(C) still be used to query the Windows Security Center in Win8+?
If not, has anybody seen any reports/warnings about this?
Or is this a Microsoft bug?
Or is ESET (and McAfee?) doing something wrong (registering a new version without deregistering the old one)?
Any help is much appreciated.
I am using the Media Creation Tool to download an ISO image of Windows 10 - the download is still running (as of 1659 July 24, 2016.
I will use that ISO to create an install DVD.
My question is: If I try to use the DVD to upgrade to Windows 10 after July 29, 2016, will it do a free upgrade?
Or does the installation itself have to occur before July 29th?
If it isn't obvious to you what the answer is, I'd call the Microsoft Marketing Department during business hours on the West Coast.
But my instincts tell me that they're going to ping a server at Microsoft, and that said server is going to have a clock . . .
. . . so, if it matters, in some significant way, whether-or-not the process will work after this date, I reckon you've got exactly one week to find out, "straight from the horse's mouth." :-)
"Don't guess, when you can ask."
I am try to install oracle developer suite 10g (32bit) on window 7.
Actually I want to install oracle form which is in complete option of Installation window.
I have already solved swap memory issue and compatibility issues.
oracle developer suite 10g Installer met all Requirement.
I have passed all requirement with is follow snap-shot:
After I got Installation window, I select Complete Installation option.
I am reached up to follow window but few second it get Automatically close :
Two-Three time I have tried to installation but every time installation get close before coming Oracle product installation list.
I am completely blank, why this ?
Please some body help me for solving this issue.
You can troubleshoot the installation based on installation log files which are available in
oracle_inventory\logs\installActionstimestamp.log
oracle_inventory\logs\oraInstalltimestamp.err
oracle_inventory\logs\oraInstalltimestamp.out
where
The form of timestamp in the file log name is
yyyy-mm-dd_hh-mm-ss[AM|PM] where:
yyyy is the current year, for example 2003
mm is the current month number, for example 07 for July
dd is the current day number, for example 15 for the fifteenth
hh, mm, and ss are the hour, minute, and second at which the installation started
[AM/PM] is either AM or PM, depending on when the installation started
and
the location of the oracle_inventory directory is specified
during the first installation of an Oracle product on your computer
(for example oracle client or oracle database etc)
In My system the location is
C:\Program Files (x86)\Oracle\Inventory\logs
Once you get the installation log you can trouble shoot the issue using search engine or post in oracle forums
I have got the solution for the above issue.
I have uninstalled the oracle 11g database.
installed the oracle 10g forms and report.
installed the oracle 11g DB.
Now it's working fine.
It is building the builds at a time that is five hours ahead of the actual time. I have remoted to the Server box and the time on it is correct. How can I get TeamCity to build in the correct timezone?
Usually, TeamCity shows the time in the Server's local time.
On the My Settings & Tools page, there is a setting, which enables showing times at current user local time. So if you've enabled this setting and your machine is 5 hours ahead from Server's time, you'll see time which is 5 hours ahead.
I have PostgreSQL installed in several customers (always in Windows).
I'm facing some situation with current_timestamp, wich depending of "Windows Auto Adjust DST", is returning "wrong" time, even if I set the same timezone used by windows (in this case 'BRAZIL/EAST').
The problem is: I can tell to the users to set (or unset) Auto DST. So, is there any way to workaround this? I mean, some kind of setting on PG that will allways get the exactly same time shown on taskbar clock?
Thanks in advance.
Does it display a good time if you use the following?
select current_timestamp at time zone 'BRAZIL/EAST' as now;
Maybe your Windows clients or server have timezone set wrong or outdated timezone data. Is your server supported (at least Windows 2003 SP2) and updated with WindowsUpdate? Is your client at least Windows XP SP3 and WindowsUpdated too.
What the following query returns when connected locally from server and from remote client?
SELECT current_setting('TIMEZONE');
Christian,
i've faced the same problem.
try setting this in postgresql.conf:
timezone = 'BRAZIL/EAST'
hope that helps! ;)