Windows 10: Why Microsoft windows explorer still doesn't support long filenames?

I usually have file paths that cross 1000 characters. For local backup, I used to boot into Live Ubuntu and then copy files. Of course, shortening the filepath is not an option for me.Recently, I wanted to backup all the data to OneDrive Business 1TB. The problem with OneDrive is, If I use PowerShell to copy files with long names, it creates a local copy of the file too and I don't have enough space to accommodate 2 times the same 640GB data. I know I can right-click and choose ''free up space" to delete the local copy, but for that, I need to copy the files first. And unfortunately, I can't

:)

 

Microsoft Internet Explorer renamed to Windows Internet Explorer ?




Since version 7 of the world`s most popular web browser - Microsoft Internet Explorer was silently renamed to Windows Internet Explorer.Such a step from Microsoft is not a surprise since Internet Explorer is part of the Windows operation system for a long time.Obviously Microsoft corp. wants to state that Internet Explorer is already considered as a part of Windows and not as an external browser (remember the IE and WMP law issues last year!?).

 

Windows doesn`t start. Authomatic repair doesn`t work.

Thanks again!!

I`m sorry I had not noticed that the text on the picture was in spanish. It says that windows has replaced some damaged clusters in "name" file and "directory". Then, at the end "an unspecified error occurred (75736e6a726e6c2e 4f6)".

I`ll do it and I`ll be updating this thread when I have the report.

- - - Updated - - -

I ran SeaTools. These are the results:




Does it mean my HDD is useless?

 

Windows File Explorer long paths/filenames

Enabling long path support is only meaningful for programs that support that.

I can't see whether XYplorer supports long paths or not. The only clear reference I found was that it does support a way to scan for them:
XYplorer - Highlights

An experiment showed that:
a. file explorer crashed when attempting to create a file within a nested folder whose path name had been limited when I created the final nested folder (I.e. the folder path name had reached or exceeded the long path limit)

whereas
b. Xyplorer allowed me to navigate to that folder and when I double clicked on the file I had in fact created when explorer had crashed:



Clicking 'Yes' didn't open the file, and XYplorer closed too, although without the WER-like delay that was what probably happened when explorer took time to close.