New Build# 17.27.0.1146
Christian posted the Changelog of fixes and changes made, including changing Autoscan to the more appropriate and telling name Idle scan: http://forum.bitdefender.com/index.php?s=&...st&p=212451
See this link for finding your Build number and other useful information: http://forum.bitdefender.com/index.php?showtopic=35499
Comments
-
Christian posted the Changelog of fixes and changes made, including changing Autoscan to the more appropriate and telling name Idle scan: http://forum.bitdefender.com/index.php?s=&...st&p=212451
See this link for finding your Build number and other useful information: http://forum.bitdefender.com/index.php?showtopic=35499
It would be helpful if when an a new update is released if a comment was added to the Fixes and Changes post as to how many reboots could be expected before the update is complete. I prefer not to be caught in the middle of a product update so if do the first reboot I am going to keep rebooting as soon as I see another is required. The problem is if I am running a program that takes a while to run I have to stop it and then restart it and stop it and restart it everytime a new reboot is required in order to process the entire update.
If I knew in advance about how many reboots were required to complete the update I would not keep restarting and then restopping programs that are running in order to reboot. Now I realise that the number of reboots can vary but if at least some notations was made in the update post indicating a maximum number of reboots that may be required to finish the update it would be very helpful0 -
It would be helpful if when an a new update is released if a comment was added to the Fixes and Changes post as to how many reboots could be expected before the update is complete. I prefer not to be caught in the middle of a product update so if do the first reboot I am going to keep rebooting as soon as I see another is required. The problem is if I am running a program that takes a while to run I have to stop it and then restart it and stop it and restart it everytime a new reboot is required in order to process the entire update.
If I knew in advance about how many reboots were required to complete the update I would not keep restarting and then restopping programs that are running in order to reboot. Now I realise that the number of reboots can vary but if at least some notations was made in the update post indicating a maximum number of reboots that may be required to finish the update it would be very helpful
Did you try and turning on "postpone reboot"? that way you can reboot at a later time when you have time.
0 -
Did you try and turning on "postpone reboot"? that way you can reboot at a later time when you have time.
That does not solve the problem. The issues is that updates often require multiple reboots to complete. Now if an update requires only reboot to complete and it said so in the update notice on the forum or better yet on the GUI next to 'reboot to update' than I might not mind shutting everything down and rebooting. In fact I think that is a great idea. Put a reboot counter next to where it says 'reboot to update.' So if it says there are five reboots left to complete the entire update a user might decide not to update at that time and delay it
Now if I am running programs pretty much all day long for say the next several days and if I know that there will be multiple reboots to complete the install I can delay it like you suggest. However, if I know there will be only one reboot to complete the update I may decide to bite the bullet then, shut everything down and reboot at that time.
The issue is: 'Not knowing how many reboots will be required to complete the complete update and therefore not knowing whether I should start the update process when I see the notice or delay it.' In otherwords, the number of updates required to complete the reboot process will determine if I do the update when I see the Event notice or whether I will delay it to a more convienent time.0 -
Christian posted the Changelog of fixes and changes made, including changing Autoscan to the more appropriate and telling name Idle scan: http://forum.bitdefender.com/index.php?s=&...st&p=212451
See this link for finding your Build number and other useful information: http://forum.bitdefender.com/index.php?showtopic=35499
I had what appears to have been a conflict between MBAM Premium 2.0 and the current update. After rebooting about a dozen times when the reboot to replace files message kept popping up in BDIS I decided yesterday afternoon to uninstall MBAM Premium 2.0 before doing the next reboot, though I might have been able to just temporarily disable Protection in MBAM, the update to BDIS was successful. I then reinstalled MBAM Premium 2.0 and have not seen any mesages from BDIS since. I subsquently added 'updatesrv.exe' to MBAM Malware exlusions though this may not solve possible future conflicts between MBAM 2.0 Premium and BDIS updates.
The conflict if there was one could have been due to the intergration of the TrafficLight SDK 1.5.0.169 into BDIS, conflicting with MBAM Website Protection feature. This however is just a guess and all appears to be good now.
P.S. The small installer file for the new update is now available on the internet for download. I don't belive Christian provides a link for the updated installer in his update notification post. Sorry if I missed it.0
