View Single Post
  #1 (permalink)  
Old October 20th 07, 10:10 PM posted to microsoft.public.windows.vista.performance_maintenance,microsoft.public.windowsupdate
Robert Aldwinckle
external usenet poster
 
Posts: 369
Default Error 1719 - Windows Vistsa Home Premium

(cross-post added to Vista Perf & Maint)
"Charlie" wrote in message

....
[Subject: Error 1719 - Windows Vistsa Home Premium]


It drives me crazy that every post about this error in the "Vista community"
is about XP.



That's because the web interface to newsgroups that you are using
misleads you into thinking that all the links it offers are Vista-specific
newsgroups. Some of them are common to more than one OS.
In fact this one is common to all OS and typically there is more knowledge
about XP in here than about Vista.


None of the XP "solutions" work for me and I've found nothing
that addresses this error for Vista. Please help.


Error codes by themselves are relatively useless.
For example here is what that one may mean on XP.

cmd_output OS="XPsp2"
F:\net helpmsg 1719

There are no protocol sequences.
/cmd_output

Is that what Vista shows for net helpmsg 1719 too?
As you can see it doesn't tell you much about anything. ; )


Try to find some context for them in any log files that the update
created. BTW the code that you are quoting is a decimal code
and in general you may find more references to its hex equivalent
(0x0687) instead. In fact, you might find those hex nibbles in a
longer hex code such as 0x80070687. Etc.



I have a Toshiba laptop with Vista premium installed. After installing MS
Office Standard 2007 I can no longer install or uninstall anything, getting
the 1719 error. I've surfed the web and this problem based on MSI problems
seems to have been around for months but I can find no solution to it.
Attempting to uninstall anything hangs the process, which can't be stopped
even through the task mgr. Installs are the same way - using Windows Update
simply hangs the computer.



If you are having more general problems with WU you should try using
its log. Ref. KB902093.



I could really use some help.



In case there is something different about Vista's production of this symptom
I've cross-posted this reply to a Vista-specific newsgroup.


HTH

Robert Aldwinckle
---