Hi there. I've run into a problem with copying *.xlsx files over network share from Windows Server 2003 R2 to Windows Server 2008 R2. When the copy process is initiated by Windows Server 2008 R2 machine, the explorer hangs on "Discovering items" step and won't respond. Weird thing is that this applies only to .xlsx files, other files like .exe are copied without any problems. After hangs like this process explorer won't let to kill explorer.exe as well as restart takes much more time than usual (hangs on "Please wait for System Event Notification Service"), however eventually it reboots. Removing Remote Differential Compression future didn't help. Microsoft Office is installed on both machines as well as they are up to date with Windows Update. On source machine with Windows Server 2003 R2 the sysinternals handle utility shows that the file being copied is used by System process (PID = 4) and it remains so until system reboot. Any ideas on the issue? UPD: Some more details. Disabling autotuning didn't help either. Strictly speaking it helped to copy files after clean reboot of both machines, but just after you open and close some of xlsx files, they won't copy.

Anybody? What feature do I have to disable to prevent such a behavior?

This issue can be caused by anti-virus or firewall. Please temporary disable the security programs and check the result. If the issue still occurs, please let us know if there is any issue when you open other files, like *.pdf or *.txt. Also please let us know if the issue occurs when you will any files that are needed to be opened by Microsoft Office *such as *.doc or *.ppt. If the issue only occur with *.xlsx files, or files that are opened by Microsoft Office, I suggest you contact our Office support. Product Solution Center – Office productsArthur Xie - MSFT

This is only an empathy vote for you... I am having an unequivocally difficult time learning what needs to be done to properly configure the virtual network management on a HYPER-V machine. When the virtual cards cannot get an address on the network (card defaults to 169.254.xx.xx) and if the system is diagnosing the connection state [and I force a reboot], the virtual will hang on "Please wait for the System Event Notification Service..." I rather suspect that the issue is internal to the network and that, as stated, it might be a firewall issue, or, in any event, it may be a permission issue, - signal sent, waiting for acknowledgement - for example. Whatever it is, there isn't much to google on the subject. R, J