ChefDK Install Failing on Windows 10
dburnellSC opened this issue · 5 comments
Description
Installing chefdk-3.2.30-1-x64 to my Windows 10 Surface Pro and getting the following error in the install GUI (all default settings);-
Chef Development Kit v3.2.30 Setup Wizard ended prematurely because of an error. Your system has not been modified. To install this program at a later time, run Setup Wizard again. Click the Finish button to exit the Setup Wizard.
ChefDK Version
chefdk-3.2.30-1-x64
Platform Version
Windows 10
PS C:> [System.Environment]::OSVersion.Version
Major Minor Build Revision
10 0 16299 0
Replication Case
Running install MSI. Ran again through Powershell using this as commented in another issue thread
$result = Start-Process msiexec.exe -Wait -PassThru -ArgumentList "/qn /L*v msiexec_log.log /i $ (Get-Location)\chefdk-x64.msi"
$result.ExitCode
Attached log output >>
msiexec_log.log
Access denied error in attachment. I am running as local admin on this machine. Have tried taking ownership of install directory and ensuring effective permissions set to Full Control.
I have also tried using 7zip to extract all files manually and ensuring permissions have inherited OK - issue persists.
System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.UnauthorizedAccessException: Access to the path 'C:\opscode\chefdk\embedded\lib\ruby\gems\2.5.0\gems\opscode-pushy-client-2.4.11\omnibus\resources\push-jobs-client\msi\assets\LICENSE.rtf' is denied.
I'm having this same issue when attempting to install 3.3.23 on Windows 10.
After closing out of everything and renaming the existing C:/opscode/chefdk folder installation succeeded. I'm guessing a handle was open on a file or something.
I tried something similar but in the end I just created a new Windows 10 VM.
I'm unable to reproduce this locally so I'm going to close this out at this point. If someone is still having this issue on ChefDK 4.x please create a new issue and we'll see what we can do.
This issue still exist on Chef 4.2.0. The solution is same as @jakauppila did. Rename C:/opscode/chefdk ( to something chefdk-old ) then retrying running .msi again
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.