Resolved Windows Explorer is not responding when selecting Properties tab

I am getting the same issue on two separate Win 7 boxes. (And, after a last minute check, also on a Vista box).

It only occurs when I select Properties for a chosen folder. The usual tabs: General, Security, Previous Versions and Customize all function correctly with no problem observed.

However, when I press the Sharing tab the current display, for example, General, (or indeed, one of the others), does not change and the program stops responding. Whilst this is not a major issue at present it does mean that I cannot make any changes or additions to the currently set permissions and nor can I add sharing capabilities to other folders if I should so wish..


Any ideas?? It may be relevant that all three boxes are using McAfee 'protection'!

 

Thanks Arie.

I did try the ShellEx Utility on the off-chance that it may help. The only 'alien' link in the right context window was for a McAfee scan, but none of the shell extensions related to McAfee disabled the link so the problem continued to exist.


However, in a further bout of lateral thinking I thought about the Firewall as an outside chance of being the issue here, especially as it was common across three different boxes.

Lo and behold, disabling McAfee firewall allows the Sharing to tab to function. So far so good, so I'm keeping my fingers crossed that this is the answer.


I've tried enabling and disabling and every time the 'disabled' state allows me access.

I have to say that I now strongly suspect the latest McAfee update related the Firewall as being the root cause of the trouble.


Thanks for your input!

 

I have now investigated further and found that the more elegant solution is actually very simple.

When using McAfee, (although this may be applicable to other programs too), simply set the firewall to allow access to the Microsoft Directory Server, (MSFTDS), port 445 on all computers as required.


This is actually rather intriguing because the issue seems to have arisen fairly recently, possibly due either a McAfee or Microsoft upgrade.

Either way problem solved in a more elegant manner.