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 |
#11
|
|||
|
|||
Mike M 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 |
#12
|
|||
|
|||
(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" wrote in message ... 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 (yet another) Steve 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.] |
#13
|
|||
|
|||
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 (yet another) Steve 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. |
#14
|
|||
|
|||
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" wrote in message ... 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 (yet another) Steve 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. |
#15
|
|||
|
|||
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 (yet another) Steve 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. |
#16
|
|||
|
|||
Mike,
I fully understand what you are saying. I was just pointing out why I was misled (by the MS statement). Steve "Mike M" wrote in message ... 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 (yet another) Steve 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. |
#17
|
|||
|
|||
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. ************************************************** **** |
#19
|
|||
|
|||
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 (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. ************************************************** **** |
#20
|
|||
|
|||
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. ************************************************** **** |
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 |