Visual Studio 2012/MSFT Dev Tools not working under Windows 8.1?

Discussion in 'Windows 8' started by ShotSkydiver, Jul 2, 2013.

  1. ShotSkydiver

    ShotSkydiver MDL Novice

    Aug 31, 2012
    5
    1
    0
    I looked through the apps that are incompatible with Windows 8.1 thread and didn't find a single mention of this, nor does a Google search turn up anything. I'm running a fresh brand new install of Windows 8.1 x64, and when I run the installer for either Visual Studio 2012 Pro or Windows Phone SDK, the installer gets to the splash screen and immediately crashes. I've tried running the installer in compatibility mode, I've made sure literally every optional feature under "Turn Windows features on or off" is turned on, I've made sure I'm up-to-date with the 8.1 updates, my Windows 8.1 is activated with the key from Microsoft, but no matter what, the installers just crash immediately. How did Microsoft break compatibility with its own developer tools?

    I know, I know, it's a beta, and obviously if I can't get Visual Studio to work I'll go back to 8, but I'd really love to keep running 8.1 and use Visual Studio, has anyone else encountered this problem and possibly found a way to fix it?
     
  2. CODYQX4

    CODYQX4 MDL Developer

    Sep 4, 2009
    4,803
    45,234
    150
    Try VS 2013 BETA, I used and compiled MTK with it. Also opened my VS2012 projects without any problems.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. sevenacids

    sevenacids MDL Addicted

    Aug 17, 2012
    628
    186
    30
    If you get it to install/run: It is also required to install Update 3 to Visual Studio 2012 on Windows 8.1 Preview - I think I read this on the Visual Studio blog.
     
  4. AmuletOfNight

    AmuletOfNight MDL Novice

    Apr 10, 2010
    12
    1
    0
    VS2012 works for me, and I was running update 2. I installed update 3 after i launched it:eek:
     
  5. ShotSkydiver

    ShotSkydiver MDL Novice

    Aug 31, 2012
    5
    1
    0
    #5 ShotSkydiver, Jul 3, 2013
    Last edited by a moderator: Apr 20, 2017
    (OP)
    Goddammit

    uEnhTSw.png ‚Äč

    Looking at the Event Viewer log for the crash isn't at all helpful either...

    Code:
    Faulting application name: vs_professional.exe, version: 12.0.20617.1, time stamp: 0x518c17d0
    Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
    Exception code: 0xc0000005
    Fault offset: 0x00000000
    Faulting process id: 0x%9
    Faulting application start time: 0x%10
    Faulting application path: %11
    Faulting module path: %12
    Report Id: %13
    Faulting package full name: %14
    
    
    
    EventData
    vs_professional.exe
    12.0.20617.1
    518c17d0
    unknown
    0.0.0.0
    00000000
    c0000005
    00000000
     
  6. Superfly

    Superfly MDL Expert

    Jan 12, 2010
    1,133
    542
    60
    AFAIK that's an access violation error - may not have anything to do with VS - rather user permissions? just taking a shot in the dark...;)
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  7. ShotSkydiver

    ShotSkydiver MDL Novice

    Aug 31, 2012
    5
    1
    0
    I hope that's it... right now I'm going to try installing VS onto another computer running Windows 8.1, we'll see if it works. If it does for some reason work, I'm at a loss as to why it won't work on my computer, as they're both fresh installs. :confused:
     
  8. Superfly

    Superfly MDL Expert

    Jan 12, 2010
    1,133
    542
    60
    Cool!.. update installs causes dll-hell for some reason... corrupt files pushing memory allocation errors etc - the alternative was to scannow to check them..:eek:
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  9. ShotSkydiver

    ShotSkydiver MDL Novice

    Aug 31, 2012
    5
    1
    0
    Ugh.... of course the setup runs perfectly on my other computer. I guess my only option is a re-re-install of 8.1....
     
  10. Superfly

    Superfly MDL Expert

    Jan 12, 2010
    1,133
    542
    60
    Yup that's the cleanest solution - last resort is u you may have to do memtest for hardware
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  11. Josh Cell

    Josh Cell MDL Developer

    Jan 8, 2011
    3,519
    7,106
    120
    #11 Josh Cell, Sep 22, 2013
    Last edited: Sep 22, 2013
    Both VS 2012 and VS 2013 RC was crashing around my machine.

    Reading some articles, looks like a video driver problem, but I already have updated it to the latest inside the Windows 8.1 RTM.

    After checking for some updates, a new video driver appears. I have updated then solved the problem (Even I don't like to download driver updates by the Windows Update)...
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  12. ShotSkydiver

    ShotSkydiver MDL Novice

    Aug 31, 2012
    5
    1
    0
    I'm bumping this because I ended up finding a solution, the issue was the Intel Iris graphics drivers under Windows 8.1. In my case, it was on my MacBook Air 2013. After researching into it and trying a lot of different Intel drivers, I finally found one that works perfectly with VS under Windows 8.1 RTM. It's not listed on Intel's site, but the driver is "Intel Iris/HD Graphics Driver 15.33.2.64.3282 Beta for Windows 8.1 64 bit". Here's the link to download it:

    http(dot)(dot)//downloadmirror.intel.com/23194/a08/Win64_15332b.zip
     
  13. mydigitaldesktop

    mydigitaldesktop MDL Junior Member

    Sep 18, 2013
    55
    24
    0
    Intel seems to have top position for wonky 8.1 drivers and for some reason a lot of people see their upgrades to 8.1 as some sort of minor service pack that doesn't need a comprehensive driver check....