Microsoft FSLogix · Lifecycle Status

Microsoft FSLogix End of Life (EOL) Dates & Support Timeline

Complete end-of-life dates, support windows, and security status for all Microsoft FSLogix versions. Dates read at the vendor's own lifecycle pages (learn.microsoft.com). Updated at every deploy.

✓ Microsoft FSLogix 26.08 is actively supported. No versions approaching EOL in the next 6 months.

Microsoft FSLogix 26.08 is supported, with no end-of-life or end-of-support date announced yet. 14 of 15 tracked Microsoft FSLogix versions are past end of life; the most recent to reach it, 25.06, did so on September 9, 2025. The full Microsoft FSLogix lifecycle, with every version's release and end-of-support date, is in the table below.

Running an EOL version? Get matched with support options — free ↓
Latest Active
26.08
26.08 series
Next EOL
—
None upcoming
Active Versions
1
of 15 total
EOL Versions
14
no longer patched
45 / 100
Medium Risk
EOL Risk Score™  How is this calculated? →
EOL Recency
35/40
Attack Surface
10/30 Medium tier
CISA KEV Exposure
0/20 Not in KEV
Extended Support
0/10 Available
EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build. Methodology →
CPE Identifier
cpe:2.3:a:microsoft:fslogix
The Common Platform Enumeration name vulnerability scanners and CVE records use for Microsoft FSLogix. Verified against the NIST CPE dictionary. Machine-readable for all products: cpe-map.json
Release Cycle Timeline
■ EOL   ■ Warning   ■ Active   ┊ Today
Release cycle timeline 2023202420252026202722012201 Hotfix 12201 Hotfix 222102210 Hotfix 12210 Hotfix 22210 Hotfix 32210 Hotfix 425.0225.0425.0625.0926.0126.01 CU126.08TODAY
14 versions of Microsoft FSLogix are past end of life — security patches have stopped. Get matched with support →
All Versions
VersionLatest ReleaseRelease DateEOL DateDaysStatus
2201 2201 Mar 25, 2022 May 24, 2022 1639 days past EOL EOL
2201 Hotfix 1 2201 Hotfix 1 May 24, 2022 Jul 21, 2022 1581 days past EOL EOL
2201 Hotfix 2 2201 Hotfix 2 Jul 21, 2022 Dec 13, 2022 1436 days past EOL EOL
2210 2210 Dec 13, 2022 Mar 3, 2023 1356 days past EOL EOL
2210 Hotfix 1 2210 Hotfix 1 Mar 3, 2023 Aug 22, 2023 1184 days past EOL EOL
2210 Hotfix 2 2210 Hotfix 2 Aug 22, 2023 Feb 13, 2024 1009 days past EOL EOL
2210 Hotfix 3 2210 Hotfix 3 Feb 13, 2024 May 14, 2024 918 days past EOL EOL
2210 Hotfix 4 2210 Hotfix 4 May 14, 2024 Feb 11, 2025 645 days past EOL EOL
25.02 25.02 Feb 11, 2025 Apr 8, 2025 589 days past EOL EOL
25.04 25.04 Apr 8, 2025 Jul 8, 2025 498 days past EOL EOL
25.06 25.06 Jul 8, 2025 Sep 9, 2025 435 days past EOL EOL
25.09 25.09 Sep 9, 2025 Not published Past EOL EOL
26.01 26.01 Jan 13, 2026 Not published Past EOL EOL
26.01 CU1 26.01 CU1 Feb 10, 2026 Not published Past EOL EOL
26.08 26.08 Aug 31, 2026 TBD Supported Active
Spotted a date that disagrees with the vendor's own lifecycle page? Report it with the vendor's link → Every correction is published on the accuracy page.
Microsoft FSLogix EOL status badge Live EOL badge for your README — updates automatically at every build. [![Microsoft FSLogix EOL](https://img.shields.io/endpoint?url=https%3A%2F%2Fendoflife.ai%2Fbadge%2Fmicrosoft-fslogix.json)](https://endoflife.ai/microsoft-fslogix)

Microsoft FSLogix lifecycle status — the real story

Microsoft FSLogix is the profile software for Windows virtual desktop environments such as Azure Virtual Desktop: it keeps a user's profile and Office data in Profile and ODFC containers so that they follow the user between session hosts.

FSLogix follows Microsoft's Modern Lifecycle Policy and Microsoft does not back-port fixes: every change ships in a new release, and Microsoft requires customers to be on the latest release to be under support. On Microsoft's lifecycle page each release ends on the day the next one ships. Releases newer than that page's table come from the FSLogix release notes, which give a publication day and no end day, so a superseded release from the release notes is shown as out of support without a date.

In practice a session host image that is built once and left alone is out of support as soon as the next FSLogix release ships. Microsoft also removed support for 32-bit operating systems and for Windows Server 2012 R2 with the first version 3 release.

Microsoft FSLogix release and support pattern

Across the 15 release lines with a published release date, Microsoft FSLogix has shipped a new line roughly every 3 months (median interval). A line typically stays supported for about 3 months from its release to its end-of-life date (measured on the 11 lines with both dates published).

Of the 15 release lines tracked, 14 are past end of life and 1 is still within support; 3 are marked end of life without a published date. The newest line, 26.08, was released August 31, 2026. No end-of-life date is currently published for the 1 supported line.

Computed from the tracked release data at every build — the figures above are the dates in the table, restated, not an editorial estimate.

What does Microsoft FSLogix end of life mean for your organization?

When a version of Microsoft FSLogix reaches end of life, the vendor's standard security patches for that version stop. Vulnerabilities found after that date are still published on the National Vulnerability Database, exploit code often becomes public, and systems on that version stay exposed until they are upgraded or covered by extended support.

The CVE blind spot: A CVE-based scan does not show the accumulation of unpatched vulnerabilities in EOL software. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but the vendor's policy provides no patch for the ended version. This is one of the most dangerous gaps in enterprise security posture.

Organizations running EOL Microsoft FSLogix should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.

Your options when Microsoft FSLogix reaches end of life

There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.

OptionBest whenWatch out for
Move to a supported version The system will outlive the current version's support window and you can schedule the work Budget for compatibility testing, not just the upgrade itself — that is where the real cost sits
Replace the component The project is unmaintained, or a better-supported alternative exists The replacement has its own lifecycle and its own end-of-life date — you are changing vendors, not escaping the problem
Buy extended support Migration is genuinely underway but cannot finish before the deadline, or the workload is frozen by certification or a third-party application A bridge, not a destination — every year purchased is a year the migration still has to happen
Document accepted risk The system is isolated, short-lived, or scheduled for retirement Only defensible with real compensating controls and a written decision — auditors treat undocumented end-of-life software as a finding

How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.

Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.

Formalizing decisions like this across your estate? Our free EOL policy template is a ready-to-adopt policy with risk tiers, remediation SLAs, and audit mapping — no signup, free to use and share.

Extended Support Options

If you cannot migrate immediately, check whether the vendor or a third party sells extended support with security patches for your Microsoft FSLogix version; coverage varies by product and version. Where it exists it is a bridge, not a permanent solution — plan your migration in parallel.

endoflife.ai
Get Microsoft FSLogix Support Options

Microsoft FSLogix has 14 versions past end of life — security patches have stopped, but CVE disclosures haven't. Extended support past the official date exists for many products in this position — whether it exists for Microsoft FSLogix is exactly what we check. Tell us where to reach you and we'll reply with matched options and pricing guidance — or an honest "no vendor covers this."

Free · No obligation · Independent — we track the dates, vendors don't pay for placement · Dates verified against vendor sources
Frequently Asked Questions
What is the end-of-life date for Microsoft FSLogix?
See the full table above for all Microsoft FSLogix version EOL dates.
When is the Microsoft FSLogix support end date?
Each Microsoft FSLogix version has its own support end date — see the table above for every version's date.
What is the latest supported version of Microsoft FSLogix?
The latest active version of Microsoft FSLogix is 26.08. Always verify against the table above as support windows can change.
What happens when Microsoft FSLogix reaches end of life?
When Microsoft FSLogix reaches end of life, the vendor stops issuing security patches. Any CVEs disclosed after the EOL date accumulate with no vendor patch path — a growing attack surface that a CVE-based scan does not show. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give the date in advance.
How do I check if I'm running an EOL version of Microsoft FSLogix?
Check your current version against the table above. If your version's EOL date has passed, you are running unsupported software. You can also use the endoflife.ai Stack Scanner to check your entire dependency file at once.
Is there extended support available for EOL Microsoft FSLogix versions?
Some vendors offer extended support for EOL software. Contact the original vendor or check with enterprise support providers for options.

Related Products

✓ 26 of 26 lifecycle dates vendor-sourced · read from Microsoft (FSLogix lifecycle page and release notes) on 2026-11-18 · confidence: 26 high, 0 medium, 0 low (each version page shows where every date comes from) · provenance · Source: the vendor's own lifecycle pages (learn.microsoft.com) · Generated at build time · How we source data →
Microsoft FSLogix end-of-life status badge