none
Visual Studio 2017 crashes on startup (Professional and Enterprise, build 15.5.2) RRS feed

  • Question

  • VS 2017 crashes on startup. I've tried:

    • Updating to latest build 15.5.2
    • Running VS as admin
    • Deleting the .vs folder.
    • Repairing VS installation 
    • devenv.exe /ResetSettings
    • devenv.exe /ResetUserData
    • devenv.exe /SafeMode
    • devenv.exe /ResetSkipPkgs
    • Checking if font MT Extra had a long path rather than file name in registry HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts
    • Cleared out %TEMP% folder
    • Renaming/deleting %LOCALAPPDATA%\Microsoft\VisualStudio\15.xxx
    • Uninstalling GitExtensions 
    • Uninstalling VS Professional, installing VS Enterprise 
    • Uninstalling again, this time searching for every folder named VisualStudio and deleting every string match of VisualStudio in registry (regedit), and installing again 
    • Formatting my C drive. Worked as soon as I installed it, but as soon as I started adding additional programs (Steam, Notepad++, Office, etc) it starting crashing again. 

    None of the above has fixed the issue.
    I am running win 10 enterprise,  Intel Core i7-5960X CPU @ 3GHz,  32GB RAM,  64 bit OS

    From event viewer:

    Fault bucket 2110112439321335099, type 1 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: devenv.exe P2: 15.0.27130.2010
     P3: 5a31e4ea P4: KERNELBASE.dll P5: 10.0.16299.15 P6: 2cd1ce3d P7: c000041d P8: 001008b2 P9:  P10: 
    Faulting application name: devenv.exe, version: 15.0.27130.2010, time stamp: 0x5a31e4ea Faulting module name: KERNELBASE.dll, version: 10.0.16299.15,
     time stamp: 0x2cd1ce3d Exception code: 0xc000041d Fault offset: 0x001008b2 Faulting process id: 0x38e8 Faulting application start time: 0x01d37a1f74f9b587 Faulting application path: C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\IDE\devenv.exe
     Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll Report Id: ddf05ace-23e1-45a6-bb84-fc0bba5bcdd8 Faulting package full name:  Faulting package-relative application ID: 
    Fault bucket 1293705288626429016, type 5
    Event Name: CLR20r3 Response: Not available
    Cab Id: 0 Problem signature: 
    P1: devenv.exe P2: 15.0.27130.2010 P3: 5a31e4ea
    P4: mscorlib P5: 4.7.2600.0 
    P6: 59d789f1 P7: 5f9e P8: 4 
    P9: System.ArgumentException P10: 
     
    Application: devenv.exe
    Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception.
    Exception Info: System.ArgumentException    at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32, IntPtr)
       at System.Runtime.InteropServices.Marshal.ThrowExceptionForHR(Int32, IntPtr)
       at MS.Internal.Text.TextInterface.Native.Util.ConvertHresultToException(Int32)
       at MS.Internal.Text.TextInterface.Font.DisplayMetrics(Single, Single)
       at MS.Internal.FontFace.PhysicalFontFamily.MS.Internal.FontFace.IFontFamily.LineSpacing(Double, Double, Double, System.Windows.Media.TextFormattingMode)
       at MS.Internal.TextFormatting.SimpleTextLine..ctor(MS.Internal.TextFormatting.FormatSettings, Int32, Int32, System.Collections.ArrayList, Int32 ByRef, Int32 ByRef, Double)
       at MS.Internal.TextFormatting.SimpleTextLine.Create(MS.Internal.TextFormatting.FormatSettings, Int32, Int32, Double)
       at MS.Internal.TextFormatting.TextFormatterImp.FormatLineInternal(System.Windows.Media.TextFormatting.TextSource, Int32, Int32, Double, System.Windows.Media.TextFormatting.TextParagraphProperties, System.Windows.Media.TextFormatting.TextLineBreak,
     System.Windows.Media.TextFormatting.TextRunCache)    at MS.Internal.TextFormatting.TextFormatterImp.FormatLine(System.Windows.Media.TextFormatting.TextSource, Int32, Double, System.Windows.Media.TextFormatting.TextParagraphProperties,
     System.Windows.Media.TextFormatting.TextLineBreak, System.Windows.Media.TextFormatting.TextRunCache)
       at MS.Internal.Text.Line.Format(Int32, Double, System.Windows.Media.TextFormatting.TextParagraphProperties, System.Windows.Media.TextFormatting.TextLineBreak, System.Windows.Media.TextFormatting.TextRunCache, Boolean)
       at System.Windows.Controls.TextBlock.MeasureOverride(System.Windows.Size)
       at System.Windows.FrameworkElement.MeasureCore(System.Windows.Size)
       at System.Windows.UIElement.Measure(System.Windows.Size)
       at System.Windows.Controls.DockPanel.MeasureOverride(System.Windows.Size)
       at System.Windows.FrameworkElement.MeasureCore(System.Windows.Size)
       at System.Windows.UIElement.Measure(System.Windows.Size)
       at System.Windows.Controls.Border.MeasureOverride(System.Windows.Size)
       at System.Windows.FrameworkElement.MeasureCore(System.Windows.Size)
       at System.Windows.UIElement.Measure(System.Windows.Size)
       at System.Windows.Controls.Grid.MeasureCell(Int32, Boolean)
       at System.Windows.Controls.Grid.MeasureCellsGroup(Int32, System.Windows.Size, Boolean, Boolean, Boolean ByRef)
       at System.Windows.Controls.Grid.MeasureCellsGroup(Int32, System.Windows.Size, Boolean, Boolean)
       at System.Windows.Controls.Grid.MeasureOverride(System.Windows.Size)
       at System.Windows.FrameworkElement.MeasureCore(System.Windows.Size)
       at System.Windows.UIElement.Measure(System.Windows.Size)
       at Microsoft.VisualStudio.PlatformUI.Shell.Controls.WindowContentPresenter.MeasureOverride(System.Windows.Size)
       at System.Windows.FrameworkElement.MeasureCore(System.Windows.Size)
       at System.Windows.UIElement.Measure(System.Windows.Size)
       at System.Windows.Window.MeasureOverrideHelper(System.Windows.Size)
       at System.Windows.Window.MeasureOverride(System.Windows.Size)
       at System.Windows.FrameworkElement.MeasureCore(System.Windows.Size)
       at System.Windows.UIElement.Measure(System.Windows.Size)
       at System.Windows.Interop.HwndSource.Process_WM_SIZE(System.Windows.UIElement, IntPtr, MS.Internal.Interop.WindowMessage, IntPtr, IntPtr)
       at System.Windows.Interop.HwndSource.LayoutFilterMessage(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
       at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
       at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
       at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
       at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
       at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
       at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
    
     

     

    Thursday, December 21, 2017 6:25 AM

Answers

  • UPDATE 1/11/18
    Issue solved! The problem was with the installation of WindowBlinds 10.65 (048 - Windows 10 Edition) - 64 bit OS, and using a theme that applies style system wide fonts.
    The fix is to disable this feature by checking "Do not apply any style system wide fonts" by clicking Style on the left hand side menu of WindowBlinds (1), clicking Fonts (2), then checking the box described above.

    Friday, January 12, 2018 3:17 AM

All replies

  • Hi,

    Welcome to MSDN forum.

    Please have a look at the thread:

    Try temporarily renaming the MLCFG32.CPL just to see if it stops the error.

    Go here: C:\Program Files\Microsoft Office\Office14

    In that folder right-click the MLCFG32.CPL and rename the MLCFG32.CPL to MLCFG32.old.

    >>Formatting my C drive. Worked as soon as I installed it, but as soon as I started adding additional programs (Steam, Notepad++, Office, etc) it starting crashing again. 

    Try to Start your PC in safe mode in Windows 10, Safe mode starts Windows in a basic state, using a limited set of files and drivers. It can help you troubleshoot problems on your PC.

    Best regards,

    Joyce


    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Friday, December 22, 2017 2:47 AM
  • (UPDATE 12/31/17: This was NOT it, it started breaking again, after renaming the file.)

    This was it. Thank you, Joyce. 

    Wondering if renaming MLCFG32.CPL breaks something else, though.

    I tried the following:

    Repaired the Microsoft Office installation. This action breaks Visual Studio again because it places the original MLCFG32.CPL file back in its original location, and deletes the renamed MLCFG32.CPL.old one. I then renamed MLCFG32.CPL to MLCFG32.CPL.old again, and Visual Studio opens successfully once more.

    Although I renamed the file, I can still open Word, Powerpoint, etc. without issue.

    In closing, do we need MLCFG32.CPL at all for Office to work?

    UPDATE 12/31/17 This is not a permament fix.VS 2017 starts crashing after executing a not yet determined process. I have to repeatedly rename the file MLCFG32.CPL to .old and back, and then VS starts normally. Then the next day, it would start breaking again.


    Saturday, December 23, 2017 9:14 PM
  • Hi,

    The MLCFG32.CPL is the Office Mail Control Panel applet. Right click on it and select open with control panel, you will get Mail setup.

    In my side, MLCFG32.CPL has no effect on visual studio, It seems there is something wrong with your office.

    Best regards,

    Joyce


    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Tuesday, December 26, 2017 7:22 AM
  • Hi,

    >>UPDATE 12/31/17 This is not a permament fix.VS 2017 starts crashing after executing a not yet determined process. I have to repeatedly rename the file MLCFG32.CPL to .old and back, and then VS starts normally. Then the next day, it would start breaking again.

    • Try to reinstall Office.
    • Do not rename MLCFG32.CPL and  Start your PC in safe mode in Windows 10, Safe mode starts Windows in a basic state, using a limited set of files and drivers, then check it if the issue persists. If VS works well, there may be something you installed affecting visual studio.

    Best regards,

    Joyce


    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Tuesday, January 2, 2018 8:47 AM
    • Try to reinstall Office.
    • Do not rename MLCFG32.CPL and  Start your PC in safe mode in Windows 10, Safe mode starts Windows in a basic state, using a limited set of files and drivers, then check it if the issue persists. If VS works well, there may be something you installed affecting visual studio.

    Did this. Started in Safe Mode. Visual Studio opened. Now I have no other clues. What other logs do you need to see what program could be conflicting with visual studio? Do you need my logs or some sort of dump? Let me know if I can upload these logs somwhere where you can see them. Thanks!

    Wednesday, January 3, 2018 7:27 AM
  • Hi,

    Please reproduce the problem and run the command: devenv /log in the evaluated command prompt. And upload the file (%APPDATA%\Microsoft\VisualStudio\Version\ActivityLog.xml) to https://onedrive.live.com/ and share the link here.

    Best regards,

    Joyce


    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Wednesday, January 3, 2018 9:54 AM
  • Here's the link:

    https://1drv.ms/u/s!ArIx11IF4gAogqZ0RLBWyy5N7z01Rw

    Thursday, January 4, 2018 4:04 AM
  • Hi,

    I can't find useful information from the log. You can have a look at the link which talk about use safemode to diagnose pc problem

     http://sea.pcmag.com/microsoft-windows-10/16065/news/how-to-use-safe-mode-to-diagnose-a-pc-problem

    Meanwhile, I will invite other senior members to help you troubleshoot this.

    Best regards,

    Joyce


    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Friday, January 5, 2018 10:04 AM
  • UPDATE 1/11/18
    Issue solved! The problem was with the installation of WindowBlinds 10.65 (048 - Windows 10 Edition) - 64 bit OS, and using a theme that applies style system wide fonts.
    The fix is to disable this feature by checking "Do not apply any style system wide fonts" by clicking Style on the left hand side menu of WindowBlinds (1), clicking Fonts (2), then checking the box described above.

    Friday, January 12, 2018 3:17 AM
  • UPDATE 1/11/18
    Issue solved! The problem was with the installation of WindowBlinds 10.65 (048 - Windows 10 Edition) - 64 bit OS, and using a theme that applies style system wide fonts.
    The fix is to disable this feature by checking "Do not apply any style system wide fonts" by clicking Style on the left hand side menu of WindowBlinds (1), clicking Fonts (2), then checking the box described above.

    Same problem. Solution works!!!  Thank you!
    I also recommend  set "Total Exclusion for skinning" for devenv.exe:    WindowBlinds 10 - Settings - Per Application. Add.. 

    VS 2017 will load faster.


    Ing. Luis Danilo Ruiz Tórrez

    Thursday, January 18, 2018 7:15 PM
  • Thank You. Searched far and wide for solution.  Don't know how you zeroed in

    on WindowsBlinds.  But it solved the problem.

    Thursday, January 18, 2018 10:17 PM
  • Excellent Tip. Improved startup immeasurably

    Thank you. 

    Thursday, January 18, 2018 10:18 PM