Application crash after Windows Update KB951847 dutch

Wizard for WPF Forum

Posted 10 years ago by Kris Goossens - Remmicom
Version: 4.5.0485
Platform: Windows Forms Controls
Environment: Windows Vista (32-bit)
Running the Live demo, using the wizard, the application crashes with Windows Vista Business (No problem with Windows Vista Ultimate)

This started hapening after the installation of KB951847 : Microsoft .NET Framework 3.5 Service Pack 1 en .NET Framework 3.5 Family Update x86

If we remove part of the windows update : KB949249 everything is fine again.

We are using Windows Vista in Dutch language. The Windows Vista Ultimate has more languages build in by default.

When the wizard crashes we get this error :
"De aangevraagde waarde LINKS is niet gevonden." which means "The requested value LINKS is not found."

I supose there's some value in the dutch language pack in the .NET Framework 3.5 SP1 missing and the wizzard doesn't like this.


bij System.Enum.Parse(Type enumType, String value, Boolean ignoreCase)

bij System.Windows.Input.KeyConverter.GetKey(String keyToken, CultureInfo culture)

bij System.Windows.Input.KeyConverter.ConvertFrom(ITypeDescriptorContext context, CultureInfo culture, Object source)

bij System.Windows.Input.KeyGestureConverter.ConvertFrom(ITypeDescriptorContext context, CultureInfo culture, Object source)

bij System.ComponentModel.TypeConverter.ConvertFromInvariantString(String text)

bij System.Windows.Input.KeyGesture.CreateFromResourceStrings(String keyGestureToken, String keyDisplayString)

bij System.Windows.Input.KeyGesture.AddGesturesFromResourceStrings(String keyGestures, String displayStrings, InputGestureCollection gestures)

bij System.Windows.Input.NavigationCommands.LoadDefaultGestureFromResource(Byte commandId)

bij System.Windows.Input.RoutedCommand.GetInputGestures()

bij System.Windows.Input.RoutedCommand.get_InputGesturesInternal()

bij System.Windows.Input.CommandBindingCollection.FindMatch(Object targetElement, InputEventArgs inputEventArgs)

bij System.Windows.Input.CommandManager.TranslateInput(IInputElement targetElement, InputEventArgs inputEventArgs)

bij System.Windows.UIElement.OnMouseDownThunk(Object sender, MouseButtonEventArgs e)

bij System.Windows.Input.MouseButtonEventArgs.InvokeEventHandler(Delegate genericHandler, Object genericTarget)

bij System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target)

bij System.Windows.RoutedEventHandlerInfo.InvokeHandler(Object target, RoutedEventArgs routedEventArgs)

bij System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)

bij System.Windows.UIElement.RaiseEventImpl(DependencyObject sender, RoutedEventArgs args)

bij System.Windows.UIElement.RaiseEvent(RoutedEventArgs args, Boolean trusted)

bij System.Windows.Input.InputManager.ProcessStagingArea()

bij System.Windows.Input.InputManager.ProcessInput(InputEventArgs input)

bij System.Windows.Input.InputProviderSite.ReportInput(InputReport inputReport)

bij System.Windows.Interop.HwndMouseInputProvider.ReportInput(IntPtr hwnd, InputMode mode, Int32 timestamp, RawMouseActions actions, Int32 x, Int32 y, Int32 wheel)

bij System.Windows.Interop.HwndMouseInputProvider.FilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)

bij System.Windows.Interop.HwndSource.InputFilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)

bij MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)

bij MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)

bij System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Boolean isSingleParameter)

bij System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Boolean isSingleParameter, Delegate catchHandler)

bij System.Windows.Threading.Dispatcher.WrappedInvoke(Delegate callback, Object args, Boolean isSingleParameter, Delegate catchHandler)

bij System.Windows.Threading.Dispatcher.InvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Boolean isSingleParameter)

bij System.Windows.Threading.Dispatcher.Invoke(DispatcherPriority priority, Delegate method, Object arg)

bij MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)

bij MS.Win32.UnsafeNativeMethods.DispatchMessage(MSG& msg)

bij System.Windows.Threading.Dispatcher.PushFrameImpl(DispatcherFrame frame)

bij System.Windows.Threading.Dispatcher.PushFrame(DispatcherFrame frame)

bij System.Windows.Threading.Dispatcher.Run()

bij System.Windows.Application.RunDispatcher(Object ignore)

bij System.Windows.Application.RunInternal(Window window)

bij System.Windows.Application.Run(Window window)

bij System.Windows.Application.Run()

bij ActiproSoftware.Windows.SampleBrowser.WindowsApp.Main()

Comments (2)

Posted 10 years ago by Actipro Software Support - Cleveland, OH, USA
Hi Kris,

We haven't had any reports of an issue. However based on your stack trace, our controls aren't even mentioned so I doubt there is anything in our code that is related to this.

The only thing is that we make use of the Microsoft-created NavigationCommands and this is failing in Microsoft's code related to loading input gestures for NavigationCommands. However many other Microsoft framework controls use NavigationCommands as well so the exception would likely happen when any of those controls were used to based on what you describe.

This is all we do in our Wizard code related to NavigationCommands, and this is common usage:
this.CommandBindings.Add(new CommandBinding(NavigationCommands.BrowseBack, new ExecutedRoutedEventHandler(navigationCommandsBrowseBack_Executed), new CanExecuteRoutedEventHandler(navigationCommandsBrowseBack_CanExecute)));
this.CommandBindings.Add(new CommandBinding(NavigationCommands.BrowseForward, new ExecutedRoutedEventHandler(navigationCommandsBrowseForward_Executed), new CanExecuteRoutedEventHandler(navigationCommandsBrowseForward_CanExecute)));
You could probably duplicate this same issue with a custom control you make that has those lines.

Therefore my recommendation would be to duplicate it with a custom control and provide Microsoft with details on this issue since it is something they would need to fix.

Actipro Software Support

Posted 10 years ago by Kris Goossens - Remmicom
We can simulate the crash without using the Actipro Wizzard.

We'll pass this to Microsoft.

Kris Goossens
The latest build of this product (v2018.1 build 0675) was released 1 month ago, which was after the last post in this thread.

Add Comment

Please log in to a validated account to post comments.