tag:blogger.com,1999:blog-2109043157682332740.post469658517830755545..comments2023-11-28T01:44:31.345-07:00Comments on Network Defend: Fix: Windows 10 Error 0x8007003B When Creating or Renaming Folders on a Network Share (Very Slow Folder Creation)Unknownnoreply@blogger.comBlogger65125tag:blogger.com,1999:blog-2109043157682332740.post-10102862661600937122017-12-17T09:52:03.313-07:002017-12-17T09:52:03.313-07:00I started having this issue within the past week o...I started having this issue within the past week or so. Of course, Windows is way past this version/update now. Nothing so far is working.Donhttps://www.blogger.com/profile/07214209054533283361noreply@blogger.comtag:blogger.com,1999:blog-2109043157682332740.post-23915431524651026282017-03-20T03:51:12.665-06:002017-03-20T03:51:12.665-06:00The latest updates appear to have done the trick f...The latest updates appear to have done the trick for me. Both creating and renaming folders now work as expected (prior to the issue). Search/indexing is on.Danhttps://www.blogger.com/profile/08046369195939983032noreply@blogger.comtag:blogger.com,1999:blog-2109043157682332740.post-59876830620557963662017-03-19T17:55:39.773-06:002017-03-19T17:55:39.773-06:00Unfortunately the "Cumulative Update for Wind...Unfortunately the "Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4013429)" did not fix the issue on my end.<br /><br />Still getting errors and painfully slow.Buckhttps://www.blogger.com/profile/11786344883192080052noreply@blogger.comtag:blogger.com,1999:blog-2109043157682332740.post-74591636219087851122017-03-16T05:12:47.497-06:002017-03-16T05:12:47.497-06:00Many thanks once again, Rob! Looks like this was a...Many thanks once again, Rob! Looks like this was among the misterious skipped February updates. I have now finally received the update and will retest, will report if the issue reappears.Anguelhttps://www.blogger.com/profile/12684801283689942402noreply@blogger.comtag:blogger.com,1999:blog-2109043157682332740.post-80736753099173476532017-03-15T11:51:48.372-06:002017-03-15T11:51:48.372-06:00Looks like MS rolled the fix for this into the Mar...Looks like MS rolled the fix for this into the March patch roll-up being delivered this week via Automatic updates for all 1607 editions: "Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4013429)" . . .Rob Shttps://www.blogger.com/profile/14611962094074368182noreply@blogger.comtag:blogger.com,1999:blog-2109043157682332740.post-29268093556157048972017-03-15T06:20:04.126-06:002017-03-15T06:20:04.126-06:00Has the fix been distributed through automatic upd...Has the fix been distributed through automatic updates in the meantime?Anguelhttps://www.blogger.com/profile/12684801283689942402noreply@blogger.comtag:blogger.com,1999:blog-2109043157682332740.post-5114530321670935052017-02-27T11:30:01.190-07:002017-02-27T11:30:01.190-07:00Life Saver, thank you! :) Life Saver, thank you! :) HoneyNovahttps://www.blogger.com/profile/12658912570515491140noreply@blogger.comtag:blogger.com,1999:blog-2109043157682332740.post-30494869121626496952017-02-05T23:39:23.217-07:002017-02-05T23:39:23.217-07:00Awesome! I've suffered this issue with Win10 a...Awesome! I've suffered this issue with Win10 at a couple of sites and your solution using the cumulative update has resolved them!Anonymoushttps://www.blogger.com/profile/12760376096543022992noreply@blogger.comtag:blogger.com,1999:blog-2109043157682332740.post-2276846930318925212017-01-24T14:17:39.260-07:002017-01-24T14:17:39.260-07:00I have had this same issue on Server 2016, just in...I have had this same issue on Server 2016, just installed the latest update and now renaming of folders takes around 2 - 3 seconds no mention in the write up that it should have fixed it mind.<br />https://support.microsoft.com/en-gb/help/4009938/january-10-2017-kb3213986-os-build-14393-693 <br />Regards,<br />DaveDavehttps://www.blogger.com/profile/08291252897212394171noreply@blogger.comtag:blogger.com,1999:blog-2109043157682332740.post-6770124194413277412017-01-21T15:52:00.716-07:002017-01-21T15:52:00.716-07:00Ah. Thanks for clarifying! Continuing to wait on M...Ah. Thanks for clarifying! Continuing to wait on Microsoft then. :-/Paul & Valerie Powershttps://www.blogger.com/profile/17955883549215490622noreply@blogger.comtag:blogger.com,1999:blog-2109043157682332740.post-40396411105009270532017-01-21T15:42:46.651-07:002017-01-21T15:42:46.651-07:00We were discussing the scenario where the client w...We were discussing the scenario where the client workstation is joined to a Domain Controller. FQDN is an abbreviation for "Fully Qualified Domain Name" which is a "long" or "full" name of the local network name that includes the local domain name plus the machine name. It's all wrapped into a system we call Active Directory. In your case none of that applies since you are using a peer to peer network topology instead of one where you have a central network authority.Rob Shttps://www.blogger.com/profile/14611962094074368182noreply@blogger.comtag:blogger.com,1999:blog-2109043157682332740.post-3640487532588987762017-01-21T12:39:06.388-07:002017-01-21T12:39:06.388-07:00I have this problem copying over large files from ...I have this problem copying over large files from my NAS (local networked drive). In your example, I don't know what you mean by "FQDN". And it's not hooked up to a "domain.org". May you please clarify what to do there? Thanks for your time!Paul & Valerie Powershttps://www.blogger.com/profile/17955883549215490622noreply@blogger.comtag:blogger.com,1999:blog-2109043157682332740.post-73506178492728717092017-01-20T04:57:28.757-07:002017-01-20T04:57:28.757-07:00I'm curious why it is taking so long to fix th...I'm curious why it is taking so long to fix this on a technical level. I'm curious as to what things the fix might break that has Microsoft taking so long, or is it simply that it's not as important to focus on this as it is other aspects of windows.Compro Computershttps://www.blogger.com/profile/02640501973481967831noreply@blogger.comtag:blogger.com,1999:blog-2109043157682332740.post-31393937333034503082017-01-19T17:56:07.890-07:002017-01-19T17:56:07.890-07:00Can confirm seeing the same result.Can confirm seeing the same result.Anonymoushttps://www.blogger.com/profile/10607088532476184992noreply@blogger.comtag:blogger.com,1999:blog-2109043157682332740.post-50222143664513301852017-01-19T14:21:24.049-07:002017-01-19T14:21:24.049-07:00Definitely came in handy today. A brand new W10 f...Definitely came in handy today. A brand new W10 fully patched could create a folder on a network share with no issue. But when I would try to delete the folder, it took upwards of 60-90 seconds. On a Windows 7 PC on the same network using the same account, the folder is deleted instantly. Disabling and stopping the service fixed the issue. Jameshttps://www.blogger.com/profile/02496130325256438601noreply@blogger.comtag:blogger.com,1999:blog-2109043157682332740.post-89439646231411639242017-01-19T09:15:56.921-07:002017-01-19T09:15:56.921-07:00I saw this on a few systems. A fix that worked fo...I saw this on a few systems. A fix that worked for me on the Windows 10 systems was to click Start, Settings, Apps and Features, find the App Connector app, click it, then go into advance, then click reset. This fixed two Win 10 laptops that were taking 1-2 mins when trying to create a folder on a Windows Server 2012 R2 Essentials server.Obyone89https://www.blogger.com/profile/11933390325375364139noreply@blogger.comtag:blogger.com,1999:blog-2109043157682332740.post-33104736682890735312017-01-19T04:36:22.763-07:002017-01-19T04:36:22.763-07:00The 3rd solution works only up to the second level...The 3rd solution works only up to the second level subfolder. Anything deeper is coming with the same issue.Anonymoushttps://www.blogger.com/profile/17711851057610345296noreply@blogger.comtag:blogger.com,1999:blog-2109043157682332740.post-46707667894058848072017-01-18T16:05:13.201-07:002017-01-18T16:05:13.201-07:00I was able to get it to work on my small test bed,...I was able to get it to work on my small test bed, but this morning I tried it on a production network and the result was disappointing. Same pause and error. Now trying to analyze the differences to see if I can find more clues.Rob Shttps://www.blogger.com/profile/14611962094074368182noreply@blogger.comtag:blogger.com,1999:blog-2109043157682332740.post-66858322216921423412017-01-18T12:53:36.210-07:002017-01-18T12:53:36.210-07:00SoCal Church IT Guy fix did not work in my situati...SoCal Church IT Guy fix did not work in my situation. Does anyone else have any ideas on how to correct Microsoft's big issue?Anonymoushttps://www.blogger.com/profile/09034823887079910321noreply@blogger.comtag:blogger.com,1999:blog-2109043157682332740.post-3534094338229969852017-01-17T11:03:01.276-07:002017-01-17T11:03:01.276-07:00Now this is very interesting! I'm going to te...Now this is very interesting! I'm going to test this out this week. Thanks for the insight!Rob Shttps://www.blogger.com/profile/14611962094074368182noreply@blogger.comtag:blogger.com,1999:blog-2109043157682332740.post-90481736714931828772017-01-17T11:02:19.796-07:002017-01-17T11:02:19.796-07:00We found the same thing, but with the current 1607...We found the same thing, but with the current 1607 builds it's become very difficult to disable Cortana unless you use the Enterprise license versus the Pro license for small businesses.Rob Shttps://www.blogger.com/profile/14611962094074368182noreply@blogger.comtag:blogger.com,1999:blog-2109043157682332740.post-36796860215333992882017-01-17T09:56:24.744-07:002017-01-17T09:56:24.744-07:00I had a bit of a breakthrough in this long running...I had a bit of a breakthrough in this long running issue... entirely by accident.<br />The issue is repeatable if we use \\server\sharename\(and then any depth of folder tree) from any Windows 10 machine.<br /><br />Today, I accidentally discovered that if we use \\FQDN\sharename(and then any depth of folder tree) the behavior goes away every time. And this holds true if we map a drive using FQDN as well.<br /><br />So, for example:<br />BAD: \\fileserver\users\bob --> create any folder and try and rename it during 'creation' or rename it later... will fail, give errors, etc. after significant delay.<br /><br />GOOD: \\fileserver.ourdomain.org\users\bob --> can rename it however you like, at point of creation or later.<br /><br />Also GOOD: MAP Z: to \\fileserver.ourdomain.org\users ... then use z: to create and or rename folders - no issues.<br /><br />Indexed searches remain enabled and all searching is MUCH faster than the official workaround of disabling indexing.SoCal Church IT Guyhttps://www.blogger.com/profile/17126981336602036576noreply@blogger.comtag:blogger.com,1999:blog-2109043157682332740.post-1144724422834786982017-01-17T09:13:00.702-07:002017-01-17T09:13:00.702-07:00Not sure if it's relevant or not, but I did no...Not sure if it's relevant or not, but I did not have this issue before the anniversary update although most of my office mates were experiencing problems. The main difference that I know of is that I disabled Cortana immediately after updating to Win10, whereas nearly everyone else left it running.<br /><br />Now that I'm forced to leave Cortana alone, it's a 10-15 minute process to try and rename a folder. I rename a file and hit enter, then everything freezes. When the error message finally pops up after about 5 minutes I lose access to server files (except for 1 specific folder ??? ) for anywhere from 5-10 minutes on average (I've tried timing it and it is very inconsistent, with 4 minutes being the fastest and 18 being the slowest). <br /><br />Whenever I regain access to the server file system, the file shows the new name... so it works, but it's a major PITA. Hopefully they fix this soon.Anonymoushttps://www.blogger.com/profile/08093209842524535938noreply@blogger.comtag:blogger.com,1999:blog-2109043157682332740.post-27255064947466193082017-01-13T12:01:50.923-07:002017-01-13T12:01:50.923-07:00Thanks for the Jan 9, 2017 update. I am eagerly a...Thanks for the Jan 9, 2017 update. I am eagerly awaiting this update. I hope that they identify whether the problem lies in Windows client access issues or in the Windows Search running on the server. Happy New Year!husband2https://www.blogger.com/profile/17733201186142161897noreply@blogger.comtag:blogger.com,1999:blog-2109043157682332740.post-45918680720217479652017-01-12T21:25:38.498-07:002017-01-12T21:25:38.498-07:00I've noticed this error on my windows 10 machi...I've noticed this error on my windows 10 machine. However, I don't have any "network" drives but only local drives that are mapped locations. So, for example "w:" refers to a location on my machine that is c:\users\jason\downloads. <br />If I'm in windows explorer and then I add a folder in w: it can error. <br />However, I'm in windows explorer and then I add a folder in c:\users\jason\downloads it does not error. <br /><br />Also, if I use FreeCommander instead of windows explorer, there's no error. <br /><br />So, to me, this seems like a bug in windows explorer.<br />Anonymousnoreply@blogger.com