Biggest disappointment Long file names don't work

Hi there

I was really hoping for the Long file names to work (> 260 chars inc Directory names) -- No go --still don't work.

I've some other issues - but this is a real disappointment.

Cheers
Jimbo

swarfega said:

You might want to read this article: Microsoft removes 260 character limit for NTFS Path in new Windows 10 Insider Preview - MSPoweruser

Hi there
@swarfega

On One system I got Windows can't find gpedit.msc and on the other there's no long file names option.

The one with no gpedit.msc is the one updated via Automatic update and the other vis the update assistant tool so even the updates aren't identical

What a dogs dinner --surely people test this stuff before letting it out of the door. This is BASIC !! to have the update consistent on systems. Both running W10 x-64 Pro GB edition and version is (on both) Version 1607 (Os Build 14393.10) ??????

I think in future I'll wait a few weeks before doing anything like this again.
I've backed up both, installed in VM's in case there's some testing I can do meanwhile and reverted back to 1511.

Cheers
jimbo

Jimbo45 is right, the option has been removed.

Brink said:

Hello Jimbo, :)

You might see if the tutorial below may be able to help with this. It has a registry option included.

https://www.tenforums.com/tutorials/5...dows-10-a.html

Hi there

I tried that too --although registry keys were changed / created didn't work even after re-boot.

Temporary solution - run VM in HYPER-V / VMware and run server from Linux VM.

Another issue is VMware - BRIDGED networking doesn't work --could be a while before VMWARE fixes that. Using NAT isn't an acceptable alternative unfortunately.

I'll keep 1511 until some of the early adopters have got issues fixed. !!

Cheers
jimbo

Once more jimbo45, bridged networking works. Please take a look at the output of ifconfig, executed in my virtual machine (Fedora 24) under VMWare Workstation 12 Pro. You can clearly see that an IP of my LAN pool has been assigned to the virtual machine by the router (network is 192.168.1.0/24). I've also attached a screenshot of the virtual network editor.

What software of VMWare (player or workstation) do you use? And what version? On my system the existing network configuration for VMWare Workstation also stopped working after the update. But restoring defaults fixed that issue.