When updating AVG today, I received the error "Invalid Update Control CTF File". After searching the AVG support forum, I found a couple of easy solutions which can resolve the error.
Note: (Nov 03, 2009): AVG Team is working on this issue and should fix this update issue soon. No user action is needed. The following methods worked for some users, though.
Method 1
1. Double-click the AVG icon in the Notification area.
2. Click the Tools menu and click Advanced Settings…
3. Navigate to the Manage option in the Update branch.
(The Manage option is included in AVG version 8.0.233 and higher.)
4. Click the Delete temporary update files button.
5. Click Yes to confirm removal.
See if you’re now able to update AVG.
Note: The above button deletes all the temporary files, downloaded .BIN and .CTF files which were created by AVG. Whereas the Vbscript file included under "Method 2" deletes only the .CTF files.
Method 2
From AVG forum:
You need to rename/remove the CTF temp files in C:\Documents and Settings\All Users\Application Data\Avg8\update\download…. Dont delete all the .bin files in there unless you want to re-run all updates since your original installation (reinstallation seems to cause a problem in IEs Link Scanner which causes IE to Crash). Only rename/remove the avginfo files that end with .ctf.
There were two .CTF files (avginfoavi.ctf and avginfowin.ctf) in that folder, and deleting them fixed the problem indeed.
Note: The Application Data folder is hidden by default. You need to enable Windows Explorer to show hidden files in order to view the Application Data folder. Alternately, type the above folder path in the Start, Run dialog and press {ENTER} to launch the folder.
Windows Vista users: Delete the .CTF files from the following folder:
Script to automate the task
I’ve scripted the above so that it can help if you want to run the task in multiple PCs. Download del_avg_ctf.zip and save to Desktop. Unzip the file and run the script del_avg_ctf.vbs. The AVG Update .CTF files should be deleted automatically. The script runs fine in Windows XP and Windows Vista systems.
Related Posts
- Error “a .Bin File Is Missing” When Updating AVG Anti-Virus 8.0
- Update AVG Anti-Virus Silently Using Command-Line
- Reliability and Performance Monitor Not Detecting Anti-Virus Product in Windows 7/Vista
- Microsoft Security Essentials (MSE) Update Utility
- How to Disable Updating of Definitions When Running a Command-Line Scan Using MpCmdRun.Exe
If you enjoyed this post, make sure you subscribe to our RSS feed! We feature Tips, Troubleshooting information, Scripts and Utilities for Microsoft Windows Operating Systems!
Prefer an E-mail subscription?
This was exactly what I needed…thank you !
Against the recommendation, I used the “delete temporary files” option and it still didn’t work since my.bin files were gone. I solved the problem by stating a new scan and stopping it. This recreated the needed files. Updating fine now.
the script couldn´t find any CTF files.
what to do now?
I’m getting the “invalid update control CTF file” error, but there are no CTF files in the folder. Just BIN files. I ran your script, and it just told me that there are no CTF files to delete…
Unfortunately neither of your methods worked for me. I shall continue scouring the Internet for other solutions, and let you know how I resolved this issue. By the way, have now bookmarked your blog for its wonderful informative content.
I tried the first method (which diddn’t work) and at the bottom it says it deletes all the files instead of only the ctf files. Now I can’t try method 2 anymore. What do I do now?
None of the above worked for me. I went through every method — including the zip file — which said I didn’t have a .ctf file.
Manually I’m unable to find the files, and same goes for your script; says “No CTF files were found. No changes were made.”
It turns out that MY problem was that I was signed in my University’s wireless network with guest access. Signing in with my University ID allowed AVG to communicate with the update server.
Actually this didn’t work in a corporate environment. I restarted the AVG Update proxy server for the branch location experiencing this issue and that fixed it.