KB947738

[Bob Frasca]

I've installed this update 20 times. Each time it says it updated
successfully; however, it immediately prompts me to install it again. I've
tried downloading it manually and installing it. I've tried deleting the
Windows Update download folder. In the registry, it is listed, along with
VS 2005 sp1, as a patch; however, if I look in Add or Remove Programs it is
not listed as having been installed.

I'm running XP sp3 and I also have VS 2008 DB Developers (CTP 16) edition
installed.

The only reason I have this installed is to run BIDS. My goal is simply to
have it stop prompting me to install the patch. Anyone have any ideas?

[PA Bear [MS MVP]]

See the section "How to obtain help and support for this security update" of
http://support.microsoft.com/kb/947738, Bob.

[Did you post about this issue elsewhere (e.g., another newsgroup or a
public forum)?]
--
~Robear Dyer (PA Bear)
MS MVP-IE, Mail, Security, Windows Desktop Experience - since 2002
AumHa VSOP & Admin http://aumha.net
DTS-L http://dts-l.net/

[TonyC]

With respect, I've now read that advice around two dozen times in various
places all over the internet during my desperate search to get to the bottom
of this issue, but unfortunately it just isn't very helpful. The only useful
suggestion offered in the proffered link is to check the version of the
Windows Installer that one has to ensure that it is v3.1 but this is not my
problem.

I also have the same issue with KB954606 - i.e. a refusal to install despite
numerous attempts over the last several months.

After many attempts both updates did eventually install successfully on my
Thinkpad T61p but this is running Vista 64 bit, and if anything you might
have thought that this would be the 'problem' system. Both 32 bit XP Pro SP3
systems (on Dell Precision 'workstations') are still stubbornly refusing to
cooperate, and it is driving me nuts.

I always keep all of my systems bang up to the minute with MS updates, so
the fact that I have these two refusing to play ball is most infuriating.
Nothing like it has ever happened before in all the years I have been taking
automated updates from MS.

There seems to be surprisingly little information available from MS on this
issue which is clearly effecting quite a few people.

Can anybody point to a more direct source of advice or assistance at all
please?

(You will have my undying gratitude if you can. :-))

[Bob Frasca]

Yes, I have also followed many threads and gone down many paths and none of
them work. I can't believe there isn't some way to simply refuse an update
even if it is "critical". I'm not a home user so I'd have to jump through
hoops to get support for what amounts to an annoyance. Perhaps the goal is
to annoy XP users enough to switch to Vista...chuckle. (I've got Vista at
home and it is currently unable to obtain updates for some mysterious reason
that I can't find any answers to either. Unfortunately, I haven't had time
to do much research on that one yet.)

"TonyC" <To...@discussions.microsoft.com> wrote in message
news:C46B486A-D7C3-4CC5...@microsoft.com...

[Robert Aldwinckle]

"TonyC" <To...@discussions.microsoft.com> wrote in message
news:C46B486A-D7C3-4CC5...@microsoft.com...

> With respect, I've now read that advice around two dozen times in various
> places all over the internet during my desperate search to get to the bottom
> of this issue, but unfortunately it just isn't very helpful.

If you're implying that you are willing to do some diagnosis
you should be starting your own thread and describing whatever
problems you are having with the analysis of the diagnostics
you have assembled so far. (BTW so far I have only seen this
one post from TonyC.)

> The only useful
> suggestion offered in the proffered link is to check the version of the
> Windows Installer that one has to ensure that it is v3.1 but this is not my
> problem.
>

> I also have the same issue with KB954606 - i.e. a refusal to install despite
> numerous attempts over the last several months.

So, look at that KB article and the modules it mentions.
Go to the corresponding TechNet Bulletin for instructions
on how to check it if necessary.

And then if you need more help start your own thread
(to avoid hijacking this one which is about a completely
different update for a completely different product
on a completely different OS.)

Good luck

Robert Aldwinckle
---

[PA Bear [MS MVP]]

Repost:

>> See the section "How to obtain help and support for this security update"

>> of http://support.microsoft.com/kb/947738...

Spelling it your for you:

Start a free Windows Update support incident request:
https://support.microsoft.com/oas/default.aspx?gprid=6527

Support for Windows Update:
http://support.microsoft.com/gp/wusupport

For home users, no-charge support is available by calling 1-866-PCSAFETY in
the United States and in Canada or by contacting your local Microsoft
subsidiary. There is no-charge for support calls that are associated with
security updates. When you call, clearly state that your problem is related
to a Security Update and cite the update's KB number (e.g., KB947738)

For more information about how to contact your local Microsoft subsidiary
for security update support issues, visit the International Support Web
site: http://support.microsoft.com/common/international.aspx

For enterprise customers, support for security updates is available through
your usual support contacts.

--
~Robear Dyer (PA Bear)

MS MVP-Windows (IE, OE, Security, Shell/User)
AumHa VSOP & Admin; DTS-L.net

[TonyC]

I'm not hijacking the thread. I was adding (meagre, because it's all I
have)additional information concerning the same symptoms with a different
update.

I am perfectly well versed in general netiquette thank you very much, and I
have already gone through all of the usual self-help measures - including
reading all the available relevant material that I can find - including that
which you mention - several times over.

I am sorry that you have jumped to conclusions about me and my post, but I
guess I should have realised that my expression of frustration at the paucity
of available information would be misinterpreted as an attack on an
individual.

To avoid fanning the flames further I will avoid pointing out the factual
errors in your own response as they were no doubt triggered by your own
eagerness to engage in a fight on the back of a hasty (mis)reading of my note.

[TonyC]

> Spelling it your for you:

Thanks for that. I guess my past experiences with trying to get an answer
out of MS have coloured my judgement on this as I tend to dismiss the idea of
trying to contact them until the very last resort.

However since this has been going on for months now perhaps that is what I
will have to do.

I will take a crack at contacting MS as you suggest, and If I get an answer
that improves the matter in any way I will report it back to this thread.

Wish me luck. :-)

[Robert Aldwinckle]

"Bob Frasca" <bfr...@xostech.com> wrote in message news:OIkd3eDO...@TK2MSFTNGP02.phx.gbl...

> [Subject: KB947738]

<title>MS08-052&#58; Description of the security update for GDI&#43;
for Visual Studio 2005 Service Pack 1&#58; September 9, 2008</title>
http://support.microsoft.com/?kbid=947738

> I've installed this update 20 times. Each time it says it updated
> successfully; however, it immediately prompts me to install it again.

> I've tried downloading it manually and installing it.

Then your symptoms for that case are essentially independent of AU/MU
and you may get more informed help from newsgroups which specialize
in the product(s) being updated.

> I've tried deleting the Windows Update download folder.

That wouldn't affect your symptoms with your manual install attempt.

> In the registry, it is listed, along with VS 2005 sp1, as a patch;
> however, if I look in Add or Remove Programs
> it is not listed as having been installed.

Assuming you have "Show updates" checked, that would suggest
that your install did not complete. So check the install log to figure out
what didn't work. If you have access to another user's KB947738
install log who updated successfully, for the same environment
and maintenance levels, then you could usefully compare them and add
any differences to your symptom description.

Alternatively, for your manual install at least, you could supplement
that log with verbose logging and if that's not enough you could
supplement that with a ProcMon trace which can help clarify
what the log messages you are getting really mean.

Use the KB article and its list of modules as a guide to analysing
your log and to help figure out which ones haven't been copied
into the system directories correctly. Take note of what all was
running when the install attempt was made. Perhaps something
in that set interferes enough that the update can't complete? Etc.

>
> I'm running XP sp3 and I also have VS 2008 DB Developers (CTP 16) edition
> installed.
>
> The only reason I have this installed is to run BIDS. My goal is simply to
> have it stop prompting me to install the patch. Anyone have any ideas?

Good luck

Robert
---

[PA Bear [MS MVP]]

You're welcome. By now you know that no one here (including MVPs)
represents or works for MS.

FYI, when an update "refuses to install," one usually finds an error in
WindowsUpdate.log related to the failure(s). Including such errors (e.g.,
0x8024000B; 0x8007F0DA) in your posts to this newsgroup or when seeking free
support from MS is always helpful.

How to read the WindowsUpdate.log file
http://support.microsoft.com/kb/902093

You can also compare the error(s) to those listed here:
http://www.bleepingcomputer.com/blogs/mowgreen/index.php?showentry=1122
and/or go to http://windowsupdate.microsoft.com > click on Help and Support
link in left pane > Solve problems on your own.
--
~PA Bear

[Bob Frasca]

> Then your symptoms for that case are essentially independent of AU/MU
> and you may get more informed help from newsgroups which specialize
> in the product(s) being updated.

I'm not sure what you mean by that. This is all about AU/MU. The fact that
the update in question is for VS 2005 Service Pack 1 is incidental. I
didn't ask for the update, I don't want the update, but I can't stop it from
arriving. For what it's worth, I have researched it extensively on every
thread I can find including the VS 2005 threads, the KB947738 threads, and
the "Why won't Windows Update stop annoying me" threads. It is these other
threads that suggested things like downloading the patch installer manually
and running it or deleting the Download directory. I didn't really expect
them to work but it was better than nothing.

I did find some posts from "PA Bear" about this patch but it was for people
that actually got an error when installing it. I also found posts from you
about this same scenario and this same patch dated 19-Sep-2008. I didn't
really understand what you were telling the guy so it wasn't much use to me.

http://www.tech-archive.net/Archive/Windows/microsoft.public.windowsupdate/2008-09/msg01683.html

I just "installed" it again and here's the log. As you can see, it
installed without incident. Approximately 30 seconds later it prompted me
to install it again.

2008-10-29 16:42:56:641 1916 c34 AU AU received install approval from client
for 1 updates
2008-10-29 16:42:56:641 1916 c34 AU #############
2008-10-29 16:42:56:641 1916 c34 AU ## START ## AU: Install updates
2008-10-29 16:42:56:641 1916 c34 AU #########
2008-10-29 16:42:56:641 1916 c34 AU # Initiating manual install
2008-10-29 16:42:56:641 1916 c34 AU # Approved updates = 1
2008-10-29 16:42:56:641 1916 c34 AU <<## SUBMITTED ## AU: Install updates /
installing updates [CallId = {FC2EA419-B778-4231-8661-FA4BC311001D}]
2008-10-29 16:42:56:657 1916 1654 Agent *************
2008-10-29 16:42:56:657 1916 1654 Agent ** START ** Agent: Installing
updates [CallerId = AutomaticUpdates]
2008-10-29 16:42:56:657 1916 1654 Agent *********
2008-10-29 16:42:56:657 1916 1654 Agent * Updates to install = 1
2008-10-29 16:42:56:969 1916 1654 Agent * Title = Security Update for
Microsoft Visual Studio 2005 Service Pack 1 (KB947738)
2008-10-29 16:42:56:969 1916 1654 Agent * UpdateId =
{808F2582-9438-492D-960F-12C7D184C043}.104
2008-10-29 16:42:56:969 1916 1654 Agent * Bundles 1 updates:
2008-10-29 16:42:56:969 1916 1654 Agent *
{0CDBFF88-FA7F-4211-B8DD-608C4F34FDD4}.104
2008-10-29 16:43:15:063 1916 1654 Handler Attempting to create remote
handler process as TEAMXXXXX\bfrasca in session 0
2008-10-29 16:43:15:625 1916 1654 DnldMgr Preparing update for install,
updateId = {0CDBFF88-FA7F-4211-B8DD-608C4F34FDD4}.104.
2008-10-29 16:43:18:875 5520 151c Misc =========== Logging initialized
(build: 7.2.6001.784, tz: -0400) ===========
2008-10-29 16:43:18:875 5520 151c Misc = Process:
C:\WINDOWS\system32\wuauclt.exe
2008-10-29 16:43:18:875 5520 151c Misc = Module:
C:\WINDOWS\system32\wuaueng.dll
2008-10-29 16:43:18:875 5520 151c Handler :::::::::::::
2008-10-29 16:43:18:875 5520 151c Handler :: START :: Handler: Command Line
Install
2008-10-29 16:43:18:875 5520 151c Handler :::::::::
2008-10-29 16:43:18:875 5520 151c Handler : Updates to install = 1
2008-10-29 16:49:39:857 5520 151c Handler : Command line install
completed. Return code = 0x00000000, Result = Succeeded, Reboot required =
false
2008-10-29 16:49:39:857 5520 151c Handler :::::::::
2008-10-29 16:49:39:857 5520 151c Handler :: END :: Handler: Command Line
Install
2008-10-29 16:49:39:857 5520 151c Handler :::::::::::::
2008-10-29 16:49:41:810 1916 12c8 AU >>## RESUMED ## AU: Installing update
[UpdateId = {808F2582-9438-492D-960F-12C7D184C043}, succeeded]
2008-10-29 16:49:42:045 1916 1654 Agent *********
2008-10-29 16:49:42:045 1916 12c8 AU Install call completed.
2008-10-29 16:49:42:045 1916 1654 Agent ** END ** Agent: Installing
updates [CallerId = AutomaticUpdates]
2008-10-29 16:49:42:045 1916 12c8 AU # WARNING: Install call completed,
reboot required = No, error = 0x00000000
2008-10-29 16:49:42:045 1916 1654 Agent *************
2008-10-29 16:49:42:045 1916 12c8 AU #########
2008-10-29 16:49:42:045 1916 12c8 AU ## END ## AU: Installing updates
[CallId = {FC2EA419-B778-4231-8661-FA4BC311001D}]
2008-10-29 16:49:42:045 1916 12c8 AU #############
2008-10-29 16:49:42:045 1916 12c8 AU Install complete for all calls, reboot
NOT needed
2008-10-29 16:49:46:857 1916 dc8 Report REPORT EVENT:
{95F62C7E-15A0-4981-81A8-04BEAFAA6AD9} 2008-10-29 16:49:41:810-0400 1 183
101 {808F2582-9438-492D-960F-12C7D184C043} 104 0 AutomaticUpdates Success
Content Install Installation Successful: Windows successfully installed the
following update: Security Update for Microsoft Visual Studio 2005 Service
Pack 1 (KB947738)
2008-10-29 16:49:48:498 1916 1470 AU Triggering Offline detection
(non-interactive)
2008-10-29 16:49:48:560 1916 f2c AU #############
2008-10-29 16:49:48:560 1916 f2c AU ## START ## AU: Search for updates
2008-10-29 16:49:48:560 1916 f2c AU #########
2008-10-29 16:49:48:576 1916 f2c AU <<## SUBMITTED ## AU: Search for updates
[CallId = {0B6D52A3-2FEA-4626-8C19-07668DB0EE3A}]
2008-10-29 16:49:48:576 1916 dc8 Agent *************
2008-10-29 16:49:48:576 1916 dc8 Agent ** START ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2008-10-29 16:49:48:576 1916 dc8 Agent *********
2008-10-29 16:49:48:576 1916 dc8 Agent * Online = No; Ignore download
priority = No
2008-10-29 16:49:48:576 1916 dc8 Agent * Criteria = "IsHidden=0 and
IsInstalled=0 and DeploymentAction='Installation' and IsAssigned=1 or
IsHidden=0 and IsPresent=1 and DeploymentAction='Uninstallation' and
IsAssigned=1 or IsHidden=0 and IsInstalled=1 and
DeploymentAction='Installation' and IsAssigned=1 and RebootRequired=1 or
IsHidden=0 and IsInstalled=0 and DeploymentAction='Uninstallation' and
IsAssigned=1 and RebootRequired=1"
2008-10-29 16:49:48:576 1916 dc8 Agent * ServiceID =
{7971F918-A847-4430-9279-4A52D1EFE18D}
2008-10-29 16:49:48:576 1916 dc8 Agent * Search Scope = {Machine}
2008-10-29 16:49:48:654 4212 1078 CltUI AU client got new directive =
'Shutdown', serviceId = {7971F918-A847-4430-9279-4A52D1EFE18D}, return =
0x00000000
2008-10-29 16:49:48:998 1916 f2c AU AU received handle event

"Robert Aldwinckle" <rob...@techemail.com> wrote in message
news:OOIIxSU...@TK2MSFTNGP03.phx.gbl...

[PA Bear [MS MVP]]

> I did find some posts from "PA Bear" about this patch but it was for
> people
> that actually got an error when installing it.

"PA Bear" was the first responder to your thread but you never replied to
his post:
http://groups.google.com/group/microsoft.public.windowsupdate/msg/45e1531c0fe1358b
--
~PA Bear <wink>

[Harry Johnston [MVP]]

Bob Frasca wrote:

> I'm not sure what you mean by that. This is all about AU/MU. The fact that
> the update in question is for VS 2005 Service Pack 1 is incidental. I
> didn't ask for the update, I don't want the update, but I can't stop it from
> arriving.

Have you tried doing a custom install and deselecting the update?

I assume you've read the associated security bulletin and confirmed that the
software you're developing / have developed isn't affected?

Harry.

[Robert Aldwinckle]

"Bob Frasca" <bfr...@xostech.com> wrote in message news:evGdwsgO...@TK2MSFTNGP03.phx.gbl...

>> Then your symptoms for that case are essentially independent of AU/MU
>> and you may get more informed help from newsgroups which specialize
>> in the product(s) being updated.
>
> I'm not sure what you mean by that. This is all about AU/MU.

You snipped the context of that remark.

>>> I've tried downloading it manually and installing it.

Therefore, neither AU nor MU were involved then for either
the download or the install attempt of the update in question.

> The fact that
> the update in question is for VS 2005 Service Pack 1 is incidental. I
> didn't ask for the update, I don't want the update, but I can't stop it from
> arriving.

Sure you can. Just uncheck it when you see it offered,
either using AU or MU.

But why don't you identify the problem which is preventing
the successful install of the update, then it would not be
reoffered *and* your product would be patched properly. ; )

> For what it's worth, I have researched it extensively on every
> thread I can find including the VS 2005 threads, the KB947738 threads, and
> the "Why won't Windows Update stop annoying me" threads. It is these other
> threads that suggested things like downloading the patch installer manually
> and running it or deleting the Download directory. I didn't really expect
> them to work but it was better than nothing.
>
> I did find some posts from "PA Bear" about this patch but it was for people
> that actually got an error when installing it. I also found posts from you
> about this same scenario and this same patch dated 19-Sep-2008. I didn't
> really understand what you were telling the guy so it wasn't much use to me.
>
> http://www.tech-archive.net/Archive/Windows/microsoft.public.windowsupdate/2008-09/msg01683.html

I was discussing an update which required a reboot to be complete.
Does your update require a reboot too? Then you could be looking
at the PendingFileRenameOperations registry value before allowing
the reboot to see which modules were involved in that phase.

>
>
> I just "installed" it again and here's the log. As you can see, it
> installed without incident. Approximately 30 seconds later it prompted me
> to install it again.

This is the log of AU's involvement with the install.
I'd rather see the install log to see what it tried to do
so then we would know what tests to suggest to understand
whether it actually worked or why it is failing. ; )

Once you're sure that the update's modules are in place
I suppose we could then assume that there is a bug in AU/MU
which keeps reoffering an already installed patch
but until then I think we should assume that it is not fully
installed.

BTW the log suggests that reboot is not required
but have you tried rebooting anyway? Also, since you have
downloaded the patch manually you could try doing the install
during a safe mode boot when less things would be running
which could be interfering with the install phase.

Hmm... according to the KB article there are only two modules involved,
so at the very least you could try doing (e.g. in a cmd window)

tasklist /fi "Modules eq Modules eq Microsoft.Reportviewer.Webforms.dll"
and
tasklist /fi "Imagname eq ReportViewerLP.exe"

and stopping any processes which are listed before doing any
install attempt.

BTW another advantage to trying a manual install would be that
it would avoid a potential unusual authentication issue I noticed
in your log. I'm not sure what that means. I haven't seen it
before.

Also, did I mention supplementing any diagnostics you do get
by running ProcMon.? The only thing to be aware of is that
occasionally ProcMon's driver will cause a BSOD... ; )

Good luck

Robert
---