In Windows 10, after installing Java, the following problems arise with unpacking the src archive included in jdk:

  1. The standard Windows unpacker states: "The zip folder component could not create the specified directory. Make sure the directory does not exist yet and that the path is entered correctly."

  2. 7-zip unpacks everything and in its manager the created folder of the unpacked archive is displayed, but Windows Explorer still does not show it. The unpacked archive can be deleted from the 7-zip manager and it is perfectly located in the basket. After its recovery from the recycle bin, it finally becomes available in Windows Explorer.

  3. If desired, the experiments can be continued. For example, unpack all the same archive using 7-zip. Unpack it again in a folder with a different name. Windows Explorer, of course, does not see any of them. Delete one of the folders from the 7-zip manager and restore it from the archive. The conductor sees it. Rename it exactly the same one that was created in the 7-zip manager. Nobody swears at anything. Go to the manager 7-zip. It shows only one folder with that name. Remove it. The folder is deleted, but immediately in its place appears the same name. Remove it. There are no more folders like this. We go in the basket - both folders with the same name are available.

How to explain all these wonders?

Update

In principle, it is clear that the problem lies in the area of ​​access to the folder located in the Program files (although administrator rights). But why is everything so screwed up? Well, for example, the system does not allow you to create a file and save it in a folder located in the Program files, but can you create, save it on the desktop, and then move it to the same folder? Well, or all the same to do with the archive.

    1 answer 1

    According to your description of the two options, either you run the installation of Java without administrator rights, or there is an undesirable software on the PC.

    The installation of the program itself must be forced to run as an administrator, then there will be no problems. Right-click on the installer ---> run as administrator.