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 \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).
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 \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 ;
-
I deleted C:\Program Files\Alwil Software\Avast4\Setup\reboot.txt
-
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 . -
Found :
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\SessionManager,“PendingFileRenameOperations”.
Exported the “Key” as a .reg file , then deleted it from registry .
Re-Booted . -
C:\Program Files\Alwil Software\Avast4\Setup\reboot.txt has been re-created .
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?
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 …
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.
- the registry edit to remove the 8.3 tweak
- 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 .
-
I deleted C:\Program Files\Alwil Software\Avast4\Setup\reboot.txt
-
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 , ???
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…
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
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