Reason for update bug: Local file permissions

  • Thread starter Thread starter Matthias
  • Start date Start date
M

Matthias

There are dozens of complains about the update function.
autoupdate always updates backwards to definition 5678 (or
the #number when the package was originally installed),
while starting the manual update seems to install the
actual version.

On my system (XP Home version, SP2) the answer is simple:
Update doesn't work at all when I'm logged in as ordinary
user. Even the manual update is just a fake. It simply
can't work, because an ordinary user has no permission to
write into the [C:]/programs/... subdirectories where the
anitspyware information is localized. After logging in as
local administrator, a real update is performed, as can be
seen by the directory content.

Are the developers of Microsoft aware about this problem?

Matthias
 
There are several bugs in this area, one of which is a display
issue--updates happen, and the correct update is downloaded, but the display
is incorrect, both in the AutoUpdate notification and in Help, about.
Running a manual update, which doesn't in fact bring in new bits, corrects
the appearance bug.

I can't confirm the details of your permissions/user type issue, but it
wouldn't surprise me. I believe the developers are aware of both sets of
issues.
 
Back
Top