5 months later... Win10 with indexed file shares still broken with no fix on the horizon.

[momurda]

Was going to migrate all our shares to Server 2012 with fully indexed shares this weekend. Then i did some tests(have been doing them for awhile) with my workstation and some other Win10 machines.
Nope

https://social.technet.microsoft.com/Forums/windows/en-US/b72c763e-d029-4e65-a2dc-885a5aabf643/problem-creatingrenaming-a-folder-on-a-network-share-with-win10-anniversary-update-error?forum=win10itpronetworking

August is when that thread starts.
Ive been putting this project off for months now because of this.
Very nearly unbelievable. I am curious since this problem seems to not affect everyone(though it affects many), anybody here waiting for this fix?

[Dashrender]

so what is the migration you are considering?

Migrating your servers to 2012 R2? or migrating the workstations to Windows 10 1607?

If the server, why not skip 2012 R2 and go to 2016?

[momurda]

The patch released yesterday for Win10 1607 seems to have fixed this issue. I can now move our massive unindexed userdata file share to our indexed file shares that have been empty for 6 months.