Windows 10: "Source Path Too Long" despite making changes to gpedit.msc. Solution?
"Source Path Too Long" despite making changes to gpedit.msc. Solution?
I receive the following error when attempting to copy and paste a 25GB large folder with many sub-folders and files:
"Source Path Too Long. The source file name(s) are larger than is supported by the file system. Try moving to a location which has a shorter path name, or try renaming to shorter name(s) before attempting this operation."
I'm given an option to cancel the operation and nothing else. I'm a little bit surprised to see this message as both the source and destination drives are set to NTFS file system, I'm running a Windows 10 Pro ver 1607 build 14393.447 (which has long file path names turned on by default as indicated online), as well as I've done 'enable ntfs long path filenames' by accessing win + r > gpedit.msc > computer configuration > administrative templates > system > filesystem > enable win32 long paths (as 'enable ntfs long paths' has been renamed since some build). I've restarted my computer but am still facing the same old error message. I can't afford to manually rename files and folders in at least 200 objects in best case scenario. Because of this error I'm unable to use Dropbox as I should as well as backup my data locally on thumb drives. Is there a way to copy these kind of folders or files without creating virtual drives or manually renaming a large portion of objects?
I have the Purchased Retail Version of MR6 and have made several successful (NO Failed Yet) of my ENTIRE WIN 10 Computer (Image) onto my USB Seagate 1.5TB External HD.
In the Log I get this: Event ID: 513 Source: "Microsoft-Windows-CAPI2"
How can I make the file explorer always use "list" view when opening files and folders?
I have done an SFC /scannow at least two dozen times now on my Windows 10 tablet, resulting in "Found corrupt files but was unable to fix them" message
Several posts on this site alone tell me to do a "dism /online /cleanup-image /restorehealth"...
When I create a shortcut to file in Program Files, the target path for that shortcut will be to Program Files (x86), even though the start in path will be correct. Furthermore, even though the target path is incorrect and no icon is displayed for...
I have upgraded 5 machines and clean installed 3 machines.
Experienced an issue with one machine with continuous corruption problems
After the 3rd attempt I discovered that even with a Clean Install of Win 10 I get unrepairable errors - Sorry...