Iím having issues with Windows Updates. Prior to getting to this point I removed a lot of spyware including Look2Me. I had to use a L2MFix remover which did take control of some registry keys as well as deleted some registry keys. I donít know if this is the exact cause of my current issues but I just thought Iíd throw this out there.
Iíve searched all of Googleís Groups as well as exhausted all options on Microsoftís Newsgroups. Whenever I attempt to use Windows Update, it will download all available updates but as soon as it says initializing installation, every single download fails to install. I go straight to my WindowsUpdate.log and find that error # 0x80240020 is the culprit which means something along the lines of there was no INTERACTIVE USER to input data.
Iíve renamed and deleted the SoftwareDistribution folder, re-registered numerous .dlls, almost everything and anything I can think of. The administrator group includes my user name as well as test user names I created in hopes I could get the other user accounts to do the Windows Updates.
Now Iím wondering if anyone here has any extensive knowledge on how Windows Updates works. Iíd like to know exactly what it looks for before going ahead with the installation of the downloads.
People are speculating that it is some type of permissions issue. Iíve also had this issue come up with a Windows XP Home installation. To alleviate the WinXP Home problem I just did an overlay of the OS. However, I do not have a Windows 2000 Pro Upgrade CD so I cannot do an overlay at this time.
Iíd love for more than anything to solve this issue. Even Microsoft themselves cannot seem to solve this issue. Iíve been talking to them through e-mails and we are still unable to resolve this situation.
I know this is long and drawn out, so here are some cliff notes:
Windows 2000 Pro installation
Unable to do Windows Updates
Receiving error: 0x80240020 which means no interactive user available to input data
Need to resolve said error
Tried numerous things and nothing has worked
I believe it has something to do with the registry permissions and or some other type of Local Policy Settings