› ›

Host wont run on Windows 8.1 64bit

lmclarenlmclaren
in Windows
I have tried to install and run 1.5.6 host on Windows 64bit 8.1. When I click the desktop shortcut to run, it goes busy for 5sec and then nothing.

I have tried running with administrator privileges, comparability settings, reinstalling, turning off one screen (I have 2) changing screen resolution, nothing helps.
I have tried launching directly from the executable, deleting the registry settings etc.

Are there any debug setting or suggestions?

many thanks.


Comments

  • lmclarenlmclaren
    I forgot to mention, I also tried to install the font.
  • RepetierRepetier
    Do you see anything? Any message? Messages in windows event log?

    What graphic card and color resolution are you using?

  • lmclarenlmclaren
    Nvidia, my main screen is 2560x1600 and my second screen is 1280x1024

    Faulting application name: RepetierHost.exe, version: 1.0.0.0, time stamp: 0x55f3c59a
    Faulting module name: KERNELBASE.dll, version: 6.3.9600.18007, time stamp: 0x55c4c341
    Exception code: 0xe0434352
    Fault offset: 0x000000000000871c
    Faulting process ID: 0x94c
    Faulting application start time: 0x01d107ff6658338d
    Faulting application path: C:\Program Files\Repetier-Host\RepetierHost.exe
    Faulting module path: C:\Windows\system32\KERNELBASE.dll
    Report ID: a4137fc7-73f2-11e5-bfb1-001fbc095a89
    Faulting package full name: 
    Faulting package-relative application ID: 

    Application: RepetierHost.exe
    Framework Version: v4.0.30319
    Description: The process was terminated due to an unhandled exception.
    Exception Info: System.Reflection.TargetInvocationException
    Stack:
       at System.RuntimeMethodHandle.InvokeMethod(System.Object, System.Object[], System.Signature, Boolean)
       at System.Reflection.RuntimeConstructorInfo.Invoke(System.Reflection.BindingFlags, System.Reflection.Binder, System.Object[], System.Globalization.CultureInfo)
       at System.Security.Cryptography.CryptoConfig.CreateFromName(System.String, System.Object[])
       at System.Security.Cryptography.MD5.Create(System.String)
       at RepetierHostExtender.basic.Custom.GetMd5Hash(System.String)
       at RepetierHostExtender.basic.Custom.VerifyFile()
       at RepetierHostExtender.basic.Custom.Initialize()
       at RepetierHost.Program.Main(System.String[])

    Application: RepetierHost.exe
    Framework Version: v4.0.30319
    Description: The process was terminated due to an unhandled exception.
    Exception Info: System.Reflection.TargetInvocationException
    Stack:
       at System.RuntimeMethodHandle.InvokeMethod(System.Object, System.Object[], System.Signature, Boolean)
       at System.Reflection.RuntimeConstructorInfo.Invoke(System.Reflection.BindingFlags, System.Reflection.Binder, System.Object[], System.Globalization.CultureInfo)
       at System.Security.Cryptography.CryptoConfig.CreateFromName(System.String, System.Object[])
       at System.Security.Cryptography.MD5.Create(System.String)
       at RepetierHostExtender.basic.Custom.GetMd5Hash(System.String)
       at RepetierHostExtender.basic.Custom.VerifyFile()
       at RepetierHostExtender.basic.Custom.Initialize()
       at RepetierHost.Program.Main(System.String[])


    hope that helps

    thanks

    Lee

  • lmclarenlmclaren
    Has anyone got any suggestions?

    Are there any beta versions that I can test?
  • lmclarenlmclaren
    I have found the cause, it is to do with the FIPS encryption, needed for many vpn clients.

    It would be nice if the Repetier could be fixed so I don't need to do this.

    This key will turn it off so Repetier can run but stops the vpn client working, 

    This is to turn it off:
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\FipsAlgorithmPolicy]
    "Enabled"=dword:00000000

    This turns it back on again.
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\FipsAlgorithmPolicy]
    "Enabled"=dword:00000001




  • RepetierRepetier
    What a stupid thing. I googled after your comment and you are right. MD5 is not FIPS compliant so it simply stops working in that case crashing the app.

    Modifying the registry is error prone so I do not like this approach. I think the better solution to have a own MD5 implementation that does not depend on anything. That way VPN will still continue to work. Will add this for next update.
Sign In or Register to comment.