Problem with Windows 2000

[DavidR]

Avast does need the MS Visual C++ 2008 Redistributable.

See this from one of the avast developers:

Uninstall KB2467174 update.

Microsoft has already withdrawn that update to correct this general issue.

[igor]

Yes, but not necessarily this updated one - the one that was installed on the computer before the update should be enough.

[wscott44]

I am relieved and thankful for the web and forums for finding solutions to problems.

The following worked beautifully for me.  No reboots required, nor did I have to remove and reinstall Avast.  After the "Microsoft Visual C++ 2008 Service Pack 1 Redistributable Package ATL Security Update" was applied, Avast started right up.

Thursday, April 14, 2011 8:48 PM
http://social.msdn.microsoft.com/Forums/en-IE/vcgeneral/thread/81bd0f9b-f4b9-4fec-925c-42bae8830002

Thank you for this post everyone! We performed the following and problem was resolved (no reboots required)

Removed KB2467174
Installed Microsoft Visual C++ 2008 Service Pack 1 Redistributable Package ATL Security Update (vcrdist_x86.exe) downloaded from this post the following link provided in this post

http://www.microsoft.com/downloads/en/details.aspx?FamilyID=2051a0c1-c9b5-4b0a-a8f5-770a549fd78c

[antdude]

Ah, so it was MS' fault that broke Avast. I noticed a newer Avast update and didn't see anything about it fixing this problem.

[igor]

There's nothing we can do about it on our side, I'm afraid.

[antdude]

There's nothing we can do about it on our side, I'm afraid.

Igor: Thanks.

[tahoekid]

I encountered this problem after the C++++ fixes were installed. Not only did Avast 5 quit working, but my DeLorme map software also generated the same error. "The procedure entry point FindActCtxSectionStringW could not be located
in the dynamic link library KERNEL32.dll"

Following "Paulynator's" advise I removed the two C+++ updates Visual Studio 2008 (KB2467174)and (KB2467175)
I uninstalled Avast - I rebooted my computer - I reinstalled Avast

That took care of the error message being generated by Avast, but the DeLorme map software still generated the error message so I had to take three more steps, as it appeared the M.S. updates corrupted the two *.dll files MFC80.DLL and MFC90.DLL Per Ted's log at:
http://tedwvc.wordpress.com/2011/04/13/new-redists-break-all-dynamically-linked-mfc-20052008-apps-on-windows-2000/
Windows 2000 puts uncorrupted versions of MFC80.dll in the following folders:
C:\WINNT\winsxs\x86_Microsoft.VC80.MFC_1fc8b3b9a1e18e3b_8.0.50727.5592_x-ww_e87e0bcd
C:\WINNT\winsxs\x86_Microsoft.VC80.MFC_1fc8b3b9a1e18e3b_8.0.50727.762_x-ww_3bf8fa05

and....... MFC 90.DLL in the following folder:
C:\WINNT\winsxs\x86_Microsoft.VC90.MFC_1fc8b3b9a1e18e3b_9.0.30729.4148_x-ww_a57c1f53

Copy these two files from the above folders to the C:\WINNT\system32, or your program folder using Windows Explorer. It will ask if you want to replace the existing files. Click either "yes", or "yes to all."

Then test whichever software is giving you grief. It should work. It did for me. My map software opens now as well as Avast working without issue.