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