Sign in with
Sign up | Sign in
Your question

[Win Me] Automatic Updates isn't working

Tags:
Last response: in Windows 95/98/ME
Share
February 24, 2005 3:28:13 PM

Archived from groups: microsoft.public.windowsme.general (More info?)

[Windows Me OS, all updates, very stable system, runs great-no error
messages. No registry hacks, still running the factory year 2000 OS install.
Very knowledgeable user-engineer with lots of PC background. NAV 2005 all
updates, Ad-aware, SpyBot S & D run regularly. Hardware NAT Firewall (behind
a router). No virus/trojans/spyware. System Restore works fine.]



My problem...

Automatic Updates is not working on my system and it had worked before. For
about the past few years I've had it turned-off (update manually) but turned
it back on a few months ago. I even got the Windows Update for AU
(manually). Then I started to notice that there were critical updates
available that I wasn't notified about by AU.



I've performed this procedure from the MS knowledge base with the exception
of renaming the Windows Update folder).
http://support.microsoft.com/default.aspx?scid=kb;en-us;275645



I also found this procedure (below) on the web that Mike Maltby MS-MVP
wrote for someone else (with a different problem) that resets Automatic
Updating. This that didn't work either.



******************************************************

...try opening the Automatic Updates applet in the Control Panel, select
"Turn off automatic updating", and OK out. Now go to your Program
Files\Windows Update folder
and delete the file AUState.cfg. Reboot and then go back to the Control
Panel and reopen the Automatic Updates applet and configure AU to meet your
requirements.

******************************************************



Any ideas?



Steve
Anonymous
February 24, 2005 9:35:51 PM

Archived from groups: microsoft.public.windowsme.general (More info?)

Steve,

What follows may not work now that Win Me uses the version 4 Windows
Update site but is worth a go.

1) Delete the file AUState.cfg from your WindowsUpdate folder
2) Delete any cab files there may be in your WindowsUpdate folder.
3) Using Regedit, edit the registry and browse to the key:
HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update
and create a new dword "DebugType" (no quotes, and no space between Debug
& Type with its value equal to 1
4) Reboot your system.

PLEASE do NOT reset or configure AutoUpdates in the Control Panel nor
attempt to visit the WindowsUpdate site.

Your system should now be logging AU activity and will create a text file
"wupdlog.txt" in the ..\Program Files\WindowsUpdate\wupd\<user name>\
folder. I may have missed something but hopefully the above will be
sufficient. Note you will only get an update offered to you if deemed to
be "critical" by Microsoft and not already installed.

The first thing that should happen is that you are offered the Automatic
Update EULA and asked to accept it. You can now adjust the AU settings to
suit your requirements.

Let this run for a few days or so. The log shouldn't get too large -
normally four or five lines are added each time you boot but a fair number
are added each time that the system actually runs AU. I doubt if the file
will be even 50K after a week (but may well be wrong). Once set up AU
should attempt to connect to the net and check for updates every 24 hours
or when next on line and the connection is lightly loaded.

Remember to disable logging by deleting the DebugType value in the
registry when you have finished other wiser the log could get quite large
over time.
--
Mike Maltby MS-MVP
mike.maltby@gmail.com


(yet another) Steve <nomail@nomail.com> wrote:

> [Windows Me OS, all updates, very stable system, runs great-no error
> messages. No registry hacks, still running the factory year 2000 OS
> install. Very knowledgeable user-engineer with lots of PC background.
> NAV 2005 all updates, Ad-aware, SpyBot S & D run regularly. Hardware
> NAT Firewall (behind a router). No virus/trojans/spyware. System
> Restore works fine.]
>
>
>
> My problem...
>
> Automatic Updates is not working on my system and it had worked
> before. For about the past few years I've had it turned-off (update
> manually) but turned it back on a few months ago. I even got the
> Windows Update for AU (manually). Then I started to notice that there
> were critical updates available that I wasn't notified about by AU.
>
>
>
> I've performed this procedure from the MS knowledge base with the
> exception of renaming the Windows Update folder).
> http://support.microsoft.com/default.aspx?scid=kb;en-us;275645
>
>
>
> I also found this procedure (below) on the web that Mike Maltby
> MS-MVP wrote for someone else (with a different problem) that resets
> Automatic Updating. This that didn't work either.
>
>
>
> ******************************************************
>
> ..try opening the Automatic Updates applet in the Control Panel,
> select "Turn off automatic updating", and OK out. Now go to your
> Program Files\Windows Update folder
> and delete the file AUState.cfg. Reboot and then go back to the
> Control Panel and reopen the Automatic Updates applet and configure
> AU to meet your requirements.
>
> ******************************************************
February 24, 2005 9:35:52 PM

Archived from groups: microsoft.public.windowsme.general (More info?)

Thanks Mike.
I'll give that a try when I get time this weekend. I take-it the log will
reveal whats happening / not happening.

I'll get back to you on how it works out.

Steve

"Mike M" <No_Spam@Corned_Beef.Only> wrote in message
news:%23qu6o%23pGFHA.1948@TK2MSFTNGP10.phx.gbl...
> Steve,
>
> What follows may not work now that Win Me uses the version 4 Windows
> Update site but is worth a go.
>
> 1) Delete the file AUState.cfg from your WindowsUpdate folder
> 2) Delete any cab files there may be in your WindowsUpdate folder.
> 3) Using Regedit, edit the registry and browse to the key:
> HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update
> and create a new dword "DebugType" (no quotes, and no space between Debug
> & Type with its value equal to 1
> 4) Reboot your system.
>
> PLEASE do NOT reset or configure AutoUpdates in the Control Panel nor
> attempt to visit the WindowsUpdate site.
>
> Your system should now be logging AU activity and will create a text file
> "wupdlog.txt" in the ..\Program Files\WindowsUpdate\wupd\<user name>\
> folder. I may have missed something but hopefully the above will be
> sufficient. Note you will only get an update offered to you if deemed to
> be "critical" by Microsoft and not already installed.
>
> The first thing that should happen is that you are offered the Automatic
> Update EULA and asked to accept it. You can now adjust the AU settings to
> suit your requirements.
>
> Let this run for a few days or so. The log shouldn't get too large -
> normally four or five lines are added each time you boot but a fair number
> are added each time that the system actually runs AU. I doubt if the file
> will be even 50K after a week (but may well be wrong). Once set up AU
> should attempt to connect to the net and check for updates every 24 hours
> or when next on line and the connection is lightly loaded.
>
> Remember to disable logging by deleting the DebugType value in the
> registry when you have finished other wiser the log could get quite large
> over time.
> --
> Mike Maltby MS-MVP
> mike.maltby@gmail.com
>
>
> (yet another) Steve <nomail@nomail.com> wrote:
>
> > [Windows Me OS, all updates, very stable system, runs great-no error
> > messages. No registry hacks, still running the factory year 2000 OS
> > install. Very knowledgeable user-engineer with lots of PC background.
> > NAV 2005 all updates, Ad-aware, SpyBot S & D run regularly. Hardware
> > NAT Firewall (behind a router). No virus/trojans/spyware. System
> > Restore works fine.]
> >
> >
> >
> > My problem...
> >
> > Automatic Updates is not working on my system and it had worked
> > before. For about the past few years I've had it turned-off (update
> > manually) but turned it back on a few months ago. I even got the
> > Windows Update for AU (manually). Then I started to notice that there
> > were critical updates available that I wasn't notified about by AU.
> >
> >
> >
> > I've performed this procedure from the MS knowledge base with the
> > exception of renaming the Windows Update folder).
> > http://support.microsoft.com/default.aspx?scid=kb;en-us;275645
> >
> >
> >
> > I also found this procedure (below) on the web that Mike Maltby
> > MS-MVP wrote for someone else (with a different problem) that resets
> > Automatic Updating. This that didn't work either.
> >
> >
> >
> > ******************************************************
> >
> > ..try opening the Automatic Updates applet in the Control Panel,
> > select "Turn off automatic updating", and OK out. Now go to your
> > Program Files\Windows Update folder
> > and delete the file AUState.cfg. Reboot and then go back to the
> > Control Panel and reopen the Automatic Updates applet and configure
> > AU to meet your requirements.
> >
> > ******************************************************
>
Related resources
Anonymous
February 24, 2005 10:40:55 PM

Archived from groups: microsoft.public.windowsme.general (More info?)

Steve,

It's a long time since I've created and looked an AU log and that was for
the previous v3 but as far as I can recall it will record attempts to
contact the windowsupdate site. In addition you will need to also check
the file "Windows Update.log" in the Windows folder. The latter log may
already contain a clue as to the problem such as any errors encountered in
downloading the manifest (iuident.cab) from
https://v4beta.windowsupdate.com/autoupdate/getmanifest...
--
Mike Maltby MS-MVP
mike.maltby@gmail.com


(yet another) Steve <nomail@nomail.com> wrote:

> I'll give that a try when I get time this weekend. I take-it the log
> will reveal whats happening / not happening.
>
> I'll get back to you on how it works out.
February 24, 2005 10:40:56 PM

Archived from groups: microsoft.public.windowsme.general (More info?)

I'll check the WU log file tonight when I get home (a few hours from now-
EST, USA)

Thanks again Mike, you've provided a wealth of knowledge.

Steve

"Mike M" <No_Spam@Corned_Beef.Only> wrote in message
news:%234Oi$iqGFHA.2472@TK2MSFTNGP10.phx.gbl...
> Steve,
>
> It's a long time since I've created and looked an AU log and that was for
> the previous v3 but as far as I can recall it will record attempts to
> contact the windowsupdate site. In addition you will need to also check
> the file "Windows Update.log" in the Windows folder. The latter log may
> already contain a clue as to the problem such as any errors encountered in
> downloading the manifest (iuident.cab) from
> https://v4beta.windowsupdate.com/autoupdate/getmanifest...
> --
> Mike Maltby MS-MVP
> mike.maltby@gmail.com
>
>
> (yet another) Steve <nomail@nomail.com> wrote:
>
> > I'll give that a try when I get time this weekend. I take-it the log
> > will reveal whats happening / not happening.
> >
> > I'll get back to you on how it works out.
>
February 25, 2005 2:26:06 PM

Archived from groups: microsoft.public.windowsme.general (More info?)

Mike,
Something I found is very interesting.

First, my Windows Update.log file looks normal-all "Success" events. (I
tried posting this with the log attached but it would never show as posted.
If you want to see it I can email it to you.)

Here's where it get interesting, I decided to look at the contents time/date
data and file time/date
stamp of my original AUstate.cfg file and found the date was exactly the
same as the date I applied the "Windows Automatic Updating (Windows Me)"
update from the Windows Update site (on Friday, September 17, 2004):

In the Installation History (at WU site) The "Read more." link for this
update says:

"Within 24 hours of installing this update, the Automatic Update setup
wizard appears, to guide you through configuring your operating system so
you will be notified when critical updates are available for your computer."

Mike, the Automatic Update setup wizard never ran on my PC after applying
this update. This has to be the problem. How do I get the Automatic Update
setup wizard to run?

[.Or maybe I've got it all wrong with my hunch.]

Steve

"(yet another) Steve" <nomail@nomail.com> wrote in message
news:%232wtAuqGFHA.2132@TK2MSFTNGP14.phx.gbl...
> I'll check the WU log file tonight when I get home (a few hours from now-
> EST, USA)
>
> Thanks again Mike, you've provided a wealth of knowledge.
>
> Steve
>
> "Mike M" <No_Spam@Corned_Beef.Only> wrote in message
> news:%234Oi$iqGFHA.2472@TK2MSFTNGP10.phx.gbl...
> > Steve,
> >
> > It's a long time since I've created and looked an AU log and that was
for
> > the previous v3 but as far as I can recall it will record attempts to
> > contact the windowsupdate site. In addition you will need to also check
> > the file "Windows Update.log" in the Windows folder. The latter log may
> > already contain a clue as to the problem such as any errors encountered
in
> > downloading the manifest (iuident.cab) from
> > https://v4beta.windowsupdate.com/autoupdate/getmanifest...
> > --
> > Mike Maltby MS-MVP
> > mike.maltby@gmail.com
> >
> >
> > (yet another) Steve <nomail@nomail.com> wrote:
> >
> > > I'll give that a try when I get time this weekend. I take-it the log
> > > will reveal whats happening / not happening.
> > >
> > > I'll get back to you on how it works out.
> >
>
>
Anonymous
February 25, 2005 3:30:30 PM

Archived from groups: microsoft.public.windowsme.general (More info?)

Steve,

I'm sorry but I have nothing to add to my earlier suggestions which I set
out in my previous post. What does the AU log tell you? If AUState.cfg
has the date Sept 17 2004 it would appear that you didn't delete this file
as in the first step of my initial post or was this a copy you saved? If
the latter then I'm not surprised that it has the same date as when you
updated the Automatic Update control which brings us back to why the EULA
didn't display. I would suggest you start over again, delete AUState.cfg
and configure AU to start logging and then keep an eye on both the
"Windows Update.log" and wupdlog.txt files.

Regards,
--
Mike Maltby MS-MVP
mike.maltby@gmail.com


(yet another) Steve <nomail@nomail.com> wrote:

> Mike,
> Something I found is very interesting.
>
> First, my Windows Update.log file looks normal-all "Success" events.
> (I tried posting this with the log attached but it would never show
> as posted. If you want to see it I can email it to you.)
>
> Here's where it get interesting, I decided to look at the contents
> time/date data and file time/date
> stamp of my original AUstate.cfg file and found the date was exactly
> the same as the date I applied the "Windows Automatic Updating
> (Windows Me)" update from the Windows Update site (on Friday,
> September 17, 2004):
>
> In the Installation History (at WU site) The "Read more." link for
> this update says:
>
> "Within 24 hours of installing this update, the Automatic Update setup
> wizard appears, to guide you through configuring your operating
> system so you will be notified when critical updates are available
> for your computer."
>
> Mike, the Automatic Update setup wizard never ran on my PC after
> applying this update. This has to be the problem. How do I get the
> Automatic Update setup wizard to run?
>
> [.Or maybe I've got it all wrong with my hunch.]
February 25, 2005 3:30:31 PM

Archived from groups: microsoft.public.windowsme.general (More info?)

(1) Mike, I had saved the *original* AUstate.cfg file in a temp folder.
(2) The EULA didn't display because the Automatic Update setup wizard never
ran on my PC after
applying this update as it was supposed to.
(3) Yes I will start the logging process wupdlog.txt
(4) The Windows Update.log shows current (and past), to the minute,
successfil connections/downloads from WU site. I'll email you a copy I made
yesterday.

Steve

"Mike M" <No_Spam@Corned_Beef.Only> wrote in message
news:o do4KXzGFHA.2156@TK2MSFTNGP09.phx.gbl...
> Steve,
>
> I'm sorry but I have nothing to add to my earlier suggestions which I set
> out in my previous post. What does the AU log tell you? If AUState.cfg
> has the date Sept 17 2004 it would appear that you didn't delete this file
> as in the first step of my initial post or was this a copy you saved? If
> the latter then I'm not surprised that it has the same date as when you
> updated the Automatic Update control which brings us back to why the EULA
> didn't display. I would suggest you start over again, delete AUState.cfg
> and configure AU to start logging and then keep an eye on both the
> "Windows Update.log" and wupdlog.txt files.
>
> Regards,
> --
> Mike Maltby MS-MVP
> mike.maltby@gmail.com
>
>
> (yet another) Steve <nomail@nomail.com> wrote:
>
> > Mike,
> > Something I found is very interesting.
> >
> > First, my Windows Update.log file looks normal-all "Success" events.
> > (I tried posting this with the log attached but it would never show
> > as posted. If you want to see it I can email it to you.)
> >
> > Here's where it get interesting, I decided to look at the contents
> > time/date data and file time/date
> > stamp of my original AUstate.cfg file and found the date was exactly
> > the same as the date I applied the "Windows Automatic Updating
> > (Windows Me)" update from the Windows Update site (on Friday,
> > September 17, 2004):
> >
> > In the Installation History (at WU site) The "Read more." link for
> > this update says:
> >
> > "Within 24 hours of installing this update, the Automatic Update setup
> > wizard appears, to guide you through configuring your operating
> > system so you will be notified when critical updates are available
> > for your computer."
> >
> > Mike, the Automatic Update setup wizard never ran on my PC after
> > applying this update. This has to be the problem. How do I get the
> > Automatic Update setup wizard to run?
> >
> > [.Or maybe I've got it all wrong with my hunch.]
>
February 25, 2005 3:31:21 PM

Archived from groups: microsoft.public.windowsme.general (More info?)

Another thought,

I found the "Windows Automatic Updating (Windows Me)" in the Window Update
Catalog at the Windows Update site. Maybe if I try re-installing the update
(over the old install which is not uninstallable) this will fix the
problem.

My question is, how do I manually install the update after downloading it?

Steve



"(yet another) Steve" <nomail@nomail.com> wrote in message
news:iXDTd.8796$yf3.2100@newssvr31.news.prodigy.com...
> Mike,
> Something I found is very interesting.
>
> First, my Windows Update.log file looks normal-all "Success" events. (I
> tried posting this with the log attached but it would never show as
posted.
> If you want to see it I can email it to you.)
>
> Here's where it get interesting, I decided to look at the contents
time/date
> data and file time/date
> stamp of my original AUstate.cfg file and found the date was exactly the
> same as the date I applied the "Windows Automatic Updating (Windows Me)"
> update from the Windows Update site (on Friday, September 17, 2004):
>
> In the Installation History (at WU site) The "Read more." link for this
> update says:
>
> "Within 24 hours of installing this update, the Automatic Update setup
> wizard appears, to guide you through configuring your operating system so
> you will be notified when critical updates are available for your
computer."
>
> Mike, the Automatic Update setup wizard never ran on my PC after applying
> this update. This has to be the problem. How do I get the Automatic Update
> setup wizard to run?
>
> [.Or maybe I've got it all wrong with my hunch.]
>
> Steve
>
> "(yet another) Steve" <nomail@nomail.com> wrote in message
> news:%232wtAuqGFHA.2132@TK2MSFTNGP14.phx.gbl...
> > I'll check the WU log file tonight when I get home (a few hours from
now-
> > EST, USA)
> >
> > Thanks again Mike, you've provided a wealth of knowledge.
> >
> > Steve
> >
> > "Mike M" <No_Spam@Corned_Beef.Only> wrote in message
> > news:%234Oi$iqGFHA.2472@TK2MSFTNGP10.phx.gbl...
> > > Steve,
> > >
> > > It's a long time since I've created and looked an AU log and that was
> for
> > > the previous v3 but as far as I can recall it will record attempts to
> > > contact the windowsupdate site. In addition you will need to also
check
> > > the file "Windows Update.log" in the Windows folder. The latter log
may
> > > already contain a clue as to the problem such as any errors
encountered
> in
> > > downloading the manifest (iuident.cab) from
> > > https://v4beta.windowsupdate.com/autoupdate/getmanifest...
> > > --
> > > Mike Maltby MS-MVP
> > > mike.maltby@gmail.com
> > >
> > >
> > > (yet another) Steve <nomail@nomail.com> wrote:
> > >
> > > > I'll give that a try when I get time this weekend. I take-it the log
> > > > will reveal whats happening / not happening.
> > > >
> > > > I'll get back to you on how it works out.
> > >
> >
> >
>
>
Anonymous
February 25, 2005 4:11:13 PM

Archived from groups: microsoft.public.windowsme.general (More info?)

(yet another) Steve <nomail@nomail.com> wrote:

> Another thought,
>
> I found the "Windows Automatic Updating (Windows Me)" in the Window
> Update Catalog at the Windows Update site. Maybe if I try
> re-installing the update (over the old install which is not
> uninstallable) this will fix the problem.
>
> My question is, how do I manually install the update after
> downloading it?

By running the downloaded executable in the same way you would any other
downloaded hotfix. However why not try my suggestions first or would you
prefer me not to respond to your posts in future?
--
Mike Maltby MS-MVP
mike.maltby@gmail.com
February 25, 2005 4:22:18 PM

Archived from groups: microsoft.public.windowsme.general (More info?)

> My question is, how do I manually install the update after downloading it?

Extract the files, eg with Winzip or Winrar. R-click the .inf file and
select *Install*.

But I have to admit, like Mike, I'm wondering why you're not going with his
advice.



Shane
Anonymous
February 25, 2005 4:47:16 PM

Archived from groups: microsoft.public.windowsme.general (More info?)

Mike M <No_Spam@Corned_Beef.Only> wrote:

> By running the downloaded executable in the same way you would any
> other downloaded hotfix.

My apologies. I now see that this downloads as a CAB file. I also see
that Shane has explained how to install this.

> However why not try my suggestions first or
> would you prefer me not to respond to your posts in future?
--
Mike Maltby MS-MVP
mike.maltby@gmail.com
Anonymous
February 25, 2005 6:33:47 PM

Archived from groups: microsoft.public.windowsme.general (More info?)

Please don't send me unsolicited e-mails, especially ones containing
attachments.

There is no Automatic Update setup wizard as such, the EULA display is
triggered by AU when it first runs and finds no AUState.cfg file..
--
Mike Maltby MS-MVP
mike.maltby@gmail.com


(yet another) Steve <nomail@nomail.com> wrote:

> (1) Mike, I had saved the *original* AUstate.cfg file in a temp
> folder. (2) The EULA didn't display because the Automatic Update
> setup wizard never ran on my PC after
> applying this update as it was supposed to.
> (3) Yes I will start the logging process wupdlog.txt
> (4) The Windows Update.log shows current (and past), to the minute,
> successfil connections/downloads from WU site. I'll email you a copy
> I made yesterday.
February 25, 2005 6:33:48 PM

Archived from groups: microsoft.public.windowsme.general (More info?)

Mike,
Sorry about the email.

I guess the MS information regarding the "Automatic Update setup wizard" is
incorrect. I copied (below) from the "Read more..." link of the update in my
WU History.

"Within 24 hours of installing this update, the Automatic Update setup
wizard appears, to guide you through configuring your operating system so
you will be notified when critical updates are available for your computer."

This weekend I'll start the logging to see why the EULA never shows up.

Steve

"Mike M" <No_Spam@Corned_Beef.Only> wrote in message
news:uTpwk90GFHA.3928@TK2MSFTNGP09.phx.gbl...
> Please don't send me unsolicited e-mails, especially ones containing
> attachments.
>
> There is no Automatic Update setup wizard as such, the EULA display is
> triggered by AU when it first runs and finds no AUState.cfg file..
> --
> Mike Maltby MS-MVP
> mike.maltby@gmail.com
>
>
> (yet another) Steve <nomail@nomail.com> wrote:
>
> > (1) Mike, I had saved the *original* AUstate.cfg file in a temp
> > folder. (2) The EULA didn't display because the Automatic Update
> > setup wizard never ran on my PC after
> > applying this update as it was supposed to.
> > (3) Yes I will start the logging process wupdlog.txt
> > (4) The Windows Update.log shows current (and past), to the minute,
> > successfil connections/downloads from WU site. I'll email you a copy
> > I made yesterday.
>
Anonymous
February 25, 2005 8:30:39 PM

Archived from groups: microsoft.public.windowsme.general (More info?)

Steve,

There is no wizard that you can run, as I have already said it is
triggered when AU first kicks in and finds that the file AUState.cfg is
missing. Oh dear, I do seem to be repeating myself here.
--
Mike Maltby MS-MVP
mike.maltby@gmail.com


(yet another) Steve <nomail@nomail.com> wrote:

> Mike,
> Sorry about the email.
>
> I guess the MS information regarding the "Automatic Update setup
> wizard" is incorrect. I copied (below) from the "Read more..." link
> of the update in my WU History.
>
> "Within 24 hours of installing this update, the Automatic Update setup
> wizard appears, to guide you through configuring your operating
> system so you will be notified when critical updates are available
> for your computer."
>
> This weekend I'll start the logging to see why the EULA never shows
> up.
February 25, 2005 8:30:40 PM

Archived from groups: microsoft.public.windowsme.general (More info?)

Mike,
I fully understand what you are saying. I was just pointing out why I was
misled (by the MS statement).

Steve

"Mike M" <No_Spam@Corned_Beef.Only> wrote in message
news:o y$PCB2GFHA.1500@TK2MSFTNGP09.phx.gbl...
> Steve,
>
> There is no wizard that you can run, as I have already said it is
> triggered when AU first kicks in and finds that the file AUState.cfg is
> missing. Oh dear, I do seem to be repeating myself here.
> --
> Mike Maltby MS-MVP
> mike.maltby@gmail.com
>
>
> (yet another) Steve <nomail@nomail.com> wrote:
>
> > Mike,
> > Sorry about the email.
> >
> > I guess the MS information regarding the "Automatic Update setup
> > wizard" is incorrect. I copied (below) from the "Read more..." link
> > of the update in my WU History.
> >
> > "Within 24 hours of installing this update, the Automatic Update setup
> > wizard appears, to guide you through configuring your operating
> > system so you will be notified when critical updates are available
> > for your computer."
> >
> > This weekend I'll start the logging to see why the EULA never shows
> > up.
>
February 27, 2005 6:35:45 PM

Archived from groups: microsoft.public.windowsme.general (More info?)

Mike,

I tried your procedure (below) and it didn't work. No error messages, but
here's the details:
1) AUState.cfg never got recreated
2) wupdlog.txt never was created (searched the HD for it)
3) Windows Update.log never got updated (no new entries)
4) Never saw a Eula

Tried three times, rebooting and giving the system the idle time
required--nothing expected happened. I should have at-least seen updates in
the Window Update.log reflecting reboots and/or idle time since I knew that
was updating before.

After do this:
1) deleting the registry DebugType dword
2) rebooting,
3) re-applying the WinMe AU patch from Windows Update Catalog
4) rebooting

Windows Update.log started updating again. Here's a WU log snippet that
happened as I was typing this reply:

10:10:20 15:10:20 Success IUCTL Starting
2005-02-27 10:10:42 15:10:42 Success IUCTL Downloaded
iuident.cab from http://windowsupdate.microsoft.com/v4/ to C:\Program
Files\WindowsUpdate\V4
2005-02-27 10:10:42 15:10:42 Success IUCTL Checking to see if
new version of Windows Update software available
2005-02-27 10:10:42 15:10:42 Success IUCTL Current iuctl.dll
version: 5.3.3790.13
2005-02-27 10:10:42 15:10:42 Success IUCTL Current
iuengine.dll versiMike, I'on: 5.3.3790.13
2005-02-27 10:10:42 15:10:42 Success IUENGINE Starting
2005-02-27 10:10:42 15:10:42 Success IUENGINE Determining machine
configuration
2005-02-27 10:10:42 15:10:42 Success IUENGINE Determining machine
configuration
2005-02-27 10:10:46 15:10:46 Success IUENGINE Shutting down
2005-02-27 10:10:46 15:10:46 Success IUCTL Shutting down

Mike, I've been using the time stamp of AUstate.cfg (see
http://support.microsoft.com/default.aspx?scid=kb;en-us;275645) as an
indicator as to weather or not AU is working. According to the The Windows
Update.log, AU appears to be semi-functional (for lack of better words). Is
it possible the MS description is not correct and the time stamp of
Austate.cfg only changes when the AU cp gets changed? Just throwing out
ideas here.


Anyway, thanks for the effort,
Steve


"Mike M" <No_Spam@Corned_Beef.Only> wrote in message
news:%23qu6o%23pGFHA.1948@TK2MSFTNGP10.phx.gbl...
> Steve,
>
> What follows may not work now that Win Me uses the version 4 Windows
> Update site but is worth a go.
>
> 1) Delete the file AUState.cfg from your WindowsUpdate folder
> 2) Delete any cab files there may be in your WindowsUpdate folder.
> 3) Using Regedit, edit the registry and browse to the key:
> HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update
> and create a new dword "DebugType" (no quotes, and no space between Debug
> & Type with its value equal to 1
> 4) Reboot your system.
>
> PLEASE do NOT reset or configure AutoUpdates in the Control Panel nor
> attempt to visit the WindowsUpdate site.
>
> Your system should now be logging AU activity and will create a text file
> "wupdlog.txt" in the ..\Program Files\WindowsUpdate\wupd\<user name>\
> folder. I may have missed something but hopefully the above will be
> sufficient. Note you will only get an update offered to you if deemed to
> be "critical" by Microsoft and not already installed.
>
> The first thing that should happen is that you are offered the Automatic
> Update EULA and asked to accept it. You can now adjust the AU settings to
> suit your requirements.
>
> Let this run for a few days or so. The log shouldn't get too large -
> normally four or five lines are added each time you boot but a fair number
> are added each time that the system actually runs AU. I doubt if the file
> will be even 50K after a week (but may well be wrong). Once set up AU
> should attempt to connect to the net and check for updates every 24 hours
> or when next on line and the connection is lightly loaded.
>
> Remember to disable logging by deleting the DebugType value in the
> registry when you have finished other wiser the log could get quite large
> over time.
> --
> Mike Maltby MS-MVP
> mike.maltby@gmail.com
>
>
> (yet another) Steve <nomail@nomail.com> wrote:
>
> > [Windows Me OS, all updates, very stable system, runs great-no error
> > messages. No registry hacks, still running the factory year 2000 OS
> > install. Very knowledgeable user-engineer with lots of PC background.
> > NAV 2005 all updates, Ad-aware, SpyBot S & D run regularly. Hardware
> > NAT Firewall (behind a router). No virus/trojans/spyware. System
> > Restore works fine.]
> >
> >
> >
> > My problem...
> >
> > Automatic Updates is not working on my system and it had worked
> > before. For about the past few years I've had it turned-off (update
> > manually) but turned it back on a few months ago. I even got the
> > Windows Update for AU (manually). Then I started to notice that there
> > were critical updates available that I wasn't notified about by AU.
> >
> >
> >
> > I've performed this procedure from the MS knowledge base with the
> > exception of renaming the Windows Update folder).
> > http://support.microsoft.com/default.aspx?scid=kb;en-us;275645
> >
> >
> >
> > I also found this procedure (below) on the web that Mike Maltby
> > MS-MVP wrote for someone else (with a different problem) that resets
> > Automatic Updating. This that didn't work either.
> >
> >
> >
> > ******************************************************
> >
> > ..try opening the Automatic Updates applet in the Control Panel,
> > select "Turn off automatic updating", and OK out. Now go to your
> > Program Files\Windows Update folder
> > and delete the file AUState.cfg. Reboot and then go back to the
> > Control Panel and reopen the Automatic Updates applet and configure
> > AU to meet your requirements.
> >
> > ******************************************************
>
Anonymous
February 27, 2005 7:14:03 PM

Archived from groups: microsoft.public.windowsme.general (More info?)

Your WindowsUpdate log contains no entries relating to the operation of
Automatic Update but instead just the usual WU activity.

> Tried three times, rebooting and giving the system the idle time
> required--nothing expected happened.

Well you are way ahead of me as I don't have a clue as to the idle time
required. All I know is that this can be 24 hours or more after resetting
AU. Did you wait that long? I suspect not given the number of times you
say you have tried.

> Mike, I've been using the time stamp of AUstate.cfg (see
> http://support.microsoft.com/default.aspx?scid=kb;en-us;275645) as an
> indicator as to weather or not AU is working.

And the relevance of this is what? You have already confirmed that you
have not had a new copy of AUState.cfg created so to me at least AU has
yet to kick in which is also why you will see no wupdlog.txt. I feel you
may perhaps need to be a little more patient.
--
Mike Maltby MS-MVP
mike.maltby@gmail.com


(yet another) Steve <nomail@nomail.com> wrote:

> Mike,
>
> I tried your procedure (below) and it didn't work. No error messages,
> but here's the details:
> 1) AUState.cfg never got recreated
> 2) wupdlog.txt never was created (searched the HD for it)
> 3) Windows Update.log never got updated (no new entries)
> 4) Never saw a Eula
>
> Tried three times, rebooting and giving the system the idle time
> required--nothing expected happened. I should have at-least seen
> updates in the Window Update.log reflecting reboots and/or idle time
> since I knew that was updating before.
>
> After do this:
> 1) deleting the registry DebugType dword
> 2) rebooting,
> 3) re-applying the WinMe AU patch from Windows Update Catalog
> 4) rebooting
>
> Windows Update.log started updating again. Here's a WU log snippet
> that happened as I was typing this reply:
>
> 10:10:20 15:10:20 Success IUCTL Starting
> 2005-02-27 10:10:42 15:10:42 Success IUCTL Downloaded
> iuident.cab from http://windowsupdate.microsoft.com/v4/ to C:\Program
> Files\WindowsUpdate\V4
> 2005-02-27 10:10:42 15:10:42 Success IUCTL Checking to
> see if new version of Windows Update software available
> 2005-02-27 10:10:42 15:10:42 Success IUCTL Current
> iuctl.dll version: 5.3.3790.13
> 2005-02-27 10:10:42 15:10:42 Success IUCTL Current
> iuengine.dll version: 5.3.3790.13
> 2005-02-27 10:10:42 15:10:42 Success IUENGINE Starting
> 2005-02-27 10:10:42 15:10:42 Success IUENGINE Determining
> machine configuration
> 2005-02-27 10:10:42 15:10:42 Success IUENGINE Determining
> machine configuration
> 2005-02-27 10:10:46 15:10:46 Success IUENGINE Shutting down
> 2005-02-27 10:10:46 15:10:46 Success IUCTL Shutting down
>
> Mike, I've been using the time stamp of AUstate.cfg (see
> http://support.microsoft.com/default.aspx?scid=kb;en-us;275645) as an
> indicator as to weather or not AU is working. According to the The
> Windows Update.log, AU appears to be semi-functional (for lack of
> better words). Is it possible the MS description is not correct and
> the time stamp of Austate.cfg only changes when the AU cp gets
> changed? Just throwing out ideas here.
Anonymous
February 27, 2005 7:21:09 PM

Archived from groups: microsoft.public.windowsme.general (More info?)

I've just started the same test here myself.

I deleted AUState.cfg and iudent.cab from the WindowsUpdate folder. Set
DebugType = 1 and rebooted.

I have not yet seen the EULA nor has a new copy of AUState.cfg been
created. Logging however has started and wupdlog.txt contains:

fffd7639 2005.02.27 16:08:19 : Hook: Shell thread beginning
fffd7639 2005.02.27 16:08:19 : Executing AUThreadWorkerProc in current
dll
fffd7639 2005.02.27 16:08:19 : Hook: New cycle. State file says :
state=2, timeout=0, timestamp=2005.02.27 16:08:19
fffd7639 2005.02.27 16:08:19 : Hook: After adjusting passed time since
timestamp in state file, timeout=0
fffd7639 2005.02.27 16:08:19 : Hook State: Detect pending, Timeout = 0
fffd7639 2005.02.27 16:08:19 : Hook: Polling for connection
fffd7639 2005.02.27 16:08:19 : Hook: Got connection
fffd7639 2005.02.27 16:08:19 : Hook: Got connection, execute cmd in 5
mins - C:\WINDOWS\WUAUBoot.exe

Now to see how long it is before the EULA pops up and AUState.cfg is
created.
--
Mike Maltby MS-MVP
mike.maltby@gmail.com


(yet another) Steve <nomail@nomail.com> wrote:

> Mike,
>
> I tried your procedure (below) and it didn't work. No error messages,
> but here's the details:
> 1) AUState.cfg never got recreated
> 2) wupdlog.txt never was created (searched the HD for it)
> 3) Windows Update.log never got updated (no new entries)
> 4) Never saw a Eula
>
> Tried three times, rebooting and giving the system the idle time
> required--nothing expected happened. I should have at-least seen
> updates in the Window Update.log reflecting reboots and/or idle time
> since I knew that was updating before.
>
> After do this:
> 1) deleting the registry DebugType dword
> 2) rebooting,
> 3) re-applying the WinMe AU patch from Windows Update Catalog
> 4) rebooting
>
> Windows Update.log started updating again. Here's a WU log snippet
> that happened as I was typing this reply:
>
> 10:10:20 15:10:20 Success IUCTL Starting
> 2005-02-27 10:10:42 15:10:42 Success IUCTL Downloaded
> iuident.cab from http://windowsupdate.microsoft.com/v4/ to C:\Program
> Files\WindowsUpdate\V4
> 2005-02-27 10:10:42 15:10:42 Success IUCTL Checking to
> see if new version of Windows Update software available
> 2005-02-27 10:10:42 15:10:42 Success IUCTL Current
> iuctl.dll version: 5.3.3790.13
> 2005-02-27 10:10:42 15:10:42 Success IUCTL Current
> iuengine.dll versiMike, I'on: 5.3.3790.13
> 2005-02-27 10:10:42 15:10:42 Success IUENGINE Starting
> 2005-02-27 10:10:42 15:10:42 Success IUENGINE Determining
> machine configuration
> 2005-02-27 10:10:42 15:10:42 Success IUENGINE Determining
> machine configuration
> 2005-02-27 10:10:46 15:10:46 Success IUENGINE Shutting down
> 2005-02-27 10:10:46 15:10:46 Success IUCTL Shutting down
>
> Mike, I've been using the time stamp of AUstate.cfg (see
> http://support.microsoft.com/default.aspx?scid=kb;en-us;275645) as an
> indicator as to weather or not AU is working. According to the The
> Windows Update.log, AU appears to be semi-functional (for lack of
> better words). Is it possible the MS description is not correct and
> the time stamp of Austate.cfg only changes when the AU cp gets
> changed? Just throwing out ideas here.
>
>
> Anyway, thanks for the effort,
> Steve
>
>
> "Mike M" <No_Spam@Corned_Beef.Only> wrote in message
> news:%23qu6o%23pGFHA.1948@TK2MSFTNGP10.phx.gbl...
>> Steve,
>>
>> What follows may not work now that Win Me uses the version 4 Windows
>> Update site but is worth a go.
>>
>> 1) Delete the file AUState.cfg from your WindowsUpdate folder
>> 2) Delete any cab files there may be in your WindowsUpdate folder.
>> 3) Using Regedit, edit the registry and browse to the key:
>> HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto
>> Update and create a new dword "DebugType" (no quotes, and no space
>> between Debug & Type with its value equal to 1
>> 4) Reboot your system.
>>
>> PLEASE do NOT reset or configure AutoUpdates in the Control Panel nor
>> attempt to visit the WindowsUpdate site.
>>
>> Your system should now be logging AU activity and will create a text
>> file "wupdlog.txt" in the ..\Program Files\WindowsUpdate\wupd\<user
>> name>\ folder. I may have missed something but hopefully the above
>> will be sufficient. Note you will only get an update offered to you
>> if deemed to be "critical" by Microsoft and not already installed.
>>
>> The first thing that should happen is that you are offered the
>> Automatic Update EULA and asked to accept it. You can now adjust
>> the AU settings to suit your requirements.
>>
>> Let this run for a few days or so. The log shouldn't get too large -
>> normally four or five lines are added each time you boot but a fair
>> number are added each time that the system actually runs AU. I
>> doubt if the file will be even 50K after a week (but may well be
>> wrong). Once set up AU should attempt to connect to the net and
>> check for updates every 24 hours or when next on line and the
>> connection is lightly loaded.
>>
>> Remember to disable logging by deleting the DebugType value in the
>> registry when you have finished other wiser the log could get quite
>> large over time.
>> --
>> Mike Maltby MS-MVP
>> mike.maltby@gmail.com
>>
>>
>> (yet another) Steve <nomail@nomail.com> wrote:
>>
>>> [Windows Me OS, all updates, very stable system, runs great-no error
>>> messages. No registry hacks, still running the factory year 2000 OS
>>> install. Very knowledgeable user-engineer with lots of PC
>>> background. NAV 2005 all updates, Ad-aware, SpyBot S & D run
>>> regularly. Hardware NAT Firewall (behind a router). No
>>> virus/trojans/spyware. System Restore works fine.]
>>>
>>>
>>>
>>> My problem...
>>>
>>> Automatic Updates is not working on my system and it had worked
>>> before. For about the past few years I've had it turned-off (update
>>> manually) but turned it back on a few months ago. I even got the
>>> Windows Update for AU (manually). Then I started to notice that
>>> there were critical updates available that I wasn't notified about
>>> by AU.
>>>
>>>
>>>
>>> I've performed this procedure from the MS knowledge base with the
>>> exception of renaming the Windows Update folder).
>>> http://support.microsoft.com/default.aspx?scid=kb;en-us;275645
>>>
>>>
>>>
>>> I also found this procedure (below) on the web that Mike Maltby
>>> MS-MVP wrote for someone else (with a different problem) that resets
>>> Automatic Updating. This that didn't work either.
>>>
>>>
>>>
>>> ******************************************************
>>>
>>> ..try opening the Automatic Updates applet in the Control Panel,
>>> select "Turn off automatic updating", and OK out. Now go to your
>>> Program Files\Windows Update folder
>>> and delete the file AUState.cfg. Reboot and then go back to the
>>> Control Panel and reopen the Automatic Updates applet and configure
>>> AU to meet your requirements.
>>>
>>> ******************************************************
Anonymous
February 27, 2005 7:53:07 PM

Archived from groups: microsoft.public.windowsme.general (More info?)

OK.
AUState.cfg has now been created but no request to accept EULA popped up.
This is a little unexpected but Microsoft may have changed this
requirement since AU was first introduced in Win Me.

wupdlog.txt now has the following additional entries:
fffd7639 2005.02.27 16:20:14 : Hook State:Waiting for wuauboot with pid
fff053c5
fff053c5 2005.02.27 16:20:14 : ------------------------WUAUBOOT
BEGINS---------------------------
fff053c5 2005.02.27 16:20:14 : First connect, rescheduling 24hrs later
fff053c5 2005.02.27 16:20:14 : ------------------------WUAUBOOT
ENDS---------------------------
fffd7639 2005.02.27 16:20:14 : Hook State: Wuauboot terminated
fffd7639 2005.02.27 16:20:14 : Hook: New cycle. State file says :
state=1, timeout=86400, timestamp=2005.02.27 16:20:14
fffd7639 2005.02.27 16:20:16 : Hook: After adjusting passed time since
timestamp in state file, timeout=86398
fffd7639 2005.02.27 16:20:16 : Hook State: Detect pending, Timeout =
86398

Windows Update.log has no new entries.

I wonder whether re-registering iuclt.dll might help kick things off.
At Start | Run enter
REGSVR32 IUCTL.DLL
and then click OK
--
Mike Maltby MS-MVP
mike.maltby@gmail.com


(yet another) Steve <nomail@nomail.com> wrote:

> Mike,
>
> I tried your procedure (below) and it didn't work. No error messages,
> but here's the details:
> 1) AUState.cfg never got recreated
> 2) wupdlog.txt never was created (searched the HD for it)
> 3) Windows Update.log never got updated (no new entries)
> 4) Never saw a Eula
>
> Tried three times, rebooting and giving the system the idle time
> required--nothing expected happened. I should have at-least seen
> updates in the Window Update.log reflecting reboots and/or idle time
> since I knew that was updating before.
>
> After do this:
> 1) deleting the registry DebugType dword
> 2) rebooting,
> 3) re-applying the WinMe AU patch from Windows Update Catalog
> 4) rebooting
>
> Windows Update.log started updating again. Here's a WU log snippet
> that happened as I was typing this reply:
>
> 10:10:20 15:10:20 Success IUCTL Starting
> 2005-02-27 10:10:42 15:10:42 Success IUCTL Downloaded
> iuident.cab from http://windowsupdate.microsoft.com/v4/ to C:\Program
> Files\WindowsUpdate\V4
> 2005-02-27 10:10:42 15:10:42 Success IUCTL Checking to
> see if new version of Windows Update software available
> 2005-02-27 10:10:42 15:10:42 Success IUCTL Current
> iuctl.dll version: 5.3.3790.13
> 2005-02-27 10:10:42 15:10:42 Success IUCTL Current
> iuengine.dll versiMike, I'on: 5.3.3790.13
> 2005-02-27 10:10:42 15:10:42 Success IUENGINE Starting
> 2005-02-27 10:10:42 15:10:42 Success IUENGINE Determining
> machine configuration
> 2005-02-27 10:10:42 15:10:42 Success IUENGINE Determining
> machine configuration
> 2005-02-27 10:10:46 15:10:46 Success IUENGINE Shutting down
> 2005-02-27 10:10:46 15:10:46 Success IUCTL Shutting down
>
> Mike, I've been using the time stamp of AUstate.cfg (see
> http://support.microsoft.com/default.aspx?scid=kb;en-us;275645) as an
> indicator as to weather or not AU is working. According to the The
> Windows Update.log, AU appears to be semi-functional (for lack of
> better words). Is it possible the MS description is not correct and
> the time stamp of Austate.cfg only changes when the AU cp gets
> changed? Just throwing out ideas here.
>
>
> Anyway, thanks for the effort,
> Steve
>
>
> "Mike M" <No_Spam@Corned_Beef.Only> wrote in message
> news:%23qu6o%23pGFHA.1948@TK2MSFTNGP10.phx.gbl...
>> Steve,
>>
>> What follows may not work now that Win Me uses the version 4 Windows
>> Update site but is worth a go.
>>
>> 1) Delete the file AUState.cfg from your WindowsUpdate folder
>> 2) Delete any cab files there may be in your WindowsUpdate folder.
>> 3) Using Regedit, edit the registry and browse to the key:
>> HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto
>> Update and create a new dword "DebugType" (no quotes, and no space
>> between Debug & Type with its value equal to 1
>> 4) Reboot your system.
>>
>> PLEASE do NOT reset or configure AutoUpdates in the Control Panel nor
>> attempt to visit the WindowsUpdate site.
>>
>> Your system should now be logging AU activity and will create a text
>> file "wupdlog.txt" in the ..\Program Files\WindowsUpdate\wupd\<user
>> name>\ folder. I may have missed something but hopefully the above
>> will be sufficient. Note you will only get an update offered to you
>> if deemed to be "critical" by Microsoft and not already installed.
>>
>> The first thing that should happen is that you are offered the
>> Automatic Update EULA and asked to accept it. You can now adjust
>> the AU settings to suit your requirements.
>>
>> Let this run for a few days or so. The log shouldn't get too large -
>> normally four or five lines are added each time you boot but a fair
>> number are added each time that the system actually runs AU. I
>> doubt if the file will be even 50K after a week (but may well be
>> wrong). Once set up AU should attempt to connect to the net and
>> check for updates every 24 hours or when next on line and the
>> connection is lightly loaded.
>>
>> Remember to disable logging by deleting the DebugType value in the
>> registry when you have finished other wiser the log could get quite
>> large over time.
>> --
>> Mike Maltby MS-MVP
>> mike.maltby@gmail.com
>>
>>
>> (yet another) Steve <nomail@nomail.com> wrote:
>>
>>> [Windows Me OS, all updates, very stable system, runs great-no error
>>> messages. No registry hacks, still running the factory year 2000 OS
>>> install. Very knowledgeable user-engineer with lots of PC
>>> background. NAV 2005 all updates, Ad-aware, SpyBot S & D run
>>> regularly. Hardware NAT Firewall (behind a router). No
>>> virus/trojans/spyware. System Restore works fine.]
>>>
>>>
>>>
>>> My problem...
>>>
>>> Automatic Updates is not working on my system and it had worked
>>> before. For about the past few years I've had it turned-off (update
>>> manually) but turned it back on a few months ago. I even got the
>>> Windows Update for AU (manually). Then I started to notice that
>>> there were critical updates available that I wasn't notified about
>>> by AU.
>>>
>>>
>>>
>>> I've performed this procedure from the MS knowledge base with the
>>> exception of renaming the Windows Update folder).
>>> http://support.microsoft.com/default.aspx?scid=kb;en-us;275645
>>>
>>>
>>>
>>> I also found this procedure (below) on the web that Mike Maltby
>>> MS-MVP wrote for someone else (with a different problem) that resets
>>> Automatic Updating. This that didn't work either.
>>>
>>>
>>>
>>> ******************************************************
>>>
>>> ..try opening the Automatic Updates applet in the Control Panel,
>>> select "Turn off automatic updating", and OK out. Now go to your
>>> Program Files\Windows Update folder
>>> and delete the file AUState.cfg. Reboot and then go back to the
>>> Control Panel and reopen the Automatic Updates applet and configure
>>> AU to meet your requirements.
>>>
>>> ******************************************************
February 27, 2005 8:25:17 PM

Archived from groups: microsoft.public.windowsme.general (More info?)

Tried your suggestion (REGSVR32 IUCTL.DLL). Still no wupdlog.txt file
getting created. No ..\Program Files\WindowsUpdate\wupd\<user
>> name>\ folder either. I'm assuming your seeing wupdlog.txt right after
the reg mod and reboot.

Mike, for the reg mod I'm selecting [Edit-New-DWORD value] and entering
[DebugType] (no brackets). Then I right-click on [DebugType], select
[Modify] and then set the [Value data] to 1. Correct?

Steve

"Mike M" <No_Spam@Corned_Beef.Only> wrote in message
news:%23BDsPzOHFHA.3196@TK2MSFTNGP15.phx.gbl...
> OK.
> AUState.cfg has now been created but no request to accept EULA popped up.
> This is a little unexpected but Microsoft may have changed this
> requirement since AU was first introduced in Win Me.
>
> wupdlog.txt now has the following additional entries:
> fffd7639 2005.02.27 16:20:14 : Hook State:Waiting for wuauboot with pid
> fff053c5
> fff053c5 2005.02.27 16:20:14 : ------------------------WUAUBOOT
> BEGINS---------------------------
> fff053c5 2005.02.27 16:20:14 : First connect, rescheduling 24hrs later
> fff053c5 2005.02.27 16:20:14 : ------------------------WUAUBOOT
> ENDS---------------------------
> fffd7639 2005.02.27 16:20:14 : Hook State: Wuauboot terminated
> fffd7639 2005.02.27 16:20:14 : Hook: New cycle. State file says :
> state=1, timeout=86400, timestamp=2005.02.27 16:20:14
> fffd7639 2005.02.27 16:20:16 : Hook: After adjusting passed time since
> timestamp in state file, timeout=86398
> fffd7639 2005.02.27 16:20:16 : Hook State: Detect pending, Timeout =
> 86398
>
> Windows Update.log has no new entries.
>
> I wonder whether re-registering iuclt.dll might help kick things off.
> At Start | Run enter
> REGSVR32 IUCTL.DLL
> and then click OK
> --
> Mike Maltby MS-MVP
> mike.maltby@gmail.com
>
>
> (yet another) Steve <nomail@nomail.com> wrote:
>
> > Mike,
> >
> > I tried your procedure (below) and it didn't work. No error messages,
> > but here's the details:
> > 1) AUState.cfg never got recreated
> > 2) wupdlog.txt never was created (searched the HD for it)
> > 3) Windows Update.log never got updated (no new entries)
> > 4) Never saw a Eula
> >
> > Tried three times, rebooting and giving the system the idle time
> > required--nothing expected happened. I should have at-least seen
> > updates in the Window Update.log reflecting reboots and/or idle time
> > since I knew that was updating before.
> >
> > After do this:
> > 1) deleting the registry DebugType dword
> > 2) rebooting,
> > 3) re-applying the WinMe AU patch from Windows Update Catalog
> > 4) rebooting
> >
> > Windows Update.log started updating again. Here's a WU log snippet
> > that happened as I was typing this reply:
> >
> > 10:10:20 15:10:20 Success IUCTL Starting
> > 2005-02-27 10:10:42 15:10:42 Success IUCTL Downloaded
> > iuident.cab from http://windowsupdate.microsoft.com/v4/ to C:\Program
> > Files\WindowsUpdate\V4
> > 2005-02-27 10:10:42 15:10:42 Success IUCTL Checking to
> > see if new version of Windows Update software available
> > 2005-02-27 10:10:42 15:10:42 Success IUCTL Current
> > iuctl.dll version: 5.3.3790.13
> > 2005-02-27 10:10:42 15:10:42 Success IUCTL Current
> > iuengine.dll versiMike, I'on: 5.3.3790.13
> > 2005-02-27 10:10:42 15:10:42 Success IUENGINE Starting
> > 2005-02-27 10:10:42 15:10:42 Success IUENGINE Determining
> > machine configuration
> > 2005-02-27 10:10:42 15:10:42 Success IUENGINE Determining
> > machine configuration
> > 2005-02-27 10:10:46 15:10:46 Success IUENGINE Shutting down
> > 2005-02-27 10:10:46 15:10:46 Success IUCTL Shutting down
> >
> > Mike, I've been using the time stamp of AUstate.cfg (see
> > http://support.microsoft.com/default.aspx?scid=kb;en-us;275645) as an
> > indicator as to weather or not AU is working. According to the The
> > Windows Update.log, AU appears to be semi-functional (for lack of
> > better words). Is it possible the MS description is not correct and
> > the time stamp of Austate.cfg only changes when the AU cp gets
> > changed? Just throwing out ideas here.
> >
> >
> > Anyway, thanks for the effort,
> > Steve
> >
> >
> > "Mike M" <No_Spam@Corned_Beef.Only> wrote in message
> > news:%23qu6o%23pGFHA.1948@TK2MSFTNGP10.phx.gbl...
> >> Steve,
> >>
> >> What follows may not work now that Win Me uses the version 4 Windows
> >> Update site but is worth a go.
> >>
> >> 1) Delete the file AUState.cfg from your WindowsUpdate folder
> >> 2) Delete any cab files there may be in your WindowsUpdate folder.
> >> 3) Using Regedit, edit the registry and browse to the key:
> >> HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto
> >> Update and create a new dword "DebugType" (no quotes, and no space
> >> between Debug & Type with its value equal to 1
> >> 4) Reboot your system.
> >>
> >> PLEASE do NOT reset or configure AutoUpdates in the Control Panel nor
> >> attempt to visit the WindowsUpdate site.
> >>
> >> Your system should now be logging AU activity and will create a text
> >> file "wupdlog.txt" in the ..\Program Files\WindowsUpdate\wupd\<user
> >> name>\ folder. I may have missed something but hopefully the above
> >> will be sufficient. Note you will only get an update offered to you
> >> if deemed to be "critical" by Microsoft and not already installed.
> >>
> >> The first thing that should happen is that you are offered the
> >> Automatic Update EULA and asked to accept it. You can now adjust
> >> the AU settings to suit your requirements.
> >>
> >> Let this run for a few days or so. The log shouldn't get too large -
> >> normally four or five lines are added each time you boot but a fair
> >> number are added each time that the system actually runs AU. I
> >> doubt if the file will be even 50K after a week (but may well be
> >> wrong). Once set up AU should attempt to connect to the net and
> >> check for updates every 24 hours or when next on line and the
> >> connection is lightly loaded.
> >>
> >> Remember to disable logging by deleting the DebugType value in the
> >> registry when you have finished other wiser the log could get quite
> >> large over time.
> >> --
> >> Mike Maltby MS-MVP
> >> mike.maltby@gmail.com
> >>
> >>
> >> (yet another) Steve <nomail@nomail.com> wrote:
> >>
> >>> [Windows Me OS, all updates, very stable system, runs great-no error
> >>> messages. No registry hacks, still running the factory year 2000 OS
> >>> install. Very knowledgeable user-engineer with lots of PC
> >>> background. NAV 2005 all updates, Ad-aware, SpyBot S & D run
> >>> regularly. Hardware NAT Firewall (behind a router). No
> >>> virus/trojans/spyware. System Restore works fine.]
> >>>
> >>>
> >>>
> >>> My problem...
> >>>
> >>> Automatic Updates is not working on my system and it had worked
> >>> before. For about the past few years I've had it turned-off (update
> >>> manually) but turned it back on a few months ago. I even got the
> >>> Windows Update for AU (manually). Then I started to notice that
> >>> there were critical updates available that I wasn't notified about
> >>> by AU.
> >>>
> >>>
> >>>
> >>> I've performed this procedure from the MS knowledge base with the
> >>> exception of renaming the Windows Update folder).
> >>> http://support.microsoft.com/default.aspx?scid=kb;en-us;275645
> >>>
> >>>
> >>>
> >>> I also found this procedure (below) on the web that Mike Maltby
> >>> MS-MVP wrote for someone else (with a different problem) that resets
> >>> Automatic Updating. This that didn't work either.
> >>>
> >>>
> >>>
> >>> ******************************************************
> >>>
> >>> ..try opening the Automatic Updates applet in the Control Panel,
> >>> select "Turn off automatic updating", and OK out. Now go to your
> >>> Program Files\Windows Update folder
> >>> and delete the file AUState.cfg. Reboot and then go back to the
> >>> Control Panel and reopen the Automatic Updates applet and configure
> >>> AU to meet your requirements.
> >>>
> >>> ******************************************************
>
Anonymous
February 27, 2005 8:44:13 PM

Archived from groups: microsoft.public.windowsme.general (More info?)

(yet another) Steve <nomail@nomail.com> wrote:

> Tried your suggestion (REGSVR32 IUCTL.DLL). Still no wupdlog.txt file
> getting created. No ..\Program Files\WindowsUpdate\wupd\<user
> name>\ folder either. I'm assuming your seeing wupdlog.txt right
> after the reg mod and reboot.

No, one has to wait.

> Mike, for the reg mod I'm selecting [Edit-New-DWORD value] and
> entering [DebugType] (no brackets). Then I right-click on
> [DebugType], select [Modify] and then set the [Value data] to 1.
> Correct?

Yes
--
Mike Maltby MS-MVP
mike.maltby@gmail.com
February 28, 2005 5:18:31 AM

Archived from groups: microsoft.public.windowsme.general (More info?)

PC has been on for 7 hours. Rebooted twice. Still no wupdlog.txt file. No
new AUState.cfg.

Steve

"Mike M" <No_Spam@Corned_Beef.Only> wrote in message
news:eVdazPPHFHA.2280@TK2MSFTNGP15.phx.gbl...
> (yet another) Steve <nomail@nomail.com> wrote:
>
> > Tried your suggestion (REGSVR32 IUCTL.DLL). Still no wupdlog.txt file
> > getting created. No ..\Program Files\WindowsUpdate\wupd\<user
> > name>\ folder either. I'm assuming your seeing wupdlog.txt right
> > after the reg mod and reboot.
>
> No, one has to wait.
>
> > Mike, for the reg mod I'm selecting [Edit-New-DWORD value] and
> > entering [DebugType] (no brackets). Then I right-click on
> > [DebugType], select [Modify] and then set the [Value data] to 1.
> > Correct?
>
> Yes
> --
> Mike Maltby MS-MVP
> mike.maltby@gmail.com
>
>
Anonymous
February 28, 2005 1:55:32 PM

Archived from groups: microsoft.public.windowsme.general (More info?)

It looks as if the EULA is no longer "popped-up" following the removal of
the file AUState.cfg but I won't be able to confirm that here for some
hours yet as my test PC (actually a virtual PC running on this box in a
window) hasn't been running for 24 hours since I removed AUState.cfg and
started logging. However unlike your system AUState.cfg was recreated here
and logging commenced.

Meanwhile all I can suggest is that you check the version of various AU/WU
related files. What are the version of the following files?
WUAURES.DLL v5.4.5681.0
WUAUBOOT.EXE v5.4.5681.0
WUAUCLT.EXE v5.4.5681.0
WUPDMGR.EXE v5.0.2013.1
WUAUPD98.DLL v5.4.1083.11
WUAUCPL.CPL v5.4.1083.11
WUV3IS.DLL5.v4.1083.11
IUCTL.DLL v5.3.3790.13
IUENGINE.DLL v5.3.3790.13

You may also want to try re-registering WUAUPD98.DLL (which I meant to
suggest earlier but for some reason omitted) and WUV3IS.DLL although I am
not sure as to whether WUV3IS.DLL is used now the AU and WU use the v4
site.
--
Mike Maltby MS-MVP
mike.maltby@gmail.com


(yet another) Steve <nomail@nomail.com> wrote:

> PC has been on for 7 hours. Rebooted twice. Still no wupdlog.txt
> file. No new AUState.cfg.
Anonymous
March 1, 2005 1:39:59 AM

Archived from groups: microsoft.public.windowsme.general (More info?)

Steve,

Not that it helps, but I can now confirm that after deleting the file
AUState.cfg users are no longer asked to accept the AU EULA again. I
suspect this behaviour changed when Win me moved from using the old v3
Windows Update site to the v4 site.
--
Mike Maltby MS-MVP
mike.maltby@gmail.com


(yet another) Steve <nomail@nomail.com> wrote:

> PC has been on for 7 hours. Rebooted twice. Still no wupdlog.txt
> file. No new AUState.cfg.
March 1, 2005 2:10:18 AM

Archived from groups: microsoft.public.windowsme.general (More info?)

OK Mike, I just finished re-registering the files (WUAUPD98.DLL and
WUV3IS.DLL).and checking the file versions. All file versions matched yours
with these two exceptions:

WUpdMgr.exe -v5.3.220.1000
WUV3IS.DLL5 -v5.4.5440.0

Remember, I applied the AU update [Windows Automatic Updating (Windows Me) -
(Posted Date: November 22, 2002] from windows update (which I also suspect
broke AU).

Steve

"Mike M" <No_Spam@Corned_Beef.Only> wrote in message
news:o dI1wZeHFHA.3088@tk2msftngp13.phx.gbl...
> Steve,
>
> Not that it helps, but I can now confirm that after deleting the file
> AUState.cfg users are no longer asked to accept the AU EULA again. I
> suspect this behaviour changed when Win me moved from using the old v3
> Windows Update site to the v4 site.
> --
> Mike Maltby MS-MVP
> mike.maltby@gmail.com
>
>
> (yet another) Steve <nomail@nomail.com> wrote:
>
> > PC has been on for 7 hours. Rebooted twice. Still no wupdlog.txt
> > file. No new AUState.cfg.
>
Anonymous
March 1, 2005 3:24:46 AM

Archived from groups: microsoft.public.windowsme.general (More info?)

Steve,

A different Win Me box (a real one this time rather than a virtual
machine, that has been running Win Me since launch) has the same file
versions as yourself.

WUPDMGR.EXE v5.0.2013.1 is the version distributed with Win Me which was
updated to v5.3.220.1000 within days of Win Me's release. I'm not even
certain as to whether this file is still used now that Win Me uses the v4
site. Certainly the file WUV3IS.DLL is history having been replaced by
iuctl.dll when Win Me moved to using the v4 site. When Win Me was
launched wuv3is.dll was version 5.4.29.0 finally reaching 5.4.5440.0 in
June 2002 and then replaced by iuctl.dll when WUv4 was launched.
Incidentally for some reason I gave the wrong version for wuv3is.dll in my
previous post.

Not that this helps solve your problem. You appear to have the correct
version of the current files used by AU and WU and can safely ignore
wuv3is.dll and possibly also wupdmgr.exe. I'll look through my notes and
see what I can find about kick-starting AU.
--
Mike Maltby MS-MVP
mike.maltby@gmail.com


(yet another) Steve <nomail@nomail.com> wrote:

> OK Mike, I just finished re-registering the files (WUAUPD98.DLL and
> WUV3IS.DLL).and checking the file versions. All file versions matched
> yours with these two exceptions:
>
> WUpdMgr.exe -v5.3.220.1000
> WUV3IS.DLL5 -v5.4.5440.0
>
> Remember, I applied the AU update [Windows Automatic Updating
> (Windows Me) - (Posted Date: November 22, 2002] from windows update
> (which I also suspect broke AU).
Anonymous
March 1, 2005 3:36:44 AM

Archived from groups: microsoft.public.windowsme.general (More info?)

Mike M <No_Spam@Corned_Beef.Only> wrote:

> Not that it helps, but I can now confirm that after deleting the file
> AUState.cfg users are no longer asked to accept the AU EULA again. I
> suspect this behaviour changed when Win me moved from using the old v3
> Windows Update site to the v4 site.

CORRECTION. Have just been prompted to accept AU EULA some 32+ hours
after deleting AUState.cfg and enabling AU logging. Rebooted once in that
time (at 24½ hours) due to need to do maintenance work on the parent PC.
--
Mike Maltby MS-MVP
mike.maltby@gmail.com
March 1, 2005 3:38:41 AM

Archived from groups: microsoft.public.windowsme.general (More info?)

Ok Mike, I'm with you here. Since the re-registration of the files (and a
reboot) its been about 1.5 hours and no creation of wupdlog.txt yet.

And again, thank you very much for helping out...
Steve


"Mike M" <No_Spam@Corned_Beef.Only> wrote in message
news:e7zAUUfHFHA.3628@TK2MSFTNGP15.phx.gbl...
> Steve,
>
> A different Win Me box (a real one this time rather than a virtual
> machine, that has been running Win Me since launch) has the same file
> versions as yourself.
>
> WUPDMGR.EXE v5.0.2013.1 is the version distributed with Win Me which was
> updated to v5.3.220.1000 within days of Win Me's release. I'm not even
> certain as to whether this file is still used now that Win Me uses the v4
> site. Certainly the file WUV3IS.DLL is history having been replaced by
> iuctl.dll when Win Me moved to using the v4 site. When Win Me was
> launched wuv3is.dll was version 5.4.29.0 finally reaching 5.4.5440.0 in
> June 2002 and then replaced by iuctl.dll when WUv4 was launched.
> Incidentally for some reason I gave the wrong version for wuv3is.dll in my
> previous post.
>
> Not that this helps solve your problem. You appear to have the correct
> version of the current files used by AU and WU and can safely ignore
> wuv3is.dll and possibly also wupdmgr.exe. I'll look through my notes and
> see what I can find about kick-starting AU.
> --
> Mike Maltby MS-MVP
> mike.maltby@gmail.com
>
>
> (yet another) Steve <nomail@nomail.com> wrote:
>
> > OK Mike, I just finished re-registering the files (WUAUPD98.DLL and
> > WUV3IS.DLL).and checking the file versions. All file versions matched
> > yours with these two exceptions:
> >
> > WUpdMgr.exe -v5.3.220.1000
> > WUV3IS.DLL5 -v5.4.5440.0
> >
> > Remember, I applied the AU update [Windows Automatic Updating
> > (Windows Me) - (Posted Date: November 22, 2002] from windows update
> > (which I also suspect broke AU).
>
March 1, 2005 4:06:36 AM

Archived from groups: microsoft.public.windowsme.general (More info?)

Very interesting indeed!

One thing I should mention. I have SpyBot Search & Destroy 1.3 w/Immunize
(no TeaTimer), SpywareBlaster 3.2 and NAV 2005 running (all latest final
release versions--no betas, fully updated).

Hopefully one of these aren't causing my problem.

Steve


"Mike M" <No_Spam@Corned_Beef.Only> wrote in message
news:e76UAbfHFHA.2700@TK2MSFTNGP09.phx.gbl...
> Mike M <No_Spam@Corned_Beef.Only> wrote:
>
> > Not that it helps, but I can now confirm that after deleting the file
> > AUState.cfg users are no longer asked to accept the AU EULA again. I
> > suspect this behaviour changed when Win me moved from using the old v3
> > Windows Update site to the v4 site.
>
> CORRECTION. Have just been prompted to accept AU EULA some 32+ hours
> after deleting AUState.cfg and enabling AU logging. Rebooted once in that
> time (at 24½ hours) due to need to do maintenance work on the parent PC.
> --
> Mike Maltby MS-MVP
> mike.maltby@gmail.com
>
>
Anonymous
March 1, 2005 4:28:17 AM

Archived from groups: microsoft.public.windowsme.general (More info?)

SpyBot and Spyware Blaster (which doesn't usually run continuously but
rather blocks access to various sites through the registry) will cause no
problems. More than can be said for NAV. To be honest I'm not normally
prepared to even help those who have installed NAV other than to remove it
as it does more damage to systems running Win Me than any other piece of
software other than of course System Works, System Doctor, LiveUpdate and
NIS all of which make a pretty good job in time of destroying most systems
where they are installed and especially so Win Me.

Do you have NAV blocking scripts by any chance?
--
Mike Maltby MS-MVP
mike.maltby@gmail.com


(yet another) Steve <nomail@nomail.com> wrote:

> Very interesting indeed!
>
> One thing I should mention. I have SpyBot Search & Destroy 1.3
> w/Immunize (no TeaTimer), SpywareBlaster 3.2 and NAV 2005 running
> (all latest final release versions--no betas, fully updated).
>
> Hopefully one of these aren't causing my problem.
March 1, 2005 5:27:37 AM

Archived from groups: microsoft.public.windowsme.general (More info?)

> Do you have NAV blocking scripts by any chance?
Not to my knowledge. I'm using 2005 with the default settings. Been using
NAV on this PC since version 2000 with never a problem.

Steve

"Mike M" <No_Spam@Corned_Beef.Only> wrote in message
news:u6jcm4fHFHA.4084@TK2MSFTNGP14.phx.gbl...
> SpyBot and Spyware Blaster (which doesn't usually run continuously but
> rather blocks access to various sites through the registry) will cause no
> problems. More than can be said for NAV. To be honest I'm not normally
> prepared to even help those who have installed NAV other than to remove it
> as it does more damage to systems running Win Me than any other piece of
> software other than of course System Works, System Doctor, LiveUpdate and
> NIS all of which make a pretty good job in time of destroying most systems
> where they are installed and especially so Win Me.
>
> Do you have NAV blocking scripts by any chance?
> --
> Mike Maltby MS-MVP
> mike.maltby@gmail.com
>
>
> (yet another) Steve <nomail@nomail.com> wrote:
>
> > Very interesting indeed!
> >
> > One thing I should mention. I have SpyBot Search & Destroy 1.3
> > w/Immunize (no TeaTimer), SpywareBlaster 3.2 and NAV 2005 running
> > (all latest final release versions--no betas, fully updated).
> >
> > Hopefully one of these aren't causing my problem.
>
Anonymous
March 1, 2005 5:39:32 AM

Archived from groups: microsoft.public.windowsme.general (More info?)

> using NAV on this PC since version 2000 with never a problem

Until now that is. AU isn't working.
--
Mike Maltby MS-MVP
mike.maltby@gmail.com


(yet another) Steve <nomail@nomail.com> wrote:

> Not to my knowledge. I'm using 2005 with the default settings. Been
> using NAV on this PC since version 2000 with never a problem.
Anonymous
March 1, 2005 3:40:58 PM

Archived from groups: microsoft.public.windowsme.general (More info?)

Mike M <No_Spam@Corned_Beef.Only> wrote:

> Until now that is. AU isn't working.

PS. There was supposed to be a smiley :-) at the end of my last post.
--
Mike Maltby MS-MVP
mike.maltby@gmail.com
March 1, 2005 3:51:47 PM

Archived from groups: microsoft.public.windowsme.general (More info?)

I believe you see so many Me and NAV problems is because its installed bas
is usually many thousands of times more than any other AV. I've had AU
working using NAV versions 2000, 2001, 2002, 2003 and 2004. AU stopped
working *while* I had 2004 installed.

There's nothing wrong with NAV if you understand it. The biggest problem Me
and NAV have is using a System Restore point that was made before NAV did an
update. In that case the only fix is to uninstall and reinstall NAV.
Remember NAV still the second best AV (to KAV) out there
http://www.av-comparatives.org/.

Steve

"Mike M" <No_Spam@Corned_Beef.Only> wrote in message
news:uhSwnfgHFHA.400@TK2MSFTNGP14.phx.gbl...
> > using NAV on this PC since version 2000 with never a problem
>
> Until now that is. AU isn't working.
> --
> Mike Maltby MS-MVP
> mike.maltby@gmail.com
>
>
> (yet another) Steve <nomail@nomail.com> wrote:
>
> > Not to my knowledge. I'm using 2005 with the default settings. Been
> > using NAV on this PC since version 2000 with never a problem.
>
March 1, 2005 3:55:33 PM

Archived from groups: microsoft.public.windowsme.general (More info?)

I posted before seeing the smiley. Seriously though, do you see a trend of
NAV breaking AU?

Steve

"(yet another) Steve" <nomail@nomail.com> wrote in message
news:D zZUd.15276$hU7.4443@newssvr33.news.prodigy.com...
> I believe you see so many Me and NAV problems is because its installed bas
> is usually many thousands of times more than any other AV. I've had AU
> working using NAV versions 2000, 2001, 2002, 2003 and 2004. AU stopped
> working *while* I had 2004 installed.
>
> There's nothing wrong with NAV if you understand it. The biggest problem
Me
> and NAV have is using a System Restore point that was made before NAV did
an
> update. In that case the only fix is to uninstall and reinstall NAV.
> Remember NAV still the second best AV (to KAV) out there
> http://www.av-comparatives.org/.
>
> Steve
>
> "Mike M" <No_Spam@Corned_Beef.Only> wrote in message
> news:uhSwnfgHFHA.400@TK2MSFTNGP14.phx.gbl...
> > > using NAV on this PC since version 2000 with never a problem
> >
> > Until now that is. AU isn't working.
> > --
> > Mike Maltby MS-MVP
> > mike.maltby@gmail.com
> >
> >
> > (yet another) Steve <nomail@nomail.com> wrote:
> >
> > > Not to my knowledge. I'm using 2005 with the default settings. Been
> > > using NAV on this PC since version 2000 with never a problem.
> >
>
>
March 1, 2005 4:30:21 PM

Archived from groups: microsoft.public.windowsme.general (More info?)

CORRECTION. I actually didn't have AU working with all those NAV versions. I
had AU working on this PC for about a year 2000 to 2001. Then I'd opted to
turn it off and keep the PC updated by manually visiting the WU site. I
turned AU back ON in Sept. of 2004--the same date that the WU for AU was
offered to me.

Steve

"(yet another) Steve" <nomail@nomail.com> wrote in message
news:9DZUd.15277$hU7.2064@newssvr33.news.prodigy.com...
> I posted before seeing the smiley. Seriously though, do you see a trend of
> NAV breaking AU?
>
> Steve
>
> "(yet another) Steve" <nomail@nomail.com> wrote in message
> news:D zZUd.15276$hU7.4443@newssvr33.news.prodigy.com...
> > I believe you see so many Me and NAV problems is because its installed
bas
> > is usually many thousands of times more than any other AV. I've had AU
> > working using NAV versions 2000, 2001, 2002, 2003 and 2004. AU stopped
> > working *while* I had 2004 installed.
> >
> > There's nothing wrong with NAV if you understand it. The biggest problem
> Me
> > and NAV have is using a System Restore point that was made before NAV
did
> an
> > update. In that case the only fix is to uninstall and reinstall NAV.
> > Remember NAV still the second best AV (to KAV) out there
> > http://www.av-comparatives.org/.
> >
> > Steve
> >
> > "Mike M" <No_Spam@Corned_Beef.Only> wrote in message
> > news:uhSwnfgHFHA.400@TK2MSFTNGP14.phx.gbl...
> > > > using NAV on this PC since version 2000 with never a problem
> > >
> > > Until now that is. AU isn't working.
> > > --
> > > Mike Maltby MS-MVP
> > > mike.maltby@gmail.com
> > >
> > >
> > > (yet another) Steve <nomail@nomail.com> wrote:
> > >
> > > > Not to my knowledge. I'm using 2005 with the default settings. Been
> > > > using NAV on this PC since version 2000 with never a problem.
> > >
> >
> >
>
>
Anonymous
March 1, 2005 4:31:05 PM

Archived from groups: microsoft.public.windowsme.general (More info?)

Rather than a trend I see a mighty avalanche with virtually all domestic
Symantec products (as distinct from some of their enterprise products) in
time destroying whatever system they are installed on, not just Win Me but
also XP, etc. To be totally frank Symantec products are a total disaster
and provide more income to support engineers than any other product on the
market - just possible challenged by some of the more invasive recent
commercial malware/spyware. The moment Symantec get their hands on a
product it condemns that product to a lingering death be it Ghost (when
they took over Binary Research), GoBack (bought from Adaptec/Roxio) or
Partition Magic and Drive Image (formerly PowerQuest). Symantec have done
nothing to reassure users that the same won't now be happening with the
various products from Veritas due to its merger with Symantec.
--
Mike Maltby MS-MVP
mike.maltby@gmail.com


(yet another) Steve <nomail@nomail.com> wrote:

> I posted before seeing the smiley. Seriously though, do you see a
> trend of NAV breaking AU?
March 1, 2005 4:57:07 PM

Archived from groups: microsoft.public.windowsme.general (More info?)

Hmmm. Not good. Maybe its time to reconsider a new AV. I currently use NAV
05 on this PC and my daughters Win XP Home (SP2) PC. Any recommendations?

Back to my issue. Just snipped this from my Windows Update.log file. It's
from last night when I got home from work and powered-up the PC.

2005-02-28 17:44:33 22:44:33 Success IUCTL Starting
2005-02-28 17:44:35 22:44:35 Success IUCTL Shutting down
2005-02-28 18:08:40 23:08:40 Success IUCTL Starting
2005-02-28 18:08:41 23:08:41 Success IUCTL Downloaded
iuident.cab from http://windowsupdate.microsoft.com/v4/ to C:\Program
Files\WindowsUpdate\V4
2005-02-28 18:08:41 23:08:41 Success IUCTL Checking to see if
new version of Windows Update software available
2005-02-28 18:08:41 23:08:41 Success IUCTL Current iuctl.dll
version: 5.3.3790.13
2005-02-28 18:08:41 23:08:41 Success IUCTL Current
iuengine.dll version: 5.3.3790.13
2005-02-28 18:08:41 23:08:41 Success IUENGINE Starting
2005-02-28 18:08:42 23:08:42 Success IUENGINE Determining machine
configuration
2005-02-28 18:08:42 23:08:42 Success IUENGINE Determining machine
configuration
2005-02-28 18:09:26 23:09:26 Success IUENGINE Shutting down
2005-02-28 18:09:26 23:09:26 Success IUCTL Shutting down

Steve

"Mike M" <No_Spam@Corned_Beef.Only> wrote in message
news:ub3zSLmHFHA.1528@TK2MSFTNGP09.phx.gbl...
> Rather than a trend I see a mighty avalanche with virtually all domestic
> Symantec products (as distinct from some of their enterprise products) in
> time destroying whatever system they are installed on, not just Win Me but
> also XP, etc. To be totally frank Symantec products are a total disaster
> and provide more income to support engineers than any other product on the
> market - just possible challenged by some of the more invasive recent
> commercial malware/spyware. The moment Symantec get their hands on a
> product it condemns that product to a lingering death be it Ghost (when
> they took over Binary Research), GoBack (bought from Adaptec/Roxio) or
> Partition Magic and Drive Image (formerly PowerQuest). Symantec have done
> nothing to reassure users that the same won't now be happening with the
> various products from Veritas due to its merger with Symantec.
> --
> Mike Maltby MS-MVP
> mike.maltby@gmail.com
>
>
> (yet another) Steve <nomail@nomail.com> wrote:
>
> > I posted before seeing the smiley. Seriously though, do you see a
> > trend of NAV breaking AU?
>
Anonymous
March 1, 2005 6:27:43 PM

Archived from groups: microsoft.public.windowsme.general (More info?)

Steve,

To be honest I don't think that NAV is the cause of your problems provided
that it isn't blocking scripting or the like, not that I know whether this
would be a factor or not. Also, as far as I can see from two PCs here
running Win Me, AU makes no entries in the Windows Update.log when
checking although it may well do so when it pulls down a file.
Regrettably I don't have a Win Me PC here that requires an update to allow
me to check. What I do have though is a Win Me virtual image I can use
that is clean, that is it is in an as out of the box condition. I'll set
that up in a bit and see what happens but suspect it might take 24 hours
for things to kick in and provide a usable log. I'll post back more
later.

The big problem we have is that few users ever report problems as such
with AU, either because it just works or just as likely because they have
it disabled.
--
Mike Maltby MS-MVP
mike.maltby@gmail.com


(yet another) Steve <nomail@nomail.com> wrote:

> Hmmm. Not good. Maybe its time to reconsider a new AV. I currently
> use NAV 05 on this PC and my daughters Win XP Home (SP2) PC. Any
> recommendations?
>
> Back to my issue. Just snipped this from my Windows Update.log file.
> It's from last night when I got home from work and powered-up the PC.
>
> 2005-02-28 17:44:33 22:44:33 Success IUCTL Starting
> 2005-02-28 17:44:35 22:44:35 Success IUCTL Shutting down
> 2005-02-28 18:08:40 23:08:40 Success IUCTL Starting
> 2005-02-28 18:08:41 23:08:41 Success IUCTL Downloaded
> iuident.cab from http://windowsupdate.microsoft.com/v4/ to C:\Program
> Files\WindowsUpdate\V4
> 2005-02-28 18:08:41 23:08:41 Success IUCTL Checking to
> see if new version of Windows Update software available
> 2005-02-28 18:08:41 23:08:41 Success IUCTL Current
> iuctl.dll version: 5.3.3790.13
> 2005-02-28 18:08:41 23:08:41 Success IUCTL Current
> iuengine.dll version: 5.3.3790.13
> 2005-02-28 18:08:41 23:08:41 Success IUENGINE Starting
> 2005-02-28 18:08:42 23:08:42 Success IUENGINE Determining
> machine configuration
> 2005-02-28 18:08:42 23:08:42 Success IUENGINE Determining
> machine configuration
> 2005-02-28 18:09:26 23:09:26 Success IUENGINE Shutting down
> 2005-02-28 18:09:26 23:09:26 Success IUCTL Shutting down
Anonymous
March 1, 2005 8:42:08 PM

Archived from groups: microsoft.public.windowsme.general (More info?)

Yet another correction. AU access to the WU site does indeed create
entries in the Windows Update.log as I originally indicated. Sorry about
that.
--
Mike Maltby MS-MVP
mike.maltby@gmail.com


Mike M <No_Spam@Corned_Beef.Only> wrote:

> To be honest I don't think that NAV is the cause of your problems
> provided that it isn't blocking scripting or the like, not that I
> know whether this would be a factor or not. Also, as far as I can
> see from two PCs here running Win Me, AU makes no entries in the
> Windows Update.log when checking although it may well do so when it
> pulls down a file. Regrettably I don't have a Win Me PC here that
> requires an update to allow me to check. What I do have though is a
> Win Me virtual image I can use that is clean, that is it is in an as
> out of the box condition. I'll set that up in a bit and see what
> happens but suspect it might take 24 hours for things to kick in and
> provide a usable log. I'll post back more later.
>
> The big problem we have is that few users ever report problems as such
> with AU, either because it just works or just as likely because they
> have it disabled.
>> 2005-02-28 18:09:26 23:09:26 Success IUENGINE Shutting
>> down 2005-02-28 18:09:26 23:09:26 Success IUCTL Shutting
>> down
March 1, 2005 8:42:09 PM

Archived from groups: microsoft.public.windowsme.general (More info?)

So at-least there's some evidence of AU activitity in my WU log.

Steve
(who's seeing the light at the end of the tunnel or pointing out the glass
is half full....)

"Mike M" <No_Spam@Corned_Beef.Only> wrote in message
news:%232mI$XoHFHA.3148@TK2MSFTNGP14.phx.gbl...
> Yet another correction. AU access to the WU site does indeed create
> entries in the Windows Update.log as I originally indicated. Sorry about
> that.
> --
> Mike Maltby MS-MVP
> mike.maltby@gmail.com
>
>
> Mike M <No_Spam@Corned_Beef.Only> wrote:
>
> > To be honest I don't think that NAV is the cause of your problems
> > provided that it isn't blocking scripting or the like, not that I
> > know whether this would be a factor or not. Also, as far as I can
> > see from two PCs here running Win Me, AU makes no entries in the
> > Windows Update.log when checking although it may well do so when it
> > pulls down a file. Regrettably I don't have a Win Me PC here that
> > requires an update to allow me to check. What I do have though is a
> > Win Me virtual image I can use that is clean, that is it is in an as
> > out of the box condition. I'll set that up in a bit and see what
> > happens but suspect it might take 24 hours for things to kick in and
> > provide a usable log. I'll post back more later.
> >
> > The big problem we have is that few users ever report problems as such
> > with AU, either because it just works or just as likely because they
> > have it disabled.
> >> 2005-02-28 18:09:26 23:09:26 Success IUENGINE Shutting
> >> down 2005-02-28 18:09:26 23:09:26 Success IUCTL Shutting
> >> down
>
Anonymous
March 1, 2005 10:18:33 PM

Archived from groups: microsoft.public.windowsme.general (More info?)

I take it that you still don't have a wupdlog.txt being created?
--
Mike Maltby MS-MVP
mike.maltby@gmail.com


(yet another) Steve <nomail@nomail.com> wrote:

> So at-least there's some evidence of AU activitity in my WU log.
March 1, 2005 10:18:34 PM

Archived from groups: microsoft.public.windowsme.general (More info?)

I'm not home right now but as of this morning there's wasn't any wupdlog.txt
file yet.

Steve
"Mike M" <No_Spam@Corned_Beef.Only> wrote in message
news:%23m$H3NpHFHA.2936@TK2MSFTNGP15.phx.gbl...
> I take it that you still don't have a wupdlog.txt being created?
> --
> Mike Maltby MS-MVP
> mike.maltby@gmail.com
>
>
> (yet another) Steve <nomail@nomail.com> wrote:
>
> > So at-least there's some evidence of AU activitity in my WU log.
>
March 2, 2005 2:57:27 AM

Archived from groups: microsoft.public.windowsme.general (More info?)

PC has been on for 1.5 hrs tonight and still no wupdlog.txt or AUState.cfg.

Steve

"(yet another) Steve" <nomail@nomail.com> wrote in message
news:umLrxSpHFHA.4048@TK2MSFTNGP15.phx.gbl...
> I'm not home right now but as of this morning there's wasn't any
wupdlog.txt
> file yet.
>
> Steve
> "Mike M" <No_Spam@Corned_Beef.Only> wrote in message
> news:%23m$H3NpHFHA.2936@TK2MSFTNGP15.phx.gbl...
> > I take it that you still don't have a wupdlog.txt being created?
> > --
> > Mike Maltby MS-MVP
> > mike.maltby@gmail.com
> >
> >
> > (yet another) Steve <nomail@nomail.com> wrote:
> >
> > > So at-least there's some evidence of AU activitity in my WU log.
> >
>
>
!