If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#22
|
|||
|
|||
(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 |
#23
|
|||
|
|||
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 |
#24
|
|||
|
|||
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. |
#25
|
|||
|
|||
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. |
#26
|
|||
|
|||
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. |
#27
|
|||
|
|||
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). |
#28
|
|||
|
|||
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 |
#29
|
|||
|
|||
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). |
#30
|
|||
|
|||
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 |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
alt-ctrl-del not working on AMD motherboard? | Zalek Bloom | General | 4 | September 11th 04 04:20 AM |
Windows automatic updates | littlebarney | General | 4 | August 2nd 04 12:40 AM |
Reinstalling Updates After Reinstalling Windows | Jim | General | 1 | July 22nd 04 06:15 AM |
installing updates | Krys | Setup & Installation | 1 | July 8th 04 06:17 AM |
Automatic Windows Update Not Working | Michael Cummings | Software & Applications | 1 | July 5th 04 06:53 AM |