TIP: Click on subject to list as thread! ANSI
echo: nthelp
to: David Blair
from: Rich
date: 2004-01-02 23:31:20
subject: Re: Windows Update- rollback?

From: "Rich" 

This is a multi-part message in MIME format.

------=_NextPart_000_077D_01C3D188.875CCFF0
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

   The Windows Update installation history is just a for your benefit.  =
It has no purpose other than that.  If you want to reset your client =
settings you can delete \Program Files\WindowsUpdate.  Kill the whole =
directory and your next visit to Windows Update will reinitialize the =
client side.

   None of this affects the selection of applicable updates.

Rich

  "David Blair"  wrote in message =
news:3ff59a71$1{at}w3.nls.net...
  I would only replace those files which are the "same"- so both the
  Installation History and Windows Update won't have an issue. Both
  installation, from an XP perspective, are the same.


  "Jan van Hoek (NL)"  wrote in message
  news:VA.000001c6.008cc35e{at}xs4alldot.nl...
  > >> || Why don't you just copy the files
  > >> ||from you up to date install
  > >> ||to your non-up-to-date  install?
  > >> I thought of that, but was unsure if it would be wise.
  >
  > It may prove effective, IF it succeeds. However, if either partition =
is
  > active, you will receive a lot of "file in use" errors, which will =
defeat
  > your purpose.
  >
  > True installation programs (like the Windows Update function) have
  > workarounds for that, e.g. via the infamous re-boot. But the =
COPY/XCOPY
  > cannot cope with such situations, and neither does Windows Explorer. =
All
  > will fail to get those files accross.
  >
  > Whether it is unwise to bypass the Windows Update (and Restore)
  > functions, noone can tell. For starters, it won't correctly update =
the
  > Add/Remove Programs list, and it will falsify the Installation =
History as
  > displayed by Windows Update. Everyone will advise you against such a
  > bypass action. But some of the time you have no alternative than to =
jump
  > blindfolded and hope for the best


------=_NextPart_000_077D_01C3D188.875CCFF0
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable








   The
Windows Update =
installation=20
history is just a for your benefit.  It has no purpose other
than=20 that.  If you want to reset your client settings you can
delete = \Program=20
Files\WindowsUpdate.  Kill the whole directory and your next visit = to=20
Windows Update will reinitialize the client side.
 
   None of
this affects the =
selection of=20
applicable updates.
 
Rich
 

  "David Blair" <drb{at}u-spam-u-die.com>">mailto:drb{at}u-spam-u-die.com">drb{at}u-spam-u-die.com>
=
wrote in=20
  message news:3ff59a71$1{at}w3.nls.net...I=20
  would only replace those files which are the "same"- so both=20
  theInstallation History and Windows Update won't have an issue.=20
  Bothinstallation, from an XP perspective, are the =
same."Jan=20
  van Hoek (NL)" <janvanhoekAT{at}xs4allDOT.nl&g=">mailto:janvanhoekAT{at}xs4allDOT.nl">janvanhoekAT{at}xs4allDOT.nl&g=
t;=20
  wrote in messagenews:VA.000001c6.008cc35e=
{at}xs4alldot.nl...>=20
  >> || Why don't you just copy the files>
>> ||from =
you up=20
  to date install> >> ||to your
non-up-to-date =20
  install?> >> I thought of that, but was
unsure if it =
would be=20
  wise.>> It may prove effective, IF it
succeeds. However, =
if=20
  either partition is> active, you will receive a lot of
"file in =
use"=20
  errors, which will defeat> your
purpose.>> True=20
  installation programs (like the Windows Update function) have>=20
  workarounds for that, e.g. via the infamous re-boot. But the=20
  COPY/XCOPY> cannot cope with such situations, and neither does =
Windows=20
  Explorer. All> will fail to get those files =
accross.>>=20
  Whether it is unwise to bypass the Windows Update (and =
Restore)>=20
  functions, noone can tell. For starters, it won't correctly update =
the>=20
  Add/Remove Programs list, and it will falsify the Installation History =

  as> displayed by Windows Update. Everyone will advise you =
against such=20
  a> bypass action. But some of the time you have no alternative =
than to=20
  jump> blindfolded and hope for the=20
best

------=_NextPart_000_077D_01C3D188.875CCFF0--

--- BBBS/NT v4.01 Flag-5
* Origin: Barktopia BBS Site http://HarborWebs.com:8081 (1:379/45)
SEEN-BY: 633/267 270
@PATH: 379/45 1 633/267

SOURCE: echomail via fidonet.ozzmosis.com

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.