When starting outlook 2007 dutch version I get the error …error loading ashoutxt.dll…
As mentioned on this forum:
1° Deleting extend.dat …does not solve the problem
2° Add/Delete → avast home → repair… does not solve the problem
Opening avast home edition protection console:
Item outlook: Warnig …This service is waiting for a sub system…
Cannot adjust sensitivity…access denied
This is correct. The problem persists.
There are no disabled items in: Outlook 2007 > Tools > Trust center > Add-inns > Manage Disabled items
I cannot find any plugins from “avast” in the add-inns sector, not in the enabled nor in the disabled section, only add-inns from Microsoft istself are enabled…
Sorry to disappoint you but there was no previous install of any 1. Previous antivirus installation? AVG, ClamWin, Norton?
I installed it on a clean new computer!
Control Panel > Add/Remove > Change/Remove > Change (check if the provider is being installed). Did this.
…check if the provider is being installed…
What exactly do you mean by this? I checked the connection for updates, as mentioned. Was succesful.
uninstalled dutch edition of avast using aswclear.exe
dowloaded and installed english version of avast home
3 possible choices to install: typical - minimal - custom —> used typical
after restart same problem when starting outlook 2007: —error loading ashoutxt.dll
Looking for plugins: Outlook 2007 > Tools > Trust center > Add-inns >
Finding avast plugin in Exhange-Clientextensions:
Trying to restart this plugin results in a error window: Configuration error in ashoutXt.dll —contact avast
Opening avast On access controlcenter: outlook-exchange: This service is waiting for a sub system
Is there a modified ashoutXt.dll available somewhere or any other suggestions, please
the ashOutXt.dll file (or a dependent module) is somehow corrupted
Outlook’s somehow blocking the file from loading.
Option 1. seems unlikely since you’ve already tried reinstalling the program.
I have seen cases where Outlook somehow simply decided to not load our dll. Mere renaming of it basically resolved the issue (i.e. you copied ashOutXt.dll to ashOutXt2.dll and changed the appropriate path in registry).