iot
3 TopicsUpdate bootloader in Win10 Iot Ent LTSC (21H2) applied images?
The product I work on uses Windows 10 IoT Enterprise LTSC (21H2). I am trying to update the bootloader in the extracted and applied images to the version signed in 2023, to work around the issue with the default bootloader signatures expiring in 2026 (see KB5012170). KB5012170 updates the bootloader on an installed system. I can apply this hotfix to an installed device, and the bootloader on the hidden partition indeed gets updated. However, if I sysprep and extract the image from this machine, and apply it to a new machine, after using bcdboot to set the boot image, the new machine ends up with the old expiring bootloader installed. It seems KB5012170 only updates the "live" version of the bootloader on the hidden partition. It does not update the bootloader that ends up in the extracted image? Updating to Windows 10 IoT 22H2 or Windows 11 IoT is not an option for us for now. I do not want to have to require users to always install KB5012170 every time they install our product moving forward. I would like newly created images of our product to contain the updated bootloader by default. But I cannot find a way to do this. KB5012170 seems to be the only way to get the updated bootloader for our edition of Windows. Is there another way to get the updated bootloader I am missing? Is there a tool or trick that I am missing that would allow us to update the bootloader in the extracted, applied image without requiring a subsequent install of KB5012170?40Views0likes2CommentsI2cDevice class / Method WriteReadPartial issuing "unknown error"
Hello community, I'm currently working on an Intel Atom E39340 platform with Windows 10 IOT 2021 LTSC installed on it. The Read and Write methods of the I2cDevice class everything are working just fine. Nevertheless, one of my sensors needs a Write+Read access (Start / Write / Restart / Read /Stop) to access some registers. When I use the WriteRead(byte[] writebuffer, byte[] readbuffer) I get a System.Argument.Exception:'The parameter is incorrect'. (which is really weird because its compiling). When I use the WriteReadPartial(byte[] writebuffer, byte[] readbuffer) method to get the error code the result is 4 (i.e Unknown error). Overall, nothing happens on the I2C bus. I have explored the online documentation but can't find a lead... https://docs.microsoft.com/en-us/uwp/api/windows.devices.i2c.i2cdevice.writereadpartial?view=winrt-22621 Does anyone has ever experienced this ? Thanks a lot for your feedback. Best regards.Solved1.5KViews0likes1CommentJoin & ask questions Monday 9am-10am PT, July 20 for Deep Dive: #WindowsIoT!
Join & ask questions with our amazing speakers next Monday 9am-10am PT for Deep Dive: #WindowsIoT! https://aka.ms/deepdive/windows-iot (iCal on page) Michael Bervell from Windows IoT team showcasing what is next for Windows for IoT & answering the top questions from the community. (Raspberry Pi, vNext, etc) Amelia Casciola doing a technical demo of the new ARM64 support. Plus, giving top tips on creating apps! Henry Fieglein from Dover Fueling Solutions showcasing a real world solution that delivers personalized experiences in content and targeted advertising, right at the gas pump! #iot #azureiot #windows10 #Developer #IoTArchitect #RealWorldScenario1.1KViews1like0Comments