That’s really not good enough for such an important piece of software. Updating those notes should must become part of the process of releasing a new version and it should must be completed before the update is pushed to the users.
I just had a quick update also, with reboot required.
I would not worry about that. What CIS tells is what is installed. Updaters or updating with an installer sometimes forget to change the version number in the list of installed Software; just a minor shortcoming.
Thanks Eric, I wasn't sure if to call it a bug or not. Thanks
Updated won XP SP3 without a glitch, reboot needed. No popup for a second update, check for update told me my version is already up to date. Version 5.5.195786.1383
So now, the update is in one time and not like yesterday in 2 times or am I missing something?
The update yesterday was two times because of a change in the updater process:
[b]IMPROVED![/b] Program updater now uses a new updating mechanism which reduces the update size significantly
[quote="Qibbler post:68, topic:269313"]
Erm...
I've just had my in-program installer upgrade me to version 1383. I was on version 1355.
Didn’t need two reboots like this thread suggests (but haven’t read every page) so maybe on a roll.
[/quote]
That’s odd given the change in binaries as stated in the Release Notes. But that being said we still don’t know what the update from .1382 to.1383 is about.
I'd like to download this new beast in case of need to reinstall. Is the link at the start of this thread now version 1382 or 1383?
I bug-broke my last version twice, so hopefully I’ll be kinder with this one ;D
I would suggest to wait until the Release Notes are updated.
Can we get a definite explanation for why every single comodo update re-enables weekly virus scanning? Also great job on not providing a 64bit download link.
[quote]FIXED! Various incompatibilities between BO defense and various applications(e.g. games, windows applications etc.)
[/quote]
Anyone know if starcraft 2 is able to run without excluding it ?
We have changed the build number from 1382 to 1383.
What does this mean and why?
During the 2 stage update, some client computers received inconsistent executables with the update. Specifically, inspect.sys(WHQL certified version) has been received by some clients and this version was the version associated with the ARP protection and internet connection issues.
So if you get another update notification, you might get this file replaced as well as cfpver.dat file. For some of you, it will be only cfpver.dat which is simply the version information file while for some of you it will be 2 files.
At egemen. I am using the .1382 mod preview now updated to .1383. I noticed that in the CIS installation folder I have version .1320 for inspect.sys where I have version .1382 in the \repair\ and \system32\drivers\ folders. I assume I can safely overwrite the 1320 with the 1382 from the repair folder?