EOL.WikiEOL.Wiki
← ← Back to all products

UnionTech OS (UOS)

Active
Operating SystemsLatest Version: V25Latest Release: Apr 15, 2026

UnionTech OS (UOS) is a commercial Chinese operating system developed by UnionTech, widely used in government and enterprise for domestic IT substitution.

Support summary

UnionTech OS (UOS) has cycles in security-only maintenance. Production workloads should move toward actively supported releases.

What do EOL and support statuses mean?

Next EOL

No announced EOL date is currently listed.

Supported cycles

4

3 lts

Versions

4

Latest Version

V25

Active Support

3

EOL

0

Lifecycle Timeline

Today
V25 Desktop
V25 Desktop
V20 Professional
V20 Professional
V20 Server
V20 Server
V20 Home
V20 Home
Active SupportSecurity SupportEOL

Versions

ReleaseRelease DateActive SupportEOLLatest VersionLTSStatus
V25 DesktopApr 15, 2026YesNoV25
Yes
Active
V20 ProfessionalJan 14, 2020YesNo1070
Yes
Active
V20 ServerMar 25, 2020YesNo1070
Yes
Active
V20 HomeJul 21, 2020Jun 30, 2025No22.1No
Security

Data sources

Last verified

Jun 24, 2026

Community-maintained lifecycle data. Verify against official release notes before production migration.

Frequently Asked Questions

Is it safe to continue using UnionTech OS (UOS) V20 Home?
UnionTech OS (UOS) V20 Home is currently supported and receiving updates. You can continue using it safely until its end-of-life date.
What is the latest version of UnionTech OS (UOS)?
The latest version of UnionTech OS (UOS) is V25, released in the V25 Desktop release cycle.
How many versions of UnionTech OS (UOS) are currently supported?
UnionTech OS (UOS) currently has 4 actively supported version(s): V25 Desktop, V20 Professional, V20 Server, V20 Home.
When does UnionTech OS (UOS) V25 Desktop reach end of life?
UnionTech OS (UOS) V25 Desktop does not have a specific end-of-life date announced yet.
What should I do when UnionTech OS (UOS) reaches end of life?
When a UnionTech OS (UOS) version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.