ESP-IDF Tools 2.0 Installed for windows fails with "Installation has failed with exit code 7" (IDFGH-1545)

[dlafont]

The windows installed fails at a point when extracting ESP-IDF reference repository
with error "Installation has failed with exit code 7".

This appears to happen if you accidentally have space and dash " -" in your filename for your destination installation directory.

This is further complicated if you try to rerun and re-install using the installer because there is no way to change (it appears) the default destination directory for the repo as it will never ask you again where you would like to install the repo on subsequent installs. It always seems to remember the prior repo destination you entered from the first attempt at installation and never ask you again in subsequent installs by running the installer.

You can't, therefore, fix it by entering the destination directory name in subsequent installations with a folder that has a corrected destination name that doesnt have a space an dash " -" in the folder name.

An extract from the install log that shows the issues as follows.. You can see the repo destination is attempting to install in "03 - ESP-IDF" folder name and fail/exit:

2019-07-21 21:20:08.770 Extracting temporary file: C:\Users\dlafont\AppData\Local\Temp\is-AR7PN.tmp\7za.exe
2019-07-21 21:20:08.828 Extracting ESP-IDF reference repository: C:\Users\dlafont\AppData\Local\Temp\is-AR7PN.tmp\7za.exe x -oC:\Users\dlafont\AppData\Local\Temp\is-AR7PN.tmp -r -aoa C:\Users\dlafont\Dropbox\03 - ESP-IDF.espressif\releases\esp-idf-v3.2.2.zip
2019-07-21 21:20:08.828 Reference repository path: C:\Users\dlafont\AppData\Local\Temp\is-AR7PN.tmp\esp-idf-v3.2.2
2019-07-21 21:20:09.268 Done, exit code=7

----------------------------- Delete below -----------------------------

If your issue is a general question, starts similar to "How do I..", or is related to 3rd party development kits/libs, please discuss this on our community forum at esp32.com instead.

INSTRUCTIONS

Before submitting a new issue, please follow the checklist and try to find the answer.

• I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
• I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
• I have searched the issue tracker for a similar issue and not found a similar issue.

If the issue cannot be solved after the steps before, please follow these instructions so we can get the needed information to help you in a quick and effective fashion.

1. Fill in all the fields under Environment marked with [ ] by picking the correct option for you in each case and deleting the others.
2. Describe your problem.
3. Include debug logs on the monitor or the coredump.
4. Provide more items under Other items if possible can help us better locate your problem.
5. Use markup (buttons above) and the Preview tab to check what the issue will look like.
6. Delete these instructions from the above to the below marker lines before submitting this issue.

----------------------------- Delete above -----------------------------

Environment

• Development Kit: [ESP32-Wrover-Kit|ESP32-DevKitC|ESP32-PICO-Kit|ESP32-LyraT|ESP32-LyraTD-MSC|none]
• Kit version (for WroverKit/PicoKit/DevKitC): [v1|v2|v3|v4]
• Module or chip used: [ESP32-WROOM-32|ESP32-WROOM-32D|ESP32-WROOM-32U|ESP32-WROVER|ESP32-WROVER-I|ESP32-WROVER-B|ESP32-WROVER-IB|ESP32-SOLO-1|ESP32-PICO-D4|ESP32]
• IDF version (run git describe --tags to find it):
  // v3.2-dev-1148-g96cd3b75c
• Build System: [Make|CMake]
• Compiler version (run xtensa-esp32-elf-gcc --version to find it):
  // 1.22.0-80-g6c4433a
• Operating System: [Windows|Linux|macOS]
• Power Supply: [USB|external 5V|external 3.3V|Battery]

Problem Description

//Detailed problem description goes here.

Expected Behavior

Actual Behavior

Steps to repropduce

1. step1
2. ...

// It helps if you attach a picture of your setup/wiring here.

Code to reproduce this issue

// the code should be wrapped in the ```cpp tag so that it will be displayed better.
#include "esp_log.h"

void app_main()
{
    
}

// If your code is longer than 30 lines, GIST is preferred.

Debug Logs

Debug log goes here, should contain the backtrace, as well as the reset source if it is a crash.
Please copy the plain text here for us to search the error log. Or attach the complete logs but leave the main part here if the log is *too* long.

Other items if possible

• sdkconfig file (attach the sdkconfig file from your project folder)
• elf file in the build folder (note this may contain all the code details and symbols of your project.)
• coredump (This provides stacks of tasks.)