Parallels Tools won't install on Windows 10 build 10166

Discussion in 'Windows Virtual Machine' started by JasonC2, Jul 14, 2015.

  1. JasonC2

    JasonC2 Bit poster

    Messages:
    6
    Using Parallels Desktop 10.2.1 and Windows 10 Pro 10166.
    Parallels Tools was installed in Windows 10 and everything had been working great for several months now. I'm on the Insider Fast Ring and have been doing in place upgrades as they are available.
    This morning I decided to change some shared profile settings in Parallels. After doing this, Parallels would constantly pop up as soon as I logged into Windows and tell me that profile sharing settings have changed and I need to log off to apply changes. This was an infinite loop; this popup appeared on every login. I searched the knowledge base and discovered this was a known bug and the resolution is to uninstall / reinstall Parallels Tools.
    So... I uninstalled Parallels Tools but now it won't reinstall. When I attempt to initiate an install from the Actions | Install Parallels Tools menu, nothing happens. When I mount the Parallels Tools CD in Windows and manually launch the installer, it gets to 10% before giving me a generic "There was a problem installing Parallels Tools" error and telling me to reboot.
    Anyone have any suggestions?
    Jason
     
  2. Manu@Parallels

    Manu@Parallels Guest

    Messages:
    261
  3. JasonC2

    JasonC2 Bit poster

    Messages:
    6
    Thanks for the reply but there's nothing in that KB that addresses Parallels Tools installation problems.
     
  4. Maria@Parallels

    Maria@Parallels Problem solver

    Messages:
    8,121
    @JasonC2 please try to start sfc/scannow command:

    1. Start your Windows virtual machine -> click on Start and type in the "Search" box "cmd" -> on the top of the list please right click on the "Command prompt" and choose run as administrator (for more information please see the screenshot in the attachment)
    2. In the Command prompt window please type the following command:

    sfc /scannow and hit Enter.
    3. Restart your Virtual machine and check the issue.
     
  5. JasonC2

    JasonC2 Bit poster

    Messages:
    6
    Thanks, that worked!
     
  6. Maria@Parallels

    Maria@Parallels Problem solver

    Messages:
    8,121

Share This Page