[Win Me] Automatic Updates isn't working

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" wrote in message
...
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



(yet another) Steve 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...b;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" wrote in message
...
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\Win dowsUpdate\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



(yet another) Steve 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...b;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.

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

(yet another) Steve 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

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

Steve

"Mike M" wrote in message
...
(yet another) Steve 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

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



(yet another) Steve wrote:

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

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



(yet another) Steve wrote:

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

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" wrote in message
...
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



(yet another) Steve wrote:

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

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



(yet another) Steve 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).

Mike M 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

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" wrote in message
...
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



(yet another) Steve 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).

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" wrote in message
...
Mike M 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