Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: bob3160 on May 05, 2007, 02:36:01 PM
-
(http://img.photobucket.com/albums/v190/bob3160/ShellFTP/avast!RestartingLoop.png)
This seems to have occured sinc the update to the latest version. Evety time avast updates,
it's asking to reboot. (vps update) ???
-
It may be a remnant of the last program update.
- First check the contents of the C:\Program Files\Alwil Software\Avast4\Setup\setup.log file, which should show you why it thinks the reboot is needed.
This could be solved, in some systems, by deleting the file C:\Program Files\Alwil Software\Avast4\Setup\reboot.txt
-
Thanks David. I've removed the Reboot.txt file :)
-
There is a BUG in the latest Avast, so systems which has the 8.3 tweak installed, will get the reboots dialogs
For some weird reason Avast dont want to fix this bug, stating it will require a reboot with all their users. Which is correct, but ignoring the thousands of users right now, who are getting reboot popups constantly, is just not an option and Avast needs to fix the bugs they have introduced in to their products.
Anyway disable the 8.3 tweak: http://forum.avast.com/index.php?topic=28102.msg229764#msg229764
-
Hi Erroneus ,
I would have to agree I have the very problem as mentioned above . I have been using Avast since 2005 and been mostly happy with how it performs I may have to reconsider it's use and move over to a different product as this not satisfactory all for any users affected they should send over a update fix for this .
-
I don't know why it has an effect on those who have applied the 8.3 tweak, because earlier updates with those that had the same 8.3 tweak applied didn't have this problem.
I don't know what has changed, but what I do know the amount of people who have applied this 8.3 tweak is going to be infinitesimal by comparison the the 10s of millions of avast users and those that don't have this 8.3 tweak applied. So I can understand where they are coming from when they say they suggest reversing the tweak and even give the .reg to make it easier.
I have never felt it necessary to apply this tweak to stop the conversion to 8.3 short name conversion. There might have been a performance issue when this tweak was first thought of but I doubt that now as many have reported there either appears to be no noticeable impact on performance or none at all. I would tend to believe Igor's comment in this post http://forum.avast.com/index.php?topic=28102.msg230206#msg230206 (http://forum.avast.com/index.php?topic=28102.msg230206#msg230206) about the Short File Name generation (not its minimal impact). When the impact on the tens of millions not having any problems effectively being forced into another program update IMHO is much greater. These kind of decisions are taken all the time by all program developers (it is called change control, the impact of your changes Vs the impact of not making an immediate change) MS is a good/bad example. It is just that you don't see them being open an honest and up front about it.
Would abandon avast over this if I had previously applied the tweak, absolutely not, I would apply the .reg reversal on the advice of people who are working at this sort of system level application programming that there really is no performance impact.
Not when you consider the activity of the application programmers in these forums directly responding to problems I have never seen this kind of input by the software developers/programmers. However, it is your system and your choice but you should consider your own personal experience and the support levels with avast.
-
Avast should be able to push out an silent update, which fixes this problem, only for those running this "tweak".
-
Removing the reboot text didn't help!
As you can see, I'm up-to date:
(http://img.photobucket.com/albums/v190/bob3160/ShellFTP/avastAbout.png)
If I now do a manual program update:
(http://img.photobucket.com/albums/v190/bob3160/ShellFTP/avastProgramupdate.png)
avast! should just tell me that my system is up-to-date but, it doesn't. I get the following:
(http://img.photobucket.com/albums/v190/bob3160/ShellFTP/avastInstaltionProgress.png)
when this completes, I get the following which only confirms the same information in the first picture:
(http://img.photobucket.com/albums/v190/bob3160/ShellFTP/avastSeptupSummary.png)
Once I close this, I then am greeted with the following:
(http://img.photobucket.com/albums/v190/bob3160/ShellFTP/avastRestartingLoop.png)
It's asking me to reboot for a program update that was never updated.......... ??? ??? ???
-
bob3160 ,
I understand where your coming from this bug is not acceptable and should be sorted but they wont until they send out another program update which may not be for sometime so this leave me little alternative than to review my security arrangements .
-
Had you tried a repair?
-
bob did you try to disable the 8.3 tweak?
http://forum.avast.com/index.php?topic=28102.msg229764#msg229764
-
@ Bob
Have you at some point in the past applied this 8.3 short file name conversion tweak ?
If so apply the reversal:
Did you disable creating of short file names (8+3) by some tool?
Download this registry fix and run it to enable short file names again:
http://public.avast.com/~forejt/Enable8dot3Name.reg
Then start program update and restart afterwards.
If not step two:
You can also check this registry entry (right after computer restart):
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager, if it contains "PendingFileRenameOpertaions".
Check its contents and if there's only "reboot.txt" from avast4\setup folder, delete PendingFileRenameOperations, don't delete any other key.
Back-up (export) the registry key before you edit/delete, just in case.
-
Just tried to update program... Everything seems to be fine :)
-
bob3160 ,
I understand where your coming from this bug is not acceptable and should be sorted but they wont until they send out another program update which may not be for sometime so this leave me little alternative than to review my security arrangements .
Running away from a problem doesn't solve it. I've been using avast! for many years and don't intend to leave over a little hick-up..... ;D
I just applied the patch and after a reboot, tried another program update.
I still get the same results as outlined in my post. avast! still asks to reboot. ??? :'(
Obviously the registry patch wasn't the answer.
Any other suggestions from Alwil would be greatly appreciated.
Thanks
-
Anything in that registry key I posted ?
-
Anything in that registry key I posted ?
No David that Key doesn't exist in my registry.
-
So, you have nothing (or zero value) in
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem : NtfsDisable8dot3NameCreation
and after a VPS update (or probably just a check if you manually invoke VPS update - a new version shouldn't be necessary?) is performed, avast! asks for restart, but there's no value called PendingFileRenameOpertaions in
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager : PendingFileRenameOpertaions ?
If that's really the case, please post the last part of setup.log.
-
So, you have nothing (or zero value) in
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem : NtfsDisable8dot3NameCreation
and after a VPS update (or probably just a check if you manually invoke VPS update - a new version shouldn't be necessary?) is performed, avast! asks for restart, but there's no value called PendingFileRenameOpertaions in
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager : PendingFileRenameOpertaions ?
If that's really the case, please post the last part of setup.log.
This occurred after doing a manual Program update and still does.
16:03:47 min/gen Started: 05.05.2007, 16:03:47
16:03:47 min/gen Running setup_av_pro-3e9 (1001)
16:03:47 nrm/sys Operating system: WindowsXP ver 5.1, build 2600, sp 2.0 [Service Pack 2]
16:03:47 vrb/sys Computer WinName: BOB3160-2426B19
16:03:47 min/sys Windows Net User: SYSTEM
16:03:47 min/gen Cmdline: /stopstat /verysilent /noreboot
16:03:47 vrb/gen Operation set to INST_OP_[16]
16:03:47 min/gen Old version: 3e9 (1001)
16:03:48 nrm/gen SGW32P::CheckIfInstalled set m_bAlreadyInstalled to 1
16:03:52 nrm/int SYNCER: Type: use IE settings
16:03:52 nrm/int SYNCER: Auth: another authentication, use WinInet
16:03:56 vrb/pkg Part prg_av_pro-3e9 is installed
16:03:56 vrb/pkg Part vps-73803 is installed
16:03:57 vrb/pkg Part news-4b is installed
16:03:58 vrb/pkg Part setup_av_pro-3e9 is installed
16:03:59 vrb/pkg Part jrog-3 is installed
16:04:00 min/gen Old version: 3e9 (1001)
16:04:02 nrm/pkg Transferred files: 0
16:04:02 nrm/pkg Transferred bytes: 0
16:04:02 nrm/pkg Transfer time: 0 ms
16:04:02 vrb/fil NeedReboot=false
16:04:02 min/gen Return code: 0x20000001 [Nothing done]
16:04:02 min/gen Stopped: 05.05.2007, 16:04:02
-
Bob, after reading all the posts, I'm lost... I can't understand this problem IF you don't have that Registry key...
A canned solution would be:
Operating system restart needed by avast message could be solved, in some systems, by deleting the file <avast>\setup\reboot.txt
If deleting reboot.txt doesn't stop the requests for reboot check this:
Check this registry entry (right after computer restart):
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager, if it contains "PendingFileRenameOperations".
Check its contents and if there's only "reboot.txt" from avast4\setup folder, delete PendingFileRenameOperations, don't delete any other key.
Back-up (export) the registry key before you edit/delete, just in case.
-
Bob, after reading all the posts, I'm lost... I can't understand this problem IF you don't have that Registry key...
A canned solution would be:
Operating system restart needed by avast message could be solved, in some systems, by deleting the file <avast>\setup\reboot.txt
If deleting reboot.txt doesn't stop the requests for reboot check this:
Check this registry entry (right after computer restart):
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager, if it contains "PendingFileRenameOperations".
Check its contents and if there's only "reboot.txt" from avast4\setup folder, delete PendingFileRenameOperations, don't delete any other key.
Back-up (export) the registry key before you edit/delete, just in case.
See for yourself:
-
Wouldn't the key be on the right side of registry editor, when your click Session Manager on the left side, in the tree view.
The same goes with the 8.3 fix, remember to look in the right side.
-
Erroneus is right, "PendingFileRenameOperation" is a value, not a key - i.e. if you select the "Session Manager" key, all its values should appear in the right pane.
-
I don't have it:
-
I'm having the same reboot after update problem as Bob is describing .
I went to add/remove programs earlier and did a Repair , which basically ran setup and asked for a Re-Boot , which I did .
I've 'cut' the <avast>\setup\reboot.txt to a folder , it's got no text in it .
I do have the value HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager, "PendingFileRenameOperations". ( see pic)
Do I try deleting this value ? (confusion )
This has been happening since the program update 4.7.1001 . I've been assuming with each update and subsequent re-boot that this problem has been fixed and being applied . No such luck ...
Never have applied 8.3 short file name conversion tweak .
-
I've removed the \setup\reboot.txt as I said before .
Closed down my browser and invoked a vps update .
Checked for HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem : NtfsDisable8dot3NameCreation which does exist on my system , value (1)
-
Abraxas: Doubleclick the value to open it and see its content.
Edit: So, you have the short filename generation disabled. Please change the value to 0 (or use the .reg file from here (http://forum.avast.com/index.php?topic=28102.msg229764#msg229764)).
Bob: The part of the log doesn't indicate that a reboot should be requested (at least according to my understanding of the logs)... Please, delete the <avast4>\setup\reboot.txt file first, invoke VPS update and post the end of the setup.log again (there may be 2 blocks with the same time there, actually, so please send both of them). Thanks.
-
Abraxas: Doubleclick the value to open it and see its content.
Edit: So, you have the short filename generation disabled. Please change the value to 0 (or use the .reg file from here).
O.K. igor shall use .reg file ...
-
Gremlins at work:
I have rebooted the system a few times since the last post but just did an update and got the following:
-
igor ;
1. I deleted C:\Program Files\Alwil Software\Avast4\Setup\reboot.txt
2. Applied the .reg file ; Enable8dot3Name.reg , checked that the value was 0 . It is , and still is .
Re-Booted . Went online and updated vps . Avast! wanted to restart Comp. I said , No .
3. Found :
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\SessionManager,"PendingFileRenameOperations".
Exported the "Key" as a .reg file , then deleted it from registry .
Re-Booted .
4. C:\Program Files\Alwil Software\Avast4\Setup\reboot.txt has been re-created .
5.
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\SessionManager,"PendingFileRenameOperations"
The "Key" has also been re-created .
I'm lost ???
Any ideas ?
It's past my bedtime over here ;)
-
Hi all
Had the same problem yesterday. I ran Advanced WindowsCare V2 Personal and ccleaner this cured yhe problem
Buzzby
-
In XP, if you press F8 when starting Windows and select 'Last known good configuration' from the boot menu, will this 'reboot loop' disappear?
-
Hi all
Had the same problem yesterday. I ran Advanced WindowsCare V2 Personal and ccleaner this cured yhe problem
Buzzby
That's odd . I have used Advanced WindowsCare in the past and recently unInstalled it . Just before reading this I copied the installer to my Hard disk thinking it may show up some obscure setting which has been changed. I'm clutching at straws . Since applying the registry changes listed earlier I've had connectivity problems ??? So restored my original settings from a registry backup I made before tinkering ...
In XP, if you press F8 when starting Windows and select 'Last known good configuration' from the boot menu, will this 'reboot loop' disappear?
No Tech , it doesn't . I suppose it's some system setting which has conflicted with the Latest Avast! program update , doesn't seem to be only myself experiencing this problem though ::)
-
I'm just guessing ... since I cannot reproduce the problem (I've never installed the 8.3 tweak).
However, after reading the posts of Buzzby, I am wondering if two things might be needed.
1) the registry edit to remove the 8.3 tweak
2) cleanup of the Windows temporary files folder to clean up any rubbish left by avast in earlier efforts
I think a manual check of the Windows temporary folder and deletion any avast files (but not the folder containing Webshlock.txt) might be worth trying.
-
I'm still experiencing the the " Avast! needs to restart Computer " popup problem after Auto Update of Vps update to 000738-4 .
1. I deleted C:\Program Files\Alwil Software\Avast4\Setup\reboot.txt
2. Applied the .reg file ; Enable8dot3Name.reg , checked that the value was 0 . It is , and still is .
Seems I have to endure the restart message , ???
-
C:\Program Files\Alwil Software\Avast4\Setup\reboot.txt
I suggest you uninstall, boot, use the avast Uninstall tool, boot, install again.
I my mind something is telling that folder access rights have some to due with this...
2. Applied the .reg file ; Enable8dot3Name.reg , checked that the value was 0 . It is , and still is .
Re-Booted . Went online and updated vps . Avast! wanted to restart Comp. I said , No .
3. Found :
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\SessionManager,"PendingFileRenameOperations".
Exported the "Key" as a .reg file , then deleted it from registry.
Re-Booted.
Indeed, you need to reboot when the system file option is changed.
NtfsDisable8dot3NameCreation
REG_DWORD
• Set the value to 0 to enable the creation of 8.3 file names.
• Set the value to 1 to disable the creation of 8.3 file names.
You must restart the computer before this change takes effect.
More info: http://www.microsoft.com/technet/scriptcenter/guide/sas_fsd_xdvz.mspx?mfr=true
I think these options do NOT apply to FAT32 as seems to be the Abraxas' system file.
-
Tech:
I suggest you uninstall, boot, use the avast Uninstall tool, boot, install again.
I my mind something is telling that folder access rights have some to due with this...
Thanks for your advice Tech . Will follow the these instructions . Yes I'm using FAT32 file system , have two smallish Hard disks .
-
Tech:
I suggest you uninstall, boot, use the avast Uninstall tool, boot, install again.
Performed a clean install as suggested , problem solved. After using Avast! for many years was probably a good move to freshen up the installation . Working perfectly , one happy camper here ... ;D
-
Tech:
I suggest you uninstall, boot, use the avast Uninstall tool, boot, install again.
Performed a clean install as suggested , problem solved. After using Avast! for many years was probably a good move to freshen up the installation . Working perfectly , one happy camper here ... ;D
Abraxas, you deserve the help here. You're always welcome 8)
-
Yep I can confirmed have followed these instructions with new fresh install all is well . Thanks
-
:)I erased the reboot.txt file and it worked 100%!!!
Thanks
-
I uninstalled, used the removal tool, and did a clean install but the problem remains for me. I'm running Vista business.
-
I uninstalled, used the removal tool, and did a clean install but the problem remains for me. I'm running Vista business.
Please, post the last 100-150 files of avast log: C:\Program Files\Alwil Software\Avast4\DATA\log\Setup.log
-
(http://img.photobucket.com/albums/v190/bob3160/ShellFTP/avast!RestartingLoop.png)
This seems to have occured sinc the update to the latest version. Evety time avast updates,
it's asking to reboot. (vps update) ???
me too :P every time I check for updates manually or avast! updates its virus database I have to reboot :'(
-
every time I check for updates manually or avast! updates its virus database I have to reboot :'(
Did you try a clean installation of avast, from the scratch?
-
martosurf,
one of the folks I support reported the same issue to me after the 4.7.1001 update.
Before trying a complete re-install I took a look at his system (remotely).
Here's what worked for him:
1) checked and found he had the 8.3 registry tweak installed - set it to 0 (as advised by avast).
2) deleted the reboot.txt file from the folder C:\Program Files\Alwil Software\Avast4\Setup
3) used the Repair option of avast - it said it had repaired avast and requested a restart
4) restarted the system
Since then there have been no more requests by avast to restart after a manual VPS update check or an automatic VPS update.
-
hi guys thanks 4 your time :)
Tech Yes indeed. When I first come with issues with the latest build and after applying the 8.3 tweak to revert to windows by default name system, I just had to uninstall avast! and download a fresh new copy from the website because the continued ask for reboot. Before installing the fresh copy I was asked to reboot anytime I manually checked for updates or even right after log in, now I have reboot requests just after updating VPS :'(
alanrf I already did:
1. Get back to 8.3 system by downloading and applying the registry tweak from avast! I checked later with regedt32 and it worked fine.
2. As vlk and igor asked I already did that.
3. I didn't Repair yet avast!
Will try this and let you know :)
Best regards, Martín
By the way: I don't want to open a new thread on main forum so because I have you both at hand I need to ask you about the webshield: do you experience a notorious slowdown when websurfing and the WebShield on? I just started to note this today... I did read about this on other topics but never experienced it to this point until today... there's a real noticeable lag between hitting enter and IE7 showing for example this forum, and I didn't make any other change to the system so far...
-
Deleting the reboot text file and then doing the repair works for me... so far.
-
I just had to uninstall avast! and download a fresh new copy from the website because the continued ask for reboot.
But when you uninstall, did you boot and the use the Avast Uninstall (http://www.avast.com/eng/avast-uninstall-utility.html) for complete uninstallation? I mean, to install from the scratch, you should have NO avast previous folder in the computer.
-
Yes already did it :P
Just for the case I did a repair too, let's see next update ???
-
:) I repeat, read the past previous threads. You only need to delete the Reboot.txt file in Avast/setup (see appropriate past thread for more precise location). 8)
-
For some, deletion of the reboot.txt isn't enough.
-
Yes already did it :P
Just for the case I did a repair too, let's see next update ???
still the same... :'(
-
martosurf,
one of the folks I support reported the same issue to me after the 4.7.1001 update.
Before trying a complete re-install I took a look at his system (remotely).
Here's what worked for him:
1) checked and found he had the 8.3 registry tweak installed - set it to 0 (as advised by avast).
2) deleted the reboot.txt file from the folder C:\Program Files\Alwil Software\Avast4\Setup
3) used the Repair option of avast - it said it had repaired avast and requested a restart
4) restarted the system
Since then there have been no more requests by avast to restart after a manual VPS update check or an automatic VPS update.
I was having the same problems with rebooting and gollower the steps here and it resolved the rebooting issue. It also fixed another problem that I was having which I would not hve attributed to the change by Avast. I have been having connectibity issues over my wireless link the past two weeks and poof once I did this that all cleared up. I mention this because in another post someone else mentioned connectivity issues.
I wish we had an explanation for the change. There may be more that are fighting connectivity issues and have not made a connection to Avast being a part of them.
Tarkus
-
I love this AV but this recent issue bothers a lot. I just uninstalled and cleaned with the avast! cleanup, reinstalled then and after the first signatures update it asked to reboot (f*ck)
besides that it seems to be stable, let's see what happens after next signatures update...
meanwhile i tested nod32... excellent, but i get stuck with avast!... it's a skin matter xD
-
<snip>
I was having the same problems with rebooting and gollower the steps here and it resolved the rebooting issue.
It also fixed another problem that I was having which I would not hve attributed to the change by Avast. I have been having connectibity issues over my wireless link the past two weeks and poof once I did this that all cleared up. I mention this because in another post someone else mentioned connectivity issues.
The above issue (8,3 file name tweak) reverses a tweak that was applied by the user to their copy of windows, avast's action of providing a .reg file to reverse that user initiated tweak is correcting a windows tweak problem by the user not an avast problem. avast happened to bump into it in probably the same way your other program did.
-
The issue is that all was fine before the avast update. Disabling 8.3 filenames did not cause any issues prior to the avast update and that has been for over a year on this box. The box worked great. Updateing avast caused connectivity issues with my wireless setup and also avast wanted me to constandly reboot. Applying their 'fix' , which basically was enabling 8.3 filenames and doing a repair on avast fixed both of these problems. There should never had been any effect to connectivity but there was. You figure it out.
Tarkus
-
I just tried installing a program and now get the following error:
(http://img.photobucket.com/albums/v190/bob3160/ShellFTP/ShortFileNameDisabled.png)
This is obviously the result of fixing the reboot request problem for avast!
GreenBorder Pro. will not install without reversing the fix requested to fix the reboot problem.
Does someone from Alwil have an answer for me?
-
bob3160
I am not from avast but I think you are are having a little trouble with English as she is used.
That message asks you to do precisely what avast asked you to do.
Try:
fsutil behavior query disable8dot3
on your system. GreenBorder wants you to make sure the setting is 0 which is just the same as avast asked.
-
Thanks alanrf I've changed the value to 0 and that did the trick.
-
Here's how I fixed it.
In regedit I had to set BOTH the following keys to 0 AND delete the file reboot.txt mentioned previously.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem : NtfsDisable8dot3NameCreation
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem : NtfsDisableLastAccessUpdate
I stumbled across
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem : NtfsDisableLastAccessUpdate
while looking at the NtfsDisable8dot3NameCreation value and thought "Gee, I wonder if Avast is looking at when something was last accessed"... (I hate uninstall/reinstall as a fix) ;D
-
Check out this thread and see if some of the possible solutions can help you with the 8.3 issue.
http://forum.avast.com/index.php?topic=28199.0
-
ComputerVet
I regret to say that your post is unhelpful and likely to confuse others.
The setting of HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem : NtfsDisableLastAccessUpdate
is completely irrelevant to avast and this thread.
-
My copy of Avast is asking to restart at least once daily, sometimes more. I have 8.3 names turned off, and I refuse to turn them back on just to work around a bug in Avast. Avast worked just fine before the recent update that caused this. When will this get fixed? Is it fixed in the Pro version?
-
I refuse to turn them back on just to work around a bug in Avast.
So, you'll need another antivirus...
Anyway, it's a myth that 8.3 off improves detection...
Is it fixed in the Pro version?
The Home and Pro versions work the same in this point.
-
It's not a myth that 8.3 off reduces MFT clutter.
-
It's not a myth that 8.3 off reduces MFT clutter.
Can you prove that? This was discussed in this board before... If I'm not wrong it is a myth.
If I'm wrong, I have no problem on changing my opinion 8)
-
"Every time you create a file with a long file name, NTFS creates a second file entry that has a similar 8.3 short file name."
http://technet2.microsoft.com/windowsserver/en/library/8cc5891d-bf8e-4164-862d-dac5418c59481033.mspx?mfr=true
-
http://www.microsoft.com/technet/scriptcenter/guide/sas_fsd_dkfi.mspx?mfr=true
So, it's Alwil time to say something. Why do they need this setting? Is it related to low level configuration (I don't think so...) and protection? Accented characters in the installation path?
-
If you use large numbers of files in an NTFS folder (300,000 or more), disable short-file name generation for better performance, and especially if the first six characters of the long file names are similar.
Hardly likely for most of us.
-
If you use large numbers of files in an NTFS folder (300,000 or more), disable short-file name generation for better performance, and especially if the first six characters of the long file names are similar.
Hardly likely for most of us.
Me too... Something is telling this is still a myth...
-
(http://img.photobucket.com/albums/v190/bob3160/ShellFTP/avast!RestartingLoop.png)
This seems to have occured sinc the update to the latest version. Evety time avast updates,
it's asking to reboot. (vps update) ???
Hi!
Same hire!
Trying all above, unsuccessful. I was waiting new update, can’t wait any more! Have uninstalled AVAST! Been with you 5 years! :'(
Thank you!
-
So, voyager, do you have the latest update already? (4.7.1029)
-
So, voyager, do you have the latest update already? (4.7.1029)
Yes, I have all update.
I just was following to all instructions of this forum.
Before last update everything works perfect. Now hm…. I’m with no antivirus!
Compaq V5000
Intel Centrino DUO.
Memory 1gig
-
Regardless of the 8.3 tweak being set or not, is a solution being worked up at Alwil?
Due to your own success, your users have placed their trust in Avast. A reboot due to a legitimate tweak made available in a normal windows environment, regardless if there are debates on its benefit, is unacceptable to the common user. Not everyone is going to come to the forum to read the "workaround". They will simply fall off the edge of the planet without saying goodbye.
For all of the machines that I have installed this on, my phone will be ringing to give them a different solution that will work in the 8.3 tweak environment.
Please think about your position. If you CAN make a quick and easy update that will FIX the ISSUE, regardless of the fault of the ISSUE, then please make it so.
-
My deep belief was that v4.7.1029 DOES FIX THE ISSUE, i.e. everything's OK even with the tweak enabled.
Are you telling me otherwise?
Thanks
Vlk
-
Well I was required to restart again this morning, and reading the above posts between tech and voyager, it was not obvious that an Avast fix was deployed. I just did a manual program update (no updates required), and a restart prompt was not given. So, from my perspective, it does seem that 4.7.1029 is working.
If you say that 1029 is THE fix on the ISSUE, then my apologies for the doubts and confusion. Keep up the great work!
Bill
-
Hi!
After reinstall again, is start work perfectly. YHAAAA AVAST 4.7.1029 is BACK to normal!
Thank you!
-
As I said, we DID modify the program so it should be fixed in 4.7.1029.
Thanks
Vlk
-
Hm! Is back after updating of virus date base (current version 000763-3)! :'( :'( :'( :'( :'( :'( :'( :'( :'(
??? ??? ???
-
It isn't the Virus database you need to update but the program, do a manual program update to get version 4.7.1029.
-
After reinstall again, is start work perfectly. YHAAAA AVAST 4.7.1029 is BACK to normal!
All ready get new program AVAST 4.7.1029 before database update. Work well! But when program starting update virus database version 000763-3 program again asking reboot my computer.
-
Have you done a reboot since the program update ?
If so follow through on the previous actions because there might have been remnants remaining from the original reboot problem.
It may be best to do a clean reinstall, uninstall, reboot, run the uninstall utility, reboot, install, reboot.
Download the avast! Uninstall Utility, find it here (http://www.avast.com/eng/avast-uninstall-utility.html) and save it to your HDD so you can find it later.
Download the latest version of avast http://www.avast.com/eng/programs.html (http://www.avast.com/eng/programs.html) and save it to your HDD. Use that when you reinstall.