That key has the reboot.txt followed by lots and lots of other filenames.
You said delete if it contains only reboot.txt. I left it alone.
What is the next step.
You can also check this registry entry (right after computer restart):
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager, if it contains “PendingFileRenameOperations”.
Delete that key.
Back-up (export) the registry key before you edit/delete, just in case.
That is what I told him to do in the post above his.
@Frank1
What were the other file names in the “PendingFileRenameOperations” list ?
It may be possible just to delete the reboot.txt value from the list, but don’t do anything untill you report what other files are in there.
Here are the filenames in “PendingFileRenameOperations”:
??\D:\PROGRA~2\ALWILS~1\Avast4\Setup\reboot.txt
??\D:\PROGRA~2\ALWILS~1\Avast4\Aav5.tmp
!??\D:\PROGRA~2\ALWILS~1\Avast4\Aavm4h.dll
??\D:\PROGRA~2\ALWILS~1\Avast4\Aav6.tmp
!??\D:\PROGRA~2\ALWILS~1\Avast4\AavmGuih.dll
??\D:\PROGRA~2\ALWILS~1\Avast4\Aav7.tmp
!??\D:\PROGRA~2\ALWILS~1\Avast4\AavmRpch.dll
??\D:\PROGRA~2\ALWILS~1\Avast4\AhR8.tmp
!??\D:\PROGRA~2\ALWILS~1\Avast4\AhResMai.dll
??\D:\PROGRA~2\ALWILS~1\Avast4\ahR9.tmp
!??\D:\PROGRA~2\ALWILS~1\Avast4\ahResMes.dll
??\D:\PROGRA~2\ALWILS~1\Avast4\AhRA.tmp
!??\D:\PROGRA~2\ALWILS~1\Avast4\AhResNS.dll
??\D:\PROGRA~2\ALWILS~1\Avast4\AhRB.tmp
!??\D:\PROGRA~2\ALWILS~1\Avast4\AhResOut.dll
??\D:\PROGRA~2\ALWILS~1\Avast4\ahRC.tmp
!??\D:\PROGRA~2\ALWILS~1\Avast4\ahResP2P.dll
??\D:\PROGRA~2\ALWILS~1\Avast4\AhRD.tmp
!??\D:\PROGRA~2\ALWILS~1\Avast4\AhResStd.dll
??\D:\PROGRA~2\ALWILS~1\Avast4\AhRE.tmp
!??\D:\PROGRA~2\ALWILS~1\Avast4\AhResWS.dll
??\D:\PROGRA~2\ALWILS~1\Avast4\AhRF.tmp
!??\D:\PROGRA~2\ALWILS~1\Avast4\AhRuiMai.dll
??\D:\PROGRA~2\ALWILS~1\Avast4\ahR10.tmp
!??\D:\PROGRA~2\ALWILS~1\Avast4\ahRuiMes.dll
??\D:\PROGRA~2\ALWILS~1\Avast4\AhR11.tmp
!??\D:\PROGRA~2\ALWILS~1\Avast4\AhRuiNS.dll
??\D:\PROGRA~2\ALWILS~1\Avast4\AhR12.tmp
!??\D:\PROGRA~2\ALWILS~1\Avast4\AhRuiOut.dll
??\D:\PROGRA~2\ALWILS~1\Avast4\ahR13.tmp
!??\D:\PROGRA~2\ALWILS~1\Avast4\ahRuiP2P.dll
??\D:\PROGRA~2\ALWILS~1\Avast4\AhR14.tmp
!??\D:\PROGRA~2\ALWILS~1\Avast4\AhRuiStd.dll
??\D:\PROGRA~2\ALWILS~1\Avast4\AhR15.tmp
!??\D:\PROGRA~2\ALWILS~1\Avast4\AhRuiWS.dll
??\D:\PROGRA~2\ALWILS~1\Avast4\ash16.tmp
!??\D:\PROGRA~2\ALWILS~1\Avast4\ashBase.dll
??\D:\PROGRA~2\ALWILS~1\Avast4\ash17.tmp
!??\D:\PROGRA~2\ALWILS~1\Avast4\ashCfgP.dll
??\D:\PROGRA~2\ALWILS~1\Avast4\ash18.tmp
!??\D:\PROGRA~2\ALWILS~1\Avast4\ashCfgT.dll
??\D:\PROGRA~2\ALWILS~1\Avast4\ash19.tmp
!??\D:\PROGRA~2\ALWILS~1\Avast4\ashChest.dll
??\D:\PROGRA~2\ALWILS~1\Avast4\ash1A.tmp
!??\D:\PROGRA~2\ALWILS~1\Avast4\ashOutXt.dll
??\D:\PROGRA~2\ALWILS~1\Avast4\ash1B.tmp
!??\D:\PROGRA~2\ALWILS~1\Avast4\ashShA64.dll
??\D:\PROGRA~2\ALWILS~1\Avast4\ash1C.tmp
!??\D:\PROGRA~2\ALWILS~1\Avast4\ashShell.dll
??\D:\PROGRA~2\ALWILS~1\Avast4\ash1D.tmp
!??\D:\PROGRA~2\ALWILS~1\Avast4\ashSODBC.dll
??\D:\PROGRA~2\ALWILS~1\Avast4\ash1E.tmp
!??\D:\PROGRA~2\ALWILS~1\Avast4\ashSSqlt.dll
??\D:\PROGRA~2\ALWILS~1\Avast4\ash1F.tmp
!??\D:\PROGRA~2\ALWILS~1\Avast4\ashSXML.dll
??\D:\PROGRA~2\ALWILS~1\Avast4\ash20.tmp
!??\D:\PROGRA~2\ALWILS~1\Avast4\ashTask.dll
??\D:\PROGRA~2\ALWILS~1\Avast4\ash21.tmp
!??\D:\PROGRA~2\ALWILS~1\Avast4\ashUInt.dll
??\D:\PROGRA~2\ALWILS~1\Avast4\ash22.tmp
!??\D:\PROGRA~2\ALWILS~1\Avast4\ashWsFtr.dll
??\D:\PROGRA~2\ALWILS~1\Avast4\asw23.tmp
!??\D:\PROGRA~2\ALWILS~1\Avast4\aswAux.dll
??\D:\PROGRA~2\ALWILS~1\Avast4\asw24.tmp
!??\D:\PROGRA~2\ALWILS~1\Avast4\aswIdle.dll
??\D:\PROGRA~2\ALWILS~1\Avast4\asw25.tmp
!??\D:\PROGRA~2\ALWILS~1\Avast4\aswInteg.dll
??\D:\PROGRA~2\ALWILS~1\Avast4\asw26.tmp
!??\D:\PROGRA~2\ALWILS~1\Avast4\aswRawFS.dll
??\D:\PROGRA~2\ALWILS~1\Avast4\asw27.tmp
!??\D:\PROGRA~2\ALWILS~1\Avast4\aswRes.dll
??\D:\PROGRA~2\ALWILS~1\Avast4\avC28.tmp
!??\D:\PROGRA~2\ALWILS~1\Avast4\avCommEx.dll
??\D:\PROGRA~2\ALWILS~1\Avast4\AVS29.tmp
!??\D:\PROGRA~2\ALWILS~1\Avast4\AVSSHOOK.dll
??\D:\PROGRA~2\ALWILS~1\Avast4\XT12A.tmp
!??\D:\PROGRA~2\ALWILS~1\Avast4\XT1922.dll
??\D:\PROGRA~2\ALWILS~1\Avast4\ash2B.tmp
!??\D:\PROGRA~2\ALWILS~1\Avast4\ashAvast.exe
??\D:\PROGRA~2\ALWILS~1\Avast4\ash2C.tmp
!??\D:\PROGRA~2\ALWILS~1\Avast4\ashBug.exe
??\D:\PROGRA~2\ALWILS~1\Avast4\ash2D.tmp
!??\D:\PROGRA~2\ALWILS~1\Avast4\ashChest.exe
??\D:\PROGRA~2\ALWILS~1\Avast4\ash2E.tmp
!??\D:\PROGRA~2\ALWILS~1\Avast4\ashCnsnt.exe
??\D:\PROGRA~2\ALWILS~1\Avast4\ash2F.tmp
!??\D:\PROGRA~2\ALWILS~1\Avast4\ashDisp.exe
??\D:\PROGRA~2\ALWILS~1\Avast4\ash30.tmp
!??\D:\PROGRA~2\ALWILS~1\Avast4\ashLogV.exe
??\D:\PROGRA~2\ALWILS~1\Avast4\ash31.tmp
!??\D:\PROGRA~2\ALWILS~1\Avast4\ashMaiSv.exe
??\D:\PROGRA~2\ALWILS~1\Avast4\ash32.tmp
!??\D:\PROGRA~2\ALWILS~1\Avast4\ashPopWz.exe
??\D:\PROGRA~2\ALWILS~1\Avast4\ash33.tmp
!??\D:\PROGRA~2\ALWILS~1\Avast4\ashQuick.exe
??\D:\PROGRA~2\ALWILS~1\Avast4\ash34.tmp
!??\D:\PROGRA~2\ALWILS~1\Avast4\ashServ.exe
??\D:\PROGRA~2\ALWILS~1\Avast4\ash35.tmp
!??\D:\PROGRA~2\ALWILS~1\Avast4\ashSimp2.exe
??\D:\PROGRA~2\ALWILS~1\Avast4\ash36.tmp
!??\D:\PROGRA~2\ALWILS~1\Avast4\ashSimpl.exe
??\D:\PROGRA~2\ALWILS~1\Avast4\ash37.tmp
!??\D:\PROGRA~2\ALWILS~1\Avast4\ashSkPcc.exe
??\D:\PROGRA~2\ALWILS~1\Avast4\ash38.tmp
!??\D:\PROGRA~2\ALWILS~1\Avast4\ashSkPck.exe
??\D:\PROGRA~2\ALWILS~1\Avast4\ash39.tmp
!??\D:\PROGRA~2\ALWILS~1\Avast4\ashUpd.exe
??\D:\PROGRA~2\ALWILS~1\Avast4\ash3A.tmp
!??\D:\PROGRA~2\ALWILS~1\Avast4\ashWebSv.exe
??\D:\PROGRA~2\ALWILS~1\Avast4\asw3B.tmp
!??\D:\PROGRA~2\ALWILS~1\Avast4\aswUpdSv.exe
??\D:\PROGRA~2\ALWILS~1\Avast4\sch3C.tmp
!??\D:\PROGRA~2\ALWILS~1\Avast4\sched.exe
??\D:\PROGRA~2\ALWILS~1\Avast4\Vis3D.tmp
!??\D:\PROGRA~2\ALWILS~1\Avast4\VisthAux.exe
??\D:\PROGRA~2\ALWILS~1\Avast4\Vis3E.tmp
!??\D:\PROGRA~2\ALWILS~1\Avast4\VisthLic.exe
??\D:\PROGRA~2\ALWILS~1\Avast4\Vis3F.tmp
!??\D:\PROGRA~2\ALWILS~1\Avast4\VisthUpd.exe
??\D:\PROGRA~2\ALWILS~1\Avast4\ENGLISH\Bas40.tmp
!??\D:\PROGRA~2\ALWILS~1\Avast4\ENGLISH\Base.dll
??\D:\PROGRA~2\ALWILS~1\Avast4\ENGLISH\Lan41.tmp
!??\D:\PROGRA~2\ALWILS~1\Avast4\ENGLISH\Lang.dll
??\D:\PROGRA~2\ALWILS~1\Avast4\ENGLISH\Lan42.tmp
!??\D:\PROGRA~2\ALWILS~1\Avast4\ENGLISH\LangMai.dll
??\D:\PROGRA~2\ALWILS~1\Avast4\asw43.tmp
!??\D:\PROGRA~2\ALWILS~1\Avast4\aswCmnB.dll
??\D:\PROGRA~2\ALWILS~1\Avast4\asw44.tmp
!??\D:\PROGRA~2\ALWILS~1\Avast4\aswCmnOS.dll
??\D:\PROGRA~2\ALWILS~1\Avast4\asw45.tmp
!??\D:\PROGRA~2\ALWILS~1\Avast4\aswCmnS.dll
??\D:\PROGRA~2\ALWILS~1\Avast4\asw46.tmp
!??\D:\PROGRA~2\ALWILS~1\Avast4\aswEngin.dll
??\D:\PROGRA~2\ALWILS~1\Avast4\asw47.tmp
!??\D:\PROGRA~2\ALWILS~1\Avast4\aswScan.dll
There is a blank line after the reboot.txt.
The computer has asked to reboot but I didn’t for a few hours now.
Frank1
I have installed Avast on my 2 other computers - seems to work fine.
By the way Wuz further up this thread states he has the same problem.
Neil (Problem with latest upgrade) subject has started that thread that looks the same as my problem also.
With this problem I thought that it is something peculiar about this computer with the problem. But it looks like others are having as well
Frank1
Wow that is some list and I have no idea why it would be that long.
I would do the export of the “PendingFileRenameOperations” part so that you have a copy just in case. Can you just delete the reboot.txt line and the blank line after it and then exit the registry.
Don’t reboot just yet.
What is in the reboot.txt file, open with notepad ?
Without looking further into the details it isn’t possible to say if the problem is exactly the same, unless he too post the same information.
By the way I ticked the following in the troubleshooting section:
Delay loading of Avast services …
Disable rootkit scan on system startup
Disable avast self-defense module
These setting didn’t do anything regarding the problem. Startup request still comes up.
Removed those 2 lines.
The reboot.txt is an empty file.
I didn’t reboot yet as you requested, DavidR
Frank1
OK delete the reboot.txt file and reboot and see if that has any impact.
Its getting late her and I’m about to call it a day, so one last thing if the reboot request comes back.
Delete the reboot.txt file, check the registry for the “PendingFileRenameOperations” again and see what the contents are.
I’m hoping at least the big list is gone and perhaps just the reboot.txt entry. If not delete the complete “PendingFileRenameOperations” part of the HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager key, nothing other than the “PendingFileRenameOperations” bit.
Finally reboot with everything crossed, fingers, legs.
Yes, I need to go away from the computer for about 7 hours.
I will be back then to continue.
Frank1
O/K, as suggested:
-
Deleted reboot.txt file, then reboot. Done - Popup to restart appeared, reboot.txt file reappeared and the “PendingFileRenameOperations” key was back with same contents as before including the reboot.txt file.
-
Deleted reboot.text file and deleted the “PendingFileRenameOperations” key. Reboot - reboot.txt file appeared and “PendingFileRenameOperations” key appeared but this time only the reboot.txt file showed with a blank line after. No request to restart!
Now I thought that we have it. But no.
I rebooted again and they all came back. The reboot.txt file, the “PendingFileRenameOperations” key with all the files as the original. So back to the start.
Any more thoughts?
By the way, is there an option during installation as to where to install Avast? I installed Avast a few times now but don’t recall being given an option. It just installs into C:\Program Files\etc.
Frank1
Sorry this is beyond my limited knowledge of the inner workings of avast, hopefullt one of the Alwil team will pick this up.
Thank you very much for trying DavidR.
Mayby you can still answer my other question about installing in another location besides C:\Program Files\ext?
Frank1
Just upgrade to the latest version by way of the program, all went well until today got a popup to restart, is it okay to disable the self defense module that might be causing this, I had this happen some time ago after every avs update but that was fixed.
ronnycopeh how was it fix for you? I had no luck so far.
Frank1
David’s post here did the trick I just had to find it again http://forum.avast.com/index.php?topic=31813.msg265587#msg265587
Thank you for that.
I have tried all that without any luck.
Frank1
There is no problem with installing avast in a different location (I have), when you install you can change the default location.
The only caution before used to be a) it shouldn’t really be on an external drive, b) that the installation location doesn’t contain any non-Latin characters, e.g. those with accents, though that issue appears to have been resolved, but probably worth avoiding just in case.
Obviously you would have to uninstall it from its current location and reboot befor einstalling in another location.
Thank you DavidR.
I will try to install on Drive D: and see what happens.
Frank1
Your welcome, though changing locations I wouldn’t have though would make any difference, we will see.
Well, at last, I solved the problem with your help DavidR.
Here it is:
I originally installed Avast and afterwards when reinstalled Avast, every time in the C:\Program Files\Alwil Software\Avast4 directory which was always the default. Then later you asked me to look in the registry in the “PendingFileRenameOperations” and post it’s contents. At that time I didn’t notice that it was showing ??\D:\PROGRA~2\ALWILS~1\Avast4\Setup\reboot.txt and all the other files also showed the D: drive which should have raised a flag to me showing D:\PROGRA~2.
I looked at this again last night and it hit me. I have an unusual setup. Because I have a small C: drive so that it’s easy to backup I created a Junction Link for the C:\Program Files. In this way the files are located in the D:\Program FilesC directory but also appear in the C:\Program Files directory. I have about 4.7.Gb of program files in the Program FilesC directory on the D: drive mirrored onto the C: drive as Program Files. All programs have worked up till now except Avast. With that registry key showing the D: drive, obviously Avast has found a duplicate installation or considered it a conflict.
I uninstalled Avast again and reinstalled it into D:\Program Files (not D:\Program FilesC). Did a manual update of the program from 1169 to 1201. The virus database updated automatically. I had to reboot after the program update. It’s up to date now and working. Now there is no reboot.txt file present and there is no “PendingFileRenameOperations” key in the registry.
Thanks a lot again.
Frank1