Visual Studio 2015 setup crashes with the following error after the splash screen is shown: “Setup detected an issue during the operation. Please click below to check for a solution and help us to improve the setup experience.”
After reviewing the Setup failure log dd_vs_****_201*******.log, I found the below failure stack:
[22C4:0820][2016-08-10T14:11:05]e000: MUX: ERROR: The type initializer for ‘System.Windows.Media.FontFamily’ threw an exception.
[22C4:0820][2016-08-10T14:11:05]e000: MUX: Stack: at System.Windows.Media.Typeface..ctor(FontFamily fontFamily, FontStyle style, FontWeight weight, FontStretch stretch)
at MS.Internal.Text.DynamicPropertyReader.GetTypeface(DependencyObject element)
at MS.Internal.Text.TextProperties.InitCommon(DependencyObject target)
at MS.Internal.Text.TextProperties..ctor(FrameworkElement target, Boolean isTypographyDefaultValue)
at System.Windows.Controls.TextBlock.GetLineProperties()
at System.Windows.Controls.TextBlock.EnsureTextBlockCache()
at System.Windows.Controls.TextBlock.MeasureOverride(Size constraint)
at System.Windows.FrameworkElement.MeasureCore(Size availableSize)
at System.Windows.UIElement.Measure(Size availableSize)
<InnerException>
[22C4:0820][2016-08-10T14:11:05]e000: MUX: Exception: Info: InnerException: Info:
[22C4:0820][2016-08-10T14:11:05]e000: MUX: ERROR: Specified argument was out of the range of valid values.
[22C4:0820][2016-08-10T14:11:05]e000: MUX: Stack: at MS.Internal.FontCache.CheckedPointer.op_Addition(CheckedPointer rhs, Int32 offset)
at MS.Internal.FontCache.HashTable.GetElementInfo(Int32*& elementOffsetPtr, ElementHeader*& elementHeader, CheckedPointer& elementDataPtr)
at MS.Internal.FontCache.HashTable.Lookup(IFontCacheElement e, Boolean add)
at MS.Internal.FontCache.CacheManager.Lookup(IFontCacheElement e)
at System.Windows.Media.FontFamily.PreCreateDefaultFamilyCollection()
at System.Windows.Media.FontFamily..cctor()
VS Setup is a WPF application and WPF apps are susceptible to broken fonts. A similar issue is described at https://support.microsoft.com/en-in/kb/2978135
In this case, the issue was resolved by stopping the “Windows Presentation Foundation Font Cache 3.0.0.0” Windows service.
