none
WPF crashes on Focus()

    Question

  •  
    I am facing an issue with setting focus to TextBox controls in WPF. I don't have my stack trace at this time (writing this from home), but this is the problem in a nutshell:
     
    I have developed my desktop GUI using WPF. I use Focus() in many places to display a virtual keyboard, if the user clicks on a text box. The program has been running with no problem when executed directly or from the debugger.
     
     One of my requirements is that my program should always be running (re-start if a crash occurs, for example). Henceforth, I have written a .NET service that monitors processes in the background and fires up my program if it doesn't find it running. I use System.Diagnostics.Process.Start to re-run my exe. This is where my problem starts. When I bring up my program from within my service I get null reference errors for every Focus() call that I make.
     
    Can someone give me some insight on why this is happening and how to fix it? I am running out of solutions.

    Thanks

    Wednesday, August 06, 2008 1:18 PM

All replies

  • Here is the stack trace:

    UITraceSource Critical: 0 : 08/06/2008 16:19:56 :
     Type        : Exception
     Message     : Object reference not set to an instance of an object.
     Source      : PresentationFramework
     Target Site : Void OnGotFocus()

     Stack Trace :    at System.Windows.Documents.TextStore.OnGotFocus()
       at System.Windows.Documents.TextEditor.OnGotKeyboardFocus(Object sender, KeyboardFocusChangedEventArgs e)
       at System.Windows.Controls.Primitives.TextBoxBase.OnGotKeyboardFocus(KeyboardFocusChangedEventArgs e)
       at System.Windows.UIElement.OnGotKeyboardFocusThunk(Object sender, KeyboardFocusChangedEventArgs e)
       at System.Windows.Input.KeyboardFocusChangedEventArgs.InvokeEventHandler(Delegate genericHandler, Object genericTarget)
       at System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target)
       at System.Windows.RoutedEventHandlerInfo.InvokeHandler(Object target, RoutedEventArgs routedEventArgs)
       at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)
       at System.Windows.UIElement.RaiseEventImpl(RoutedEventArgs args)
       at System.Windows.UIElement.RaiseEvent(RoutedEventArgs args, Boolean trusted)
       at System.Windows.Input.InputManager.ProcessStagingArea()
       at System.Windows.Input.InputManager.ProcessInput(InputEventArgs input)
       at System.Windows.Input.KeyboardDevice.ChangeFocus(DependencyObject focus, Int32 timestamp)
       at System.Windows.Input.KeyboardDevice.TryChangeFocus(DependencyObject newFocus, IKeyboardInputProvider keyboardInputProvider, Boolean askOld, Boolean askNew, Boolean forceToNullIfFailed)
       at System.Windows.Input.KeyboardDevice.Focus(DependencyObject focus, Boolean askOld, Boolean askNew)
       at System.Windows.Input.KeyboardDevice.Focus(IInputElement element)
       at System.Windows.UIElement.Focus()
       at System.Windows.FrameworkElement.OnPreviewGotKeyboardFocus(Object sender, KeyboardFocusChangedEventArgs e)
       at System.Windows.Input.KeyboardFocusChangedEventArgs.InvokeEventHandler(Delegate genericHandler, Object genericTarget)
       at System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target)
       at System.Windows.RoutedEventHandlerInfo.InvokeHandler(Object target, RoutedEventArgs routedEventArgs)
       at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)
       at System.Windows.UIElement.RaiseEventImpl(RoutedEventArgs args)
       at System.Windows.UIElement.RaiseEvent(RoutedEventArgs args, Boolean trusted)
       at System.Windows.Input.InputManager.ProcessStagingArea()
       at System.Windows.Input.InputManager.ProcessInput(InputEventArgs input)
       at System.Windows.Input.KeyboardDevice.TryChangeFocus(DependencyObject newFocus, IKeyboardInputProvider keyboardInputProvider, Boolean askOld, Boolean askNew, Boolean forceToNullIfFailed)
       at System.Windows.Input.KeyboardDevice.Focus(DependencyObject focus, Boolean askOld, Boolean askNew)
       at System.Windows.Input.KeyboardDevice.Focus(IInputElement element)
       at System.Windows.Input.Keyboard.Focus(IInputElement element)
       at System.Windows.Interop.HwndKeyboardInputProvider.OnRootChanged(Visual oldRoot, Visual newRoot)
       at System.Windows.Interop.HwndSource.set_RootVisualInternal(Visual value)
       at System.Windows.Interop.HwndSource.set_RootVisual(Visual value)
       at System.Windows.Window.SetupInitialState(Double requestedTop, Double requestedLeft, Double requestedWidth, Double requestedHeight)
       at System.Windows.Window.CreateSourceWindowImpl()
       at System.Windows.Window.SafeCreateWindow()
       at System.Windows.Window.ShowHelper(Object booleanBox)
       at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Boolean isSingleParameter)
       at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Boolean isSingleParameter, Delegate catchHandler)

    Thursday, August 07, 2008 12:19 AM
  • I don't think we can figure out what happened without debugging your application with source code available.

    Or you could debug this issue yourself since most of .NET Framework source code is available by configuring source debugging:

    http://blogs.msdn.com/sburke/archive/2008/01/16/configuring-visual-studio-to-debug-net-framework-source-code.aspx

    Thanks


    Friday, August 08, 2008 8:36 AM
  • I am tyring to debug this, but I get a lot of files as blank. Every time I leave VS and come back I get more files turned blank. UIElement.cs, TextBox.cs, EventRoute.cs, FrameworkElement.cs... are all blank. I can't step through the code.
    Friday, August 08, 2008 7:28 PM
  • BTW, this only happens for a text box. Password box works just fine. So, focusing a textbox when the program is invoked from a .net service crashes.
    Friday, August 08, 2008 7:30 PM
  • Okay, then could you please send your test project to me at v-mazho at microsoft dot com for repro? I could help debuggin this issue.

    Marco
    Monday, August 11, 2008 5:48 AM
  • Has this issue been resolved?  I haven't seen any activity lately...

    Not sure if this is helpful or not, but I'm getting a simliar crash... but only on the deployment computer, not on the development machine.  It took me a while to isolate it, but I get the crash when using a storyboard that transform renders or opacity changes an item.  Soo.... my two instances of crashes occur when I change the opacity in the UIElement, or when I rendertransform in the UIElement.  I'm still researching, but I believe my crashes are linked to UIElement.

    Does your application run without crash if you don't call or use the UIElement?  I know you need to... but just curious to know if somehow they are related.

    Best of luck.  

    Greg
    Wednesday, October 22, 2008 5:56 PM
  • Hi Greg,

    No, I haven't solved this issue yet. It is not practical to send our code to Microsoft to be tested. We are so busy trying to release our product that we decided to fix this in the next release.  When things slow down a bit, I am thinking about creating a very simple sample and re-produce the error.

    Our issue is also in UIElement, I am sure. Ours happens only when the main executable is invoked from within a .net service. We don't get this error when we directly execute the main executable.

    Thursday, October 23, 2008 6:01 PM
  • We are having the exact same issue when using WPF UI in a custom action within an MSI installer. This issue is not reproducible when executing directly.

    We narrowed the issue down to Windows Server 2003 x86. This doesn't happen on 2003 x64 or Vista/Windows Server 2008 x86/x64.
    Thursday, October 23, 2008 7:10 PM
  •     internal class SafeTextBox : TextBox 
        { 
            protected override void OnGotKeyboardFocus(System.Windows.Input.KeyboardFocusChangedEventArgs e) 
            { 
                try 
                { 
                    base.OnGotKeyboardFocus(e); 
                } 
                catch (NullReferenceException) 
                { 
                    object editor = typeof(System.Windows.Controls.Primitives.TextBoxBase).InvokeMember("_textEditor", System.Reflection.BindingFlags.Instance | System.Reflection.BindingFlags.NonPublic | System.Reflection.BindingFlags.GetField, null, this, null); 
                    object selection = editor.GetType().InvokeMember("_selection", System.Reflection.BindingFlags.Instance | System.Reflection.BindingFlags.NonPublic | System.Reflection.BindingFlags.GetField, null, editor, null); 
                    Type iTextSelectionType = Type.GetType("System.Windows.Documents.ITextSelection, PresentationFramework, Version=3.0.0.0, Culture=neutralPublicKeyToken=31bf3856ad364e35"); 
                    iTextSelectionType.InvokeMember("RefreshCaret", System.Reflection.BindingFlags.Instance | System.Reflection.BindingFlags.Public | System.Reflection.BindingFlags.InvokeMethod, null, selection, null); 
                    iTextSelectionType.InvokeMember("UpdateCaretAndHighlight", System.Reflection.BindingFlags.Instance | System.Reflection.BindingFlags.Public | System.Reflection.BindingFlags.InvokeMethod, null, selection, null); 
                } 
            } 
        } 
    We did some further testing and found that this issue occurs on Windows 2003 x86 and x64 with all latest windows updates and .NET 3.5 SP1 installed. This is obviously a bug, so we developed a nasty hack to try to get by until MS fixes it.
    Friday, October 24, 2008 5:28 PM
  • Marco,

    I created a simple test app and was able to duplicate the same problem. I emailed you both the test app and a .net service that I created to duplicate this issue.

    Thanks.
    Thursday, October 30, 2008 8:31 PM
  • Hi Barry,

    I've redirected the repro project to the WPF/Text team for further research, as long as I get any information from them, I will post back.

    Thanks
    Monday, November 03, 2008 5:05 AM
  • OMG... My app just started having this behavior after over a year of development.
    Now all the textboxes in my app are generating this exception when I click on them!

    It looks like it is only on my PC so far.

    I tried adding a very simple plain old textbox with like this:
    <TextBox Width="100" />
    and I still get the exception when I click on it.

    I don't know what changed on my PC... but I have no choice but to start trying to figure it out.
    Any help would be greatly appreciated.

    Ion

    Monday, November 03, 2008 7:40 PM
  • This post suggests clearing the NT profile could help, as a workaround.

    http://www.vistax64.com/net-general/168516-wpf-richtextbox-control.html

    Is this a clue?

    I'm not sure how to really do that... but I'm looking into it.
    Ion
    Monday, November 03, 2008 7:42 PM
  • I worked with my IT guy to wipe my profile.
    I saved off my project before the wipe, and moved it back afterwards.
    This DID NOT solve the problem.

    I then created a new folder and did a fresh checkout of my code base from our repository.
    I built it all and it worked!!!

    So, at this point I'm guessing something got corrupted or screwy somewhere in my project/solution.

    I suppose I could move the corrupt project to a different PC and see if it still has the problem, to help verify that it is indeed corrupt.
    Not sure if I will bother.

    Ion
    Tuesday, November 04, 2008 3:26 PM
  • I just learned about a work around for this issue from a colleague.

    Try installing a laguage option. Under Regional and Language Options / Laguages / Details / Add

    I had English (United States) and I added English (Canada).
    Wednesday, November 19, 2008 4:07 PM
  • Don't know if this helps or not, but BarryOms' statement about this happening in a .NET service got me thinking about this:

    We're designing a data-driven WPF app that will be deployed to our end users. Since we don't want to give the users access to the database, our DBAs don't want to use SQL Server accounts, and we aren't going the SOA route, we recently implemented impersonation (using the advapi32.dll DLL Import), so a domain service account will be used instead. The impersonation starts in the Application_Startup after the user has been authenticated.

    Anyway, after implementing the impersonation, the aforementioned exception with the textbox focus occurs when I run the project. Comment out the line that begins the impersonation, and it works fine. This is also the case with the stand-alone app (not run in the VS2008 IDE).
    Monday, December 01, 2008 11:53 PM
  •  
    MEF2A said:
    Try installing a laguage option. Under Regional and Language Options / Laguages / Details / Add

    I had English (United States) and I added English (Canada).
    This did not work for me.
    Tuesday, January 13, 2009 8:56 PM
  • Marco Zhou said:
    I've redirected the repro project to the WPF/Text team for further research, as long as I get any information from them, I will post back.

    Any progress on this?

    My team has released software to a customer and it's been awkward.

    The only way to avoid the exceptions is to turn off their advanced text services.

    Ion

    Thursday, January 15, 2009 5:13 PM
  • This is a bug, and is fixed, and fix will be included in the .NET Framework 4.0


    Thanks

    Another Paradigm Shift
    http://shevaspace.blogspot.com
    Friday, January 16, 2009 10:26 AM
  • Marco Zhou said:

    This is a bug, and is fixed, and fix will be included in the .NET Framework 4.0


    Thanks


    Another Paradigm Shift
    http://shevaspace.blogspot.com

    I'm glad there will be a fix.

    Can you possibly elaborate on what the underlying problem is?  Is there any chance you have (or I can find) a better workaround in 3.0/3.5?  It might help me find a workaround if I better understood the problem.

    The application I have delivered to my customer has this problem and my only workaround is for them to turn off advanced text services.
    They will be installing the app on many PCs... so they will have to do this many times.  Maybe I can manipulate their registry in my installer... but even then, I'd love a better workaround.

    Thanks for any more help
    Ion

    Wednesday, January 21, 2009 3:55 PM
  • Has anyone come up with a work-around on this?  It's killin' me!

       at System.Windows.Documents.TextStore.OnGotFocus()
       at System.Windows.Documents.TextEditor.OnGotKeyboardFocus(Object sender, KeyboardFocusChangedEventArgs e)
       at System.Windows.Controls.Primitives.TextBoxBase.OnGotKeyboardFocus(KeyboardFocusChangedEventArgs e)
       at System.Windows.UIElement.OnGotKeyboardFocusThunk(Object sender, KeyboardFocusChangedEventArgs e)
       at System.Windows.Input.KeyboardFocusChangedEventArgs.InvokeEventHandler(Delegate genericHandler, Object genericTarget)
       at System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target)
       at System.Windows.RoutedEventHandlerInfo.InvokeHandler(Object target, RoutedEventArgs routedEventArgs)
       at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)
       at System.Windows.UIElement.RaiseEventImpl(RoutedEventArgs args)
       at System.Windows.UIElement.RaiseEvent(RoutedEventArgs args, Boolean trusted)
       at System.Windows.Input.InputManager.ProcessStagingArea()
       at System.Windows.Input.InputManager.ProcessInput(InputEventArgs input)
       at System.Windows.Input.KeyboardDevice.ChangeFocus(DependencyObject focus, Int32 timestamp)
       at System.Windows.Input.KeyboardDevice.TryChangeFocus(DependencyObject newFocus, IKeyboardInputProvider keyboardInputProvider, Boolean askOld, Boolean askNew, Boolean forceToNullIfFailed)
       at System.Windows.Input.KeyboardDevice.Focus(DependencyObject focus, Boolean askOld, Boolean askNew)
       at System.Windows.Input.KeyboardDevice.Focus(IInputElement element)
       at System.Windows.UIElement.Focus()
       at System.Windows.Documents.TextEditorMouse.MoveFocusToUiScope(TextEditor This)
       at System.Windows.Documents.TextEditorMouse.OnMouseDown(Object sender, MouseButtonEventArgs e)
       at System.Windows.Controls.Primitives.TextBoxBase.OnMouseDown(MouseButtonEventArgs e)
       at System.Windows.UIElement.OnMouseDownThunk(Object sender, MouseButtonEventArgs e)
       at System.Windows.Input.MouseButtonEventArgs.InvokeEventHandler(Delegate genericHandler, Object genericTarget)
       at System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target)
       at System.Windows.RoutedEventHandlerInfo.InvokeHandler(Object target, RoutedEventArgs routedEventArgs)
       at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)
       at System.Windows.UIElement.RaiseEventImpl(RoutedEventArgs args)
       at System.Windows.UIElement.RaiseEvent(RoutedEventArgs args, Boolean trusted)
       at System.Windows.Input.InputManager.ProcessStagingArea()
       at System.Windows.Input.InputManager.ProcessInput(InputEventArgs input)
       at System.Windows.Input.InputProviderSite.ReportInput(InputReport inputReport)
       at System.Windows.Interop.HwndMouseInputProvider.ReportInput(IntPtr hwnd, InputMode mode, Int32 timestamp, RawMouseActions actions, Int32 x, Int32 y, Int32 wheel)
       at System.Windows.Interop.HwndMouseInputProvider.FilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
       at System.Windows.Interop.HwndSource.InputFilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
       at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
       at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
       at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Boolean isSingleParameter)
       at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Boolean isSingleParameter, Delegate catchHandler)
       at System.Windows.Threading.Dispatcher.InvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Boolean isSingleParameter)
       at System.Windows.Threading.Dispatcher.Invoke(DispatcherPriority priority, Delegate method, Object arg)
       at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)
       at MS.Win32.UnsafeNativeMethods.DispatchMessage(MSG& msg)
       at System.Windows.Threading.Dispatcher.PushFrameImpl(DispatcherFrame frame)
       at System.Windows.Threading.Dispatcher.PushFrame(DispatcherFrame frame)
       at System.Windows.Threading.Dispatcher.Run()
       at System.Windows.Application.RunInternal(Window window)
       at System.Windows.Application.Run(Window window)
       at System.Windows.Application.Run()
       at Updater.Client.App.Main()

    Tuesday, January 27, 2009 7:54 PM
  • My only work around so far is to turn off advanced text services.

    Control Panel --> Regional and Language Options --> Languages Tab --> Details... Button --> Advanced Tab --> Check "Turn off advanced text services"

    Billy P, does this work for you?

    Ion

     

     

    Tuesday, January 27, 2009 9:10 PM
  • Nope, tried this and I am getting the same error.  Tried restarting the machine, rebuilding the app, reinstalling, etc and I am getting the same problem.  Thanks for the suggestion though!
    Tuesday, January 27, 2009 9:35 PM
  • If disabling advanced text services isn't working,  you could try using the nasty hack Sergey mentioned earlier in the thread as a last resort. I can't think of any other workaround.
    Tuesday, January 27, 2009 11:59 PM
  • Juhani Torkkola - MSFT said:

    If disabling advanced text services isn't working,  you could try using the nasty hack Sergey mentioned earlier in the thread as a last resort. I can't think of any other workaround.


    Do you know what the underlying problem is?

    In my case, this problem presented itself when I added impersonation to my app.

    Why does this cause a problem with textboxes and/or advanced text services?


    Wednesday, January 28, 2009 1:33 PM
  • From Sergey:

     internal class SafeTextBox : TextBox    
        {    
            protected override void OnGotKeyboardFocus(System.Windows.Input.KeyboardFocusChangedEventArgs e)    
            {    
                try    
                {    
                    base.OnGotKeyboardFocus(e);    
                }    
                catch (NullReferenceException)    
                {    
                    object editor = typeof(System.Windows.Controls.Primitives.TextBoxBase).InvokeMember("_textEditor", System.Reflection.BindingFlags.Instance | System.Reflection.BindingFlags.NonPublic | System.Reflection.BindingFlags.GetField, nullthisnull);    
                    object selection = editor.GetType().InvokeMember("_selection", System.Reflection.BindingFlags.Instance | System.Reflection.BindingFlags.NonPublic | System.Reflection.BindingFlags.GetField, null, editor, null);    
                    Type iTextSelectionType = Type.GetType("System.Windows.Documents.ITextSelection, PresentationFramework, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35");    
                    iTextSelectionType.InvokeMember("RefreshCaret", System.Reflection.BindingFlags.Instance | System.Reflection.BindingFlags.Public | System.Reflection.BindingFlags.InvokeMethod, null, selection, null);    
                    iTextSelectionType.InvokeMember("UpdateCaretAndHighlight", System.Reflection.BindingFlags.Instance | System.Reflection.BindingFlags.Public | System.Reflection.BindingFlags.InvokeMethod, null, selection, null);    
                }    
            }    
        }   
     

    I am not sure how exactly to make sure that I am using this correctly??  Help...

    Thanks!

    Wednesday, January 28, 2009 1:38 PM
  • Billy,

    You could create a new class file... say SafeTextBox.cs and paste the above code into it.

    Then replace all your TextBox with SafeTextBox (of course you'll need to specify the namespace that you define SafeTextBox in).

    SafeTextBox will now catch the exception that you're seeing when the textbox gets keyboard focus.

    Ion

     

    • Proposed as answer by Billy P Wednesday, January 28, 2009 2:55 PM
    Wednesday, January 28, 2009 2:28 PM
  • Yep, I figured that out right as you werre righting this.  I have found that this seems to fix the problem in every case I have encountered.   Thanks everyone!

    Wednesday, January 28, 2009 2:55 PM
  • ionymous said:

    Juhani Torkkola - MSFT said:

    If disabling advanced text services isn't working,  you could try using the nasty hack Sergey mentioned earlier in the thread as a last resort. I can't think of any other workaround.


    Do you know what the underlying problem is?

    In my case, this problem presented itself when I added impersonation to my app.

    Why does this cause a problem with textboxes and/or advanced text services?




    The problem has to do with the internal implementation that deals with communication with the IME. When a TextBox gets focused, the IME is notified of the event. Under certain circumstances (e.g. when an application is started by a service), the IME may go into an unusual state. Disabling advanced text services may mitigate this since we can detect that this type of IME is not available and this codepath will never be reached.
    Wednesday, January 28, 2009 6:05 PM
  • Thanks for the explanation Juhani.

     Ion

    Thursday, January 29, 2009 3:59 PM
  • Ionymous and I have been working on the same application.  I'm now looking into a way to disable advanced text services as part of the application startup to temporarily work around this problem.  Here's what I've found so far:

    Step 1: Kill ctfmon.exe

    Step 2: Run the following registry edits

    Windows Registry Editor Version 5.00
    ;This will remove the advanced tech services.
    [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run] "ctfmon.exe"=-
    [HKEY_CURRENT_USER\Software\Microsoft\CTF] "Disable Thread Input Manager"=dword:00000001
    [HKEY_CURRENT_USER\Software\Microsoft\CTF\MSUTB] "ShowDeskBand"=dword:00000000


    I've been testing this locally, and it seems to work to prevent the issue, but I've noticed that this doesn't perfectly replicate what happens when you check "Turn Off Advanced Text Services".  Checking that box closes the language bar, but the steps above will not.  That makes me wonder if other settings are being changed as well.  Can anyone tell me what else I need to do to replicate this setting?
    Thursday, February 26, 2009 7:35 PM
  • I don't mean to beat a dead horse, but I would just like to mention that my company has also found this bug to be an extremely unpleasant issue in the field. The fact that there is no hotfix or other software update is extremely disappointing. We're hoping that 4.0 causes less frustration.

    Has anyone learned anything new about this bug since January?
    Wednesday, June 17, 2009 6:41 PM
  • Not I.  I'd like to download the 4.0 beta sometime soon to confirm that it is fixed.
    Wednesday, June 17, 2009 6:53 PM
  • No fix for us either. We are just as frustrated. We have been so busy with other requirements that for now, we decided to freeze this requirement until Microsoft has an answer.
    Wednesday, June 17, 2009 8:40 PM
  • any updates on this issue? I tried the fix in the code, however this only solves the focus issue, but the same problem happens with right click, and probably other events as well.
    the registry fix also doesnt help, for starters some of the users of my app need these services, and I am running for a service, so i would need to disable it for the service, not the user.
    Wednesday, December 23, 2009 7:38 AM
  • Any update on this issue? Am also facing the same issue. I am using Windows 7 with .net framework 4.0 installed. I have also started a new thread with more details regarding this issue, http://social.msdn.microsoft.com/Forums/en-US/wpf/thread/6df62512-4a1a-44e4-b6e9-bcbc613b801d

     Please provide me with solution(any fix or windows update).

    Thanks.

    Monday, May 13, 2013 8:54 AM