UNSOLVED

DELL-Scott H

updated

2 months ago

DS

DELL-Scott H

Moderator

•

1071 Posts

•

5035 Points

0

731

August 11th, 2026 01:01

ThinOS 2605 HF1 Released

Link to RN

https://dl.dell.com/content/manual43738726-dell-thinos-10-x-2602-and-2605-release-notes.pdf?language=en-us

Link to a new Flowchart to aid in the upgrade flow based on lessons learned from the first release.

https://www.dell.com/support/manuals/en-us/wyse-thinos-maintenance/thinos_10.x_26xx_rn/thinos-10.x-upgrade-with-security-add-on-package?guid=guid-4d059767-f4d0-43a0-a2c6-c438d0a90906&lang=en-us

BIOS Packages will be posted by 8/15/2026, they are a bit delayed

Highlights of release

  • Dell Pro Micro support
  • 3'rd party HW Support
    • ****8-13-26, Hold off on this just yet . There is some internal discussion on if this is actually supported.  I will come back here as soon as i have clarification****
    • ****8-17, Confirmed that 3'rd party Hardware is not supported with this build yet. I will come back with the plan when I have it
  • BIOS Packages are not posted yet, but coming.  As of 8-13-26 They are posted
  • A number of the issues identified with the initial release, plus more. 
  • There are still a fair number of open issues (See the RN) which will get targeted for the September release.  

  • Snapshot creation failed
  • Reboot loop
  • P2P not working
  • Netscaler login issue
  • WMS check-in issue
  • F12/Recovery causing issue
  • WMS check-in page issue
    • Group change and Unregister device when privilege is high
  • Citrix Web login timeout
  • Imprivata Tap-in/Tap-out
  • Package install notice
  • DPMTC upgrade issue -> Actual fix should come via CCTK/BIOS update (which is WIP) but the team has identified an alternative way to upgrade the DPMTC to 2605 HF1
  • DeviceSecurity rule bug when configured in Parent Group
  • Dell Pro 14-ThinOS10 needs to support Audio mute function using Fn+F4, this works currently using Ctrl+Shift+M key combinations
  • DeviceSecurity Allow option no longer works in latest T10 builds
  • Chrome stuck in loop after terminal name change
  • CIPS-47535 – Mouse and keyboard responses are lagging when configure with Wifi
  • CIPS-47563 - WMS will not accept Browser URLs with a % character
  • CIPS-46690 - Dell Pro 24 All-in-One | Thin OS 10 2602 | ThinOS 10 Imprivata login error
  • CIPS-47463 - WMS v2605 | Secure Boot Enable - BIOS option is not available in ThinOS 10 Policy
  • CIPS-46970 - UPNs are duplicated in AVD Log Analytics Workspace (LAW) only when users login using short name.
  • CIPS-45081 - Time Zone Sync Issue in Blast Session After 9 to 10 2511hf | ThinOS 10 2511_10.0380
  • CIPS-47188 - Citrix Weblogin Timeout not working Consistently | ThinOS 10 2602_10.0765 | Opti3kTC
  • CIPS-47430 - WMS - OPT3000TC - ThinOS10 2602 - Citrix - Print issue
  • CIPS-46936 | A210D | ThinOS 10 | Browser shortcuts intermittently disappear when changing groups
  • CIPS-46500 | AVD remote app will not launch when security banner is enabled
  • CIPS-45930 – Allow badge reader to be used inside VMWare VDI session also FIDO 2 broker login (Omnissa 01349845, 01579418)
  • CIPS-46927 ThinOs - Omnissa - not able to register a fido stick - logon works fine with registered stick
  • CIPS-46971 - ThinOS 2602 – FIDO2 / USB mapping fails with Windows Server 2022 shared desktop (XA 2404 LTS)
  • CIPS-39330 - New case-CIPS-45058 - 2411 - Optiplex 3000 | Thin OS 10 2511HF | AVD Error: Resync Remote Applications
  • CIPS-46005 - opt3000tc - ThinOS ThinOS10_2511_10.0320 - AVD - RemoteApp Application not opening
  • Proxy WMS check-in failures
  • Gnome Keyring popup issue

(edited)


DELL-Scott H
#IWork4Dell

  • lolix2

    2 Intern

    •

    139 Posts

    •

    93 Points

    5

    1

    Posted August 11th, 2026 09:34

    Thanks DELL to add to the confusion...

    So we have now to create yet another group for >2100 to apply the "ThinOS 10 2605 Firmware Upgrade Package", aka "root upgrade".

    while what everyone is struggling about,  firmware <2100 upgrade, will be on the "Upgrade and Downgrade Package" aka "root package".

    Right ?

    MTTA. Make Thinclient Thin Again. 

    Please.

  • DELL-Scott H

    Moderator

    •

    1071 Posts

    •

    5035 Points

    6

    0

    Posted August 11th, 2026 12:35

    @lolix2​ You are correct, due to the nature of the security updates in this release a full update was required, File Name: Root_2605.10.2518_T10.pkg can bypass the requirement to get to 2100.

    I also miss the days of 25 MB firmware, but broker requirement changes and ecosystem changes made that not feasible any longer.  

    This package contains the ThinOS 10 2605 upgrade and downgrade package. This package is intended for customers who want to upgrade from ThinOS 10 2511 10.0320, 10.0327, 10.0380 and 2602 10.555, 10.580 and 765 to ThinOS 10 2605 10.2518 and downgrade to ThinOS 10 2605 from later versions.


    DELL-Scott H
    #IWork4Dell

  • xiDannYo

    2 Intern

    •

    46 Posts

    •

    49 Points

    6

    1

    Posted August 12th, 2026 09:27

    I've done exactly what the flowchart says and the 5070's with upgraded storage still just fail every time. Is no testing actually being done on each device here before releasing these upgrades?

  • lolix2

    2 Intern

    •

    139 Posts

    •

    93 Points

    3

    0

    Posted August 14th, 2026 13:16

    WMS 2605.0.2.375

    ConfigUI 1.10.856

    Optiplex 3000

    Bios 1.35

    ThinOS 2602_10.0765

    The event log says  "BIOS settings update was successful"

    Yet, when I enter the BIOS, the UEFI network stack is still enabled.

    I doudble-checked the WMS option ans the UEFI network stack in BIOS Common configuration is well disabled.

    So I don't even dare to move that device to the group to upgrade to 2605_10.2518 because previous attempt with UEFI network stack enabled failed.

    That BIOS option as prerequisite to a successful upgrade is the worst idea ever...

    I have submitted a SR.

    (edited)

  • Marek1917

    1 Rookie

    •

    3 Posts

    •

    13 Points

    6

    0

    Posted August 17th, 2026 12:33

    @lolix2​ From my understanding the UEFI Network Stack doesn't change until you actually start the 2605 upgrade. Anything below 2605 doesn't have the ability to change that setting.

  • lolix2

    2 Intern

    •

    139 Posts

    •

    93 Points

    5

    0

    Posted August 17th, 2026 13:14

    No, disabling the UEFI network stack is a prerequisite to upgrade to 2605. When set manually the upgrade goes well.

     

    After setting a stronger password (which had already been set stronger recently but not strong enough for latest requirements...) and removed the duplicate "passwords" update BIOS options in the Optiplex 3000 deprecated section , the whole upgrade process worked.

    I can't tell  if it is the cleanup or the weak password that was the culprit.

    (We will soon need more "previous password" fields in WMS...) 

    (edited)

  • Stefan3

    1 Rookie

    •

    3 Posts

    •

    13 Points

    2

    0

    Posted August 17th, 2026 13:23

    Optiplex 3000
    ThinOS: 2602_10.0555

    WMS: 2605.0.2.375
    Config UI: 1.10.856
    Bios: 1.35.0
    Security Certificate Addon: 2605.10.0009

    When trying to update to Version Root_2605.10.2518_T10.pkg, we still get the error: Signature verification failed. In WMS we have changed the settings as described in the new Flowchart: Disabled UEFI Network Stack, Disabled USDB Boot Support, Enabled Secure Boot and set the Current BIOS Admin Password. The Security Addon was installed successfully.

  • xiDannYo

    2 Intern

    •

    46 Posts

    •

    49 Points

    7

    1

    Posted August 17th, 2026 13:27

    @lolix2​ Doesn't matter what I put in as a new bios password it still says it's weak.

    Even tried just 15+ random capitals, lowercase, numbers and symbols, no luck.

  • lolix2

    2 Intern

    •

    139 Posts

    •

    93 Points

    12

    0

    Posted August 17th, 2026 13:51

    @xiDannYo​ I had this problem too and it seems that doing a "reset policy" on the deprecated BIOS section did the trick. The Optiplex 3000 entry disappeared from there.

  • DELL-Scott H

    Moderator

    •

    1071 Posts

    •

    5035 Points

    12

    0

    Posted August 17th, 2026 14:06

    @Stefan3​ Try deleting the 2518 package from WMS, re downloading and uploading the package again and testing that. I have seen a few instances of corruption causing this.


    DELL-Scott H
    #IWork4Dell