Edit 1 10-20-206. Teh release notes are incorrect and being addressed. The smaller firmware upgrade package (root_upgrade_2609_10.3096.pkg can only be used for upgrading from 2605.2100 and higher.
See Page 13 for the upgrade flow chart under new security changes for 3'rd party hardware
A big focus on this release has been the upgrade challenges (TPM errors, Snapshot errors) experienced during the 2605 release. The requirements for the update from anything before 2605 (Security certificate, BIOS changes, BIOS password) have not changed but testing of this build through the development process has been more reliable.
No ISO build with this release (expected in December build) as they are still working through security impacts of this. Reach out to your Dell team for further details.
Please share any testing results here and I Will do my best to assist.
Highlight of new features (See release notes for details)
Hide Login window during web-based authentication
This a nice improvement of the UI to not have the login box behind the web login box
Option to add RDP direct connection to desktop if broker auth fails
Add on browser no longer required for Yubikey authentication to brokers
The built in browser can handle Yubikey auth to AVD/Citrix and Horizon. No need to install Chrome
Updated presentation to AVD as Desktop client instead of Web client
Organizations desiring to enforce intune policies to block browser connections no longer affect ThinOS
Port blocking
Ability to respond to security requirements to block access to certain ports (TCP/UDP) on devices
Support for touch gestures on touch enabled devices
Security enhancements for WMS communication using mTLS
Log Export from WMS enhancements
Huge improvement in how WMS handles pulling large logs from devices during troubleshooting.
Updated SAML Support for AWS using WSP
****One important note based on my testing.
Due to the Security changes to the WMS registration
The registration takes longer than before
If you USB image a device (2602) and that device is already registered to WMS, then upgrade to 2609 the device will fail to register to WMS. This is due to the security changes to WMS registration. The error log on the thin client will indicate an error message
WMS: validate failure: TPM challenge decryption unavailable. Waiting for system retry loop
Solution, Force unregister the device from WMS, ensure it is deleted from teh unregistered group and let it re register.
I upgraded my two "bleeding edge" test machines to ThinOS 2609 successfully from 2605. Those two clients had previously had their BIOS settings manually changed. "Hands off" testing for my next update test ring had seen mixed results going to 2605. I'm waiting until the next WMS upgrade before testing the second ring on 2609. I'm hoping the BIOS Common Configuration works better to disable USB Boot Support and the UEFI Network Stack.
One specific question I have, why isn't the latest BIOS Firmware Update posted in WMS? My thin clients are OptiPlex All-in-One 7420s. The WMS BIOS package for that model is 1.21.0 (10 Dec 2025), but the current version is 1.38.0
(13 Oct 2026). I'm used to seeing the WMS BIOS package being several revisions back, probably due to one specific BIOS revision being validated with a new ThinOS release, but a version that's 9 months out of date seems a bit too far.
@Tolstoy88155 That is a great Q, and one that comes up frequently.
The BIOS is always produced by the BIOS team first as a .exe for the core client products. It then has to be validated and tested by the ThinOS team and re packaged in the format for WMS.
As you noted there is normally a delay. Since that package came out on 10/13, this ThinOS update (which was due at the end of Sept, but delayed for some critical fixes) had already hit its QA window so the testing window passed.
If you a critical need for anything in that BIOS package I would encourage you to open a support case requesting private hotfix packaging while you wait for the next development window and release (end of November/December).
@DELL-Scott H Well issue was my own donig, I had a USB drive still plugged into the unit. Support was able to see the error in the log bundle of this. He said was first time he seen this error or knew of this, must be something recent with all the security changes. I now have 2 thrid-party devices sucesufully upgraded!
Thanks for your efforts on making the upgrade process more reliable. I was able to get a couple devices updated. However, I still experienced a failure attempting to upgrade a device from 2602_10.0765 to 2609_10.3096.
I suspect I’m hitting the same bugs that were supposedly fixed:
TOS10DEFCT-2109 — Fixed an issue where updates to ThinOS 10.x 2605 failed due to snapshot creation errors.
TOS10DEFCT-2718 — Fixed an issue where the Install Snapshot Creation Failed error occurred during upgrades from ThinOS 10.x 2602 to ThinOS 10.x 2605.
I believe those same snapshot failures are still occurring in 2609. I checked the steps in the release notes and confirmed all pre-requisite steps were performed. ConfigUI is at version 1.10.885 (current version). The security add on package 2605.10.0009 was already installed. The EFI network stack was disabled.
I can confirm the settings from the logs. The installer reports that the upgrade is allowed and proceeds, generates the default BIOS password file at etc init.d .bios_val, and then runs the security pre-checks with these results: TPM 2.0 is functional, Secure Boot is enabled, USB Boot is disabled, UEFI network stack is disabled. It then reports “Security pre-checks passed” and “precheck is passed”.
However it still fails with the same old snapshot issue. At 12:59:59 the installer logs the INST stage, and in the same second logs the error “snapshot creation failed”. The rollback log at that moment shows “Deleting snapshots for version 2602_10.0765” followed by “could not find any snapshots to destroy; check snapshot names.”
The device appears to have no pre-existing snapshots, which would be expected since it has not been upgraded before.
SkrettingMannen
1 Rookie
•
16 Posts
•
31 Points
10
1
Posted October 19th, 2026 16:13
Have been working on upgrading one of our sites today. Had at least three 5070 fail, and stuck with the screen above. Not able to recover these.
Also had at least 4 Optiplex 3000 with TPM lock, but were able to unlock. Will update tomorrow.