Per JPGreen's e-mail, I ran the special procedure provided for both my XP-SP3 and Vista SP1 system to update LiveUpdate. The upgrade did not occur on either system.
The two logs generated by the special procedure have been e-mailed back.
Success on both my XP-SP3 and Vista SP1 system! 
What I found on both systems was, by using Windows Install Clean Up, that the Windows Installer was showing that V3.4.1.234 was already installed. With Windows Install Clean Up, I removed the LiveUpdate item. Then I reran LuSetup.exe. It installed the new V3.4.1.234 LiveUpdate. It now working on both systems and shows V3.4.1.234 via LuAll.exe>Options>About LiveUpdate.
Thanks for all the help and assistance. Really appreciate it.
I think I know what "generated" my problem initially....registry cleaners...which I use on both my Vista and XP systems. I have three different registry cleaners...jv16 PowerTools 2008, Ace Utilities, and RegVac...all the latest versions. All three of them will delete the following LiveUpdate key which in turn removes LiveUpdate's uninstaller entry in Add or Remove Programs (Programs and Features) and I suspect causes the LiveUpdate's installer to act up during an LiveUpdate upgrade.
[HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Uninstall\PsuedoLiveUpdate]
"WindowsInstaller"=dword:00000000
"VersionMinor"=dword:00000004
"VersionMajor"=dword:00000003
"Version"=dword:03040000
"URLUpdateInfo"=""
"URLInfoAbout"=""
"UninstallString"="MsiExec.exe /x {E80F62FF-5D3C-4A19-8409-9721F2928206} /l*v \"C:\\ProgramData\\LuUninstall.LiveUpdate\""
"Size"=""
"Readme"=""
"Publisher"="Symantec Corporation"
"NoRepair"=dword:00000001
"NoModify"=dword:00000001
"Language"=dword:00000409
"InstallSource"=""
"InstallLocation"="C:\\Program Files\\Symantec\\LiveUpdate"
"InstallDate"="5/31/2008"
"HelpTelephone"=""
"HelpLink"=""
"EstimatedSize"=dword:00003453
"DisplayVersion"="3.4.1.234"
"DisplayName"="LiveUpdate (Symantec Corporation)"
"DisplayIcon"="C:\\Program Files\\Symantec\\LiveUpdate\\LUALL.EXE,0"
"Contact"=""
"Comments"=""
"AuthorizedCDFPrefix"=""
So, watch those doggone registry cleaners (and I suspect others) closely !
siliconman01 wrote:
Excellent! This forum is such a breath of fresh air for Norton users
I still have to pinch myself that I'm not dreaming! Here's a bunch of Norton Staffers who are here nearly all the time, who are prepared to admit that their product actually has bugs in it -- or WADU if you prefer -- and who are able to get something done quickly.
And equally amazing -- they are able to get other software companies to react, even Microsoft, and not go around saying our product works OK if yours is not there so it must be your fault.
Top marks to whoever authorized this mad reckless venture <g>
"Local papers please copy"
siliconman01 wrote:I think I know what "generated" my problem initially....registry cleaners...which I use on both my Vista and XP systems. I have three different registry cleaners...jv16 PowerTools 2008, Ace Utilities, and RegVac...all the latest versions.
[ .... ]
So, watch those doggone registry cleaners (and I suspect others) closely !
You can't imagine how many cases we encounter in the Forums elsewhere where I do support when people come in and post:
"I tidied up my Windows installation and got rid of unnecessary files and registry entries ....... and now it won't work. What do I do?"
And I don't know that I can remember anyone saying that they cleaned up the registry and their computer took off like a rocket!
I wonder how many people with the recent corruption in the registry that is now identified found that their registry cleaner would deal with that? <g>
Bump..