Guest Rosa Posted September 27, 2007 Posted September 27, 2007 Where does the log file for MS07-028 Vulnerability in CAPICOM Could Allow Remote Code Execution (931906) get written to? I've installed the update and cannot find a log anywhere on the server. Thanks.
Guest Meinolf Weber Posted September 27, 2007 Posted September 27, 2007 Re: MS07-028 Log File Hello Rosa, Logfiles you find under C:\windows with the kb at beginning. Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights. > Where does the log file for MS07-028 Vulnerability in CAPICOM Could > Allow Remote Code Execution (931906) get written to? I've installed > the update and cannot find a log anywhere on the server. Thanks. >
Guest Rosa Posted September 27, 2007 Posted September 27, 2007 Re: MS07-028 Log File Thanks for the reply Meinolf - the problem is, this particular update (KB931906) is not getting written to a log file. "Meinolf Weber" wrote: > Hello Rosa, > > Logfiles you find under C:\windows with the kb at beginning. > > Best regards > > Meinolf Weber > Disclaimer: This posting is provided "AS IS" with no warranties, and confers > no rights. > > > Where does the log file for MS07-028 Vulnerability in CAPICOM Could > > Allow Remote Code Execution (931906) get written to? I've installed > > the update and cannot find a log anywhere on the server. Thanks. > > > > >
Guest Meinolf Weber Posted September 27, 2007 Posted September 27, 2007 Re: MS07-028 Log File Hello Rosa, If you just will see if it is installed correctly you can follow this: File Name Version Date Time Size License.mht NA 26-Feb-2007 23:16 142,534 License.rtf NA 26-Feb-2007 23:16 134,577 CAPICOM.dll 2.1.0.2 11-Apr-2007 18:11 511,328 Verifying that the Update Has Been Applied . File Version Verification Note Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps. 1. Click Start, and then click Search. 2. In the Search Results pane, click All files and folders under Search Companion. 3. In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search. 4. In the list of files, right-click a file name from the appropriate file information table, and then click Properties. Note Depending on the version of the operating system or programs installed, some of the files that are listed in the file information table may not be installed. 5. On the Version tab, determine the version of the file that is installed on your computer by comparing it to the version that is documented in the appropriate file information table. Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation. . Registry Key Verification You may also be able to verify the files that this security update has installed by reviewing the following registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CAPICOM.Certificates.4\CLSID Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights. > Thanks for the reply Meinolf - the problem is, this particular update > (KB931906) is not getting written to a log file. > > "Meinolf Weber" wrote: > >> Hello Rosa, >> >> Logfiles you find under C:\windows with the kb at beginning. >> >> Best regards >> >> Meinolf Weber >> Disclaimer: This posting is provided "AS IS" with no warranties, and >> confers >> no rights. >>> Where does the log file for MS07-028 Vulnerability in CAPICOM Could >>> Allow Remote Code Execution (931906) get written to? I've installed >>> the update and cannot find a log anywhere on the server. Thanks. >>>
Guest Rosa Posted September 27, 2007 Posted September 27, 2007 Re: MS07-028 Log File Meinholf - thanks again for the reply/effort. The problem is, I run a batch file that verifies patch installs based on KB logs. I really need to find out where the log file is maintained - maybe there isn't a log file for this patch (for what reason, I'm not sure). Rosa "Meinolf Weber" wrote: > Hello Rosa, > > If you just will see if it is installed correctly you can follow this: > > > File Name Version Date Time Size > License.mht > NA > 26-Feb-2007 > 23:16 > 142,534 > > License.rtf > NA > 26-Feb-2007 > 23:16 > 134,577 > > CAPICOM.dll > 2.1.0.2 > 11-Apr-2007 > 18:11 > 511,328 > > > Verifying that the Update Has Been Applied > > . File Version Verification > > Note Because there are several versions of Microsoft Windows, the following > steps may be different on your computer. If they are, see your product documentation > to complete these steps. > > 1. > Click Start, and then click Search. > > 2. > In the Search Results pane, click All files and folders under Search Companion. > > 3. > In the All or part of the file name box, type a file name from the appropriate > file information table, and then click Search. > > 4. > In the list of files, right-click a file name from the appropriate file > information table, and then click Properties. > > Note Depending on the version of the operating system or programs installed, > some of the files that are listed in the file information table may not be > installed. > > 5. > On the Version tab, determine the version of the file that is installed > on your computer by comparing it to the version that is documented in the > appropriate file information table. > > Note Attributes other than the file version may change during installation. > Comparing other file attributes to the information in the file information > table is not a supported method of verifying that the update has been applied. > Also, in certain cases, files may be renamed during installation. If the > file or version information is not present, use one of the other available > methods to verify update installation. > > > . Registry Key Verification > > You may also be able to verify the files that this security update has installed > by reviewing the following registry key: > > HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CAPICOM.Certificates.4\CLSID > > > > Best regards > > Meinolf Weber > Disclaimer: This posting is provided "AS IS" with no warranties, and confers > no rights. > > > Thanks for the reply Meinolf - the problem is, this particular update > > (KB931906) is not getting written to a log file. > > > > "Meinolf Weber" wrote: > > > >> Hello Rosa, > >> > >> Logfiles you find under C:\windows with the kb at beginning. > >> > >> Best regards > >> > >> Meinolf Weber > >> Disclaimer: This posting is provided "AS IS" with no warranties, and > >> confers > >> no rights. > >>> Where does the log file for MS07-028 Vulnerability in CAPICOM Could > >>> Allow Remote Code Execution (931906) get written to? I've installed > >>> the update and cannot find a log anywhere on the server. Thanks. > >>> > > >
Guest Meinolf Weber Posted September 27, 2007 Posted September 27, 2007 Re: MS07-028 Log File Hello Rosa, This patch is for different software, so what do you use. Maybe i can try it out. CAPICOM - Download the update . Platform SDK Redistributable: CAPICOM - Download the update . BizTalk Server 2004 Service Pack 1 - Download the update . BizTalk Server 2004 Service Pack 2 - Download the update Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights. > Meinholf - thanks again for the reply/effort. The problem is, I run a > batch file that verifies patch installs based on KB logs. I really > need to find out where the log file is maintained - maybe there isn't > a log file for this patch (for what reason, I'm not sure). > > Rosa > > "Meinolf Weber" wrote: > >> Hello Rosa, >> >> If you just will see if it is installed correctly you can follow >> this: >> >> File Name Version Date Time Size >> License.mht >> NA >> 26-Feb-2007 >> 23:16 >> 142,534 >> License.rtf >> NA >> 26-Feb-2007 >> 23:16 >> 134,577 >> CAPICOM.dll >> 2.1.0.2 >> 11-Apr-2007 >> 18:11 >> 511,328 >> Verifying that the Update Has Been Applied >> >> . File Version Verification >> >> Note Because there are several versions of Microsoft Windows, the >> following steps may be different on your computer. If they are, see >> your product documentation to complete these steps. >> >> 1. >> Click Start, and then click Search. >> 2. >> In the Search Results pane, click All files and folders under Search >> Companion. >> 3. >> In the All or part of the file name box, type a file name from the >> appropriate >> file information table, and then click Search. >> 4. >> In the list of files, right-click a file name from the appropriate >> file >> information table, and then click Properties. >> Note Depending on the version of the operating system or programs >> installed, some of the files that are listed in the file information >> table may not be installed. >> >> 5. >> On the Version tab, determine the version of the file that is >> installed >> on your computer by comparing it to the version that is documented in >> the >> appropriate file information table. >> Note Attributes other than the file version may change during >> installation. Comparing other file attributes to the information in >> the file information table is not a supported method of verifying >> that the update has been applied. Also, in certain cases, files may >> be renamed during installation. If the file or version information is >> not present, use one of the other available methods to verify update >> installation. >> >> . Registry Key Verification >> >> You may also be able to verify the files that this security update >> has installed by reviewing the following registry key: >> >> HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CAPICOM.Certificates.4\CLSID >> >> Best regards >> >> Meinolf Weber >> Disclaimer: This posting is provided "AS IS" with no warranties, and >> confers >> no rights. >>> Thanks for the reply Meinolf - the problem is, this particular >>> update (KB931906) is not getting written to a log file. >>> >>> "Meinolf Weber" wrote: >>> >>>> Hello Rosa, >>>> >>>> Logfiles you find under C:\windows with the kb at beginning. >>>> >>>> Best regards >>>> >>>> Meinolf Weber >>>> Disclaimer: This posting is provided "AS IS" with no warranties, >>>> and >>>> confers >>>> no rights. >>>>> Where does the log file for MS07-028 Vulnerability in CAPICOM >>>>> Could Allow Remote Code Execution (931906) get written to? I've >>>>> installed the update and cannot find a log anywhere on the server. >>>>> Thanks. >>>>>
Guest Rosa Posted September 27, 2007 Posted September 27, 2007 Re: MS07-028 Log File I am using the "CAPICOM" download (CAPICOM-KB931906-v2102.exe), though it looks like the links all point to the same download. "Meinolf Weber" wrote: > Hello Rosa, > > This patch is for different software, so what do you use. Maybe i can try > it out. > > > CAPICOM - Download the update > > . Platform SDK Redistributable: CAPICOM - Download the update > > . BizTalk Server 2004 Service Pack 1 - Download the update > > . BizTalk Server 2004 Service Pack 2 - Download the update > > > > > Best regards > > Meinolf Weber > Disclaimer: This posting is provided "AS IS" with no warranties, and confers > no rights. > > > Meinholf - thanks again for the reply/effort. The problem is, I run a > > batch file that verifies patch installs based on KB logs. I really > > need to find out where the log file is maintained - maybe there isn't > > a log file for this patch (for what reason, I'm not sure). > > > > Rosa > > > > "Meinolf Weber" wrote: > > > >> Hello Rosa, > >> > >> If you just will see if it is installed correctly you can follow > >> this: > >> > >> File Name Version Date Time Size > >> License.mht > >> NA > >> 26-Feb-2007 > >> 23:16 > >> 142,534 > >> License.rtf > >> NA > >> 26-Feb-2007 > >> 23:16 > >> 134,577 > >> CAPICOM.dll > >> 2.1.0.2 > >> 11-Apr-2007 > >> 18:11 > >> 511,328 > >> Verifying that the Update Has Been Applied > >> > >> . File Version Verification > >> > >> Note Because there are several versions of Microsoft Windows, the > >> following steps may be different on your computer. If they are, see > >> your product documentation to complete these steps. > >> > >> 1. > >> Click Start, and then click Search. > >> 2. > >> In the Search Results pane, click All files and folders under Search > >> Companion. > >> 3. > >> In the All or part of the file name box, type a file name from the > >> appropriate > >> file information table, and then click Search. > >> 4. > >> In the list of files, right-click a file name from the appropriate > >> file > >> information table, and then click Properties. > >> Note Depending on the version of the operating system or programs > >> installed, some of the files that are listed in the file information > >> table may not be installed. > >> > >> 5. > >> On the Version tab, determine the version of the file that is > >> installed > >> on your computer by comparing it to the version that is documented in > >> the > >> appropriate file information table. > >> Note Attributes other than the file version may change during > >> installation. Comparing other file attributes to the information in > >> the file information table is not a supported method of verifying > >> that the update has been applied. Also, in certain cases, files may > >> be renamed during installation. If the file or version information is > >> not present, use one of the other available methods to verify update > >> installation. > >> > >> . Registry Key Verification > >> > >> You may also be able to verify the files that this security update > >> has installed by reviewing the following registry key: > >> > >> HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CAPICOM.Certificates.4\CLSID > >> > >> Best regards > >> > >> Meinolf Weber > >> Disclaimer: This posting is provided "AS IS" with no warranties, and > >> confers > >> no rights. > >>> Thanks for the reply Meinolf - the problem is, this particular > >>> update (KB931906) is not getting written to a log file. > >>> > >>> "Meinolf Weber" wrote: > >>> > >>>> Hello Rosa, > >>>> > >>>> Logfiles you find under C:\windows with the kb at beginning. > >>>> > >>>> Best regards > >>>> > >>>> Meinolf Weber > >>>> Disclaimer: This posting is provided "AS IS" with no warranties, > >>>> and > >>>> confers > >>>> no rights. > >>>>> Where does the log file for MS07-028 Vulnerability in CAPICOM > >>>>> Could Allow Remote Code Execution (931906) get written to? I've > >>>>> installed the update and cannot find a log anywhere on the server. > >>>>> Thanks. > >>>>> > > >
Guest Meinolf Weber Posted September 28, 2007 Posted September 28, 2007 Re: MS07-028 Log File Hello Rosa, I tested a bit with it and it installes a folder c:\program files\microsoft CPAICOM 2.1.0.2 with the needed files for the update. More i can not find on my complete machine. Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights. > I am using the "CAPICOM" download (CAPICOM-KB931906-v2102.exe), though > it looks like the links all point to the same download. > > "Meinolf Weber" wrote: > >> Hello Rosa, >> >> This patch is for different software, so what do you use. Maybe i can >> try it out. >> >> CAPICOM - Download the update >> >> . Platform SDK Redistributable: CAPICOM - Download the update >> >> . BizTalk Server 2004 Service Pack 1 - Download the update >> >> . BizTalk Server 2004 Service Pack 2 - Download the update >> >> Best regards >> >> Meinolf Weber >> Disclaimer: This posting is provided "AS IS" with no warranties, and >> confers >> no rights. >>> Meinholf - thanks again for the reply/effort. The problem is, I run >>> a batch file that verifies patch installs based on KB logs. I >>> really need to find out where the log file is maintained - maybe >>> there isn't a log file for this patch (for what reason, I'm not >>> sure). >>> >>> Rosa >>> >>> "Meinolf Weber" wrote: >>> >>>> Hello Rosa, >>>> >>>> If you just will see if it is installed correctly you can follow >>>> this: >>>> >>>> File Name Version Date Time Size >>>> License.mht >>>> NA >>>> 26-Feb-2007 >>>> 23:16 >>>> 142,534 >>>> License.rtf >>>> NA >>>> 26-Feb-2007 >>>> 23:16 >>>> 134,577 >>>> CAPICOM.dll >>>> 2.1.0.2 >>>> 11-Apr-2007 >>>> 18:11 >>>> 511,328 >>>> Verifying that the Update Has Been Applied >>>> . File Version Verification >>>> >>>> Note Because there are several versions of Microsoft Windows, the >>>> following steps may be different on your computer. If they are, see >>>> your product documentation to complete these steps. >>>> >>>> 1. >>>> Click Start, and then click Search. >>>> 2. >>>> In the Search Results pane, click All files and folders under >>>> Search >>>> Companion. >>>> 3. >>>> In the All or part of the file name box, type a file name from the >>>> appropriate >>>> file information table, and then click Search. >>>> 4. >>>> In the list of files, right-click a file name from the appropriate >>>> file >>>> information table, and then click Properties. >>>> Note Depending on the version of the operating system or programs >>>> installed, some of the files that are listed in the file >>>> information >>>> table may not be installed. >>>> 5. >>>> On the Version tab, determine the version of the file that is >>>> installed >>>> on your computer by comparing it to the version that is documented >>>> in >>>> the >>>> appropriate file information table. >>>> Note Attributes other than the file version may change during >>>> installation. Comparing other file attributes to the information in >>>> the file information table is not a supported method of verifying >>>> that the update has been applied. Also, in certain cases, files may >>>> be renamed during installation. If the file or version information >>>> is >>>> not present, use one of the other available methods to verify >>>> update >>>> installation. >>>> . Registry Key Verification >>>> >>>> You may also be able to verify the files that this security update >>>> has installed by reviewing the following registry key: >>>> >>>> HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CAPICOM.Certificates.4\CLSID >>>> >>>> Best regards >>>> >>>> Meinolf Weber >>>> Disclaimer: This posting is provided "AS IS" with no warranties, >>>> and >>>> confers >>>> no rights. >>>>> Thanks for the reply Meinolf - the problem is, this particular >>>>> update (KB931906) is not getting written to a log file. >>>>> >>>>> "Meinolf Weber" wrote: >>>>> >>>>>> Hello Rosa, >>>>>> >>>>>> Logfiles you find under C:\windows with the kb at beginning. >>>>>> >>>>>> Best regards >>>>>> >>>>>> Meinolf Weber >>>>>> Disclaimer: This posting is provided "AS IS" with no warranties, >>>>>> and >>>>>> confers >>>>>> no rights. >>>>>>> Where does the log file for MS07-028 Vulnerability in CAPICOM >>>>>>> Could Allow Remote Code Execution (931906) get written to? I've >>>>>>> installed the update and cannot find a log anywhere on the >>>>>>> server. Thanks. >>>>>>>
Guest Rosa Posted September 28, 2007 Posted September 28, 2007 Re: MS07-028 Log File Meinolf, I can work with that. Thanks for your help, I really appreciate it. Rosa "Meinolf Weber" wrote: > Hello Rosa, > > I tested a bit with it and it installes a folder c:\program files\microsoft > CPAICOM 2.1.0.2 with the needed files for the update. More i can not find > on my complete machine. > > Best regards > > Meinolf Weber > Disclaimer: This posting is provided "AS IS" with no warranties, and confers > no rights. > > > I am using the "CAPICOM" download (CAPICOM-KB931906-v2102.exe), though > > it looks like the links all point to the same download. > > > > "Meinolf Weber" wrote: > > > >> Hello Rosa, > >> > >> This patch is for different software, so what do you use. Maybe i can > >> try it out. > >> > >> CAPICOM - Download the update > >> > >> . Platform SDK Redistributable: CAPICOM - Download the update > >> > >> . BizTalk Server 2004 Service Pack 1 - Download the update > >> > >> . BizTalk Server 2004 Service Pack 2 - Download the update > >> > >> Best regards > >> > >> Meinolf Weber > >> Disclaimer: This posting is provided "AS IS" with no warranties, and > >> confers > >> no rights. > >>> Meinholf - thanks again for the reply/effort. The problem is, I run > >>> a batch file that verifies patch installs based on KB logs. I > >>> really need to find out where the log file is maintained - maybe > >>> there isn't a log file for this patch (for what reason, I'm not > >>> sure). > >>> > >>> Rosa > >>> > >>> "Meinolf Weber" wrote: > >>> > >>>> Hello Rosa, > >>>> > >>>> If you just will see if it is installed correctly you can follow > >>>> this: > >>>> > >>>> File Name Version Date Time Size > >>>> License.mht > >>>> NA > >>>> 26-Feb-2007 > >>>> 23:16 > >>>> 142,534 > >>>> License.rtf > >>>> NA > >>>> 26-Feb-2007 > >>>> 23:16 > >>>> 134,577 > >>>> CAPICOM.dll > >>>> 2.1.0.2 > >>>> 11-Apr-2007 > >>>> 18:11 > >>>> 511,328 > >>>> Verifying that the Update Has Been Applied > >>>> . File Version Verification > >>>> > >>>> Note Because there are several versions of Microsoft Windows, the > >>>> following steps may be different on your computer. If they are, see > >>>> your product documentation to complete these steps. > >>>> > >>>> 1. > >>>> Click Start, and then click Search. > >>>> 2. > >>>> In the Search Results pane, click All files and folders under > >>>> Search > >>>> Companion. > >>>> 3. > >>>> In the All or part of the file name box, type a file name from the > >>>> appropriate > >>>> file information table, and then click Search. > >>>> 4. > >>>> In the list of files, right-click a file name from the appropriate > >>>> file > >>>> information table, and then click Properties. > >>>> Note Depending on the version of the operating system or programs > >>>> installed, some of the files that are listed in the file > >>>> information > >>>> table may not be installed. > >>>> 5. > >>>> On the Version tab, determine the version of the file that is > >>>> installed > >>>> on your computer by comparing it to the version that is documented > >>>> in > >>>> the > >>>> appropriate file information table. > >>>> Note Attributes other than the file version may change during > >>>> installation. Comparing other file attributes to the information in > >>>> the file information table is not a supported method of verifying > >>>> that the update has been applied. Also, in certain cases, files may > >>>> be renamed during installation. If the file or version information > >>>> is > >>>> not present, use one of the other available methods to verify > >>>> update > >>>> installation. > >>>> . Registry Key Verification > >>>> > >>>> You may also be able to verify the files that this security update > >>>> has installed by reviewing the following registry key: > >>>> > >>>> HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CAPICOM.Certificates.4\CLSID > >>>> > >>>> Best regards > >>>> > >>>> Meinolf Weber > >>>> Disclaimer: This posting is provided "AS IS" with no warranties, > >>>> and > >>>> confers > >>>> no rights. > >>>>> Thanks for the reply Meinolf - the problem is, this particular > >>>>> update (KB931906) is not getting written to a log file. > >>>>> > >>>>> "Meinolf Weber" wrote: > >>>>> > >>>>>> Hello Rosa, > >>>>>> > >>>>>> Logfiles you find under C:\windows with the kb at beginning. > >>>>>> > >>>>>> Best regards > >>>>>> > >>>>>> Meinolf Weber > >>>>>> Disclaimer: This posting is provided "AS IS" with no warranties, > >>>>>> and > >>>>>> confers > >>>>>> no rights. > >>>>>>> Where does the log file for MS07-028 Vulnerability in CAPICOM > >>>>>>> Could Allow Remote Code Execution (931906) get written to? I've > >>>>>>> installed the update and cannot find a log anywhere on the > >>>>>>> server. Thanks. > >>>>>>> > > >
Guest Meinolf Weber Posted September 28, 2007 Posted September 28, 2007 Re: MS07-028 Log File Hello Rosa, You're welcome. Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights. > Meinolf, > > I can work with that. > > Thanks for your help, I really appreciate it. > > Rosa > > "Meinolf Weber" wrote: > >> Hello Rosa, >> >> I tested a bit with it and it installes a folder c:\program >> files\microsoft CPAICOM 2.1.0.2 with the needed files for the update. >> More i can not find on my complete machine. >> >> Best regards >> >> Meinolf Weber >> Disclaimer: This posting is provided "AS IS" with no warranties, and >> confers >> no rights. >>> I am using the "CAPICOM" download (CAPICOM-KB931906-v2102.exe), >>> though it looks like the links all point to the same download. >>> >>> "Meinolf Weber" wrote: >>> >>>> Hello Rosa, >>>> >>>> This patch is for different software, so what do you use. Maybe i >>>> can try it out. >>>> >>>> CAPICOM - Download the update >>>> >>>> . Platform SDK Redistributable: CAPICOM - Download the update >>>> >>>> . BizTalk Server 2004 Service Pack 1 - Download the update >>>> >>>> . BizTalk Server 2004 Service Pack 2 - Download the update >>>> >>>> Best regards >>>> >>>> Meinolf Weber >>>> Disclaimer: This posting is provided "AS IS" with no warranties, >>>> and >>>> confers >>>> no rights. >>>>> Meinholf - thanks again for the reply/effort. The problem is, I >>>>> run a batch file that verifies patch installs based on KB logs. I >>>>> really need to find out where the log file is maintained - maybe >>>>> there isn't a log file for this patch (for what reason, I'm not >>>>> sure). >>>>> >>>>> Rosa >>>>> >>>>> "Meinolf Weber" wrote: >>>>> >>>>>> Hello Rosa, >>>>>> >>>>>> If you just will see if it is installed correctly you can follow >>>>>> this: >>>>>> >>>>>> File Name Version Date Time Size >>>>>> License.mht >>>>>> NA >>>>>> 26-Feb-2007 >>>>>> 23:16 >>>>>> 142,534 >>>>>> License.rtf >>>>>> NA >>>>>> 26-Feb-2007 >>>>>> 23:16 >>>>>> 134,577 >>>>>> CAPICOM.dll >>>>>> 2.1.0.2 >>>>>> 11-Apr-2007 >>>>>> 18:11 >>>>>> 511,328 >>>>>> Verifying that the Update Has Been Applied >>>>>> . File Version Verification >>>>>> Note Because there are several versions of Microsoft Windows, the >>>>>> following steps may be different on your computer. If they are, >>>>>> see your product documentation to complete these steps. >>>>>> >>>>>> 1. >>>>>> Click Start, and then click Search. >>>>>> 2. >>>>>> In the Search Results pane, click All files and folders under >>>>>> Search >>>>>> Companion. >>>>>> 3. >>>>>> In the All or part of the file name box, type a file name from >>>>>> the >>>>>> appropriate >>>>>> file information table, and then click Search. >>>>>> 4. >>>>>> In the list of files, right-click a file name from the >>>>>> appropriate >>>>>> file >>>>>> information table, and then click Properties. >>>>>> Note Depending on the version of the operating system or programs >>>>>> installed, some of the files that are listed in the file >>>>>> information >>>>>> table may not be installed. >>>>>> 5. >>>>>> On the Version tab, determine the version of the file that is >>>>>> installed >>>>>> on your computer by comparing it to the version that is >>>>>> documented >>>>>> in >>>>>> the >>>>>> appropriate file information table. >>>>>> Note Attributes other than the file version may change during >>>>>> installation. Comparing other file attributes to the information >>>>>> in >>>>>> the file information table is not a supported method of verifying >>>>>> that the update has been applied. Also, in certain cases, files >>>>>> may >>>>>> be renamed during installation. If the file or version >>>>>> information >>>>>> is >>>>>> not present, use one of the other available methods to verify >>>>>> update >>>>>> installation. >>>>>> . Registry Key Verification >>>>>> You may also be able to verify the files that this security >>>>>> update has installed by reviewing the following registry key: >>>>>> >>>>>> HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CAPICOM.Certificates.4\CLSID >>>>>> >>>>>> Best regards >>>>>> >>>>>> Meinolf Weber >>>>>> Disclaimer: This posting is provided "AS IS" with no warranties, >>>>>> and >>>>>> confers >>>>>> no rights. >>>>>>> Thanks for the reply Meinolf - the problem is, this particular >>>>>>> update (KB931906) is not getting written to a log file. >>>>>>> >>>>>>> "Meinolf Weber" wrote: >>>>>>> >>>>>>>> Hello Rosa, >>>>>>>> >>>>>>>> Logfiles you find under C:\windows with the kb at beginning. >>>>>>>> >>>>>>>> Best regards >>>>>>>> >>>>>>>> Meinolf Weber >>>>>>>> Disclaimer: This posting is provided "AS IS" with no >>>>>>>> warranties, >>>>>>>> and >>>>>>>> confers >>>>>>>> no rights. >>>>>>>>> Where does the log file for MS07-028 Vulnerability in CAPICOM >>>>>>>>> Could Allow Remote Code Execution (931906) get written to? >>>>>>>>> I've installed the update and cannot find a log anywhere on >>>>>>>>> the server. Thanks. >>>>>>>>>
Recommended Posts