none
[W10][RS1] After updating Windows 10 1607, my application fails to load dll. RRS feed

  • Question

  • Hi. i'm Jack.

    Upgrading from Window 10 1511 to 1607 is experiencing problems.

    Very well done in the existing version of 1511.

    However, it is always upgraded to Windows 10 1607 versions.

    I checked on the other PC that were installed on Windows 10 1511 version.

    And i checked with the PC already installed in Windows 10 1607 version.

    The results work normally in the 1511 version, and in 1607 is dll load fails.

    Below is a message at the time of load failure.

    Unable to load DLL 'DiagnosticRapi.dll'; The specified module could not be found. (Exception from HRESULT. 0x8007007E).

    See the end of this message for details on invoking 
    just-in-time (JIT) debugging instead of this dialog box.

    ************** Exception Text **************
    System.DllNotFoundException: Unable to load DLL 'DiagnosticRapi.dll': The specified module could not be found. (Exception from HRESULT: 0x8007007E)
       at DiagnosticRapiNet.CDiagnosticRapi.DiagnosticDataWrite_Serial_W10(IntPtr szCOM, IntPtr szSN, IntPtr szPN, IntPtr szWlanMac, IntPtr szBTMac, IntPtr szSpecialN, IntPtr szLaserN, IntPtr szIMEI)
       at DiagnosticRapiNet.CDiagnosticRapi.DataWriteSerial_W10(IntPtr szCOM, IntPtr szSN, IntPtr szPN, IntPtr szWlanMac, IntPtr szBTMac, IntPtr szSpecialN, IntPtr szLaserN, IntPtr szIMEI)
       at DiagnosticRapiNet.Form1.btn_WriteData_Click(Object sender, EventArgs e)
       at System.Windows.Forms.Control.OnClick(EventArgs e)
       at System.Windows.Forms.Button.OnClick(EventArgs e)
       at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
       at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
       at System.Windows.Forms.Control.WndProc(Message& m)
       at System.Windows.Forms.ButtonBase.WndProc(Message& m)
       at System.Windows.Forms.Button.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.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


    ************** Loaded Assemblies **************
    mscorlib
        Assembly Version: 2.0.0.0
        Win32 Version: 2.0.50727.8745 (WinRel.050727-8700)
        CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
    ----------------------------------------
    DiagnosticRapiNet
        Assembly Version: 1.0.0.0
        Win32 Version: 1.0.0.0
        CodeBase: file:///C:/Users/Jackh/Desktop/POPTest/양진이/DiagnosticRapiNet.exe
    ----------------------------------------
    System.Windows.Forms
        Assembly Version: 2.0.0.0
        Win32 Version: 2.0.50727.8745 (WinRel.050727-8700)
        CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
    ----------------------------------------
    System
        Assembly Version: 2.0.0.0
        Win32 Version: 2.0.50727.8750 (QFE.050727-8700)
        CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
    ----------------------------------------
    System.Drawing
        Assembly Version: 2.0.0.0
        Win32 Version: 2.0.50727.8745 (WinRel.050727-8700)
        CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
    ----------------------------------------

    ************** JIT Debugging **************
    To enable just-in-time (JIT) debugging, the .config file for this
    application or computer (machine.config) must have the
    jitDebugging value set in the system.windows.forms section.
    The application must also be compiled with debugging
    enabled.

    For example:

    <configuration>
        <system.windows.forms jitDebugging="true" />
    </configuration>

    When JIT debugging is enabled, any unhandled exception
    will be sent to the JIT debugger registered on the computer
    rather than be handled by this dialog box.

    DiagnosticRapi.dll is made by me.

    Both the dll and the application were build in VS2008.

    In addition, we attepted to resolve the problem and tried it on VS2015.

    But the result was the same.

    Windows 10 prefers automatic updating.

    And 10 days later, can not go back to the original.

    Please let me know how to use my application and my Dll on Windows 10 1607.

    Jack.

    • Moved by David_FF Thursday, February 9, 2017 9:28 AM related to Windows Forms
    Wednesday, February 8, 2017 6:04 AM

All replies

  • Hi,

    How do you deployment your Windows Forms application ?

    Do you debug the DiagnosticRapi.dll  on Windows 10 1607 by Visual Studio 2015?

    It is probably this DiagnosticRapi.dll has some dependencies that they are not registred or be removed in Windows 10 1607 .

    And maybe is the directory need some special permission to access where the DiagnosticRapi.dll located.

    And it may be related to. Net framework version, please be sure the same . Net framework environment and the same compile environment of dll.

    Please try to compile the  DiagnosticRapi.dll and test your application on Windows 10 1607 .

    Best regards,

    Bob


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Friday, February 10, 2017 8:27 AM
    Moderator
  • Hi Bob.

    Thanks for your comments.

    My application is both Windows Forms application and Xaml Application.

    These both applications result to same.

    But Xaml application is can't compile, because it's are other developer's application.

    The Windows Forms applications can be compiled.

    some dependencies are VC++ Redistributable?

    I already installed VC++ redistributables. (VC++ 2005, 2008, 2010, 2012, 2013, 2015)

    Finally, I tried re-compile DiagnosticRapi.dll and my test application on Windows 10 1607 with VS2015.

    but, same results.

    Please know that some details and certain solved for me.

    Thanks.

    Jack.

    Sunday, February 12, 2017 8:30 AM
  • Hi,

    I don't know what the DiagnosticRapi.dll is. It is hard to diagnose what reasons cause your problem.

    I suggest you keep your Window 10 with 1511 version if you can't wait to fix the issue on  Window 10 with 1607 version.

    Best Regards,

    Bob


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Saturday, February 25, 2017 6:50 AM
    Moderator