locked
New flight 14393 released RRS feed

  • General discussion

  • We have released a new flight with build number 14393. If you discover any new issue, please report it using the feedback app.

    What's new in this build:

    • Updated OS files including core OS bug fixes.
    • Issues with Windows Device Portal/WEBB not showing apps, processes and issues with Bluetooth pairing have been addressed.
    • Issues with speech recognition on the Raspberry Pi have been addressed.
    • Issues with the display on an MBM not displaying after a disconnect/reconnect event have been addressed.
    • An issue with passwords for default accounts resetting during updates when using the provided FFUs has been addressed.

    Known issues in this build:

    • The Raspberry Pi3 built-in Bluetooth driver currently only supports low bandwidth devices.
    • Pin.Read is failing when using GPIO on the MBM with the DMAP/Lightning Providers due to issues in the Lightning Nuget.
    • In some cases, the mouse pointer is not visible after deploying or debugging apps with Visual Studio.
    • When using the SoftAP clients will not be able to access content exposed by UAP apps.


    Friday, July 22, 2016 10:49 PM

All replies

  • Hi Folks,

    There was a question in the previous thread regarding the Feedback app. A quick web search will show that there are a number of web sites that talk about using the Windows 10 Feedback App like this one http://www.howtogeek.com/197604/how-to-send-feedback-to-microsoft-in-the-windows-10-technical-preview/

    You can launch this app from the Technical Preview Edition of Windows 10.  There is also an interesting article on how your feedback is used at https://blogs.windows.com/windowsexperience/2015/06/12/how-windows-insider-feedback-influences-windows-10-development/

    Sincerely,

    IoTGirl

    Saturday, July 23, 2016 12:29 AM
  • Just update .. another smd killed ..

    It does not restart (PI3) :-(

    No jet 14393 in insider download.

    Regards,

    CAP

    Saturday, July 23, 2016 11:37 AM
  • Apps, Processes, etc, (Windows Device Portal/WEBB) still not working on my Pis that upgraded to 14393. I can't test a full install because it's not available for download.
    • Edited by Fls-Zen Sunday, July 24, 2016 12:37 AM more info
    Saturday, July 23, 2016 11:49 PM
  • Hi,

    I've keep my RPi3 with 14376 downloading updates for more than 2 hours. However, it seems that the device still can't complete the updates. The "check for updates" button of "Windows Update" page on Windows Device Portal/WEBB is always disabled.


    Keep Fighting

    Sunday, July 24, 2016 6:03 AM
  • OK,

    Finally, it's done. And I'm waiting for installing updates.


    Keep Fighting

    Sunday, July 24, 2016 6:25 AM
  • Yes,

    It is confirmed that Apps and Processes of WEBB Portal have returned back!


    Keep Fighting


    Sunday, July 24, 2016 6:58 AM
  • RPi2 completed update without issue, Minnowboard however is stuck on "Downloading Updates" for 2 days now. Device restart does not help. How to restart the update? Or is it just this slow?
    • Edited by _mms_ Sunday, July 24, 2016 7:08 PM
    Sunday, July 24, 2016 5:32 PM
  • This build contains no addition for remote updating of apps? Is this feature planned for the future?
    Sunday, July 24, 2016 9:29 PM
  • Hi,

    The only insider versions I can see are 14366 and 14376. Where do I get 14393 ??? 

    Thanks!

    Mike

    Monday, July 25, 2016 2:49 PM
  • Hi Mike,

    Your device with 14376 should automatically update to 14393.

    Sincerely,

    IoTGirl


    Monday, July 25, 2016 3:48 PM
  • Hi,

    I have tried to update my Pi3 manually but it says that the device is up to date (14376)!!

    Will an Automatic update be any different? What is the schedule for the update ? 

    Thanks!

    Mike

    Monday, July 25, 2016 4:02 PM
  • "Your device with 14367 should automatically update to 14393."

    but .. does not restart .. (or takes an eonic time to do).

    So please put it as a downlodable insider.

    Thank You.

    CAP

    Monday, July 25, 2016 4:32 PM
  • Hi XPLAB,

    Unfortunately that is the way the system is geared. The Update release is available sooner as it is packaged differently than the download.

    Sincerely,

    IoTGirl

    Monday, July 25, 2016 4:56 PM
  • Monday, July 25, 2016 5:40 PM
  • I have been using the Microsoft Speech Recognizer. It has been working well so far, but seems different after this update. It usually recognizes the speech quickly and with a high confidence level, but after the update is much less reliable. I recorded some audio input on IoT Core, and the audio quality sounds the same as previously.

    Has something changed with the Speech Recognition engine this update or is there just some coincidental reason for the degraded results?

    Tuesday, July 26, 2016 4:08 AM
  • I2C seems to be broken again with build 10.0.14393.0. I am getting this same "semaphore timeout period has expired" on a Raspberry Pi 2.

    I have confirmed this was not an issue with an old build with 10.0.10586 I had lying around.

    Tuesday, July 26, 2016 9:34 AM
  • as my device did not update to 14393 i tried to follow the steps @Zeeshan posted but was not able to attach the zipped logs as my feedback hub app did not present that option, only screenshot...
    Tuesday, July 26, 2016 11:51 AM
  • Has something changed with the Speech Recognition engine this update or is there just some coincidental reason for the degraded results?

    please read the top most posting...
    "Issues with speech recognition on the Raspberry Pi have been addressed."

    Tuesday, July 26, 2016 12:03 PM
  • I2C seems to be broken again with build 10.0.14393.0. I am getting this same "semaphore timeout period has expired" on a Raspberry Pi 2.

    I have confirmed this was not an issue with an old build with 10.0.10586 I had lying around.

    if you think that's the case you should do what Microsoft recommend...
    "If you discover any new issue, please report it using the feedback app."

    Select "Developer Platform" and "Windows 10 IoT Core (maker hard..."

    Tuesday, July 26, 2016 12:07 PM

  • please read the top most posting...
    "Issues with speech recognition on the Raspberry Pi have been addressed."

    I am in particular wondering if the changes to the  Speech Recognition may have caused it to reduce in quality.
    Tuesday, July 26, 2016 12:25 PM
  • Hi Fls-Zen,

    What did your Pi's upgrade from?

    • fresh 14366-> upgrade 14393
    • fresh 14366-> upgrade 14376 -> upgrade 14393
    • fresh 14376 -> upgrade 14393

    Note: 14342 -> upgrade 143XX is known to have issues.  You need to start with a fresh 14366 or 14376 install to get 14393.

    What size of SD card are you using? 32GB?

    Sincerely,

    ioTGirl



    Tuesday, July 26, 2016 4:21 PM
  • Is the update 14393 down?

    I can't download them on a RPi3 or on a RPi2!

    From release 14366 both only update to 14376

    From release 14376 the Pi says its up to date!

    Regards

    Dominik

    Thursday, July 28, 2016 4:48 PM
  • Hi Dominik,

    14376 should automatically update to 14393.  Likely your device already is downloading the update in the background and will apply it once it is complete.  Note that the update has to be staged, unpacked and then applied. If you ask if it is up to date during this time, it will likely report that it is.

    Sincerely,

    IoTGirl

    Thursday, July 28, 2016 5:08 PM
  • Dear friend,

    If RPi is downloading the updates, you can see this from WEBB Portal, just as follows. Especially, the "Windows Updates" Page will inform you that it's downloading the updates.


    Keep Fighting

    Friday, July 29, 2016 12:39 AM
  • my RPi2 does not update. it tells always it is up to date.

    i installed the insider preview build 14376 to SD card, and it does not update.

    then i installed the build 14366 and that version only updates to 14376 and that's it. even that will not update to 14393!

    is it possibly, that not all update servers do have the actual build available? or does ot depends on where you are - at what region you live?

    and following the link that describes to transmit the log files is also not helpful to me. i only can upload screenshots, but no log or zip files.

    why not publishing a build 14393 as iso like 14376 and 14366???


    Friday, July 29, 2016 6:34 AM
  • my RPi2 does not update. it tells always it is up to date.

    i installed the insider preview build 14376 to SD card, and it does not update.

    then i installed the build 14366 and that version only updates to 14376 and that's it. even that will not update to 14393!

    is it possibly, that not all update servers do have the actual build available? or does ot depends on where you are - at what region you live?

    and following the link that describes to transmit the log files is also not helpful to me. i only can upload screenshots, but no log or zip files.

    why not publishing a build 14393 as iso like 14376 and 14366???


    ok, actually i got build 14393 now. i don't know the reason. it just appeared to be installed.

    the strange thing is i already tried the last two days to get that build to installed.

    first with installing fresh build 14376, update not possible. not by pressing search for update button, not by keeping system running whole day/night untouched.

    second with installing build 14366, it downloaded and updated immediately build 14376. but then it doesn't update to build 14393. even after keeping the system running whole day/night.

    this morning at 08:00 nothing but at 11:00, the system tells, that a new version is available to install... what?! why now and not two days earlier...???





    Friday, July 29, 2016 10:02 AM
  • @alpha beta-tester

    Microsoft found the reason why some devices did not update and fixed it

    Friday, July 29, 2016 11:18 AM
  • @cyberh0me  Thanks for your help in diagnosing the issue!
    Friday, July 29, 2016 5:36 PM
  • Hi ioTGirl,

    I have two Pi3 devices. One was, I believe, fresh 14366 -> upgrade 14376 -> upgrade 14393. The other I tried to reinstall on, which was fresh 14376 -> upgrade 14393. I was able to set the default app through powershell again on that 2nd one after the reinstall, but the apps page still doesn't show anything.

    Fls'Zen

    Edit: Maybe I should add that the base OS install is laid down by NOOBS.

    • Edited by Fls-Zen Saturday, July 30, 2016 2:35 AM a little more info
    Saturday, July 30, 2016 2:31 AM
  • Hi Fls-Zen,

    Cyberh0me hit this issue as well.  Have you tried using the ip address and not fqdn?

    Sincerely,

    IoTGirl

    Saturday, July 30, 2016 5:07 PM
  • IoTGirl is right

    "Windows Device Portal recently implemented CSRF protection checks. You should either use device name or the IP to access device portal. Any other mechanism might not work".

    Saturday, July 30, 2016 6:36 PM
  • Hi IoTGirl,

    I hadn't tried that yet. Yes, if I use the IP address it works. I had been using the pi.local mDNS hostname. I guess if the devices advertises itself with a certain name on the network I expect it to work properly when using that name. Is this considered a bug, or will I need to manually resolve pi.local to an IP address in future builds?

    Thanks,

    flszen

    Thursday, August 4, 2016 1:38 AM
  • @FlsZen

    CSRF works as it should be, your device has ip address and hostname but is not aware of a domain name or member of a domain

    Thursday, August 4, 2016 11:06 AM
  • As commented elsewhere in the forum, the problem was resolved by re-flashing with the 14393 image instead of using on the applied upgrade.
    Friday, August 5, 2016 9:36 PM
  • release notes on page
    https://developer.microsoft.com/en-us/windows/iot/Downloads.htm
    https://developer.microsoft.com/en-us/windows/iot/docs/releasenotesrtm
    still shows notes for "Build Number 10586. December 2015"
    but should be already notes for "Build Number 14393. August 2016",
    because you get installed build 14393 on Windows 10 IoT Core Dashboard

    Monday, August 8, 2016 10:00 AM
  • @cyberh0me

    Windows is advertising itself as pi.local out-of-the-box, it's not something I'm doing. Since both Windows Device Portal and mDNS hostname advertisement are built-in features, I expect them to work nicely together.

    If I were going off and creating a host record elsewhere for the device then I would fully agree with you that CSRF is working as intended. I'll grant that Microsoft has only recently started adding mDNS into Windows 10, so it's probably just an oversight that the WDP's CRSF doesn't take this into account.



    • Edited by Fls-Zen Monday, August 8, 2016 6:32 PM tweaking
    Monday, August 8, 2016 6:31 PM
  • Our apologies! Due to a formatting error the release notes did not update as expected. They should be online now.
    Monday, August 8, 2016 6:43 PM
  • Hi,

    Dose the latest release of the Windows 10 core OS support the built in Bluetooth module?

    If not can you recommend an external device that would be supported?

    Thanks

    Monday, August 29, 2016 9:52 AM
  • hello

    yes is supported

    Monday, August 29, 2016 10:06 AM