[Win Me] Automatic Updates isn't working

user

Splendid
Dec 26, 2003
3,943
0
22,780
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
 
G

Guest

Guest
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.
>
> ******************************************************
 

user

Splendid
Dec 26, 2003
3,943
0
22,780
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.
> >
> > ******************************************************
>
 
G

Guest

Guest
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.asp
--
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.
 

user

Splendid
Dec 26, 2003
3,943
0
22,780
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.asp
> --
> 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.
>
 

user

Splendid
Dec 26, 2003
3,943
0
22,780
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.asp
> > --
> > 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.
> >
>
>
 
G

Guest

Guest
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.]
 

user

Splendid
Dec 26, 2003
3,943
0
22,780
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:Odo4KXzGFHA.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.]
>
 

user

Splendid
Dec 26, 2003
3,943
0
22,780
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.asp
> > > --
> > > 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.
> > >
> >
> >
>
>
 
G

Guest

Guest
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
 

Shane

Distinguished
Apr 7, 2004
754
0
18,980
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
 
G

Guest

Guest
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
 
G

Guest

Guest
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.
 

user

Splendid
Dec 26, 2003
3,943
0
22,780
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.
>
 
G

Guest

Guest
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.
 

user

Splendid
Dec 26, 2003
3,943
0
22,780
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:Oy$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.
>
 

user

Splendid
Dec 26, 2003
3,943
0
22,780
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.
> >
> > ******************************************************
>
 
G

Guest

Guest
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.
 
G

Guest

Guest
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.
>>>
>>> ******************************************************
 
G

Guest

Guest
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.
>>>
>>> ******************************************************
 

user

Splendid
Dec 26, 2003
3,943
0
22,780
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.
> >>>
> >>> ******************************************************
>
 
G

Guest

Guest
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
 

user

Splendid
Dec 26, 2003
3,943
0
22,780
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
>
>
 
G

Guest

Guest
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.
 
G

Guest

Guest
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.