none
Iot Core Watcher user interface not starting

    Question

  • I followed the instructions for programming the Raspberry PI 2 with Windows 10.

    After installing the IOT Core Watcher app the UI does not appears. I re-installed the app twice and start it as an admin but it didn`t help.

    After double clicking the executable the moving circle appears but not the user interface itself.

    Do you have this problem or have any suggestions, please let me know.


    • Edited by JeffreyPI2 Tuesday, May 5, 2015 9:26 AM
    Monday, May 4, 2015 7:02 PM

Answers

  • I was seeing this exception on one of my VMs, launching the watcher in a debug session revealed;

    Could not load file or assembly 'WindowsIoTCoreWatcher, Version=10.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. Strong name validation failed. (Exception from HRESULT: 0x8013141A)

    I couldn't see anything obvious in fusion logs so I just stripped out the signature with snremove.

    This is a bit of a hack, but it allowed me to start the watcher.

    • Proposed as answer by BasRP Tuesday, May 5, 2015 4:15 PM
    • Marked as answer by JeffreyPI2 Wednesday, May 6, 2015 6:44 PM
    Tuesday, May 5, 2015 12:35 PM

All replies

  • After you launch the IoT Core Watcher app if you have minimized it, then it will not appear on your task bar.  Instead it will show in the system tray area.  If you right click on the circuit board square and say 'Restore' you should see the app watcher again.

    Hopefully that's what you were experiencing.


    Jonathan Tanner | Microsoft | Windows 10 IoT Core Insider Preview Support | This posting is provided 'as is' with no warranties and confers no rights.

    Monday, May 4, 2015 9:48 PM
    Moderator
  • I have the same problem. The Software crash:

    Windows 10 Build 10074 Visual Studio 2015 RC

    Application: WindowsIoTCoreWatcher.exe
    Framework Version: v4.0.30319
    Description: The process was terminated due to an unhandled exception.
    Exception Info: exception code e0434352, exception address 00007FFAE6A818F8
    Stack:

    Monday, May 4, 2015 10:14 PM
  • I have problem too.

    Faulting application name: WindowsIoTCoreWatcher.exe, version: 10.0.10103.0, time stamp: 0x553591f8
    Faulting module name: KERNELBASE.dll, version: 10.0.10074.0, time stamp: 0x553acf7b
    Exception code: 0xe0434352
    Fault offset: 0x00000000000218f8
    Faulting process id: 0x2178
    Faulting application start time: 0x01d0870bf5a54e47
    Faulting application path: C:\Program Files (x86)\Microsoft IoT\WindowsIoTCoreWatcher.exe
    Faulting module path: C:\Windows\system32\KERNELBASE.dll
    Report Id: 8e2a8208-71fa-49aa-83ae-7011ba35b0ff
    Faulting package full name:
    Faulting package-relative application ID:

    Tuesday, May 5, 2015 8:20 AM
  • I double-checked the system tray area but I see no icon appearing
    • Edited by JeffreyPI2 Tuesday, May 5, 2015 9:19 AM
    Tuesday, May 5, 2015 9:18 AM
  • Same problem for me ...

    After launching the watcher the error system reporter starts to send information about crash.

    Paolo.


    Paolo Patierno

    Tuesday, May 5, 2015 10:24 AM
  • I was seeing this exception on one of my VMs, launching the watcher in a debug session revealed;

    Could not load file or assembly 'WindowsIoTCoreWatcher, Version=10.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. Strong name validation failed. (Exception from HRESULT: 0x8013141A)

    I couldn't see anything obvious in fusion logs so I just stripped out the signature with snremove.

    This is a bit of a hack, but it allowed me to start the watcher.

    • Proposed as answer by BasRP Tuesday, May 5, 2015 4:15 PM
    • Marked as answer by JeffreyPI2 Wednesday, May 6, 2015 6:44 PM
    Tuesday, May 5, 2015 12:35 PM
  • Thanks Eric, that did the trick for me as well.

    For those who are wondering: download snremove.exe from here and run "snremove.exe -r WindowsIoTCoreWatcher.exe". You'll need to do this in an elevated command prompt because the executable it'll try to modify is in program files.

    Tuesday, May 5, 2015 4:16 PM
  • I also get a crash on one of my machines. From the EventLog (2 events)...

    Log Name:      Application
    Source:        Application Error
    Date:          5/5/2015 3:16:22 PM
    Event ID:      1000
    Task Category: (100)
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      Dell8700
    Description:
    Faulting application name: WindowsIoTCoreWatcher.exe, version: 10.0.10103.0, time stamp: 0x553591f8
    Faulting module name: KERNELBASE.dll, version: 10.0.10074.0, time stamp: 0x553acf7b
    Exception code: 0xe0434352
    Fault offset: 0x00000000000218f8
    Faulting process id: 0x21b0
    Faulting application start time: 0x01d087705aeddb32
    Faulting application path: C:\Program Files (x86)\Microsoft IoT\WindowsIoTCoreWatcher.exe
    Faulting module path: C:\Windows\system32\KERNELBASE.dll
    Report Id: c9cf822d-b6c6-41d0-85cc-ec2ad19f2fbc
    Faulting package full name: 
    Faulting package-relative application ID: 
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Application Error" />
        <EventID Qualifiers="0">1000</EventID>
        <Level>2</Level>
        <Task>100</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2015-05-05T20:16:22.000000000Z" />
        <EventRecordID>4707</EventRecordID>
        <Channel>Application</Channel>
        <Computer>Dell8700</Computer>
        <Security />
      </System>
      <EventData>
        <Data>WindowsIoTCoreWatcher.exe</Data>
        <Data>10.0.10103.0</Data>
        <Data>553591f8</Data>
        <Data>KERNELBASE.dll</Data>
        <Data>10.0.10074.0</Data>
        <Data>553acf7b</Data>
        <Data>e0434352</Data>
        <Data>00000000000218f8</Data>
        <Data>21b0</Data>
        <Data>01d087705aeddb32</Data>
        <Data>C:\Program Files (x86)\Microsoft IoT\WindowsIoTCoreWatcher.exe</Data>
        <Data>C:\Windows\system32\KERNELBASE.dll</Data>
        <Data>c9cf822d-b6c6-41d0-85cc-ec2ad19f2fbc</Data>
        <Data>
        </Data>
        <Data>
        </Data>
      </EventData>
    </Event>

    Log Name:      Application
    Source:        .NET Runtime
    Date:          5/5/2015 3:16:22 PM
    Event ID:      1026
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      Dell8700
    Description:
    Application: WindowsIoTCoreWatcher.exe
    Framework Version: v4.0.30319
    Description: The process was terminated due to an unhandled exception.
    Exception Info: exception code e0434352, exception address 00007FF9FBFA18F8
    Stack:

    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name=".NET Runtime" />
        <EventID Qualifiers="0">1026</EventID>
        <Level>2</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2015-05-05T20:16:22.000000000Z" />
        <EventRecordID>4706</EventRecordID>
        <Channel>Application</Channel>
        <Computer>Dell8700</Computer>
        <Security />
      </System>
      <EventData>
        <Data>Application: WindowsIoTCoreWatcher.exe
    Framework Version: v4.0.30319
    Description: The process was terminated due to an unhandled exception.
    Exception Info: exception code e0434352, exception address 00007FF9FBFA18F8
    Stack:
    </Data>
      </EventData>
    </Event>

    Tuesday, May 5, 2015 8:20 PM
  • Thank you all for providing these details. The product team is aware of this issue and will be looking into it.  I unfortunately do not have an ETA for a fix. 

      For the time being however if you do need to interact with your device I'd suggest either using Power Shell, or connecting to the web interface on the device using http://<ip address>


    Jonathan Tanner | Microsoft | Windows 10 IoT Core Insider Preview Support | This posting is provided 'as is' with no warranties and confers no rights.

    Tuesday, May 5, 2015 11:27 PM
    Moderator
  • Anyone else have problems getting the watcher utility to work?

    Faulting application name: WindowsIoTCoreWatcher.exe, version: 10.0.10103.0, time stamp: 0x553591f8
    Faulting module name: KERNELBASE.dll, version: 10.0.10074.0, time stamp: 0x553acf7b
    Exception code: 0xe0434352
    Fault offset: 0x00000000000218f8
    Faulting process ID: 0x14e0
    Faulting application start time: 0x01d0886303c5649d
    Faulting application path: C:\Program Files (x86)\Microsoft IoT\WindowsIoTCoreWatcher.exe
    Faulting module path: C:\WINDOWS\system32\KERNELBASE.dll
    Report ID: b393ea71-ee50-46db-bc99-0dceaae2e34a
    Faulting package full name:
    Faulting package-relative application ID:

    Thursday, May 7, 2015 6:02 PM
  • For those of you which are seeing this issue, if you could collect a procdump of the crash and share it with us that would be helpful towards helping us resolve the issue.

    In this case I believe you’ll want to use something like: C:\>procdump -ma -e WindowsIoTCoreWatcher.exe

    Once you have one if you can zip it up and put it on a share where we can retrieve it please reply back here.


    Jonathan Tanner | Microsoft | Windows 10 IoT Core Insider Preview Support | This posting is provided 'as is' with no warranties and confers no rights.

    Thursday, May 7, 2015 6:22 PM
    Moderator
  • Cant answer with IE11 under Windows 10. ;-) And the tool procdump doesn't creates a dump.

    Sysinternals - www.sysinternals.com
    With contributions from Andrew Richards
    Process:               WindowsIoTCoreWatcher.exe (7656)
    CPU threshold:         n/a
    Performance counter:   n/a
    Commit threshold:      n/a
    Threshold seconds:     10
    Hung window check:     Disabled
    Log debug strings:     Disabled
    Exception monitor:     Unhandled
    Exception filter:      *
    Terminate monitor:     Disabled
    Cloning type:          Disabled
    Concurrent limit:      n/a
    Avoid outage:          n/a
    Number of dumps:       1
    Dump folder:           C:\
    Dump filename/mask:    PROCESSNAME_YYMMDD_HHMMSS

    Press Ctrl-C to end monitoring without terminating the process.
    CLR Version: v4.0.30319
    [18:17:00] The process has exited.
    [18:17:00] Dump count not reached.

    and the Error comes only in the Windows Eventlog

    Protokollname: Application
    Quelle:        Application Error
    Datum:         18.05.2015 17:55:29
    Ereignis-ID:   1000
    Aufgabenkategorie:(100)
    Ebene:         Fehler
    Schlüsselwörter:Klassisch
    Benutzer:      Nicht zutreffend
    Computer:      WIN-IIMM5ONH2LS
    Beschreibung:
    Name der fehlerhaften Anwendung: WindowsIoTCoreWatcher.exe, Version: 10.0.10103.0, Zeitstempel: 0x553591f8
    Name des fehlerhaften Moduls: KERNELBASE.dll, Version: 10.0.10074.0, Zeitstempel: 0x553acf7b
    Ausnahmecode: 0xe0434352
    Fehleroffset: 0x00000000000218f8
    ID des fehlerhaften Prozesses: 0x1314
    Startzeit der fehlerhaften Anwendung: 0x01d091830f1300ca
    Pfad der fehlerhaften Anwendung: C:\Program Files (x86)\Microsoft IoT\WindowsIoTCoreWatcher.exe
    Pfad des fehlerhaften Moduls: C:\Windows\system32\KERNELBASE.dll
    Berichtskennung: 7ede95f5-e69f-4045-87a9-cbed6b8dfda7
    Vollständiger Name des fehlerhaften Pakets:
    Anwendungs-ID, die relativ zum fehlerhaften Paket ist:
    Ereignis-XML:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Application Error" />
        <EventID Qualifiers="0">1000</EventID>
        <Level>2</Level>
        <Task>100</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2015-05-18T15:55:29.000000000Z" />
        <EventRecordID>2834</EventRecordID>
        <Channel>Application</Channel>
        <Computer>WIN-IIMM5ONH2LS</Computer>
        <Security />
      </System>
      <EventData>
        <Data>WindowsIoTCoreWatcher.exe</Data>
        <Data>10.0.10103.0</Data>
        <Data>553591f8</Data>
        <Data>KERNELBASE.dll</Data>
        <Data>10.0.10074.0</Data>
        <Data>553acf7b</Data>
        <Data>e0434352</Data>
        <Data>00000000000218f8</Data>
        <Data>1314</Data>
        <Data>01d091830f1300ca</Data>
        <Data>C:\Program Files (x86)\Microsoft IoT\WindowsIoTCoreWatcher.exe</Data>
        <Data>C:\Windows\system32\KERNELBASE.dll</Data>
        <Data>7ede95f5-e69f-4045-87a9-cbed6b8dfda7</Data>
        <Data>
        </Data>
        <Data>
        </Data>
      </EventData>
    </Event>

    Monday, May 18, 2015 4:24 PM
  • Protokollname: Application
    Quelle:        .NET Runtime
    Datum:         18.05.2015 18:16:54
    Ereignis-ID:   1026
    Aufgabenkategorie:Keine
    Ebene:         Fehler
    Schlüsselwörter:Klassisch
    Benutzer:      Nicht zutreffend
    Computer:      WIN-IIMM5ONH2LS
    Beschreibung:
    Anwendung: WindowsIoTCoreWatcher.exe
    Frameworkversion: v4.0.30319
    Beschreibung: Der Prozess wurde aufgrund einer unbehandelten Ausnahme beendet.
    Ausnahmeinformationen: Ausnahmecode e0434352, Ausnahmeadresse 00007FFEF1EE18F8
    Stapel:
    Ereignis-XML:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name=".NET Runtime" />
        <EventID Qualifiers="0">1026</EventID>
        <Level>2</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2015-05-18T16:16:54.000000000Z" />
        <EventRecordID>2855</EventRecordID>
        <Channel>Application</Channel>
        <Computer>WIN-IIMM5ONH2LS</Computer>
        <Security />
      </System>
      <EventData>
        <Data>Anwendung: WindowsIoTCoreWatcher.exe
    Frameworkversion: v4.0.30319
    Beschreibung: Der Prozess wurde aufgrund einer unbehandelten Ausnahme beendet.
    Ausnahmeinformationen: Ausnahmecode e0434352, Ausnahmeadresse 00007FFEF1EE18F8
    Stapel:
    </Data>
      </EventData>
    </Event>
    Monday, May 18, 2015 4:28 PM