I have downloaded the OpenVino toolkit executable file from the OpenVino website. The product package extraction is successful and the Installation window is launched for a few seconds and closes automatically. I have tried multiple times but could not be successful. Please let me know how to install OpenVino successfully.
FYI, I use Windows 10 (64 bit) OS and I could install OpenVino earlier on my system successfully. I have attached the log file that is created while running the executable file.
Thank you for reaching out to us.
I've replicated your issue, downloaded OpenVINO 2021.4.1 LTS and ran the installer.
The installation succeeded on my side.
As a workaround, can you try to run the install.exe file manually? (It's located in the extracted directory: C:\Users\chennama\Downloads\Intel\w_openvino_toolkit_p_2021.4.689_2022-02-28_15-07-38\install.exe)
Alternatively, we recommend you give a try to freshly download and install OpenVINO Toolkit again.
I have also tried to replicate Sowjanya's issue, but on my Windows 10 notebook the installer works as expected.
Then I have compared Sowjanya's install_log.txt file with the log file that was created by my installer. They are almost equivalent, but I see a "return code of the child process" of 4, whereas Sowjanya got -1073741571. Does her value of -1073741571 provide any hint for the root cause?
28.02.2022 15:07:44 : 11576 : The following child window found: Intel(R) Distribution of OpenVINO™ toolkit 2021.4.1 for Windows*
28.02.2022 15:07:44 : 11576 : Child window was found
28.02.2022 15:07:44 : 11576 : Waiting end of child process...
28.02.2022 15:07:48 : 11576 : Return Code of child process: -1073741571
28.02.2022 15:07:48 : 11576 : Setup.exe was launched
28.02.2022 15:07:48 : 11576 : Finish
28.02.2022 15:07:48 : 11576 : WARNING : Return Code is overwrited by Setup.exe return code. [ret code] = 1000 + [setup.exe ret code]
28.02.2022 15:07:48 : 11576 : Return Code: -1073740571
From our replication, we can confirm that this is not related to OpenVINO or its dependencies.
I share this Stack Overflow case which might indicate some probable causes for this issue.
This thread will no longer be monitored since we have provided a solution. If you need any additional information from Intel, please submit a new question.