Posts: 42
Joined: Apr 2011
Reputation:
2
Sorry, I didn't put it in that forum because the description is "Questions about Kodi for Windows go here"
Should have been clearer, running Kodibuntu, this issue won't affect Kodi on Windows
Posts: 3,575
Joined: Mar 2011
Reputation:
194
You're right, but there are a ton of threads about windows' rubbishy smb sharing and they're all in here.
Posts: 6,563
Joined: Apr 2008
Reputation:
160
natethomas
Enjoying Retirement by Staying Busy
Posts: 6,563
This is actually also how you fix usb shares in Windows 10 even before anniversary edition.
Posts: 42
Joined: Apr 2011
Reputation:
2
I didn't have the issue before the update, *for me*, the update introduced it, just trying to help if it happens to anyone else
Posts: 253
Joined: Dec 2012
Reputation:
2
Same here. I have 2 USB drive bays that each hold 4 drives.
After the latest Win10 update I started getting the invalid arguement error anytime I tried to access any of the 4 drives in the second drive bay. Yet,the four drives in the first drive bay still work perfectly.
The update also screwed up the visibility of my main computer on my network as a whole. Suddenly none of my other computers could see it. I found a thread that had me identify about 10 different services, turn them from amnual to automatic, and restart them. This fixed my pc's visibility on the network.
I find it ridiculous that an update I didn't even choose to install caused such havoc with my network permissions and visibility.
I have made the change noted on this thread, but haven't been able to reboot that machine yet to see if it worked. My fingers are crossed. My kids rely on our media boxes to the point that it is a crisis around here when they suddenly stop working.
Posts: 12,452
Joined: Oct 2014
Reputation:
600
The update broke a lot of stuff. For me personally, my current count is:
SMB.
Network drop-down tag in Windows File Explorer.
Task Scheduler entries that I've added manually.
The latter two are really annoying for me, especially the task scheduler one. Having to add another program to Windows to work around it and do the job task scheduler was happily doing last week before the update.
I'm really wondering whether they actually bothered to test any of this update at all before forcing it on everyone stuck with Win10.
Posts: 990
Joined: Jul 2009
Reputation:
3
Shit man.. I restarted my server to install this update and now I can't access my movies. Thanks MS for shoving these updates down our throats.
Posts: 3,846
Joined: Mar 2006
Reputation:
156
Hmmm... are you saying that two Win10 machines shouldn't need this? Because that's my situation, I don't have that key in my registry and everything is working as it should. I just want to be sure to understand your situation.
For troubleshooting and bug reporting please make sure you
read this first (usually it's enough to follow instructions in the second post).
Posts: 403
Joined: Mar 2015
Reputation:
3
^^You shouldn't need to modify the registry, but I had to redo the sharing on my update to AE.
Posts: 990
Joined: Jul 2009
Reputation:
3
So before this last update I was able to share my Wimdows 10 Pc without needing to put in any user or password. After this update I had to create another account and on the other computers use the login to get access.
Posts: 403
Joined: Mar 2015
Reputation:
3
What prompted the need for another account? The first account you create in Windows 10 is an admin one by default.
Posts: 2
Joined: Feb 2016
Reputation:
0
The first option in this thread worked for me by increasing to 33. I no longer have the error message which started when I updated to the win10 anniversary edition. Thanks
Posts: 3
Joined: Oct 2017
Reputation:
0
I had the same issue, and no amount of registry tweaks, changing the way I tried to map the share (by IP, append the port etc etc) worked for me. Trying to connect to the network share always gave me an instant time out error, and hitting the Windows (SMB) link under browse for new share gave me the mysterious "error 2". There was just no way to make it work, and after spending hours on it, I had no option but to give up. I ended up installing Plex Server on the Windows box as a workaround, and later the Plex app on my Android TV, which is really nice by the way, but last night finally figured the issue out.
I initially assumed it was a problem with my Android TV. However, a month or so after installing Plex, I fired up Kodi on my Macbook, and noticed that it had the exact same issue when trying to connect to the Windows share. I was able to connect to the Windows share fine through Finder, just not through Kodi, so I knew that the issue was specific to Kodi and the Windows share.
Kodi only works with SMB1 apparently, and for whatever reason, in the anniversary update, that's no longer installed by default.
To resolve it, I ran appwiz.cpl, Turn Windows Features On or Off, and enabled SMB 1.0/CIFS File Sharing Support. I also installed SMB Direct, but I suspect that's unrelated.
After enabling the feature and restarting the Server service, Kodi was able to connect to the share immediately.
Hopefully if anyone else is having this issue, this is helpful and saves them from the frustration and workarounds that I had to go through.
