Отладка jit как выключить

Отладка jit как выключить

A day may come when you want to turn off the Debug dialog that appears when a .NET program has an unhandled exception.

Option 1: Registry key from Enabling JIT Debugging

• If value = 0, prompt the user by means of a message box. The choices are:
  • Continue. This results in a stack dump and process termination.
  • Attach a debugger. In this case, the runtime spawns the debugger listed in the DbgManagedDebugger registry key. If none, control is returned, and the process is terminated.

  Option 2: If you want to disable the JIT debug dialog, but still want an error dialog:

  Visual Studio.NET|Tools|Options|Debugging|Just-In-Time and deselect «Common Language Runtime» and now you’ll get an OK/Cancel dialog instead of the select a Debugger Dialog. Note: The registry entry from Option 1 above will need to be 0 for the dialog to show up.

  Thanks to Eric Deslauriers of Corillian QA for these tips!

  About Scott

  Scott Hanselman is a former professor, former Chief Architect in finance, now speaker, consultant, father, diabetic, and Microsoft employee. He is a failed stand-up comic, a cornrower, and a book author.

  Hosting By
  

  How to stop "Just In Time Debugging" messages blocking a buildserver

  Our buildserver (TeamCity, much recommended), runs our a whole bunch of testsuites on our finished c++ program.

  Once in a whole, a test causes our program to crash, often bringing up a VisualStudio dialog offering me to JustInTime debug the crash. The dialog stops the buildserver from progressing. Instead of the build marked as failed, it just hangs. I’ve turned off the Just In Time debugging feature in VisualStudio, but when it’s turned off, you still get a message «Couldn’t JustinTime Debug this, you can turn it on in the options».

  Does anybody know of a way to ensure that any unhandled exception in a program does not result in any modal dialog?

  6 Answers 6

  • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AeDebug\Debugger

  • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\DbgManagedDebugger

  • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\AeDebug\Debugger

  • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\DbgManagedDebugger

  Delete (or rename) c:\windows\system32\vsjitdebugger.exe.

  I tried deleting the registry keys, and I tried unchecking all the boxes in the Visual Studio options, but neither worked.

  To be clear, my situation wasn’t a C++ one. I was using Micro Focus COBOL for Visual Studio 2010, and by using the registry and VS options suggestions I managed to get rid of the «Want to debug?» dialog, but that resulted in a different dialog to hold up my automated process:

  Scott Hanselman

  How to turn off/disable the .NET JIT Debugging Dialog

  A day may come when you want to turn off the Debug dialog that appears when a .NET program has an unhandled exception.

  Option 1: Registry key from Enabling JIT Debugging

  • If value = 0, prompt the user by means of a message box. The choices are:
    • Continue. This results in a stack dump and process termination.
    • Attach a debugger. In this case, the runtime spawns the debugger listed in the DbgManagedDebugger registry key. If none, control is returned, and the process is terminated.

    Option 2: If you want to disable the JIT debug dialog, but still want an error dialog:

    Visual Studio.NET|Tools|Options|Debugging|Just-In-Time and deselect «Common Language Runtime» and now you’ll get an OK/Cancel dialog instead of the select a Debugger Dialog. Note: The registry entry from Option 1 above will need to be 0 for the dialog to show up.

    Thanks to Eric Deslauriers of Corillian QA for these tips!

    About Scott

    Scott Hanselman is a former professor, former Chief Architect in finance, now speaker, consultant, father, diabetic, and Microsoft employee. He is a failed stand-up comic, a cornrower, and a book author.

    Hosting By
    

    Отладка jit как выключить

    This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

    

    • ProfileText
    • Sign in

    Answered by:

    Question

    I installed Visual Studio, and had no problems. Except one. The Just-In-Time debugger. It seems to come up all the time now, and it has broken Winamp AND Cakewalk SONAR 5. I tried disabling it in Visual Studio’s options, but that doesn’t stop the pop up and the subsequent shut down of the program (which did NOT happen before). Any ideas?

    Answers

    Although anything is possible I suppose, it seems unlikely that installing the Just-In-Time debugger caused these applications to start crashing. But I guess if you really want to know if that is the problem, you can try removing HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AeDebug\Debugger.

    If it was me, I would take a look at where the app was crashing, and send a bug report to the product support team that own’s your crashing app.

    All replies

    Although anything is possible I suppose, it seems unlikely that installing the Just-In-Time debugger caused these applications to start crashing. But I guess if you really want to know if that is the problem, you can try removing HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AeDebug\Debugger.

    If it was me, I would take a look at where the app was crashing, and send a bug report to the product support team that own’s your crashing app.

    Open Start>Control Panels>Internet Options: Advanced and activate (check box)

    * Disable Script Debugging (Internet Explorer)
    * Disable Script Debuggung (Other)

    • Proposed as answer by Halima S Microsoft Support Monday, January 3, 2011 3:28 PM

    Try to set this key value to 1.

    • Proposed as answer by Voja Belgrade Thursday, January 29, 2015 9:51 AM

    I know this is my first post, but i want to apologize for bumping an old topic.

    But i wanted to state that what she says does the trick.

    Thank you very much

    Open the registry (use regedit, Click Start, Run, Regedit).

    And set it to 0.

    • Proposed as answer by CondoomDokter Monday, October 17, 2011 5:18 PM

    Thank you Bill gates, I download Visual studio, and after using it a few times 8 of my programmes won’t run because of your piece of ***. The simple answer would of course be to uninstall it, so why is it a piece of ***?
    I’ll enlighten you, I have uninstalled it. As I am typing this, I am finding components from your *** still on my computer, still crashing various applications.

    I have done the HKey value thingys, googled for answers and I keep getting the same reply from microsoft, it’s unlikely this is to do with visual studio. Here’;s a small pointer, unlikely my foot. Why is it the errors only happened AFTER I installed your programme?

    I am sick of Microsoft and Bill gates, he was on an interview recently, where he was showing off his latest media center programme. Guess what people, surprise surprise, it wouldn’t work.

    And before you suggest Vista I am a gamer, so it’s no games or games and errors. Great option that!

    Since I bought my computer, I have had nothing but errors with it. Why is it I get similar errors to my mum’s windows 95? If you can’t advance a PC in over ten years, you’re either doing something wrong, or not doing it at all.

    So now we’ve established it is your software screwing my programmes up, and we’ve established I can’t uninstall, even manually or from the control panel, I would like an answer that works and doesn’t have a disclaimer saying, this will probably screw your comp up, it’s already screwed thanks to microsoft.

    Seems to me that everyone involved with Msoft is thick. I can’t make a system, but given the money Gates has, I could make a much better system than your ***. Why would it be better?
    Here’s the main answer;
    IT WOULD WORK.

    So thank you for taking my money microsoft, thank you for not helping me thus far, and thank you for basically screwing up my computer with your own programmes. I wonder when we can expect an apology for the apes working on your systems?

    *silent laughter.*
    I didn’t think so somehow.
    Sorry, I take the last bit back, I don’t want to insult any apes that may be reading this.

    I just went through the exact same thing, so don’t listen to the reply post by the "Visual Studio Debugger Dev".

    I followed a solution a few posts down and it worked perfectly.

    Open Start>Control Panels>Internet Options: Advanced and activate (check box)

    * Disable Script Debugging (Internet Explorer)
    * Disable Script Debuggung (Other)

    BTW — when a user disables a program from Windows, a portion of that program should no longer exist (as JIT does). It’s ridiculous we have to deal with this at all. Hope this helped.

    Already tried it mate, didn’t work.

    Thanks for trying.

    I saw this book once, it’s a series, internet for dummies, photoshop for dummies, and then I saw microsoft for dummies. It’s more a case of microsoft BY dummies, not for them.

    Did your apps crash a lot before?

    • Proposed as answer by seeking Wednesday, October 21, 2009 3:08 PM

    I am having the exact same problem. I removed the visual studio, but still getting errors from JITdebugger.

    Some people suggest to change something in internet explorer, but the problem doesn’t occur in internet explorer (maybe it does, but i am not using it) so this solution doesn’t work for me.

    I found this actually resolved my issue with JIT:

    3. Type cmd (and click ok)

    4. Type drwtsn32 -i (and press enter)

    See the following for further details on the actual issue with JIT:

    • Proposed as answer by dips87 Friday, September 4, 2009 1:55 PM

    dont do anything with Registry

    simply follow the steps

    1. Open IIS Server (Internet Information Server)

    2. Open website Node and select the site in which you’re getting error of Debugger of Just In time

    3. Go on Tab of Home Directory

    4. Click on Configuration button (You will get another form)

    5. Click on Dubugging Tab.

    6. Uncheck "Enabled ASP Server-side scripting degug.

    I have remove the this way, try it

    This did the trick for me

    That got rid of the JIT debugger and put dr watson back in control, now all the suddon my apps don’t crash anymore hmmmmmmmm. Could it be that JIT was causing the crashes. YES.

    i have a solution that worked for me

    open the registry editor, and navigate to this folder:

    then delete the entire folder

    however this won’t neccessarily (and probably definately) re-enable third party applications, but it will stop JITDebugging from running.
    I Live Life One Video Game At A Time. Play It Like You Mean It.

    My problems started when I downloaded MS SilverLight. Now when I try to update my Zune software, it tells me that Windows Installer isn’t working. When I try to re-download Windows Installer, I keep getting the JIT Debugger error message. I tried un-installing SliverLight, but the problem persists.

    So, to suffice, the only three programs that are affected are ALL Microsoft programs that will NOT work together.

    Great planning strategy, Bill

    Changing the settings in IIS is a good approach — but if you are like me and you run a web app within IIS, you might want script debugging turned on (so the browser will display the error message) but you DON’T want the JIT Debugger to run (because this makes everything else stop — including IIS).

    So here is what I did — (after trying numerous other solutions, including editing the registry)

    I found these instruction on another site (but they did not work for me so I came up with my own solution, below):

    *** what I found elsewhere —
    You should be able to disable the JIT Debugger in Internet Explorer, via:
    Windows Control Panel > Internet Options > Advanced tab:

    Checkmark both "disable script debugging (IE/other)" options
    Uncheck "display a notification about every script error"

    Or go to: Control Panel > Admin Tools > Services
    and disable Visual Studio JIT Debugger, if listed.

    Look for a service that points to one of the following executables:

    C:\WINDOWS\system32\vsjitdebugger.exe
    C:\Program Files\Common Files\Microsoft Shared\VS7Debug\vs7jit.exe

    ********* THIS IS WHAT WORKED FOR ME:
    I went here C:\WINDOWS\system32\vsjitdebugger.exe and renamed vsjitdebugger.exe to vsjitdebuggerBACK.exe (*this worked for me)
    . but just in case.
    Then I went here C:\Program Files\Common Files\Microsoft Shared\VS7Debug and I also renamed the folder VS7Debug (actually VS7DEBUG) to VSDebugback (VS7DEBUGback)

    And just as an FYI — it seems that this probelm occured for me because after uninstalling Visual Studio 2005 I did not uninstall SQL Server 2005. see this article — http://support.microsoft.com/default.aspx/kb/923827

    • Proposed as answer by ron_99 Thursday, October 30, 2008 8:17 PM
    • Edited by ron_99 Thursday, October 30, 2008 8:18 PM

    I got it resloved by making JITDebug, 0 under HKEY_CURRENT_USER\Software\Microsoft\Windows Script\Settings

    • Proposed as answer by Pradeep Nulu Friday, November 2, 2012 9:35 AM

    I would think that’s the case. but I am sure my boyfriend’s computer was crashed by this aswell. He’s the one who uses visual basic..and he’s computer kept crashing down. boot it up. then dies down. it was a virus that he caught. I believe visual basic made it vulnerable for viruses or something.

    My computer had not had a problem for 5 years. when his computer crash a month ago, he installed visual on mine labtop. and now my labtop is not working property. I can not log on internet period. The just in time debugger keeps popping up in the middle of my work and killing my programe.

    I not a genius in computer, but I know Visual basic needs to fix this problem. It’s so shittie!

    I got it resloved by making JITDebug, 0 under HKEY_CURRENT_USER\Software\Microsoft\Windows Script\Settings

    can you put in more details.

    my problem is I can’t get anywher.e.that ____ just keeps popping up. seems like it’s in internet explorer. I can not go to that problem period. anything involve the net.

    • Proposed as answer by seeking Wednesday, October 21, 2009 3:06 PM
    • Proposed as answer by seeking Wednesday, October 21, 2009 3:06 PM

    I had Microsoft Expression installed which included Visual Studio and Silverlight. I use Windows XP. Expression continued to crash my computer and after a few weeks of technical support not being able to solve the problem for me, they let me return the software. However, I am still getting this error:
    An unhandled win32 exception occurred in svchost.exe [1480]. Just in time debugging this exeption failed with the following error: No installed debugger has Just in Time Debugging enabled. In Visual Studio Just in Time Debugging can be enabled from Tools/options/Debugging/Just in Time

    Well I don’t have Visual Studio anymore, that was uninstalled. Clean.

    I do have a key in the registry where it was referred to above and it is currently set to zero. Is this the problem?

    Help me fix this because my computer crashes when I play computer games, when I use Photoshop, when I use Nero Photo Viewer, etc. etc. and I’m really really sick of this.

    • Proposed as answer by Hexaae Sunday, December 24, 2017 9:56 AM
    • Unproposed as answer by Hexaae Sunday, December 24, 2017 9:56 AM

    I’m not sure if this is the right place to ask this question, but I’m having issues, so here goes.

    My problem started when I tried to sign in to Windows Live Messenger, it wouldn’t work. In my search to fix that, I realized that Internet Explorer would not work either, it kept displaying the error message, "Unable to show the webpage." Then randomly, my Mozilla Firefox started to crash. I thought all of this was due to a virus. Next I was unable to sign into Yahoo Messenger. Then I started getting the Just-In-Time Debugger error. It asked me if I wanted to use Microsoft Script Editor to fix the problem. I clicked yes and it seemed to be working well, until I received a new error, "Unable to open registry key ‘HKEY_LOCAL_MACHINE\SOFTWARE\DELL\HWDiag\PCDpath’ for reading." I am now at a loss as to how to fix things. Mozilla continues to crash (it crashed once as I tried to sign in to type this out) and nothing internet related seems to work very well. Can anyone help me? Please?!

    Now I cannot even get windows update to work without that just in time debugger error coming up. . That never happened before. I have tried setting the value to 1 as suggested above. That did not work. It already was set to zero. I uninstalled Visual Studio a long time ago with help from a microsoft tech. I did not know I’d have the just in time issue because it didn’t happen again for a while and now I’d have to pay hundreds of dollars for help.

    This is just getting to be impossible.

    Please help, someone? Anyone.

    i have had simillar problums with debug but not with the debug with the actually program and debug has not interefeared with any of my programs yet considering i only had the program now for about 2 hours i was able to copy this repeated error to clip board i hope it helps the development team

    System.InvalidOperationException was unhandled
    Message=Collection was modified; enumeration operation may not execute.
    Source=mscorlib
    StackTrace:
    at System.ThrowHelper.ThrowInvalidOperationException(ExceptionResource resource)
    at System.Collections.Generic.List`1.Enumerator.MoveNextRare()
    at System.Collections.Generic.List`1.Enumerator.MoveNext()
    at Microsoft.VisualBasic.PowerPacks.ShapeCollection.Dispose(Boolean disposing)
    at Microsoft.VisualBasic.PowerPacks.ShapeContainer.Dispose(Boolean disposing)
    at System.ComponentModel.Component.Dispose()
    at System.Windows.Forms.Control.Dispose(Boolean disposing)
    at System.Windows.Forms.Form.Dispose(Boolean disposing)
    at WindowsApplication1.Form1.Dispose(Boolean disposing) in C:\Documents and Settings\Brian\My Documents\Visual Studio 2010\Projects\WindowsApplication1\WindowsApplication1\Form1.Designer.vb:line 13
    at System.ComponentModel.Component.Dispose()
    at System.Windows.Forms.Form.WmClose(Message& m)
    at System.Windows.Forms.Form.WndProc(Message& m)
    at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
    at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
    at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
    at System.Windows.Forms.UnsafeNativeMethods.CallWindowProc(IntPtr wndProc, IntPtr hWnd, Int32 msg, IntPtr wParam, IntPtr lParam)
    at System.Windows.Forms.NativeWindow.DefWndProc(Message& m)
    at System.Windows.Forms.Form.DefWndProc(Message& m)
    at System.Windows.Forms.Control.WndProc(Message& m)
    at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
    at System.Windows.Forms.ContainerControl.WndProc(Message& m)
    at System.Windows.Forms.Form.WmSysCommand(Message& m)
    at System.Windows.Forms.Form.WndProc(Message& m)
    at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
    at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
    at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
    at System.Windows.Forms.UnsafeNativeMethods.CallWindowProc(IntPtr wndProc, IntPtr hWnd, Int32 msg, IntPtr wParam, IntPtr lParam)
    at System.Windows.Forms.NativeWindow.DefWndProc(Message& m)
    at System.Windows.Forms.Form.DefWndProc(Message& m)
    at System.Windows.Forms.Control.WndProc(Message& m)
    at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
    at System.Windows.Forms.ContainerControl.WndProc(Message& m)
    at System.Windows.Forms.Form.WmNcButtonDown(Message& m)
    at System.Windows.Forms.Form.WndProc(Message& m)
    at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
    at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
    at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
    at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
    at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr dwComponentID, Int32 reason, Int32 pvLoopData)
    at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
    at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
    at System.Windows.Forms.Application.Run(ApplicationContext context)
    at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.OnRun()
    at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.DoApplicationModel()
    at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.Run(String[] commandLine)
    at WindowsApplication1.My.MyApplication.Main(String[] Args) in 17d14f5c-a337-4978-8281-53493378c1071.vb:line 81
    at System.AppDomain._nExecuteAssembly(RuntimeAssembly assembly, String[] args)
    at System.AppDomain.ExecuteAssembly(String assemblyFile, Evidence assemblySecurity, String[] args)
    at Microsoft.VisualStudio.HostingProcess.HostProc.RunUsersAssembly()
    at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
    at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean ignoreSyncCtx)
    at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
    at System.Threading.ThreadHelper.ThreadStart()
    InnerException:

    i have had simillar problums with debug but not with the debug with the actually program and debug has not interefeared with any of my programs yet considering i only had the program now for about 2 hours i was able to copy this repeated error to clip board i hope it helps the development team

    System.InvalidOperationException was unhandled
    Message=Collection was modified; enumeration operation may not execute.
    Source=mscorlib
    StackTrace:
    at System.ThrowHelper.ThrowInvalidOperationException(ExceptionResource resource)
    at System.Collections.Generic.List`1.Enumerator.MoveNextRare()
    at System.Collections.Generic.List`1.Enumerator.MoveNext()
    at Microsoft.VisualBasic.PowerPacks.ShapeCollection.Dispose(Boolean disposing)
    at Microsoft.VisualBasic.PowerPacks.ShapeContainer.Dispose(Boolean disposing)
    at System.ComponentModel.Component.Dispose()
    at System.Windows.Forms.Control.Dispose(Boolean disposing)
    at System.Windows.Forms.Form.Dispose(Boolean disposing)
    at WindowsApplication1.Form1.Dispose(Boolean disposing) in C:\Documents and Settings\Brian\My Documents\Visual Studio 2010\Projects\WindowsApplication1\WindowsApplication1\Form1.Designer.vb:line 13
    at System.ComponentModel.Component.Dispose()
    at System.Windows.Forms.Form.WmClose(Message& m)
    at System.Windows.Forms.Form.WndProc(Message& m)
    at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
    at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
    at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
    at System.Windows.Forms.UnsafeNativeMethods.CallWindowProc(IntPtr wndProc, IntPtr hWnd, Int32 msg, IntPtr wParam, IntPtr lParam)
    at System.Windows.Forms.NativeWindow.DefWndProc(Message& m)
    at System.Windows.Forms.Form.DefWndProc(Message& m)
    at System.Windows.Forms.Control.WndProc(Message& m)
    at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
    at System.Windows.Forms.ContainerControl.WndProc(Message& m)
    at System.Windows.Forms.Form.WmSysCommand(Message& m)
    at System.Windows.Forms.Form.WndProc(Message& m)
    at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
    at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
    at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
    at System.Windows.Forms.UnsafeNativeMethods.CallWindowProc(IntPtr wndProc, IntPtr hWnd, Int32 msg, IntPtr wParam, IntPtr lParam)
    at System.Windows.Forms.NativeWindow.DefWndProc(Message& m)
    at System.Windows.Forms.Form.DefWndProc(Message& m)
    at System.Windows.Forms.Control.WndProc(Message& m)
    at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
    at System.Windows.Forms.ContainerControl.WndProc(Message& m)
    at System.Windows.Forms.Form.WmNcButtonDown(Message& m)
    at System.Windows.Forms.Form.WndProc(Message& m)
    at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
    at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
    at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
    at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
    at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr dwComponentID, Int32 reason, Int32 pvLoopData)
    at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
    at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
    at System.Windows.Forms.Application.Run(ApplicationContext context)
    at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.OnRun()
    at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.DoApplicationModel()
    at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.Run(String[] commandLine)
    at WindowsApplication1.My.MyApplication.Main(String[] Args) in 17d14f5c-a337-4978-8281-53493378c1071.vb:line 81
    at System.AppDomain._nExecuteAssembly(RuntimeAssembly assembly, String[] args)
    at System.AppDomain.ExecuteAssembly(String assemblyFile, Evidence assemblySecurity, String[] args)
    at Microsoft.VisualStudio.HostingProcess.HostProc.RunUsersAssembly()
    at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
    at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean ignoreSyncCtx)
    at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
    at System.Threading.ThreadHelper.ThreadStart()
    InnerException:

    Never mind dont ues the power pack

    are crawlling with bugs still
    dont use or incounter this reocurring error
    User beware

    Читать:

    Чем заменить active directory