Intel® Distribution of OpenVINO™ Toolkit
Community assistance about the Intel® Distribution of OpenVINO™ toolkit, OpenCV, and all aspects of computer vision-related on Intel® platforms.
6403 Discussions

OpenVINO 20.04 Windows 10 installation rolling back

Jackie67
Beginner
1,049 Views

I tried to install the OpenVINO 20.04 version on my notebook, win10 64bit 18.09 (build 17763.379).

But the setup started to roll back after all components installed.

Memory Size: 8GB

CPU: i5-8250U

 

What should I do to fix the problem?

Thanks for your supports in advance.

 

0 Kudos
1 Solution
Iffa_Intel
Moderator
1,007 Views

Greetings,


Intel will no longer monitor this thread since we have provided a solution. If you need any additional information from Intel, please submit a new question. 


Sincerely,

Iffa


View solution in original post

0 Kudos
4 Replies
Iffa_Intel
Moderator
1,040 Views

Greetings,


Could you elaborate more on what happened with the roll back?


If you referred to Openvino official documentation: https://docs.openvinotoolkit.org/latest/openvino_docs_install_guides_installing_openvino_windows.html


You need to have these in your system before proceeding further:

  1.  Intel® Distribution of OpenVINO™ toolkit core components
  2. Microsoft Visual Studio* with C++ 2019 or 2017 with MSBuild
  3. CMake 2.8.12 or higher 64-bit
  4. Python 3.5 - 3.7 64-bit


Sincerely,

Iffa


0 Kudos
Jackie67
Beginner
1,030 Views

Hi Iffa,

Yes, but as there're too many logs for each installation.(43files in total)

I don't know which file helps on the problem solving.

I just post 2 files with the latest creation time, FYI~

thanks a lot.

 

 

0 Kudos
Iffa_Intel
Moderator
1,022 Views

This installation is conducted on your host or virtual machine?

Probably you already had some of the older version of the pre-requisite installed in your system,

especially the msbuild.


I noticed that you got certain errors such as Error` = 1724, `Error` = 1709  which indicate MSI error (windows installer related error).


You may receive this error message if any one of the following conditions is true:

  • Windows Installer is attempting to install an app that is already installed on your PC.
  • The folder that you are trying to install the Windows Installer package to is encrypted.
  • The drive that contains the folder that you are trying to install the Windows Installer package to is accessed as a substitute drive.
  • The SYSTEM account does not have Full Control permissions on the folder that you are trying to install the Windows Installer package to. You notice the error message because the Windows Installer service uses the SYSTEM account to install software.


To resolve this problem, use any one of the following methods, depending on the cause of the problem:

  • Check if the app is already installed on the PC. If so, uninstall and reinstall the app.
  • If you previously had a desktop shortcut for an app, the shortcut may have been lost during the upgrade to Windows 10. In such cases, the app is likely still installed on the PC, resulting in this error when you attempt to reinstall the app. You can restore the shortcut by searching for the app, and if it's found, press and hold (or right-click) the app and select Pin to Start. Or you can resolve the issue by uninstalling and then reinstalling the app. To search for and uninstall apps in Windows 10:
  1. On the Start menu, select Settings.
    1. In Settings, select System > Apps & features.
    2. If the app is listed, then this is, select it and then select Uninstall.
    3. Follow the directions on the screen.
  • Install the package to a folder that is not encrypted.
  • Use this method if you receive the error message because you try to install the Windows Installer package to a folder that is encrypted.
  • Install the package to a drive that is not accessed as a substitute drive.
  • Use this method if you receive the error message because the drive that contains the folder that you try to install the Windows Installer package to is accessed as a substitute drive.
  • Grant Full Control permissions to the SYSTEM account.
  • Use this method if you receive the error message because the SYSTEM account does not have Full Control permissions on the folder you are installing the Windows Installer package to.
  • To grant Full Control permissions to the SYSTEM account, follow these steps:
  1. Open File Explorer (or Windows Explorer), right-click the drive that you want to install the Windows Installer package to, and then click Properties.
  2. Click the Security tab. Verify that the Group or user names box contains the SYSTEM user account. If the SYSTEM user account doesn't appear in the box, follow these steps to add the SYSTEM account:
    1. Click Edit. If prompted, approve the User Account Control.
      1. Click OK.
      2. To change permissions, click Edit. If prompted, approve the User Account Control.
      3. Select the SYSTEM user account, and verify in the Permissions section that Full Control is set to Allow. If not, select the Allow check box.
      4. Close the Permissions dialog and return to the Properties dialog. Click Advanced.
      5. Select Change permissions. If prompted, approve the User Account Control.
      6. In the Permissions tab, select the SYSTEM entry and click Edit.
      7. Click the Applies to dropdown and select This folder, subfolder, and files. Click OK.
      8. Wait for the operating system to apply the permissions that you have selected to all child folders.
      9. Run the Windows Installer package.
    2. Click Add. The Select Users or Groups  dialog box appears.
    3. In the Enter the object names to select field, type SYSTEM, and then click Check names.

Credit to website: https://docs.microsoft.com/en-us/troubleshoot/windows-server/application-management/msi-installation-error-1603


I recommended for you to uninstall any version of these that available in your system and freshly install afterward:

  1.  Intel® Distribution of OpenVINO™ toolkit core components
  2. Microsoft Visual Studio* with C++ 2019 or 2017 with MSBuild
  3. CMake 2.8.12 or higher 64-bit
  4. Python 3.5 - 3.7 64-bit




Sincerely,

Iffa


0 Kudos
Iffa_Intel
Moderator
1,008 Views

Greetings,


Intel will no longer monitor this thread since we have provided a solution. If you need any additional information from Intel, please submit a new question. 


Sincerely,

Iffa


0 Kudos
Reply