none
VB.NET windows application crashes on Windows 10 64 bit

    Question

  • Hi,

    I am working on a project which was developed in VB6 and it’s working fine. 

    Recently, I have upgraded a VB6 application to VB.NET using Visual studio 2015. The application used .NET framework 4.5 and developed for x86 CPU. It runs fine on a Windows 7/2008 server 64 bit machine but when I try to run on Windows 10 64 Bit Any help earliest would be much appreciated?machine it crashes and doesn’t run. I have googled the error details but not of much help. 

    Any help would be much appreciated?

    Regards,

    -Arun 

    Following are the details in Report.wer file from event viewer. 

    Version=1
    EventType=CLR20r3
    EventTime=131346182260729055
    ReportType=2
    Consent=1
    UploadTime=131346182261920166
    ReportIdentifier=65decac8-0e9b-11e7-a3e2-54ee7527a46f
    IntegratorReportIdentifier=1c0dd171-0cf3-47c1-b8c7-675f2afc6c4c
    WOW64=1
    NsAppName=QTV.exe
    Response.BucketId=558975c316e2b029f0d7f9a76d0ba2e6
    Response.BucketTable=5
    Response.LegacyBucketId=129396106144
    Response.type=4
    Sig[0].Name=Problem Signature 01
    Sig[0].Value=QTV.exe
    Sig[1].Name=Problem Signature 02
    Sig[1].Value=1.0.6290.18472
    Sig[2].Name=Problem Signature 03
    Sig[2].Value=58d1bb29
    Sig[3].Name=Problem Signature 04
    Sig[3].Value=System.Windows.Forms
    Sig[4].Name=Problem Signature 05
    Sig[4].Value=4.6.1038.0
    Sig[5].Name=Problem Signature 06
    Sig[5].Value=5615c2ae
    Sig[6].Name=Problem Signature 07
    Sig[6].Value=64b
    Sig[7].Name=Problem Signature 08
    Sig[7].Value=36
    Sig[8].Name=Problem Signature 09
    Sig[8].Value=System.InvalidOperationException
    DynamicSig[1].Name=OS Version
    DynamicSig[1].Value=10.0.10586.2.0.0.256.48
    DynamicSig[2].Name=Locale ID
    DynamicSig[2].Value=3081
    DynamicSig[22].Name=Additional Information 1
    DynamicSig[22].Value=bdcb
    DynamicSig[23].Name=Additional Information 2
    DynamicSig[23].Value=bdcb33e65a9843796b7ec31cc25bda3b
    DynamicSig[24].Name=Additional Information 3
    DynamicSig[24].Value=b892
    DynamicSig[25].Name=Additional Information 4
    DynamicSig[25].Value=b892054ec8a92265ec8b48f9a5510fdf
    UI[2]=C:\Users\SESA189956\Desktop\bin\QTV.exe
    UI[3]=QTV has stopped working
    UI[4]=Windows can check online for a solution to the problem.
    UI[5]=Check online for a solution and close the program
    UI[6]=Check online for a solution later and close the program
    UI[7]=Close the program
    LoadedModule[0]=C:\Users\SESA189956\Desktop\bin\QTV.exe
    LoadedModule[1]=C:\windows\SYSTEM32\ntdll.dll
    LoadedModule[2]=C:\windows\SYSTEM32\MSCOREE.DLL
    LoadedModule[3]=C:\windows\SYSTEM32\KERNEL32.dll
    LoadedModule[4]=C:\windows\SYSTEM32\KERNELBASE.dll
    LoadedModule[5]=C:\windows\SYSTEM32\ADVAPI32.dll
    LoadedModule[6]=C:\windows\SYSTEM32\msvcrt.dll
    LoadedModule[7]=C:\windows\SYSTEM32\sechost.dll
    LoadedModule[8]=C:\windows\SYSTEM32\RPCRT4.dll
    LoadedModule[9]=C:\windows\SYSTEM32\SspiCli.dll
    LoadedModule[10]=C:\windows\SYSTEM32\CRYPTBASE.dll
    LoadedModule[11]=C:\windows\SYSTEM32\bcryptPrimitives.dll
    LoadedModule[12]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\mscoreei.dll
    LoadedModule[13]=C:\windows\SYSTEM32\SHLWAPI.dll
    LoadedModule[14]=C:\windows\SYSTEM32\combase.dll
    LoadedModule[15]=C:\windows\SYSTEM32\GDI32.dll
    LoadedModule[16]=C:\windows\SYSTEM32\USER32.dll
    LoadedModule[17]=C:\windows\SYSTEM32\IMM32.DLL
    LoadedModule[18]=C:\windows\SYSTEM32\kernel.appcore.dll
    LoadedModule[19]=C:\windows\SYSTEM32\VERSION.dll
    LoadedModule[20]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
    LoadedModule[21]=C:\windows\SYSTEM32\MSVCR120_CLR0400.dll
    LoadedModule[22]=C:\windows\assembly\NativeImages_v4.0.30319_32\mscorlib\62fac835fdecb6ecf9f38ec819f1b016\mscorlib.ni.dll
    LoadedModule[23]=C:\windows\SYSTEM32\ole32.dll
    LoadedModule[24]=C:\windows\system32\uxtheme.dll
    LoadedModule[25]=C:\windows\assembly\NativeImages_v4.0.30319_32\System\3aae8931d29e60c127b9995c9aef68d1\System.ni.dll
    LoadedModule[26]=C:\windows\assembly\NativeImages_v4.0.30319_32\System.Drawing\9b9f639f8d82ea6878d3a27d3ae5042c\System.Drawing.ni.dll
    LoadedModule[27]=C:\windows\assembly\NativeImages_v4.0.30319_32\System.Windows.Forms\5b3e2a31b12f1b4d5750b0868fdb961e\System.Windows.Forms.ni.dll
    LoadedModule[28]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\clrjit.dll
    LoadedModule[29]=C:\windows\SYSTEM32\OLEAUT32.dll
    LoadedModule[30]=C:\windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.10586.0_none_811bc0006c44242b\comctl32.dll
    LoadedModule[31]=C:\windows\system32\dwmapi.dll
    LoadedModule[32]=C:\windows\assembly\NativeImages_v4.0.30319_32\System.Core\e3ec016f20b794382f55552820781dcd\System.Core.ni.dll
    LoadedModule[33]=C:\windows\assembly\NativeImages_v4.0.30319_32\System.Configuration\89f5a6a5fe12ae6b80de339d192f4844\System.Configuration.ni.dll
    LoadedModule[34]=C:\windows\assembly\NativeImages_v4.0.30319_32\System.Xml\62ee38e32af1fa90396c5e47bb0b3de6\System.Xml.ni.dll
    LoadedModule[35]=C:\windows\SYSTEM32\MSCTF.dll
    LoadedModule[36]=C:\windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.10586.633_none_1b6fde65144db32a\gdiplus.dll
    LoadedModule[37]=C:\windows\SYSTEM32\DWrite.dll
    LoadedModule[38]=C:\windows\SYSTEM32\clbcatq.dll
    LoadedModule[39]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\diasymreader.dll
    State[0].Key=Transport.DoneStage1
    State[0].Value=1
    FriendlyEventName=Stopped working
    ConsentKey=CLR20r3
    AppName=QTV
    AppPath=C:\Users\SESA189956\Desktop\bin\QTV.exe
    NsPartner=windows
    NsGroup=windows8
    ApplicationIdentity=1EA7386D33053A93AC632972C2A101DF


    Wednesday, March 22, 2017 1:29 AM

Answers

  • Thanks Reed and Acamar for replying. Appreciate your suggestions. What I found was there were some ActiveX controls which were missing and causing issues on Windows 10 but don't know how it worked on Windows 7 without these ActiveX. I included those ActiveX in my deployment package and installed the new setup on Windows 10 and it fixed my issue.

    Thanks,

    -Arun Sahani

     
    • Marked as answer by Arun Sahani Thursday, March 23, 2017 12:11 AM
    Thursday, March 23, 2017 12:11 AM

All replies

  • You'll need to debug the program on a system which can reproduce the error.

    You are encountering a System.InvalidOperationException and there are a number of thing which could cause this.  In theory you could look through your code for anything which could cause an InvalidOperationException and narrow down the potential problem lines.  But your best bet is to install VS on a problem machine, open a copy of your project, and run it.

    Keep in mind that you can use a virtual machine to test the scenario if needed.  If you don't already have access to one, you can sign up for an Azure account and use your initial credits to do the testing.


    Reed Kimble - "When you do things right, people won't be sure you've done anything at all"

    Wednesday, March 22, 2017 3:43 AM
    Moderator
  • The application used .NET framework 4.5 and developed for x86 CPU. It runs fine on a Windows 7/2008 server 64 bit machine but when I try to run on Windows 10 64 Bit

    It is not just the OS that is different - the machine configuration, including drive lettering, folder layout, network connectins etc - has also changed. You need to identify the point in the program execution where the application is failing, and examine that region of your code for anything that is dependant on a specific detail of the application environment.

    Wednesday, March 22, 2017 3:58 AM
  • Thanks Reed and Acamar for replying. Appreciate your suggestions. What I found was there were some ActiveX controls which were missing and causing issues on Windows 10 but don't know how it worked on Windows 7 without these ActiveX. I included those ActiveX in my deployment package and installed the new setup on Windows 10 and it fixed my issue.

    Thanks,

    -Arun Sahani

     
    • Marked as answer by Arun Sahani Thursday, March 23, 2017 12:11 AM
    Thursday, March 23, 2017 12:11 AM