Deprecation Notice received - Yet the server is current on updates.

Question

Deprecation Notice received - Yet the server is current on updates.

pierre shiraziefard 65

What do I do, where do I go? Screenshot 2026-06-11 091946

-date.

Manish Deshpande 6,915 Reputation points Microsoft External Staff Moderator

2026-06-11T14:11:37.5166667+00:00
Hello @pierre shiraziefard Great question and a very common source of confusion. The short answer is: 'You're up to date' in Windows Update and receiving a Deprecation Notice are actually two separate things, and both can be true at the same time.

Windows Update only confirms that your server has received the latest cumulative patches and security fixes available for your current OS version. It says nothing about whether that OS version is still within Microsoft's support lifecycle.

A Deprecation Notice is issued at the product lifecycle level — meaning Microsoft is signaling that either:

The Windows Server version you're running is approaching or has already reached End of Support (Mainstream or Extended), or

A specific feature or protocol in use on your server (e.g., NTLM, TLS 1.0/1.1, SMBv1) has been formally deprecated.

Being fully patched doesn't extend your support window — it just means you're protected within whatever window remains.

Identify your exact OS version Run 'winver' from Run (Win+R) or go to Settings > System > About. Note the full version number and build.

Check your support lifecycle Cross-reference your version against the official Microsoft Lifecycle page: https://learn.microsoft.com/en-us/lifecycle/products/?terms=windows+server

Review deprecated/removed features If the notice is feature-specific rather than OS-level, this page lists everything Microsoft has deprecated or removed by Windows Server version:

https://learn.microsoft.com/en-us/windows-server/get-started/removed-deprecated-features-windows-server

If your OS is nearing EOL, you have two paths: • Upgrade to Windows Server 2022 or 2025 (recommended long-term): https://learn.microsoft.com/en-us/windows-server/get-started/upgrade-overview • Enroll in Extended Security Updates (ESU) as a short-term bridge while you plan the migration: https://learn.microsoft.com/en-us/windows-server/get-started/extended-security-updates-overview

Dig into the Event Viewer for specifics Navigate to: Event Viewer > Applications and Services Logs > Microsoft > Windows Look for any warning events that reference the specific deprecated component — this will tell you exactly what triggered the notice.

Conclusion :
Your server being 'up to date' is a good sign, but it's not a substitute for being on a supported OS version. Think of it this way: Windows Update keeps your house secure, but a Deprecation Notice means the landlord is retiring the building.

Thanks,
Manish.
Manish Deshpande 6,915 Reputation points Microsoft External Staff Moderator

2026-06-12T12:12:28.0466667+00:00

Hello @pierre shiraziefard

I wanted to check if my last response made sense. I’d be glad to assist further or explain anything in more detail and please accept as Yes and upvote if the answer is helpful so that it can help others in the community.
pierre shiraziefard 65 Reputation points

2026-06-12T15:09:26.8733333+00:00

Yes, thank you.
Manish Deshpande 6,915 Reputation points Microsoft External Staff Moderator

2026-06-12T18:06:10.61+00:00

Hello @pierre shiraziefard

Thank you for your query regarding the .NET 6 deprecation.

As .NET 6 has reached End of Support, the associated Windows Server images (including those used in VM/VMSS scenarios) are being deprecated. While your existing VMs/VMSS instances will continue running without immediate impact, they will no longer receive security updates, which may introduce security and compliance risks over time.

Additionally, future operations such as new deployments, reimage, or VMSS scale-out may be affected as these images are phased out.

Recommended action: We suggest migrating to supported images (for example, updated Windows Server images with supported .NET versions like .NET 8). For VMSS, this would involve updating the image reference and performing a rolling upgrade to minimize disruption.

After June 9_th_ 2026:

No new version of the images that include OS and .NET 6 security patches will be provided.

After Feb 9_th_ 2027:

New deployments, scale-out operations, and reimage operations will no longer be supported using these images.

Thanks,
Manish.

1 answer

Your answer

Manish Deshpande 6,915 Reputation points Microsoft External Staff Moderator

2026-06-12T12:12:28.0466667+00:00

Hello @pierre shiraziefard

I wanted to check if my last response made sense. I’d be glad to assist further or explain anything in more detail and please accept as Yes and upvote if the answer is helpful so that it can help others in the community.
pierre shiraziefard 65 Reputation points

2026-06-12T15:09:26.8733333+00:00

Yes, thank you.
Manish Deshpande 6,915 Reputation points Microsoft External Staff Moderator

2026-06-12T18:06:10.61+00:00

Hello @pierre shiraziefard

Thank you for your query regarding the .NET 6 deprecation.

As .NET 6 has reached End of Support, the associated Windows Server images (including those used in VM/VMSS scenarios) are being deprecated. While your existing VMs/VMSS instances will continue running without immediate impact, they will no longer receive security updates, which may introduce security and compliance risks over time.

Additionally, future operations such as new deployments, reimage, or VMSS scale-out may be affected as these images are phased out.

Recommended action: We suggest migrating to supported images (for example, updated Windows Server images with supported .NET versions like .NET 8). For VMSS, this would involve updating the image reference and performing a rolling upgrade to minimize disruption.

After June 9_th_ 2026:

No new version of the images that include OS and .NET 6 security patches will be provided.

After Feb 9_th_ 2027:

New deployments, scale-out operations, and reimage operations will no longer be supported using these images.

Thanks,
Manish.

Answer 1

The deprecation notice is unrelated to whether the Windows Server OS is fully patched. It refers to Azure Marketplace image deprecation, which affects only how new VMs or scale‑set instances can be created from that image, not the update status of the existing VM.

When an Azure Marketplace image is deprecated:

Existing VMs created from that image continue to run normally and can still be started, stopped, restarted, deallocated, and redeployed.
OS updates inside the VM (Windows Update) continue to work as usual; being “up to date” in Windows Update is expected.
After the image’s enforcement date, the only blocked operations are:
- Creating new VMs or VMSS instances from that specific deprecated image version.
- Reimaging VMs from that image.
- VM scale‑set scale‑out that needs new instances from the deprecated image.

Required actions:

Identify the image and version the VM or scale set is using.
Plan to move to a supported image:
- For single VMs, create a new VM from a current, non‑deprecated Marketplace image and migrate workloads/data.
- For VM scale sets, update the model to use a supported image (for example, a newer version or “latest”) and roll out an upgrade.
Complete the migration before the enforcement date in the deprecation notice so that future deployments and scale‑out are not blocked.

There is nothing further to do on the existing server’s Windows Update side; the work is to plan and migrate to a non‑deprecated Azure image for any future deployments.

References:

Deprecated images FAQ

Share via

Deprecation Notice received - Yet the server is current on updates.

1 answer

Your answer