Jump to content
|Topic||Stats||Last action by|
|Germanwings/Lufthansa A320 down in France||
|March 2015 Desktops||
|The question of life and gods answered||
|Sony confirms massive official PlayStation TV price cut||
Posted 17 January 2014 - 03:03
Posted 17 January 2014 - 03:51
Seems like an oddball way to go about it, but the installer might do a simple filename check against a list of known "troublesome" setup files.
When I clicked the installer, it said "Program compatibility mode is on, turn it off and try again". However, it was not turned on. I did some research and I had to rename the exe file to vs_professional.exe. Ummm...WHAT? Why would the name of the installer cause this issue?
It's fine. You just need to build a time machine and hop back... No guarantee that it works, but did you try resetting the system time and date to get around it?
Next: I get about 80% through the install and it says "Unable to locate package source. So again, I did some research and there was a support article saying "Visual Studio 2012 might not install after October 2013". Again....WHAT?
Posted 17 January 2014 - 04:15