How to overcome file access denied on extra-long paths in Win 10?

Question

Windows

The contractor sent an archive containing a structure with very long folder and file names inside. According to the internal structure of the documentation, this archive was unpacked to the place allotted to it inside the directory tree.
C:\Users\Alex300\YandexDisk\DESIGN DOCUMENTATION\UGPU\P.0-OB .format\1 - Production - household building inv.nom N100378 - Code 57-01-100378-17-
TO.docx opens, Word 2016 opens but read-only and swears,

spoiler

does not save

spoiler

.
The actions described here have been done: there is an entry in the registry, long names are enabled in group policies.
PS: in the properties of the Location file it looks like this: C:\Users\Alex300\YANDEX~1\2BF6~1\9CA0~1\C326~1.0-\1--~1.N10\D828~
1 the way is shorter - I can think of it myself. The question is whether it is possible in Win 10 to get around the restriction on the length of the path + name, or is there some kind of strict restriction, such as 400 Unicode characters and that's it.
UPD2: Artem @Jump
Kulver_stukas, Of course, both the file system and the operating system have such a limitation.
For example, NTFS supports paths up to 32767 characters long.
Windows 7 supports paths up to 255 characters long
Artem, Well, this is almost an author's sheet, i.e. ~10 pages in Word, so it's obviously not NTFS that's the problem ;)
UPD3: In Windows 10 (1607), the behavior of functions for working with files has changed: it's now possible to disable MAX_PATH constraint checking at the system level. (c) Habr

Answer 1

Change long directory and file names to shorter ones - it's obvious.
And tell those who come up with such monsters that it is not technically possible to work with paths of such length.
As an option (not sure if it will work), you can make a branch of directories with shorter names, and in your long branch make links to short files.

Answer 2

Was it packaged somehow? So the paths do not exceed the allowed limits.
It is you who are lengthening the path by unpacking it into some folder with a long name.
Unpack to the root of the disk, and everything will be fine.

Answer 3

1. In one of the editions of Windows 10, this restriction was removed:
https://www.howtogeek.com/248177/whats-new-in-wind...
https://habrahabr.ru/post/307186/
2. In Linux there are no such problems, but in principle, operations with files along such long paths under Windows as: copy / move / rename are adequately handled by Total Commander, and possibly some other file managers.
3. As an intermediate option - throw everything on the ball and give network access along a shorter path (for example, directly to the folder in which the files are, ignoring the previous tree). Or create a virtual disk pointing to a folder that is not in the root.