locked
Error 0x80070079: The semaphore timeout period has expired RRS feed

  • Question

  •  

    Whenever I try to copy large files over a wireless network (Laptop > Desktop) I get the following error:-

     

    Error 0x80070079: The semaphore timeout period has expired

     

    I've done a search on Google and have found that a number of other users are having the same problem, but no-one seems to have a fix for it.

     

    Can anyone help?

     

    (I'm running Vista Ultimate on both my Laptop & Desktop)

    Monday, December 10, 2007 7:54 PM

Answers

  • Hello Ady,

     

    Thanks for your post!

     

    This issue may be a little complex and require some steps to troubleshoot:

     

    1.    Update the driver of wireless network adapters in both of your computers.

    2.    Temporarily disable all the firewalls and anti-virus applications, then check the issue again.

    3.    To exclude the factors from other services and applications, do a clean boot to check the issue and perform Step 4.

    (KB929135) How to troubleshoot a problem by performing a clean boot in Windows Vista
    http://support.microsoft.com/default.aspx?scid=kb;EN-US;929135


    4.    With clean boot, try to apply the hotfixes contained in the following KB articles:

    (KB932045) Error message when you use a network connection to copy a large file from one Windows Vista-based computer to another Windows Vista-based computer: "The connection has been lost"

    http://support.microsoft.com/default.aspx?scid=kb;EN-US;932045

    (KB932063) Several problems occur on a Windows Vista-based computer when you work in a wireless network environment

    http://support.microsoft.com/default.aspx?scid=kb;EN-US;932063

    If problem still persists after steps above, this issue is very possibly due to network devices or configurations, please let me know:

     

    1.    Whether this problem occurs in wired network?

    2.    If strengthening the network signals, the problem can be changed?

    3.    What size of files will lead to this error.

    4.    Does this error terminate the copy process?

    5.    Models of the wireless network adapter and wireless router.

    More details about his issue are preferred. Thanks!

     

    Have a nice weekend!

     

    Regards,

    Lionel Chen

    Microsoft Online Community Support

    Friday, December 14, 2007 5:19 AM

All replies

  • Can anyone please help????

     

    Tuesday, December 11, 2007 7:35 PM
  • Hello Ady,

     

    Thanks for your post!

     

    This issue may be a little complex and require some steps to troubleshoot:

     

    1.    Update the driver of wireless network adapters in both of your computers.

    2.    Temporarily disable all the firewalls and anti-virus applications, then check the issue again.

    3.    To exclude the factors from other services and applications, do a clean boot to check the issue and perform Step 4.

    (KB929135) How to troubleshoot a problem by performing a clean boot in Windows Vista
    http://support.microsoft.com/default.aspx?scid=kb;EN-US;929135


    4.    With clean boot, try to apply the hotfixes contained in the following KB articles:

    (KB932045) Error message when you use a network connection to copy a large file from one Windows Vista-based computer to another Windows Vista-based computer: "The connection has been lost"

    http://support.microsoft.com/default.aspx?scid=kb;EN-US;932045

    (KB932063) Several problems occur on a Windows Vista-based computer when you work in a wireless network environment

    http://support.microsoft.com/default.aspx?scid=kb;EN-US;932063

    If problem still persists after steps above, this issue is very possibly due to network devices or configurations, please let me know:

     

    1.    Whether this problem occurs in wired network?

    2.    If strengthening the network signals, the problem can be changed?

    3.    What size of files will lead to this error.

    4.    Does this error terminate the copy process?

    5.    Models of the wireless network adapter and wireless router.

    More details about his issue are preferred. Thanks!

     

    Have a nice weekend!

     

    Regards,

    Lionel Chen

    Microsoft Online Community Support

    Friday, December 14, 2007 5:19 AM
  • Hi,
    I'm getting the same error but in a different -- seemingly less complicated -- context.  I am trying to backup my main drive to an external eSATA drive.  Every file copied without incident except for one movie, a 143 meg WMV.  Here are some facts about my situation


    1) the folder contains 90 videos (all homemade so copy protection isn't the issue)

    2) the video sizes range from 1.2 gigs to 34 megs

    3) copying was smooth and fast, except for that one file

    4) I thought that it might be the eSATA drive but I got the same error when copying to the same HD, same folder or different folder.  Clearly wirelessness, network issues and other connections (USB, firewire, etc) aren't the problem.

    5) I'm running Vista Home Premium with all the latest updates on an HP Media Center computer running  AMD x2 5200+ with 4 gigs RAM

    6) I tried repeatedly, even after multiple reboots and still got the error for this one file

    7) I tried ZIPping it and got the same error

    8) Strangely, it seems to play just fine in Windows Media Player

    There are hints of viral activity and I've had 3 Blue Screen crashes today (which is why I'm backing everything up before reformatting my entire drive).

    My last hope is to upload it to a site like Yousendit and then download it.  Even if you don't know what's wrong, can you offer any tricks to get around the error and backup the file?

    Please help.  Thanks for any advice in advance,
    Sam
    Thursday, January 10, 2008 9:46 AM
  • Sam,

    Like you, I got the message while attempting to copy files within one system.

     

    1. The files were large video files (100MB to 600MB);

     

    2. Some smaller files of the same type copied successfully, but not all;

     

    3. The hardware involved is an external Plextor 810UF (USB) drive to my "D" (work) drive;

     

    4. Sometimes the timeout would occur while the system said it was calculating the time of the procedure. At other times it would start the process and then hangup. (A couple of times I got a message which said the process would take 45000+ days and 12 hours. I really don't feel I should have to wait 125 years for things to happen. <GG>)

     

    I am able to work around the problem by connecting the Plextor to an XP PC and then transferring the files to my Vista PC (same drive and directory that I tried before) via a cabled Linksys router. So far that works flawlessly. Therefore I'm sure the problem isn't in the network.

     

    I hope that a solution is forthcoming because the work around is a bother.

     

    Bill

     

     

     

    Tuesday, January 15, 2008 1:57 PM
  • I haven't found an answer to this problem anywhere, yet it seems to be quite common.

    I'm using HP MediaSmart Server to do automatic backups. Everything was working ok until one day I got the following error:

    An unexpected exception ocurred on the computer. COMException. The semaphore timeout period has expired (Exception from HRESULT: 0X80070079) at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRIntern at (Int32errorcode IntRtrerrorInfo).

    I checked the the Crashdump and it referred to Pinnacle11 (video editing application), and cooincidentally, the problem only started after I had been editing a couple of video files.

    Has anyone yet found a fix to this problem?

    Steve


    Monday, March 24, 2008 9:06 AM
  • Well I don't have the answer but perhaps I can simplify the problem even more for MS. I am running Windows Home Server and everytime WHS tries to go do a daily backup of my workstation, the backup fails with these two error messages -

     

    Event Type: Error
    Event Source: HomeServer
    Event Category: Backup
    Event ID: 272
    Date:  4/2/2008
    Time:  7:53:58 AM
    User:  N/A
    Computer: TNETHS01
    Description:
    Unexpected error 0x79 from WriteFile on D:\folders\{00008086-058D-4C89-AB57-A7F909A47AB4}\CT2.C.VolumeCluster.4096.dat: The semaphore timeout period has expired.

     

    Event Type: Error
    Event Source: HomeServer
    Event Category: Backup
    Event ID: 267
    Date:  4/2/2008
    Time:  7:53:58 AM
    User:  N/A
    Computer: TNETHS01
    Description:
    Client Backup server failed at d:\qhsv1_rtm_qfe\qhs\src\backup\util\diskfile.cpp(421)

     

    By reading the forums, it definitely seems that the backup is hitting a large video file and then crashing. I have many video files over 200 MB in size and while I can't tell what video file it is hitting in these error messages, I'm sure this is what is happening. Many of my larger video files are .mkv format which may also be related somehow. If anybody finds the solution before me, please let me know. Thanks.

    Wednesday, April 2, 2008 1:28 PM
  •  Lionel Chen - MSFT wrote:

    Hello Ady,

     

    Thanks for your post!

     

    This issue may be a little complex and require some steps to troubleshoot:

     

    1.    Update the driver of wireless network adapters in both of your computers.

    2.    Temporarily disable all the firewalls and anti-virus applications, then check the issue again.

    3.    To exclude the factors from other services and applications, do a clean boot to check the issue and perform Step 4.

    (KB929135) How to troubleshoot a problem by performing a clean boot in Windows Vista
    http://support.microsoft.com/default.aspx?scid=kb;EN-US;929135


    4.    With clean boot, try to apply the hotfixes contained in the following KB articles:

    (KB932045) Error message when you use a network connection to copy a large file from one Windows Vista-based computer to another Windows Vista-based computer: "The connection has been lost"

    http://support.microsoft.com/default.aspx?scid=kb;EN-US;932045

    (KB932063) Several problems occur on a Windows Vista-based computer when you work in a wireless network environment

    http://support.microsoft.com/default.aspx?scid=kb;EN-US;932063

    If problem still persists after steps above, this issue is very possibly due to network devices or configurations, please let me know:

     

    1.    Whether this problem occurs in wired network?

    2.    If strengthening the network signals, the problem can be changed?

    3.    What size of files will lead to this error.

    4.    Does this error terminate the copy process?

    5.    Models of the wireless network adapter and wireless router.

    More details about his issue are preferred. Thanks!

     

    Have a nice weekend!

     

    Regards,

    Lionel Chen

    Microsoft Online Community Support




    Well this did'nt work for me.

    Any other solution?
    Using XP Prof. Service Pack 3 beta.


    Tuesday, April 8, 2008 8:06 PM
  • Hi All,

    Similar problem with backing up one laptop running Vista Ultimate x86 on to a  WHS over a 1 gigabit LAN wired connection (DLINK G604T + Netgear switch); the laptop contains some large video files (DivX, .iso) 800mb - 2 gb and the backup proceeds until about 35% with the same 267 error previously described in the event log on the WHS, and a report on the client laptop that there was a problem accessing a specific file on the WHS server.

     

    I have no problems backing up the desktop running XP pro that has also has some smaller home movie files on it in their original state, on two WD raptors RAID 0 on a silimage controller.

     

    This is really ironic in a truly MS sense, that a server specifically designed to backup your media so you can never lose them to a drive crash or viral event or whatever hole nobody noticed, won't back up your 'precious memories' on a vista machine.

     

    Since my desktop doesn't exhibit the problem, I will be keeping all my video files on that machine having removed them from my vista laptop and see if the problem resolves. The only other suggestion I can make to vista users until a fix is found is to eihter burn all your larger video files to DVD or a high capacity removable usb drive, or revert a machine to XP if you can and use that to store video media files.

     

    If you happen to get tired of being a slave to the machine, like I do, just remember you can always turn it off and go play someplace else... and if you are considering buying WHS and only have vista 'clients' hold off for now.  I will report back once my video files have been swapped over to the xp machine and see if I can get a decent usable backup of this laptop on the WHS. There also seem to be references to issues with my shadow copy drives in my WHS event log as well. Apparently they can't grow. A truly underwhelming experience.

     

    Tuesday, April 15, 2008 12:22 PM
  • Hello Again,

     

    Yep my 'workaround' worked for me. After removing all of my large media files including an image that was over 7gb (a game beta), by burning most of them to disk and deleting them from the hard drive (+ emptying recycle bin) afterwards, I finally managed to back up this vista laptop.

     

    Given that I didn't change any other aspect of my config, and backed up the laptop the way I usually do with Acronis True Image beforehand, one can only summise that WHS has issues backing up large video files, or video files of certain file formats.

     

    I guess this method atleast gets around the problem and in no meaningful way identifies the absolutes and specifics of either the actual problem or how it can be resolved per se, but it does crudely isolate the issue and privide a stop-gap until someone way mucho intelligent than I with the time to spare can get down to tin tacks and figure it out thoroughly! That's about the longest sentence I have ever written in a post.

     

    If this helps someone avoid losing a file, like me for instance, I guess it was worth the cognitive effort. Hope it provides some short-term helps to others. Good luck.
    Wednesday, April 16, 2008 4:47 AM
  •  

    I also had this problem when i tried to copy over the cable or wireless connection from laptop to desktop. the workaround that I tried is to give the copy command from the desktop to copy from laptop to desktop.
    Tuesday, June 3, 2008 8:22 AM
  • Same problem here: Error 0x80070079: The semaphore timeout period has expired

     

    Error occurs multiple times when transferring files of 10MB and smaller (no large files at all) on a shared external USB harddisk connected to PC1 to another folder on the same external USB harddisk from a laptop.

    Copy command is issued from PC2.

     

    In my opinion this is NOT caused by a network issue or should not be possible to be caused by the network.

     

    PC1 (OEM Desktop) - Wired Gbit LAN:

    MS Windows Vista Home Premium SP1

    Shared external HD with full rights to everyone

     

    PC2 (Lenovo Laptop) - Wired Gbit LAN:

    MS Windows Vista Business

     

    Switch:

    3Com OfficeConnect with 8 Gigabit ports

     

    External USB HD:

    USB Western Digital Elements (400GB)

     

    ( I could not find any entries in the eventviewer about this error. )

    Sunday, July 13, 2008 2:24 PM
  • This is very interesting.  The current trend is laptops and video files.  I am also having this problem with a Dell D610 latitude running XP Pro SP2.  I am capturing video from my Canon GL1 via 1394a PCMCIA card into Sony Vegas 8 Pro.  All I get is the error code 0x80070079.  It will randomly occur during the capture process into uncompressed AVI's.  It is rather frustrating because I was considering that my firewire card was bad, but reading other peoples' problems leads me to think otherwise.  Is it possible that it is a problem with a hard drive controller common to laptop motherboards?  My controller is an Intel 82801FBM UATA controller.  Just something to think about.  It would be nice to solve this issue.  By the way, this is really the only issue I have with this machine, everything else works great and memory checks out fine with MemTest.
    Sunday, October 5, 2008 6:02 PM
  • It's not related to videofiles, it's related to large files. I have a Dell Inspiron 1720, Vista Home, a HP MVP 5020, and a Linksys 54G router. With wireless connection, any files larger than a few mb's causes complete disconnection after a few seconds, IP is lost and has to be reaccuired. With wired connection any size file can be transferred. On my Mac, I have never seen this problem. Don't have any solution but, are very annoyed with this.

    BR.
    T.
    Saturday, October 18, 2008 11:59 PM
  • I have recently received same message on my laptop running XP.
    Trying to upload photos using a media card reader. The SD card is a 1GB card.

    I have both a laptop and desktop running XP(updated), but when the media reader is plugged in the USB with the SD card installed, the desktop locks up. I don't remember having this issue using a smaller sized SD card, say 16MB.

    My wife has a laptop running Vista, I have had no problems with that particular machine.





    Sunday, December 7, 2008 2:42 PM
  • Actually it is neither video nor large files that is the only culprit.

    I have an HP Pavillion dv9413cl Notebook running Windows Vista Ultimate. It has two hard drives. I just added the second hard drive to the machine and installed a fresh clean install of Vista on the newly installed hard drive as it is now my primary drive. The old hard drive has all the old data on it.
    I am in the process of cleaning up the drive and consolidating needed data. In the process of deleting a few files I received this error, not only through Windows Explorer but through a command prompt as well. Here is my output of the command prompt window.

    F:\Users\Public\Downloads>del *.*
    F:\Users\Public\Downloads\*.*, Are you sure (Y/N)? y
    F:\Users\Public\Downloads\ContactChangedStatus.wav
    The semaphore timeout period has expired.
    F:\Users\Public\Downloads\ContactInvisible.wav
    The semaphore timeout period has expired.
    F:\Users\Public\Downloads\FileTransferRejected.wav
    The semaphore timeout period has expired.

    F:\Users\Public\Downloads>dir
     Volume in drive F is <HOSTNAME_F>
    Volume Serial Number is <SerialNumber>

     Directory of F:\Users\Public\Downloads

    01/09/2009  12:26 PM    <DIR>          .
    01/09/2009  12:26 PM    <DIR>          ..
    05/22/2008  05:07 PM           340,672 ContactChangedStatus.wav
    05/22/2008  05:07 PM           274,460 ContactInvisible.wav
    05/22/2008  05:07 PM           296,800 FileTransferRejected.wav
                   3 File(s)        911,932 bytes

    As you can see we are looking at sound files of a few hundred K. So not video or large files.

    This also rules out any intra drive transfers, network contention, or the like as I am just trying to delete the files not transfer them over some medium. 

    Friday, January 9, 2009 7:46 PM
  •  This is a weird one.  I'm also thinking that large video files are just one symptom of the problem, because I am getting it whenever I try to access a shared folder on another PC via Windows Explorer. 

    Everything had been working fine when both machines were running Vista Ultimate, and I never encountered this error.  But since upgrading my laptop to the Windows 7 beta, I have never been able to connect to a share on another machine without seeing this.

    I'm pulling my hair out trying to finx a solution - sure hope someone comes up with something before I go bald!  :-)

        Rob
    Thursday, January 15, 2009 5:39 PM
  • I've got the same msg trying to use Vista Ultimate Backup.  I have two internal sata drives and I'm attempting to back up from C to D when it halts with this msg.  I then tried to copy my docs folder using the desktop.  Same problem.  It's SP1 with all drivers current.  

    I used to tell everyone how good Vista is but this is really concerning me.

     

    Sunday, January 25, 2009 7:12 PM
  • This error is usually the result of a DHCP renewal.  Switch to using static IP addresses and see if that helps.  You are most likely experiencing a DHCP address renewal during your file copy operations.  If you need to use DHCP, try increasing the lease period, and if you don't control the lease period, find out what that period is and do an ipconfig /release and then an  ipconfig /renew in a command prompt to cause the lease not to renew itself during your backup window.
    Tuesday, January 27, 2009 7:42 PM
  • I ran into this problem while attempting to do a backup of my C drive. Running a check disk on the drive cleared up the problem.

     

    Friday, February 13, 2009 4:38 PM
  • i found a solution for people trying to move video on to sd cards without coming up with these errors.

    1. download and install winrar.
    2.select your file and click on "add to archive".
    3.now select "compression method" and select "good".
    4.now you need to split your file by selecting "split your volume in to bytes" and select zip100:98078kb

    this will now split your file in to 98mb size pieces, i did this with a 696mb and got 6 seperate rar files.
    when it has finished, move them one by one on to your card and when you have done this select them all and click "extract here"
    this will now unzip and piece your vid back together.

    i hop ppl out there find this helpfull in some way ;)
    Friday, March 6, 2009 9:19 PM
  • This problem seems to be about DHCP. I get it when my NIC suddenly stops holding an IP lease even if there is no traffic. I have the latest NIC driver so none of MS' suggestions help. It has nothing to do with any router, ISP as I have tried many combinations. The OS seems fine. I've tried AutoNegotiation and 10MBFD. Same problem. This has wasted about two weeks of my life. Any help would be appreciated. My NIC has many undocumented settings but I have them all on the default and none seem to have anything to do with timeouts. Power management is 'always on' for the NIC and OS. It is a NVIDIA 10/100/1000 NIC.
    • Proposed as answer by Utah Chuck Tuesday, June 30, 2009 6:28 PM
    Sunday, March 15, 2009 4:59 PM
  • I did not mean to click propose as answer. I was reading the button as Propose AN Answer, my bad. I have had a lot of problems on my home network transfering lots of data between 2 machines. The main problem child is my Vista machine. I think the NIC in it has some compatibility issues but what I did for a workaround was install sync toy. It is a great little utility for syncing folders between machines. It has built in retries so even if your transfer bags it, you will not have so start at the beginning. You will not have to click no  or yes to all on overwrite if you have to start again on a large multi file transfer. It will scan source and destination and only copy whatever files still need copied. Give it a shot. I love it.
    http://www.microsoft.com/downloads/details.aspx?FamilyID=c26efa36-98e0-4ee9-a7c5-98d0592d8c52&DisplayLang=en

    Have fun and let us know if this gets around the timeout errors. What's the worst that could happen?
    Tuesday, June 30, 2009 6:40 PM
  • Well, since about half the people on this aren't transferring over a network, I would say that DHCP isn't the problem, at least in those cases. I for one am getting this error transferring files from a 256MB USB thumb drive and from a 120GB external USB HDD to my IBM T41p Laptop running Windows XP Pro SP3. The smallest file I have had this trouble with is a 29.8MB data file. I am also getting the error while simply trying to access folders on these drives that contain large amounts of data in them. I suspected it was a problem with my USB controller as I recently started getting other USB related errors about my USB 2.0 services not working with the device even though all of my drivers are updated and the host controllers indicate they are USB 2.0 capable. First, I tried updating my BIOS. I had no change after doing this. Naxt, I installed a USB 2.0 capable PCMCIA card. I am no longer getting the USB errors this way but I am still getting the "semaphore timeout period" error. So I don't think it is related to the USB ports. Oh, and just for te record, this is a pretty fresh install of the O/S so everything is still pretty clean.

    I would say that this error appears to be a generic error that appears whenever something times out during data transfer, regardless of the medium or protocol, on machines running MS Windows XP and Vista O/S. What causes it in each case could be different, thus the difficulty in troubleshooting. Consequently, I doubt that one fix will solve everyones problem, but perhaps through this forum we can dial it down to all of the most common causes and fixes. I have tried all the ones here for my case with no luck, and I can see that others have had the same trouble. 

    If anyone has any ideas about my particular situation please advise. I will try anything at this point.
    Saturday, July 4, 2009 10:06 PM
  • Although I agree this error is not exclusive to networking, this thread was started (almost two years ago now) by someone with a network issue and is logged under networking.  (" Windows Client TechCenter > Windows Vista IT Pro Forums > Windows Vista Networking ")

    I've seen this error whilst trying to access a suspected faulty IDE drive attached via a USB interface.  (Size and type of files irrelevant)  It seems to me if you want to start to understand semaphore timeouts you can just leave out the word "semaphore" ...
    Thursday, August 6, 2009 7:59 AM
  • Well to those that bother to keep track of these issues...I for one am still having the same drama.  For extra interest, it does not happen across a wired LAN!

    Will (or perhaps they have) MS fix this?

    Vista on HP Pavilion dv5 AND static IP address.  Server is Ubuntu 8.04.  Vista is the only OS that has this drama.

    Rrrrrrrrrrrrrrr
    Thursday, August 27, 2009 6:54 AM
  • "Me too"  I've been getting this with my Windows Home Server for the past 6 days.  Checked the Event Log, rebooted the server, searched the web.  Still fighting it.  Posted something on the Home Server Forum earlier, will see if that leads to anything.
    Sunday, August 30, 2009 4:13 AM
  • The moderator on the WHS forum suggested this, and it worked for me:

    "Try running chkdsk /r on all the drives of the client having the problem."

    Good luck to all others.

    Greg
    Sunday, August 30, 2009 2:25 PM
  •  

    Whenever I try to copy large files over a wireless network (Laptop > Desktop) I get the following error:-

     

    Error 0x80070079: The semaphore timeout period has expired

     

    I've done a search on Google and have found that a number of other users are having the same problem, but no-one seems to have a fix for it.

     

    Can anyone help?

     

    (I'm running Vista Ultimate on both my Laptop & Desktop)

    Hi guys,
    I experienced this trouble for about a week, trawling forums and googling to the point where i had just about given up.
    Microsoft are no help at all, they know this problem exists yet ignore all requests of help to find a solution.
    Anyway, I managed to resolve this issue by installing a patch called 'Vista TCP/IP & UAC AutoPatch'.
    More info here http://www.netfresco.com/tech/network-copy-failure/  or directly download the patch from here
    http://www.softpedia.com/get/Tweak/Network-Tweak/TCP-IP-Limit-AutoPatch.shtml
    This solution worked for me and i have no hesitation in recommending it.
    BTW this patch is vista 32 and 64 related, so if you are an XP user then unfortunately this may not be of any help.
    Good luck guys.
    Brassnex
    Sunday, September 6, 2009 2:20 PM
  • I too received this error last night.  I was backing up a brand new installation of Ultimate, do an existing 500GB WD sata drive.  My dilema, is that it has appeared to corrupt my hard disk.  After I received this error, I rebooted and the drive is no longer available.  I supposed it is possible that I have a hardware issue with my controller, but...
    Wednesday, September 9, 2009 6:53 PM
  • Me Too.  I bought a new 500gb imation apollo hard drive. was worried about losing my data since moving country and leaving old backup at home.  running my first backup. go out and come back home. first weird thing that happened is all of my torrents I was downloading had disappeared, then computer starts freezing, receive 'the login process has failed to create the security options dialogue box".  I wonder if it has to do with installing the new backup drive (USB).  Very frustrating. Now trying to back up so that I can install everything from scratch, but getting the timeout error!! grrrr
    Wednesday, October 7, 2009 4:53 AM
  • Hello,

    here is solution for problems with sdhc memory sticks (or beter problems with Ricoh card reader).
    Friday, November 13, 2009 7:12 PM
  • Hi guys,
    I experienced this trouble for about a week, trawling forums and googling to the point where i had just about given up.
    Microsoft are no help at all, they know this problem exists yet ignore all requests of help to find a solution.
    Anyway, I managed to resolve this issue by installing a patch called 'Vista TCP/IP & UAC AutoPatch'.
    More info here http://www.netfresco.com/tech/network-copy-failure/  or directly download the patch from here
    http://www.softpedia.com/get/Tweak/Network-Tweak/TCP-IP-Limit-AutoPatch.shtml
    This solution worked for me and i have no hesitation in recommending it.
    BTW this patch is vista 32 and 64 related, so if you are an XP user then unfortunately this may not be of any help.
    Good luck guys.
    Brassnex
    And may I ask if anyone else has tried this suggested "patch" please?

    Thanks!    Hard an OS that is fit for purpose.

    Sunday, November 15, 2009 11:11 PM
  • Hello

    I have lately the same problem. I changed my NAS from Thecus N5200PRO to N7700Pro. Copying to this new NAS causes this error. As soon as round about 40MB/s are copied the wireless connection aborts and never came back. I have to unplug the router and reboot it to get it working again.

    Info:
    Windows Vista Home Premium 32 bit (Intel WiFi 5100 AGN - latest driver v13)
    Router -> LinkSys WRT54G (Wireless G - 54 MBit Connection).

    Observation:
    Even due to the fact that the router not supports 802.11n some moments before the wireless network vanishes the connection speed is shown as 300 Mbits connection.
    Sunday, November 22, 2009 4:34 PM
  • Microsoft is incredulous, ignoring this long-standing "semaphore timeout" issue.

    I OFTEN get this "semaphore timeout" on my VISTA BUSINESS system when even trying to do a "dir" command on my Buffalo NAS (network attached storage) via the mapped drive.
    I believe this is simply a timeout regarding the response from the NAS (or any drive share).
    I believe the timeout is seemingly random, thus why some people experience it on even small files, but with large file you increase the liklihood of a timeout due to more opportunities for it to happen given the longer period of time.

    Note: I also sometimes get error, "The specified network name is no longer available" when even doing a "dir" command.

    It is not DHCP as suggested earlier, because I have a static IP.
    I am wireless, and wireless often gets brief interruptions in data streams, so my guess is that it is that.  You can such interruptions such as when you watched some streamed videos from the Internet and they simply stop altogether - very frustrating!

    MY FIX:
    As a test, I connected to my network via ETHERNET (LAN) CABLE, rather than using wireless, and over the past hour of doing periodic copies, I have not had any timeouts.

    This doesn't explain the problem those of you are having with USB and SD cards...  but, perhaps whatever device you're using is so slow, say, an SD class 2 card, that timeouts result, so perhaps and SD class 6 card wouldn't give such an error.  Similar for the USB product, perhaps the attached item only communicates at on USB1 speeds and not USB2 speed?

    So, Microsoft needs to do something about the timeout or the handling of sparatic disconnect states to allow a resume upon reconnection????

    I also like the idea of doing the CHKDSK /R that was suggested by someone else above - it cannot hurt, and who of us do this even once a year!?  It should be done as regular maintenance.  Do it on both your PC and on your NAS or USB or SD drives.
    Thursday, November 26, 2009 2:09 AM
  • I have the same problem with both network and external HDD via USB.

    I hope someone will come up with a solution.
    Friday, November 27, 2009 5:19 PM
  • Don't as me why but the follwing command "work-around-ed" the problem within my network (just execute in command shell):
    netsh int tcp set global autotuning=disabled


    But MS should really soon come up with a proper solution. This is dam annoying!
    Friday, November 27, 2009 8:29 PM
  • Well if it makes any difference, I upgraded from Vista Ultimate to Windows 7 Professional and I am still having the same problem.  I have been working with MS for over a month now with no resolution yet.  My backups fail with my Outlook file - which is under 1Gb and now the Windows Media database is failing as well.  I have both wireless & a lan cable plugged into my laptop and the external HD is brand new Seagate 1.5TB.  It's amazing that this has been going on for so long with no resolution from MS.
    Saturday, December 5, 2009 5:02 AM
  • Rosedio,

    Often you cannot backup files that are open, never can backup an open .pst files (outlook files for home use).
    Make certain your outlook.exe is closed -- I would suggest ctrl-alt-del and make sure no outlook.exe is running (I've had several times it stays running even if I use file>exit from the menu).

    Similarly, database files will not backup if the database engine is running. 
    In your case of Windows Media database, make sure to first stop service windows media.  Click START > RUN> ..type in.. services.msc > find "windows media" item(s) and stop it (personally, I have them disabled ).. 
    also stop any SQL service(s) you may see on your PC for other databases...

    Really, "backup" is best run in safe mode which has a minimal # of running services and running programs that are locking up files....  That's why you pay the big bucks for backup software like Backup Excec because they can backup database and locked files off of MS VSS versions...
    In most "normal" people's cases, however, we don't really have many locked files to worry about, so we use the freebie and manually shut off processes before backup.

    John
    Saturday, December 5, 2009 2:50 PM
  • Same problem here with Windows 7 Professional when copying one 300 MB file to a WebDAV storage. Seems to be an old MS bu^W feature.
    Tuesday, December 8, 2009 3:24 PM
  • I finally fixed the problem. I had the same error over and over again.

    In my case it was the security of my router. It was set to WPA-PSK. I disabled it and now it runs perfect...

    Greetz,

    Victor
    Wednesday, January 6, 2010 1:40 PM
  • I finally fixed the problem. I had the same error over and over again.

    In my case it was the security of my router. It was set to WPA-PSK. I disabled it and now it runs perfect...

    Greetz,

    Victor

    I had almost tried everything until I did the same, changer my router from WPA-PSK to WEP. Transferred my large file without issue in seconds.

    Thanks dreads76!

    Al
    Saturday, January 30, 2010 11:48 PM
  • Hi All, i know this is an old topic, but i noticed it has still been kept alive and no real solution has been found.

    I cannot remember who but they were correct in saying youd get a better understanding if you disregard the word semaphore.

    It is a general timeout issue with data transfer.

    Now, for me, im trying, simply to access my external HDD, not transfer as such, but just browse. (still classed fundamentally as a data transfer of such due to caching and previewing) anyway, my explorer would hang for a period of time and my external HDD activity LED would blink corresponding to the duration of the hang.

    Now, im running chkdsk /r from command prompt on this drive, and after the few warnings of not being a windows drive etc...it proceeds.

    What was worrying however is an error message appeared (Popup windows standard error dialogue box) stating the system cannot read the drive, but gave 3 options.
    Try again, continue or cancel.

    Try again simply made the error re eappear, however continue proceeded and an error in cmd appeared, stating that a particular director was "entirely unreadable" and it actually removed this directory.

    It has not finished yet but i will post back with an update to let you all know if this fixes the issue where data transfer between machine and external HDD is concerned.

    Also note please, that the folder it removed, was created 2 days ago, and from the time of creating this folder was EXACTLY the point in time where i began having this issue.

    So the corrupted folder chkdsk has found may be the coulprit, will update as necessary so you can establish where your problems may lie.

    Also, id like to thank everyone for their input and help troubleshoot the issues, i signed up just to post this and help where i can as i was happy with the level of service and help from users such as myself.

    will not mention the disappointment caused by Microsoft's inability to provide not a solution, bot even an explanation to the "Semaphore timeout" message.

    • Proposed as answer by deanshpleen Friday, February 26, 2010 4:03 AM
    Thursday, February 25, 2010 10:57 PM
  • I was having the same problems for the longest time. 
    My USB pen drives were useless to me as they kept timing out when I tried to copy large files.
    I read everything in this forum (and many others) but nothing helped. Until now.

    Hopefully this will help some others as well. One of the RSS feeds I subscribe to recommended a freeware from a company called Comodo. The program is a Registry Cleaner called 'Disk Cleaner' and you can get it here if interested.  http://www.comodo.com/home/support-maintenance/system-cleaner.php

    It removes corrupt or unnecessary registry entries and not only made my pen drives 
    functional again, my computer is speedier. 

    It has a function called SAFEDELETE so you can decide if you want to restore and cancel the changes.
    SafeDelete™ lets Comodo System Cleaner clean as deeply as possible without fear of removing something vital to your PC’s performance

    This might not solve your problem but it certainly did mine. Good luck...samold
    Monday, March 1, 2010 12:34 AM
  •  

    Whenever I try to copy large files over a wireless network (Laptop > Desktop) I get the following error:-

     

    Error 0x80070079: The semaphore timeout period has expired

     

    I've done a search on Google and have found that a number of other users are having the same problem, but no-one seems to have a fix for it.

     

    Can anyone help?

     

    (I'm running Vista Ultimate on both my Laptop & Desktop)

    I have the same problem.  I'm running win7 trying to network to a share drive on winxp.  Cannot find the windows 7 forum though.  Must not have any issues with my operating system.  Searching on this exact error message number in windows.com results in no hits.  I got here by searching on the semaphore quote. 

    The error message in win7 states to easily search on the exact error number.
    "An unexpected error is keeping you from copying the file.  If you continue to receive this error, you can
    use the error code to search for help with this problem.
    Error 0x80070079: The semaphore timeout period has expired."  Well I keep getting the error.  Funny how computers keep doing the same thing over and over again.

    The network connection works as some files do copy over.  Pushing files from winxp to win7 also errors out.  I can't type in that error message though as it appears that continually telling win7 to try again froze my xp box.  If I can't get my old files on my new laptop maybe I'll attempt to return it.

     


    KMS
    Wednesday, November 17, 2010 2:13 AM
  • I suspect a hardware issue somewhere, but the SD card problem resolved for me on a Dell when I used the hardware 'lock' on the card itself, making it read-only. The problem went away immediately. If I was worried about copying *to* the card, I'd dig deeper, but I'll let someone else work that out for now ;)
    Wednesday, December 1, 2010 9:58 PM
  • I suspect a hardware issue somewhere, but the SD card problem resolved for me on a Dell when I used the hardware 'lock' on the card itself, making it read-only. The problem went away immediately. If I was worried about copying *to* the card, I'd dig deeper, but I'll let someone else work that out for now ;)

    I was experiencing Error 0x80070079 while trying to take photos from a SD card to my HDD.  I could take other files (music, videos, etc), but nothing in my "pictures" folder.  The SD card originally came from a BlackBerry, but I have never had this issue... 

     

    I tried LloydFrombriz's way and it worked like a charm... I just can't "cut" items from my card...  oh well at least I can copy! Thank you LloydFrombriz for the help!!

    Wednesday, December 8, 2010 8:38 AM
  • Hi all,

    Im getting this error while copying 28GB .bak file from one server to another at different locations through XP_cmdshell.

    The semaphore timeout period has expired.

            0 file(s) copied.

    Can anyone help with this?

    • Proposed as answer by semtimeout Monday, December 20, 2010 10:19 PM
    Tuesday, December 14, 2010 10:57 PM
  • Apart from clicking on DineshPVM's post by mistake (sorry), I have also had similar problems. The dreaded "semaphore timeout" message appeared reasonably randomly during file backup operations (from XPsp3 32bit machine - 100Mb NIC to a Ubuntu 10.10 machine- 1Gb NIC). Also suffered from "network name not available" during these processes. A lot of googling didn't get me very far. The Ubuntu box is about 10 years older than the XPsp3 one, but is reliable in almost all other circumstances (its my Squeezebox music server as well as being the backup for most files). My linux skills just about got me to mii-tool to force the NIC configuration to slower speeds, but I still got the errors. Too many errors wound up leaving me with a ubuntu box with a dead network connection!

    In the end I seem to be transfering successfully now that I've replaced the rather tatty old network cable that I had been using (for the Ubuntu to network hub connection) with a better cable. Hey presto my problems seem to be solved.

    I see people having had problems with a miriad of connectivity modes (wifi, ethernet, usb, SATA), so all I can hope for is that one day someone will take a hard look at the error messaging and come up with something a little bit more helpful. *please*! Yes, the KB article does point the way, but how many people are really going to have the time to track down the root cause of their particular "semaphore timeout period has expired"?

    Meanwhile I'm keeping my fingers crossed that it does recure or crop up in another place...

    Monday, December 20, 2010 10:30 PM
  • This page helped me:
    http://8help.osu.edu/3253.html
    I have an Acer Aspire laptop and a QNAP NAS T-209 II. I got the semaphore error before I ran the command from the page and now it works fine.
    Wednesday, December 29, 2010 7:46 PM
  • I am getting that same message but I'm not trying to copy over a network.

    Just clicking on the folder gets me that message and I can't access the

    folder or any of the files. I don't know what to do now.

    Tuesday, March 22, 2011 7:48 PM
  • Hi,

    I've had the same issue with an SD flash-card. Many files could not be copied from the SD into hard disk, and even the files which are of moderate size (3Mb for example). I solved the problem by installing the card into card-reader instead of using laptop's built-in reader, and then plugging the external card-reader into USB port.

    It seems this problem is too complicated for Microsoft, and the only possible work around is to change hardware or drivers involved into the process.

    The size of data transfered, or a type of device do not matter - the error can occur anytime. I'm not sure about which versions of Windows are involved, but I saw the error under Windows 7 only.

    Sunday, March 27, 2011 9:20 PM
  • I am also having this problem on a Windows 7 with service pack 1. I am trying to copy large picture files (500+) to my hard drive from memory card that is placed in the media slot? Have not been able to fix this issue.

     

    T

    Monday, May 2, 2011 4:40 PM
  • I am having the same problem...trying to copy media files of various sizes from my phone's microSD card put directly into my laptop's card reader and onto my hard drive.  A couple files copied, but many are not and the ones that are, are transferring sooooo slow.  I'm on an Asus with Windows 7 64 bit.

     

    Edit:  Switching the card to read-only like LloydFrombritz said worked like a charm on one folder, but still problems going very slow and same error on others.

    Wednesday, May 4, 2011 2:15 AM
  • I had the same problem when I tried to copy a larger Hi-Def movie file of 15GB size.
    I couldn't get it to copy to the location I wished no matter what ever I do.

    All I did was, performed CHKDSK /r <Drive Partition eg. E:> on the partition that the file is located in and the CHKDSK said the file has corrupt/bad clusters and it fixed it. In fact, one of the replies for your post has the same step.

    Then after I was able to movie it like a snap.

    Sorry if you already tried this.. But in my case it worked. Looks like it has nothing to do with DHCP or Network. My research said it's a write issue on the disk. For instance when a chunk of file has to be written on a certain cluster of a disk, cluster is reserved and that chunk really was never written to that portion or vice versa.

    Please ignore if this is already solved!

    Regards,
    A.

    Tuesday, August 23, 2011 8:36 AM
  • After experiencing the same issue with transferring files between disks, I opened an elevated command prompt and was able to transfer the files via the copy command without any issues.  I wouldn't call it a solution, but that's the only work-around I've been able to get to work.
    Monday, April 2, 2012 7:24 PM
  • I found that there was a bios update for my motherboard on my Win XP PC that fixed a timeout issue with file transfers.  This solved my Semaphore timeout issue with Win 7 and Win XP.  It also let me reload Win XP SP2 and correctly update to Win XP SP3.  Apparently some time during SP2 this became a problem and even program updates to the Win XP computer had started to fail.

    KMS

    Tuesday, April 3, 2012 1:17 AM
  • If anyone is curious, I got it from putting an SDmini card into a reader on the front of an Optiplex 760.  Just plugged it in, opened Explorer, clicked on the drive and waited.  No copy or move actions, just trying to open it.  XP Pro SP3.

    Finding other methods to read it, just thought I'd add.

    Tuesday, May 1, 2012 2:39 PM
  • The semaphore timeout occured

    i had the same error in copying file from a connection through vpn via internet.

    network is wired till the internet.

    in original windows xp fully updated. this error terminate copy process.

    i found the error while copying through the c# .Net code which is like this....> File.copy(source,destination);

    this error terminate copy process. the file size is just 2 MB.

    i had posted this here...

    http://social.technet.microsoft.com/Forums/en-US/itprovistanetworking/thread/b4d99cd6-a090-48a9-9561-db3617e9f475


    Titoo3070chittur


    Thursday, June 28, 2012 5:07 PM
  • I am getting the same error message

    here is the detail:

    Vista Home Premium, 32 Bit

    purchased 8  various of 8 gb storage devices. I run each through a test of loading them with 7400 pictures that I personally took and are on my computers hard drive. There is no router involved and no internet. It is a direct copy of my pictures that vary from about 64 byte to 1.6MB for a total transfer from my computer to the 8 GB storage device of about 6.6 GB. I do this to ensure that I didn't buy a fake or defect from an on line sellers ( I have found several mis label/ fakes/ defects in the past ). In any case all of the 8 new 8gb storage devices passed except the last- a TF 8gb storage device ( mini card as you all know ). It is plugged in directly to the laptop with a card adapter. The same card adapter was used on two other TF cards with flawless performance. Only this last card from a different vendor is giving me numerous error messages of 0x80070079 Semaphone timeout.... I have checked the contact with moving the card in and out various times as well as the mini card. The transfer of data to the TF card was incomplete and my computer seems to have locked out my attempt to do a scan disk. FYI, I did a Norton scan of the TF card when I first plugged it in and there were no virus on the card, properties indicated about 8GB storage ( normal 7. something ) and disk was empty. All browsers were closed out and no internet or other programs were running in the foreground ( no office, W. Perfect, games or other - only the stock background programs ). I will try a scandisk after a reboot. If I find anything I will let you know.

    • Proposed as answer by jim4fun Tuesday, July 17, 2012 3:55 AM
    Tuesday, July 17, 2012 3:54 AM
  • Hi guys,
    I experienced this trouble for about a week, trawling forums and googling to the point where i had just about given up.
    Microsoft are no help at all, they know this problem exists yet ignore all requests of help to find a solution.
    Anyway, I managed to resolve this issue by installing a patch called 'Vista TCP/IP & UAC AutoPatch'.
    More info here http://www.netfresco.com/tech/network-copy-failure/  or directly download the patch from here
    http://www.softpedia.com/get/Tweak/Network-Tweak/TCP-IP-Limit-AutoPatch.shtml
    This solution worked for me and i have no hesitation in recommending it.
    BTW this patch is vista 32 and 64 related, so if you are an XP user then unfortunately this may not be of any help.
    Good luck guys.
    Brassnex

    And may I ask if anyone else has tried this suggested "patch" please?

    Thanks!    Hard an OS that is fit for purpose.


    its not a network problem but a hardware problem or a bad connection with the sata cable, i am getting the same issue when copying files large or small and also the speeds are very slow from one drive to an other sata or usb, i did some tests and copied from a good drive to my 1 tera usb drive and no issues, but when i copy or move the same file from the faulty drive i get error or copies at very low speeds like 15mb/secand lower. i ran chkdsk/f already but its still doing it, i am moving all my stuff and going to kill the partition and format and then try again, i also ran some tests with HD Tune Pro and drive checks out no bad sectors, ill update this post once i cleared the partition and reformated
    • Edited by Pascal.D Thursday, July 19, 2012 3:23 AM
    Thursday, July 19, 2012 3:22 AM
  • Problem still exists on Windows OS 8 (Just for the record)

    Never saw this problem on my Windows XP OS systems.

    My Situation:

    * New HP Laptop Quad-Core with 4 Gigs Ram

    * Transferring video files between a 1 TB (G Hard Drive) external and a new Segate Back-up Plus 3.0 - 3 TB hard drive external.

    * There were 400 Video files to transfer (Being done over night)

    * The Semphora Error occurred at file 199 and all remaining files.

    Solution:

    * I haven't troubleshooted the problem yet since I just woke-up and figured it wasn't worth starting the morning off with a frustrating and pointless troubleshooting issue.  These things are best troubleshooted at night when there is nothing good on T.V.

    Friday, December 28, 2012 4:02 PM
  • Check Network Discovery and make sure it is turned on for whatever network type you are using (DOMAIN, PRIVATE).


    R, J

    • Proposed as answer by bonpapa Thursday, February 14, 2013 10:53 PM
    Thursday, February 14, 2013 3:00 PM
  • There is an alternate solution to the problem mention above.

    One of my friends has the above mention problem. when I used my friends internet connection I got the very same error on my laptop and I never get the above error anywhere more on that in the button of the reply. However some steps can be taken to resolve the problem.

    1: take the computer to a friends house and see if the problem persists, if it does and the friend does not have the same problem on his or hers computer then it is probably the computer itself. It can be the network interface card, a driver error, or maybe a virus.

    2: replace the switch or router, if the problem disappears it may have something to to with the switch or router, if it doesn't then it may have something to do with the computer.

    In my friends case I do believe it has something to do with the internet connection, that is a switch or router is causing the problem the best choice may be to contact the internet provider which i know my friend is going to do.

    Well, that is my thoughts of the above matter.

     


    • Edited by Ivo Santos Thursday, November 21, 2013 9:54 PM
    Thursday, November 21, 2013 9:48 PM
  • I just purchased a Buffalo LinkStation NAS ... and  trying to copy files from my wirelessly connected laptops to the NAS I have started getting these errors.

    Laptops are: Vista Home Premium and Windows7 Home Premium.

    Router:  WRT54G ( Linksys )

    I'd hate to start scheduling backups and have it barf out on large files.... I'm not sure if the issue is the NAS, Linksys, Windows or what.  I'm sure if I called Buffalo ... they'd say windows.  If I could call MSFT they'd say Linksys, and if I could call LinkSys they'd say Buffalo.

    Companies these days are the "PASS THE BUCK" experts.  


    Thanks for the Help

    Tuesday, October 28, 2014 9:10 PM
  • I was getting the exact error in the title of this page (Error 0x80070079: The semaphore timeout period has expired.) using Win7 Pro x64, just trying to rename files and folders on a 128 GB SDHC card (actually a micro-SDHC in a SD-sized adapter) in a built-in reader (made by Ricoh) of my Dell laptop.

    None of the suggestions (nor proposed solutions) above helped.

    The only work-around I've had success with so far is to eject the card, then re-insert it. Boom; the file processes then complete without the error (as long as I don't wait too long to try them... if I wait a few hours, I start getting the error message again).

    BTW, various Hardware IDs associated with the reader:

    PCI\VEN_1180&DEV_0592&CC_0880
    PCI\VEN_1180&DEV_0822&CC_0805
    PCI\VEN_1180&DEV_0852&CC_0880
    PCI\VEN_1180&DEV_0843&CC_0880

    I have zero items showing in msinfo32 - Components -> Problem Devices
    (i.e. I got those Hardware IDs from Details tabs in devmgmt.msc)

    Sunday, May 24, 2015 10:11 PM
  • Check if you are able to access the Admin$.


    Omkar umarani SCOM STUDENT

    Thursday, August 6, 2015 9:03 AM
  • Four years later here, with my two cents' worth of notes about this rather versatile error message:

    My case was trying to copy videos off an SD card. Not huge - nothing over a gig - but lots of files. The (micro)SD card came out of a Handycam, and into an old Dell Latitude laptop. Slow as molasses.

    Trying to copy the card from the card reader was a huge failure. It timed out on every file pretty much.

    Then I plugged the Handycam into my desktop and copied the files from the card using the camera as a card reader basically. While a couple of files were still giving me a read error (which makes me think a part of the card is bung), the Handycam's reader seems to be doing a way better job of copying files than whatever's in the laptop. The speed is normal/reasonable, and only two files timed out so far.

    Takeaway: if you have this problem with an SD card, try using a different reader. Check the card structure like I am going to do when it's done copying and see if there are errors on it. It seems to me the cause of this is that something is physically happening inside the drive, but Windows for some reason can't detect it and thinks that some weird internal process was interrupted by accident.

    Wednesday, October 14, 2015 10:10 AM
  • Yep, SD card on internal slot on HP Probook, copying pics/vids from camera card to computer hard drive, no wifi, no external wires, gave me the error. But put card back into camera and it flaked out too. Put it in the exact same model laptop in our lab and it worked flawlessly. So what is it? Card? laptop A?? Only difference was: laptop A is on corporate network, laptop B is stand alone. So network file protection/network security taking to long looking at files on SD card that it times out? I think so.

    Oh, and next step was to see if using USB cable with card in camera works with laptop A. If it does, I have no ideas.

    • Edited by jimmydash Thursday, March 17, 2016 10:29 PM
    Thursday, March 17, 2016 10:28 PM
  • Simply run chkdsk to allocate new sector for the data which located on bad sectors.

    use command prompt type following commands


    chkdsk [name_of_drive][path] /f /v /r /x

    Examples:

    C:\Windows\system32>chkdsk d: /f /v /r /x

    or

    C:\Windows\system32>chkdsk d:\anyFolder\anyfile.txt /f /v /r /x

    Saturday, May 14, 2016 6:51 PM
  • Hi All,

    I recomend you use robocopy, when transferring large files with Robocopy, make sure you use the /J switch. Doing this causes Robocopy to use unbuffered I/O for the file transfer and is recommended when copying very large files. If you prefer using Xcopy you can also use the /J switch with Xcopy but only if you are using Windows Server 2008 R2.

    If you already using robobopy to copy, don't use /MT to it.


    Sunday, July 31, 2016 6:04 PM
  • I was having this exact same problem on Windows 7 professional. So I downloaded XP SP3 on a seperate partition, tried to transfer 6.5 gbs worth of music to my sd card and sure enough, it works! On windows 7, it kept on saying "semaphore period has timed out" or something like that
    Sunday, December 11, 2016 3:20 AM
  • use usb 2.0 will be work! don't use 3.0!
    Tuesday, December 19, 2017 4:49 AM
  • Hi,

    This is a long thread, and I hope it's still kind of relevant.

    Personally, I find it more helpful instead of recommending to "disable the firewall completely", maybe give a clue as to what TCP/UDP packet framing options are necessary. For example, using Client for NFS service, I easily can create new files and browse the share, and I used to be able to copy large files, so all of that kind of works. I am specifically blocking incoming packets on the destination hosts that are fragmented, and have options set. It would be quite helpful to tell us specifically if those firewall options are influencing network share copying. Not related to any specific firewall stack, rather general TCP / UDP guidance.

    Perhaps it's a trade secret? Otherwise, I see no reason not to get specific on a technet forum.

    P.S. If you're thinking "Client for NFS, are you kidding me", disregard this post.

    Tuesday, March 27, 2018 4:56 PM