KB938194 Is it installed or not ????

vista 32 bit.. manually installed update KB938194 after installing it from
automatic update and failing. Says it was successfully installed but keeps
poping up that it is not installed. How do I know if it is installed or not
and how do I keep Windows update from popping up saying need to install if it
is already on my system ???? Showing 5 failed installations and 2
installation that were sucessful on update history for KB938194...Thanks

Same thing is happening to me. The automatic install kept failing, so I did
a manual install. Although Windows Update says the install was successful,
it still pops up as an available update. Seems like quite a few people are
having the same issue.

"dustyprofile" wrote:

> vista 32 bit.. manually installed update KB938194 after installing it from
> automatic update and failing. Says it was successfully installed but keeps
> poping up that it is not installed. How do I know if it is installed or not
> and how do I keep Windows update from popping up saying need to install if it
> is already on my system ???? Showing 5 failed installations and 2
> installation that were sucessful on update history for KB938194...Thanks

"dustyprofile" <> wrote in message
news:A95CA2BB-227F-4BFA-BBB1-...
> vista 32 bit.. manually installed update KB938194 after installing it from
> automatic update and failing. Says it was successfully installed but keeps
> poping up that it is not installed. How do I know if it is installed or not
> and how do I keep Windows update from popping up saying need to install if it
> is already on my system ???? Showing 5 failed installations and 2
> installation that were sucessful on update history for KB938194...Thanks


Does the update have a verbose logging option when installed manually?

Check the File information in the KB article with the versions of the modules
that you have before and after the update is run.

Is a reboot required? Then find out which modules are causing it,
e.g. either from the verbose log, from the Event log, or using RegEdit
(for PendingFileRenameOperations). Check the versions of those
modules before and after the boot. If the updated versions aren't
correct after the boot you will have found an explanation for your problem.
A specific cause might be an interfering security package. Etc.


Good luck

Robert Aldwinckle
---

The CBS.log is relevant in this situation as the update involves
Component Based Servicing.

%windir%\logs\CBS\cbs.log

Wait till you see this log, Robert. It rivals " War and Peace "

From what I've been seeing, KB938194 has a detection issue.
It installs and is consequently reoffered even if the install
was successful.

MowGreen [MVP 2003-2007]
===============
*-343-* FDNY
Never Forgotten
===============



Robert Aldwinckle wrote:

> "dustyprofile" <> wrote in message
> news:A95CA2BB-227F-4BFA-BBB1-...
>
>>vista 32 bit.. manually installed update KB938194 after installing it from
>>automatic update and failing. Says it was successfully installed but keeps
>>poping up that it is not installed. How do I know if it is installed or not
>>and how do I keep Windows update from popping up saying need to install if it
>>is already on my system ???? Showing 5 failed installations and 2
>>installation that were sucessful on update history for KB938194...Thanks
>
>
>
> Does the update have a verbose logging option when installed manually?
>
> Check the File information in the KB article with the versions of the modules
> that you have before and after the update is run.
>
> Is a reboot required? Then find out which modules are causing it,
> e.g. either from the verbose log, from the Event log, or using RegEdit
> (for PendingFileRenameOperations). Check the versions of those
> modules before and after the boot. If the updated versions aren't
> correct after the boot you will have found an explanation for your problem.
> A specific cause might be an interfering security package. Etc.
>
>
> Good luck
>
> Robert Aldwinckle
> ---
>
>

"MowGreen [MVP]" wrote:

> The CBS.log is relevant in this situation as the update involves
> Component Based Servicing.
>
> %windir%\logs\CBS\cbs.log
>
> Wait till you see this log, Robert. It rivals " War and Peace "
>
> From what I've been seeing, KB938194 has a detection issue.
> It installs and is consequently reoffered even if the install
> was successful.
>
> MowGreen [MVP 2003-2007]
> ===============
> *-343-* FDNY
> Never Forgotten
> ===============
>
>
>
> Robert Aldwinckle wrote:
>
> > "dustyprofile" <> wrote in message
> > news:A95CA2BB-227F-4BFA-BBB1-...
> >
> >>vista 32 bit.. manually installed update KB938194 after installing it from
> >>automatic update and failing. Says it was successfully installed but keeps
> >>poping up that it is not installed. How do I know if it is installed or not
> >>and how do I keep Windows update from popping up saying need to install if it
> >>is already on my system ???? Showing 5 failed installations and 2
> >>installation that were sucessful on update history for KB938194...Thanks
> >
> >
> >
> > Does the update have a verbose logging option when installed manually?
> >
> > Check the File information in the KB article with the versions of the modules
> > that you have before and after the update is run.
> >
> > Is a reboot required? Then find out which modules are causing it,
> > e.g. either from the verbose log, from the Event log, or using RegEdit
> > (for PendingFileRenameOperations). Check the versions of those
> > modules before and after the boot. If the updated versions aren't
> > correct after the boot you will have found an explanation for your problem.
> > A specific cause might be an interfering security package. Etc.
> >
> >
> > Good luck
> >
> > Robert Aldwinckle
> > ---
> >
> > Wow Robert Aldwinckle thats a lot to digest when I am computer illerate lol....Don't know what you said so cannot fix this issue but I have a feeling that it is not just my problem but a whole lot of others having the same problem...But thank you very much for responding I guess I will put up with this nonsense of the computer installing and rebooting until Microsoft does some investigating !!!!
>

"MowGreen [MVP]" <> wrote in message news:...
> The CBS.log is relevant in this situation as the update involves
> Component Based Servicing.
>
> %windir%\logs\CBS\cbs.log
>
> Wait till you see this log, Robert. It rivals " War and Peace "
>
> From what I've been seeing, KB938194 has a detection issue.
> It installs and is consequently reoffered even if the install
> was successful.


Is this one of the ones which MS Office users are finding that they have to
close MS Office before installing? That's why I'm suggesting looking
in the Event Viewer. At least for some updates it seems to be the easiest
way to find out which modules being updated are in use by which other tasks.
If users know that much then perhaps they have a chance of changing things
sufficiently before the next install attempt? Etc.


Robert
---

See the following for an explanation of why the update is reoffered:

Vista KB938194 Appears To Install And Is Then Reoffered
http://www.bleepingcomputer.com/blog...showentry=1162


Workaround:

Open Task Scheduler, and in the Windows folder
add a WindowsCalendar folder.
No task has to be assigned, just create the WindowsCalendar folder.
Install KB938194 now.

Moral of the story: Don't delete any folders in the Windows folder of
Scheduled Tasks. <w>


MowGreen [MVP 2003-2007]
===============
*-343-* FDNY
Never Forgotten
===============



dustyprofile wrote:

>
> "MowGreen [MVP]" wrote:
>
>
>>The CBS.log is relevant in this situation as the update involves
>>Component Based Servicing.
>>
>>%windir%\logs\CBS\cbs.log
>>
>>Wait till you see this log, Robert. It rivals " War and Peace "
>>
>> From what I've been seeing, KB938194 has a detection issue.
>>It installs and is consequently reoffered even if the install
>>was successful.
>>
>>MowGreen [MVP 2003-2007]
>>===============
>> *-343-* FDNY
>>Never Forgotten
>>===============
>>
>>
>>
>>Robert Aldwinckle wrote:
>>
>>
>>>"dustyprofile" <> wrote in message
>>>news:A95CA2BB-227F-4BFA-BBB1-...
>>>
>>>
>>>>vista 32 bit.. manually installed update KB938194 after installing it from
>>>>automatic update and failing. Says it was successfully installed but keeps
>>>>poping up that it is not installed. How do I know if it is installed or not
>>>>and how do I keep Windows update from popping up saying need to install if it
>>>>is already on my system ???? Showing 5 failed installations and 2
>>>>installation that were sucessful on update history for KB938194...Thanks
>>>
>>>
>>>
>>>Does the update have a verbose logging option when installed manually?
>>>
>>>Check the File information in the KB article with the versions of the modules
>>>that you have before and after the update is run.
>>>
>>>Is a reboot required? Then find out which modules are causing it,
>>>e.g. either from the verbose log, from the Event log, or using RegEdit
>>>(for PendingFileRenameOperations). Check the versions of those
>>>modules before and after the boot. If the updated versions aren't
>>>correct after the boot you will have found an explanation for your problem.
>>>A specific cause might be an interfering security package. Etc.
>>>
>>>
>>>Good luck
>>>
>>>Robert Aldwinckle
>>>---
>>>
>>>Wow Robert Aldwinckle thats a lot to digest when I am computer illerate lol....Don't know what you said so cannot fix this issue but I have a feeling that it is not just my problem but a whole lot of others having the same problem...But thank you very much for responding I guess I will put up with this nonsense of the computer installing and rebooting until Microsoft does some investigating !!!!
>>

I checked the task scheduler, and I already have a WindowsCalender folder
under Windows. Has there been any other solutions to tackle this continual
reinstallation of the update?

"MowGreen [MVP]" wrote:

> See the following for an explanation of why the update is reoffered:
>
> Vista KB938194 Appears To Install And Is Then Reoffered
> http://www.bleepingcomputer.com/blog...showentry=1162
>
>
> Workaround:
>
> Open Task Scheduler, and in the Windows folder
> add a WindowsCalendar folder.
> No task has to be assigned, just create the WindowsCalendar folder.
> Install KB938194 now.
>
> Moral of the story: Don't delete any folders in the Windows folder of
> Scheduled Tasks. <w>
>
>
> MowGreen [MVP 2003-2007]
> ===============
> *-343-* FDNY
> Never Forgotten
> ===============
>
>
>
> dustyprofile wrote:
>
> >
> > "MowGreen [MVP]" wrote:
> >
> >
> >>The CBS.log is relevant in this situation as the update involves
> >>Component Based Servicing.
> >>
> >>%windir%\logs\CBS\cbs.log
> >>
> >>Wait till you see this log, Robert. It rivals " War and Peace "
> >>
> >> From what I've been seeing, KB938194 has a detection issue.
> >>It installs and is consequently reoffered even if the install
> >>was successful.
> >>
> >>MowGreen [MVP 2003-2007]
> >>===============
> >> *-343-* FDNY
> >>Never Forgotten
> >>===============
> >>
> >>
> >>
> >>Robert Aldwinckle wrote:
> >>
> >>
> >>>"dustyprofile" <> wrote in message
> >>>news:A95CA2BB-227F-4BFA-BBB1-...
> >>>
> >>>
> >>>>vista 32 bit.. manually installed update KB938194 after installing it from
> >>>>automatic update and failing. Says it was successfully installed but keeps
> >>>>poping up that it is not installed. How do I know if it is installed or not
> >>>>and how do I keep Windows update from popping up saying need to install if it
> >>>>is already on my system ???? Showing 5 failed installations and 2
> >>>>installation that were sucessful on update history for KB938194...Thanks
> >>>
> >>>
> >>>
> >>>Does the update have a verbose logging option when installed manually?
> >>>
> >>>Check the File information in the KB article with the versions of the modules
> >>>that you have before and after the update is run.
> >>>
> >>>Is a reboot required? Then find out which modules are causing it,
> >>>e.g. either from the verbose log, from the Event log, or using RegEdit
> >>>(for PendingFileRenameOperations). Check the versions of those
> >>>modules before and after the boot. If the updated versions aren't
> >>>correct after the boot you will have found an explanation for your problem.
> >>>A specific cause might be an interfering security package. Etc.
> >>>
> >>>
> >>>Good luck
> >>>
> >>>Robert Aldwinckle
> >>>---
> >>>
> >>>Wow Robert Aldwinckle thats a lot to digest when I am computer illerate lol....Don't know what you said so cannot fix this issue but I have a feeling that it is not just my problem but a whole lot of others having the same problem...But thank you very much for responding I guess I will put up with this nonsense of the computer installing and rebooting until Microsoft does some investigating !!!!
> >>
>

Since this update involves other Components besides WindowsCalendar
suggest you check the cbs.log to see where the update is failing.
%windir%\logs\CBS\cbs.log
Also, Event Viewer may provide a clue as to the reoffering of the update.

Start > Run > eventvwr.msc
Then navigate to
Applications and Services Log => Microsoft => Windows =>
WindowsUpdateClient => Operational

See if you can locate Errors in Operational.
Hopefully, it will provide a clue as to what Component is not being updated.

MowGreen [MVP 2003-2007]
===============
*-343-* FDNY
Never Forgotten
===============



Ian C. wrote:

> I checked the task scheduler, and I already have a WindowsCalender folder
> under Windows. Has there been any other solutions to tackle this continual
> reinstallation of the update?
>
> "MowGreen [MVP]" wrote:
>
>
>>See the following for an explanation of why the update is reoffered:
>>
>>Vista KB938194 Appears To Install And Is Then Reoffered
>>http://www.bleepingcomputer.com/blog...showentry=1162
>>
>>
>>Workaround:
>>
>>Open Task Scheduler, and in the Windows folder
>>add a WindowsCalendar folder.
>>No task has to be assigned, just create the WindowsCalendar folder.
>>Install KB938194 now.
>>
>>Moral of the story: Don't delete any folders in the Windows folder of
>>Scheduled Tasks. <w>
>>
>>
>>MowGreen [MVP 2003-2007]
>>===============
>> *-343-* FDNY
>>Never Forgotten
>>===============
>>
>>
>>
>>dustyprofile wrote:
>>
>>
>>>"MowGreen [MVP]" wrote:
>>>
>>>
>>>
>>>>The CBS.log is relevant in this situation as the update involves
>>>>Component Based Servicing.
>>>>
>>>>%windir%\logs\CBS\cbs.log
>>>>
>>>>Wait till you see this log, Robert. It rivals " War and Peace "
>>>>
>>>>From what I've been seeing, KB938194 has a detection issue.
>>>>It installs and is consequently reoffered even if the install
>>>>was successful.
>>>>
>>>>MowGreen [MVP 2003-2007]
>>>>===============
>>>> *-343-* FDNY
>>>>Never Forgotten
>>>>===============
>>>>
>>>>
>>>>
>>>>Robert Aldwinckle wrote:
>>>>
>>>>
>>>>
>>>>>"dustyprofile" <> wrote in message
>>>>>news:A95CA2BB-227F-4BFA-BBB1-...
>>>>>
>>>>>
>>>>>
>>>>>>vista 32 bit.. manually installed update KB938194 after installing it from
>>>>>>automatic update and failing. Says it was successfully installed but keeps
>>>>>>poping up that it is not installed. How do I know if it is installed or not
>>>>>>and how do I keep Windows update from popping up saying need to install if it
>>>>>>is already on my system ???? Showing 5 failed installations and 2
>>>>>>installation that were sucessful on update history for KB938194...Thanks
>>>>>
>>>>>
>>>>>
>>>>>Does the update have a verbose logging option when installed manually?
>>>>>
>>>>>Check the File information in the KB article with the versions of the modules
>>>>>that you have before and after the update is run.
>>>>>
>>>>>Is a reboot required? Then find out which modules are causing it,
>>>>>e.g. either from the verbose log, from the Event log, or using RegEdit
>>>>>(for PendingFileRenameOperations). Check the versions of those
>>>>>modules before and after the boot. If the updated versions aren't
>>>>>correct after the boot you will have found an explanation for your problem.
>>>>>A specific cause might be an interfering security package. Etc.
>>>>>
>>>>>
>>>>>Good luck
>>>>>
>>>>>Robert Aldwinckle
>>>>>---
>>>>>
>>>>>Wow Robert Aldwinckle thats a lot to digest when I am computer illerate lol....Don't know what you said so cannot fix this issue but I have a feeling that it is not just my problem but a whole lot of others having the same problem...But thank you very much for responding I guess I will put up with this nonsense of the computer installing and rebooting until Microsoft does some investigating !!!!
>>>>

I resolved this issue by checking the cbs.log file (as below) and discovering
that the install procedure was throwing up a PATH_NOT_FOUND error for the
following folder:

C:\ProgramData\Microsoft\Network\Connections\Pbk\

I created an empty folder in that location, re-applied KB938194, rebooted,
and it now reports a succesful installation. I re-check the cbs.log file and
there are no new errors, and all exit conditions report OK.

That folder seems to be related to the Microsoft RAS service, for storage of
Public Keys. Nothing was created in the folder after my successful install -
so it would appear that the test to see if that path exists is falling over.

"MowGreen [MVP]" wrote:

> The CBS.log is relevant in this situation as the update involves
> Component Based Servicing.
>
> %windir%\logs\CBS\cbs.log
>
> Wait till you see this log, Robert. It rivals " War and Peace "
>
> From what I've been seeing, KB938194 has a detection issue.
> It installs and is consequently reoffered even if the install
> was successful.
>
> MowGreen [MVP 2003-2007]
> ===============
> *-343-* FDNY
> Never Forgotten
> ===============
>
>
>
> Robert Aldwinckle wrote:
>
> > "dustyprofile" <> wrote in message
> > news:A95CA2BB-227F-4BFA-BBB1-...
> >
> >>vista 32 bit.. manually installed update KB938194 after installing it from
> >>automatic update and failing. Says it was successfully installed but keeps
> >>poping up that it is not installed. How do I know if it is installed or not
> >>and how do I keep Windows update from popping up saying need to install if it
> >>is already on my system ???? Showing 5 failed installations and 2
> >>installation that were sucessful on update history for KB938194...Thanks
> >
> >
> >
> > Does the update have a verbose logging option when installed manually?
> >
> > Check the File information in the KB article with the versions of the modules
> > that you have before and after the update is run.
> >
> > Is a reboot required? Then find out which modules are causing it,
> > e.g. either from the verbose log, from the Event log, or using RegEdit
> > (for PendingFileRenameOperations). Check the versions of those
> > modules before and after the boot. If the updated versions aren't
> > correct after the boot you will have found an explanation for your problem.
> > A specific cause might be an interfering security package. Etc.
> >
> >
> > Good luck
> >
> > Robert Aldwinckle
> > ---
> >
> >
>