Those who have used the auto-updater have had their manifests changed, potentially causing errata in the latest betas. So, do a proper update. Yes, this issue was fixed once before, but the SFX archives used to silently update the product were being updated instead of recreated, causing the bug to persist.
Due to this possible manifest and configuration mismatch, to avoid certain bugs you need to run a proper update with the installer. Remember, the beta quick updater is still experimental. I've already seen problems in QA testing in XP of the latest beta build (failure to terminate PL). I will get it right by v4.1 for sure, but until then, remember that it is experimental.
In general, the auto-updater has not been particularly successful thus far, even though I thought it was. For some, it may have worked perfectly. However, for others, it may have never worked, or changed the application manifests, causing possible problems (result is Process Lasso and the governor no longer ran with highest rights).
UPDATE: I just completed new self-update of the updater capability, so we're getting there. Also, for those who saw the SFX extraction destination dialog (it wasn't silent), this was apparently due to the recreation of the archive too, in some way. It should now be fixed. I believe only 32-bit builds were affected.
Monday, 21 February 2011
Subscribe to:
Post Comments (Atom)
0 comments:
Post a Comment