1) solution assumes that user has another computer with the same OS that
actually works. in reality, i have 2 with the same OS and neither work, and
at-home-user-bob typically only has 1 computer.
2) solution takes too much work. the solution i posted takes about 5 mouse
clicks. i've got other things i'd rather be doing than free beta for bill
gates. MS to violate "if it ain't broke don't fix it". {old patcher could
be improved? maybe. new patcher working? no. old patcher working? yes.}
=use old patcher
imo v6 should be beta and not the primary patcher- wonder how many man hours
lost to ppl wasting time on windows update bugs
"SRP" wrote:
> If you are getting the annoying "Updates were unable to be successfully
> installed" message when trying to install updates, or the 0X80240020 error in
> the WindowsUpdate.log, here is the solution.
> Start regedit and goto
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
> NT\CurrentVersion\Winlogon\
> Look in the Notify folder for the SensLgn subfolder. If it isnt there,
> thats your problem. You will then have to get the SensLgn subfolder from a
> pc that is installing updates ok. Make sure the working pc has the same OS
> version as the one you cant install updates on.
> From the working pc: In regedit, highlight the SensLgn subfolder and then
> goto Registry> Export Registry File. Name it what you want (ie wusfix.reg).
> Copy that reg file to the non working pc.
> From the non working pc: Start regedit and goto Registry>Import Registry
> file. Browse to and highlight that reg file, and then click the open
> button. You should receive a message that it was successfully imported.
> Also, if it exists, delete the Notify_Disable directory under
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
> NT\CurrentVersion\Winlogon\
> Reboot and test Windows updates. All should be well.
>
> "dev" wrote:
>
> > i'm posting this b/c i've spent hours searching for fixes and am attempting
> > to save others the hassle; i've tried everything i can find and the only way
> > i can get the updates is to use the old windows update program. imo the new
> > windows update program is fubar- don't waste your time and pull your hair out
> > trying to fix it unless you work for microsoft. i copied and pasted some
> > instructions given by silverice at the bottom of this post for using the old
> > win update program 'that actually works.' personally, i'm having this
> > problem with 2 win2k machines one of which i just formatted, but i've seen
> > the same error listed over and over in various threads for various OSs.
> >
> > BASIC PROBLEMS: (in c:/windows/windowsupdate.txt)
> > -WARNING: Failed to evaluate Installed rule, updateId =
> > {ED300F67-421C-4C08-B3BA-F35C55F3B427}.100, error = 0x80041017
> > -WARNING: GetUserTokenFromSessionId failed with hr 0x800706d3
> > -WARNING: Exit code = 0x80240020
> >
> > BASIC SOLUTION:
> > Subject: Work around for Windows Update v6 8/4/2005 9:22 AM PST
> >
> > By: SilverICE In: microsoft.public.windowsupdate
> >
> >
> > I've had all sorts of problems getting Windows Update to run on several of my
> > Windows 2003 servers, and have found a work around that is very helpful.
> >
> > So, FWIW:
> > 1. Open up browser and go to Windows Update Site - it will check your
> > computer to make sure you have the latest version, blah, blah, blah.
> > 2. Don't click the 'Express' or 'Custom' buttons. Instead, click the 'Use
> > administrator options' link on the left side of the page.
> > 3. On the Administrator Option page, under 'Update multiple operating
> > systems', click the 'Windows Update Catalog' link. This will take you to the
> > previous version of Windows Update which actually works.
> > 4. On the left side of the page, under 'See Also', click the 'Windows
> > Update' link.
> > 5. Scan for updates.
> >
> > Hope this helps some of you out.
> >
|
Similar Threads
Linear Mode
