Same behaviour here. Anyone have a fix for this?
Thanks
Same problem here. Trying to install the 2012 R2 console on my Windows 8.
I solved the problem by upgrading Visual C++ 2010 redist.
Had an old version of "vcredist" installed on my machine (version 10.0.30319). Did the upgrade of "vcredist" with the installation files from the VMM 2012 R2 media (\Prerequisites\VCRedist) and after a reboot i managed to install the console.
I solved the problem by upgrading Visual C++ 2010 redist.
Had an old version of "vcredist" installed on my machine (version 10.0.30319). Did the upgrade of "vcredist" with the installation files from the VMM 2012 R2 media (\Prerequisites\VCRedist) and after a reboot i managed to install the console.
I solved the problem by upgrading Visual C++ 2010 redist.
Had an old version of "vcredist" installed on my machine (version 10.0.30319). Did the upgrade of "vcredist" with the installation files from the VMM 2012 R2 media (\Prerequisites\VCRedist) and after a reboot i managed to install the console.
I solved the problem by upgrading Visual C++ 2010 redist.
Had an old version of "vcredist" installed on my machine (version 10.0.30319). Did the upgrade of "vcredist" with the installation files from the VMM 2012 R2 media (\Prerequisites\VCRedist) and after a reboot i managed to install the console.
I solved the problem by upgrading Visual C++ 2010 redist.
Had an old version of "vcredist" installed on my machine (version 10.0.30319). Did the upgrade of "vcredist" with the installation files from the VMM 2012 R2 media (\Prerequisites\VCRedist) and after a reboot i managed to install the console.
I solved the problem by upgrading Visual C++ 2010 redist.
Had an old version of "vcredist" installed on my machine (version 10.0.30319). Did the upgrade of "vcredist" with the installation files from the VMM 2012 R2 media (\Prerequisites\VCRedist) and after a reboot i managed to install the console.
That worked for me. I did a repair. The log files showed all prerequisites as ok before, but clearly that is not the case.
Thanks!
Has anyone found another solution then the repair? I have tried that, rebooted, and tried the installation again of VMM 2012 R2 and it just hangs "installing VMM" and never completes. I was having this same issue on both my laptop and desktop. The repair solution did work on my laptop, but not desktop.
Thanks!
I had the same problem on a Win8 and Win7 computer. I found out that Logitech SetPoint was the problem. After killing Setpoint in the task manager the setup completed without problems.
- Proposed as answer by Menk S Tuesday, January 28, 2014 2:02 PM
I had the same problem on a Win8 and Win7 computer. I found out that Logitech SetPoint was the problem. After killing Setpoint in the task manager the setup completed without problems.
- Proposed as answer by Menk S Tuesday, January 28, 2014 2:02 PM
I had the same problem on a Win8 and Win7 computer. I found out that Logitech SetPoint was the problem. After killing Setpoint in the task manager the setup completed without problems.
- Proposed as answer by Menk S Tuesday, January 28, 2014 2:02 PM
I had the same problem on a Win8 and Win7 computer. I found out that Logitech SetPoint was the problem. After killing Setpoint in the task manager the setup completed without problems.
- Proposed as answer by Menk S Tuesday, January 28, 2014 2:02 PM
I had the same problem on a Win8 and Win7 computer. I found out that Logitech SetPoint was the problem. After killing Setpoint in the task manager the setup completed without problems.
- Proposed as answer by Menk S Tuesday, January 28, 2014 2:02 PM
I had the same problem on a Win8 and Win7 computer. I found out that Logitech SetPoint was the problem. After killing Setpoint in the task manager the setup completed without problems.
- Proposed as answer by Menk S Tuesday, January 28, 2014 2:02 PM
EXACTLY the solution which worked for me as well. Logitech setpoint sucks!
Too bad I suffered for 2-3 days.....multiple attempts to install :-)
Thank you! I'd love to hear how you made that connection--my hat is off to you!
Todd
- Proposed as answer by MikeB97306 Tuesday, November 04, 2014 9:41 PM
- Proposed as answer by MikeB97306 Tuesday, November 04, 2014 9:41 PM
- Proposed as answer by MikeB97306 Tuesday, November 04, 2014 9:41 PM
- Proposed as answer by MikeB97306 Tuesday, November 04, 2014 9:41 PM
- Proposed as answer by MikeB97306 Tuesday, November 04, 2014 9:41 PM
- Proposed as answer by MikeB97306 Tuesday, November 04, 2014 9:41 PM
Stopping Setpoint allowed me to install on Windows 8.1 as well.
Thanks for the tip!
- Proposed as answer by MikeB97306 Tuesday, November 04, 2014 9:42 PM
- Proposed as answer by MikeB97306 Tuesday, November 04, 2014 9:42 PM
- Proposed as answer by MikeB97306 Tuesday, November 04, 2014 9:42 PM
- Proposed as answer by MikeB97306 Tuesday, November 04, 2014 9:42 PM
- Proposed as answer by MikeB97306 Tuesday, November 04, 2014 9:42 PM
- Proposed as answer by MikeB97306 Tuesday, November 04, 2014 9:42 PM
I can confirm it - Kill Logitech Setpoint and was able to finish installation.
Thanks
- Proposed as answer by MikeB97306 Tuesday, November 04, 2014 9:42 PM
I can confirm it - Kill Logitech Setpoint and was able to finish installation.
Thanks
- Proposed as answer by MikeB97306 Tuesday, November 04, 2014 9:42 PM
I can confirm it - Kill Logitech Setpoint and was able to finish installation.
Thanks
- Proposed as answer by MikeB97306 Tuesday, November 04, 2014 9:42 PM
I can confirm it - Kill Logitech Setpoint and was able to finish installation.
Thanks
- Proposed as answer by MikeB97306 Tuesday, November 04, 2014 9:42 PM
I can confirm it - Kill Logitech Setpoint and was able to finish installation.
Thanks
- Proposed as answer by MikeB97306 Tuesday, November 04, 2014 9:42 PM
I can confirm it - Kill Logitech Setpoint and was able to finish installation.
Thanks
- Proposed as answer by MikeB97306 Tuesday, November 04, 2014 9:42 PM
- Edited by MK8 Thursday, February 05, 2015 5:16 AM
- Edited by MK8 Thursday, February 05, 2015 5:16 AM
- Edited by MK8 Thursday, February 05, 2015 5:16 AM
- Edited by MK8 Thursday, February 05, 2015 5:16 AM
- Edited by MK8 Thursday, February 05, 2015 5:16 AM
- Edited by MK8 Thursday, February 05, 2015 5:16 AM
Windows 10 build 10240 here. With SetPoint, though killing it off didn't help.
Eventually, I found Skype for Business 2015 to be the cuplrit. As soon as I exited out of it, the installation continued and finished successfully.
P.S. If you're looking for the installation logs, they're in C:\ProgramData\VMMLogs
Windows 10 build 10240 here. With SetPoint, though killing it off didn't help.
Eventually, I found Skype for Business 2015 to be the cuplrit. As soon as I exited out of it, the installation continued and finished successfully.
P.S. If you're looking for the installation logs, they're in C:\ProgramData\VMMLogs
- Proposed as answer by AkiBerg 17 minutes ago
Windows 10 build 10240 here. With SetPoint, though killing it off didn't help.
Eventually, I found Skype for Business 2015 to be the cuplrit. As soon as I exited out of it, the installation continued and finished successfully.
P.S. If you're looking for the installation logs, they're in C:\ProgramData\VMMLogs
- Proposed as answer by AkiBerg Tuesday, August 25, 2015 6:56 AM
Windows 10 build 10240 here. With SetPoint, though killing it off didn't help.
Eventually, I found Skype for Business 2015 to be the cuplrit. As soon as I exited out of it, the installation continued and finished successfully.
P.S. If you're looking for the installation logs, they're in C:\ProgramData\VMMLogs
- Proposed as answer by AkiBerg Tuesday, August 25, 2015 6:56 AM
I can confirm this too. Had the same problem with my Windows 10 build 10240 also.
Exited Skype for Business 2016 and it finished installation just fine.
- Edited by AkiBerg 16 minutes ago
- Proposed as answer by Yuan WangMicrosoft employee a few seconds ago
I can confirm this too. Had the same problem with my Windows 10 build 10240 also.
Exited Skype for Business 2016 and it finished installation just fine.
- Edited by AkiBerg Tuesday, August 25, 2015 6:57 AM
- Proposed as answer by Yuan WangMicrosoft employee Tuesday, August 25, 2015 7:13 AM
I can confirm this too. Had the same problem with my Windows 10 build 10240 also.
Exited Skype for Business 2016 and it finished installation just fine.
- Edited by AkiBerg Tuesday, August 25, 2015 6:57 AM
- Proposed as answer by Yuan WangMicrosoft employee Tuesday, August 25, 2015 7:13 AM
- Killed Setpoint
- Killed Skype for Business
Still cannot install VMM. The last lines in the install log are
Action ended 11:06:50: RenameAddInsFolder. Return value 1.
Action start 11:06:50: PublishEnvironmentVariables.