Hopefully someone will figure this out shortly.
--
tatnc1
------------------------------------------------------------------------
tatnc1's Profile: http://forums.techarena.in/members/124202.htm
View this thread: http://forums.techarena.in/windows-x64-edition/1230565.htm
So far I haven't run into this yet on my WSUS environment. But apparently
others have.
--
Charlie.
http://msmvps.com/blogs/xperts64
http://mvp.support.microsoft.com/profile/charlie.russel
"Dan XP" <Dan X...@discussions.microsoft.com> wrote in message
news:96FDD850-C125-44EF...@microsoft.com...
--
webwevers
------------------------------------------------------------------------
webwevers's Profile: http://forums.techarena.in/members/124311.htm
I found a log file under c:\windows\ with the "installation log" that
say alot of errors.
This is a part of that file:
[KB973869.log]
3.016:
================================================================================
3.016: 2009/08/12 09:08:52.734 (local)
3.016: c:\00b36c40900b03f272\update\update.exe (version 6.3.4.1)
3.016: Hotfix started with following command line:
3.016: In Function GetBuildType, line 1170, RegQueryValueEx failed with
error 0x2
6.156: In Function TestVolatileFlag, line 12013, RegOpenKeyEx failed
with error 0x2
6.156: In Function TestVolatileFlag, line 12045, RegOpenKeyEx failed
with error 0x2
6.156: DoInstallation: CleanPFR failed: 0x2
6.156: In Function GetBuildType, line 1170, RegQueryValueEx failed with
error 0x2
6.156: SetProductTypes: InfProductBuildType=BuildType.IP
6.188: SetAltOsLoaderPath: No section uses DirId 65701; done.
6.297: DoInstallation: FetchSourceURL for
c:\00b36c40900b03f272\update\update_SP2GDR.inf failed
6.297: CreateUninstall = 0,Directory = C:\WINDOWS\$NtUninstallKB973869$
6.297: LoadFileQueues: UpdSpGetSourceFileLocation for hal.dll failed:
0xe0000102
6.344: BuildCabinetManifest: update.url absent
6.344: Starting AnalyzeComponents
6.344: AnalyzePhaseZero used 0 ticks
--
binx
------------------------------------------------------------------------
binx's Profile: http://forums.techarena.in/members/124320.htm
--
jmathieu
------------------------------------------------------------------------
jmathieu's Profile: http://forums.techarena.in/members/124520.htm
This is Microsoft programmers not being thorough in their testing
before they push something out as a mandatory update. Whoever is in
charge of the Windows Update team should be replaced with someone who
knows how to get their Q&A team to do their jobs and quit creating more
problems because of poor programming.
Maybe they should just get this update off the windows update site and
fix it before trying to make us their test lab.
Why should I have to waste hour(s) of my time over the phone with the
MS support engineers, when they should have done it themselves in the
first place?
-Karmst
--
Karmst
------------------------------------------------------------------------
Karmst's Profile: http://forums.techarena.in/members/124551.htm
--
webwevers
------------------------------------------------------------------------
webwevers's Profile: http://forums.techarena.in/members/124311.htm
If they are charging big bucks for their sophisticated software, then
they should do the testing (getting a free service). Why should we do
the testing for them? In that case they should pay us back for each bug
we report.
--
Ansuman Pahari
------------------------------------------------------------------------
Ansuman Pahari's Profile: http://forums.techarena.in/members/124932.htm
Software engineers are human beings and I am not aware of any human
being on this planet being perfect. Therefore since software is written
by imperfect human beings it is absolutely impossible to engineer
software that does not some glitch in it.
I presume your are not perfect. Or are you?
--
SonicBee777
------------------------------------------------------------------------
SonicBee777's Profile: http://forums.techarena.in/members/124964.htm
Software engineering is not infallible and there is no perfect software.
All software has bugs in it somewhere and under the right circumstances
they will make themselves know.
If you think you can do better, then why aren't you developing the fixes!
When we can all walk on water then the mistakes you note below will
cease to happen.
"Common sense is not so common."
� Voltaire
Bobby Johnson;4569295 Wrote:
> You're talking apples and oranges...
>
Bobby Johnson;4569099 Wrote:
> Because, as I said before, it is humanly impossible for anyone to be
> able to test any software for every conceivable configuration.
>
> Software engineers are human beings and I am not aware of any human
> being on this planet being perfect. Therefore since software is
> written
> by imperfect human beings it is absolutely impossible to engineer
> software that does not some glitch in it.
> >
>But not ALL customers are experiencing this problem, so how can you
>classify it as unacceptable?
>
As stated before the problem only surfaces on x64 editions of Windows.
I too have noticed this problem, maintaining a couple of machines through WSUS, 32-bit is OK, 64-bit likes to install over again.
I will have the patience to wait for the fix to be available, may be I will disable deployment of the x64 version of this patch, so
users don't get annoyed.
---
Stefan Pendl
Windows Vista SP2
AMD Turion X2 RM-70 2 GHz
4 GB RAM
I am a software developer who has to test my software on every platform
that I support. I can't test for every hardware variation, but I can
test the normal software layouts. If I supported XP 64-bit, I would
have to have an XP 64-bit PC setup to test it, which I do. If I release
software that doesn't work correctly on a platform that I support, it is
my fault and I would take full responsibility for missing the
problem...
In the case of this latest snafu, M$ should have easily caught this
long before it was released to the public. This is not one of those
issues that should have escaped the M$ Testing team. M$ has the
resources to extensively test this stuff without relying on its
customers to do the testing for it. M$ testers missed an easy to catch
problem once again. This is not the first time and probably won't be
the last...
.
--
Nightrider
------------------------------------------------------------------------
Nightrider's Profile: http://forums.techarena.in/members/125010.htm
Thanks,
Ansuman
--
webwevers
------------------------------------------------------------------------
webwevers's Profile: http://forums.techarena.in/members/124311.htm
Apparently the problem is fixed today by a new revision of the update, I have just checked my WSUS server and all x64 machines are
marked as installed and not as requiring updates ;-)
Follow-up:
Re-offer reports confirmed for KB973869
<QP>
We have investigated reports that the KB973869 (MS09-037) update is
re-offered through Automatic Updates and Windows Update on some x64 systems,
after it has already been installed. We have identified some limited
scenarios where this is occurring with Windows Server 2003 x64, Windows XP
x64, and Windows Server 2003 for Itanium-based systems. No systems are
left unsecure due to this behavior. A revision to the update detection
logic will be published shortly to prevent this update from being re-offered
after it has been installed, and to ensure clients accurately describe the
updates' installed status. If you have installed this update, you do not
need to re-install the revision.
We apologize for this inconvenience,
The MU Team
</QP>
Source:
http://blogs.technet.com/wsus/archive/2009/08/14/re-offer-reports-confirmed-for-kb973869-ms09-037.aspx
--
~PA Bear
www.banthecheck.com
On 12 Aug-09, Howard wrote:
> I have Xp x64 and KB973869 will not install. I tried safemod and tried to
> manually install the update. The updates exits with out error or stating
> it
> is completed. Windows updates keep offering the update even after it says
> it has installed it. I tried system restore but the system will not
> restore
> before the last patch tuesday.
Last thing I got was an e-mail from an engineer on the PSS Security
Team on Friday indicating they were working on it, and now this morning
I see that my x64 machines are also 100% up to date. They must have
pushed out a revision to the update with the correct detection logic.
--
tatnc1
------------------------------------------------------------------------
tatnc1's Profile: http://forums.techarena.in/members/124202.htm