Not able to launch window client: after appbuilder window client update to version 2016.1.128.6

Thread is closed for posting
2 posts, 0 answers
  1. Anushri
    Anushri avatar
    5 posts
    Member since:
    Oct 2015

    Posted 28 Jan 2016 Link to this post

    My appbuilder window client got updated when i open it and after it updated showing message that first ask for ur pc at risk and when click on run anyway it try to open but ask for telerik has stop working close program.


    I did many times restart my pc  and also uninstall and re install window client but having same issue.

  2. Tina Stancheva
    Tina Stancheva avatar
    3299 posts

    Posted 29 Jan 2016 Link to this post

    Hello Anushri,

    On some Windows machines certificates signed with SHA1-based certificates are considered insecure even if they are valid and provided by a known certificate authority. At the moment even on those machines you should be able to still install the Windows client by explicitly allowing the insecure installation. Still, we will be releasing a new version of the Windows client signed with a SHA256-based security certificate next week.

    In the meantime, we'll need to research what is going wrong on your machine. Can you please submit a support ticket with the following information:
    • the contents of the %localappdata%\Telerik\BlackDragon\Logs folder
    • the crash dumps collected on your machine. You can see how to enable collecting user-mode dumps here. Then you can open them up on your side and see what they contain. The advantage of opening them on your system is that you will be able to find more detailed information about the crash, which we will not be able to get on our side. In order to examine the crash dumps you can follow these steps:  
      •    Install "Debugging Tools for Windows" from Microsoft Windows SDK for Windows. Note that you do not need to install all tools from the sdk, just the debugging tools.
      •    Open "windbg.exe" for x86 from the Debugging Tools installation folder.
      •    Click File -> Open Crash dump
      •    Select the crash dump
      •    Execute the following commands:
         .loadby sos clr
         !analyze -v
      •    Examine the result and/or click "Edit -> Write Window to text file" and send us the resulted text file.
    • Fiddler logs
      1. Download Fiddler from here and install it.
      2. Run Fiddler and go to Tools -> Fiddler Options.
      3. On the HTTPS page, verify that Capture HTTPS Connects is enabled.
      4. Verify that Decrypt HTTPS traffic is enabled with the ...from all processes option and minimize Fiddler to tray.
      5. Run your AppBuilder client and perform the operations that failed
      6. In Fiddler, go to File -> Save -> All Sessions, save the archive to disk. This will produce a SAZ file.
      7. Zip the .saz file and attach it in a ticket

    In the meantime, please follow these next steps to try and resolve the issue on your side by performing a complete re-install:

    1. Close the Windows client.
    2. Run the Task Manager and kill any Icenium.Graphite.exe processes
    3. Uninstall the Windows client.
    4. Go to %localappdata%\Telerik and delete the BlackDragon folder and the Icenium.Simulator* folder.
    5. Go to %localappdata%\Apps and delete the 2.0 folder.
    6. Download the Windows client from here and install it again
    Tina Stancheva

    Visit the Telerik Verified Plugins Marketplace and get the custom Cordova plugin you need, already tweaked to work seamlessly with AppBuilder.

Back to Top