Actual Tools
Forums list
New topics
Topics list
Search
Help
Login
Register


Topic: «Actual Window Manager 5.5b3 and McAfee AV » on forum: Beta Testing   Views: 10250
 
Jim Fraley
Registered user
 
 Posts: 32
Joined: 08/14/2007
Posted: 12/04/2009 18:26:40
 
 
 It would seem Actual Window Manager 5.5beta3 does not get along with McAfee VirusScan Enterprise 8.7i (8.7.0.570).

The symptoms are:
1) explorer.exe seems to be in a CPU burn (20-25% CPU)
2) mfeann.exe (McAfee) seems to be in a CPU burn (20-25% CPU)
3) PC is nearly totally unresponsive UNTIL you kill Actual Window Manager.  Then everything is fine.

I did not have this problem with AWM 5.5b2.

UPDATE:
I see the problem.  My employer has an Enterprise Policy to enforce this rule: "Prevent common programs from running files from the Temp folder".
This includes explorer.exe.

What is happening is explorer is attempting to use a copy of aimemb.dll located in my Temp folder rather than the one located in the folder into which I installed Actual Window Manager.  McAfee is blocking this access.  Explorer.exe continues to try to use aimemb.dll and McAfee keeps blocking it.  This seems to be a deadly embrace.

McAfee logs this message:
12/4/2009 7:39:05 PM Blocked by Access Protection rule domain\user

C:\WINDOWS\Explorer.EXE C:\DOCUME~1\user\LOCALS~1\Temp\aimemb.dll Common Standard

Protection:Prevent common programs from running files from the Temp folder Action blocked :

Execute

----------

So, WHY is Actual Window Manager using a copy of aimemb.dll in my Temp folder rather than in the folder into which I installed AWM?
 
Top
MGhell
Advanced user
 
 Posts: 141
Joined: 11/15/2008
Posted: 12/05/2009 04:50:28
 
 
 See here:

http://www.actualtools.com/forum/read.php?FID=10&TID=800&UID=2769

System:
DUAL WIN7 (32bit)/WIN10 PRO (64bit)
CPU Q9550S
4GB RAM
Nvidia 460GTX
 
Top
Jim Fraley
Registered user
 
 Posts: 32
Joined: 08/14/2007
Posted: 12/07/2009 10:45:00
 
 
 Thank you for the link.  Unfortunately, if using aimemb.dll out of Temp is a requirement, I will be unable to use v5.5.

Is there any way to have AWM not use Temp?
 
Top
Alexander Belyakov
Administrator
-retired-
 
 Posts: 196
Joined: 06/07/2007
Posted: 12/07/2009 22:36:47
 
 
 Jim,

It's really sad to hear that copying of aimemb.dll to Temp resulted in this kind of incompatibility.
In fact, this feature was primarily meant to aviod the system reboot during AWM upgrades, and also this is our first step to make a portable version of AWM.

We'll surely add a new option to enable/disable that copying to Temp folder.
 
Top
Jim Fraley
Registered user
 
 Posts: 32
Joined: 08/14/2007
Posted: 12/08/2009 14:32:21
 
 
 Alexander,

I know some people say no good deed goes unpunished.  However, I do appreciate everything you do to continuously add new features to your products.  That is certainly one of the best "features".

Thank you for your consideration of this issue, and for adding an option for those of us, however few there may be, that are affected by Corporate restrictions.


Thank You!

Jim
 
Top
Jim Fraley
Registered user
 
 Posts: 32
Joined: 08/14/2007
Posted: 12/14/2009 11:52:54
 
 
 The new option in AWM 5.5 beta 4 works great!

THANK YOU!
 
Top


User(s) reading this topic
Number of guests: 1, registered members: 0, in total hidden: 0
Forums list
New topics
Topics list
Search
Help
Login
Register



 
HomeProductsDownloadOrderContactsPress Map Privacy
Copyright © 2002-2024 Actual Tools. All rights reserved.

Windows and the Windows logo are trademarks of the Microsoft group of companies.