massgrave/massgrave.dev
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update FAQ

Browse Source
This commit is contained in:
WindowsAddict
2025-10-23 05:48:32 +05:30
parent 820604128a
commit a0a95cc259
2 changed files with 17 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
docs/faq.md
View File

@@ -44,6 +44,13 @@ Check the [troubleshooting guide](troubleshoot.md) for help.
![image](./assets/Your-device-is-no-longer-receiving-security-updates.png) ![image](./assets/Your-device-is-no-longer-receiving-security-updates.png)
:::info
- The **fix** below is applicable to Windows 10 **LTSC 2021 only**.
- This visual bug is still [**not fixed for Commercial ESU-activated editions**](tsforge.md#windows-10-esu-faq).
:::
This is a **visual bug** that started appearing on October 15, 2025. This is a **visual bug** that started appearing on October 15, 2025.
Microsoft released a **fix** the next day for the 64-bit Windows version (32-bit LTSC is still showing the EOS message); simply select "Check for updates" in Windows Update, and the end-of-support message will disappear. Microsoft released a **fix** the next day for the 64-bit Windows version (32-bit LTSC is still showing the EOS message); simply select "Check for updates" in Windows Update, and the end-of-support message will disappear.
@@ -59,6 +66,7 @@ Microsoft released a **fix** the next day for the 64-bit Windows version (32-bit
> :: If telemetry or system files are blocked through the firewall, you need to remove those rules or reset the firewall rules with the command below > :: If telemetry or system files are blocked through the firewall, you need to remove those rules or reset the firewall rules with the command below
> >
> netsh advfirewall reset > netsh advfirewall reset
>
> ``` > ```
> If you are using Pi-hole, a hosts file, or any other firewall to block telemetry, make sure the following URL is **not** blocked: > If you are using Pi-hole, a hosts file, or any other firewall to block telemetry, make sure the following URL is **not** blocked:
> `settings-win.data.microsoft.com` > `settings-win.data.microsoft.com`

15
docs/tsforge.md
View File

@@ -259,16 +259,17 @@ This activation method does not work if a phone license is not available or if l
#### I activated ESU with the TSforge, but the Windows Update page in Settings still saying "Your device is no longer receiving security updates." Why? #### I activated ESU with the TSforge, but the Windows Update page in Settings still saying "Your device is no longer receiving security updates." Why?
Microsoft provides Extended Security Updates (ESU) through several channels, such as CommercialAzureESU, CommercialW365ESU, **CommercialKeybasedESU**, and **ConsumerESU**.
TSforge activates the [Commercial Key-based ESU](https://learn.microsoft.com/en-us/windows/whats-new/enable-extended-security-updates#get-the-product-keys-for-activating-extended-security-update-esu-licenses), which is intended for use by administrators in business environments.
The Windows Update page in Settings is currently showing the incorrect status below to **all CommercialKeybasedESU users**.
![image](./assets/Your-device-is-no-longer-receiving-security-updates.png) ![image](./assets/Your-device-is-no-longer-receiving-security-updates.png)
Microsoft provides Extended Security Updates (ESU) through several channels, such as CommercialAzureESU, CommercialW365ESU, **CommercialKeybasedESU**, and **ConsumerESU**.
TSforge activates the [Commercial Key-based ESU](https://learn.microsoft.com/en-us/windows/whats-new/enable-extended-security-updates#get-the-product-keys-for-activating-extended-security-update-esu-licenses), which is intended for use by administrators in business environments.
The Windows Update page in Settings currently checks only whether a user is enrolled in Consumer ESU and fails to account for **all Commercial ESU** users (Azure, W365, and key-based).
**It’s just a visual bug**. Your ESU is activated correctly. Hopefully, Microsoft will fix it in the upcoming updates. **It’s just a visual bug**. Your ESU is activated correctly. Hopefully, Microsoft will fix it in the upcoming updates.
---
#### How can I check if TSforge ESU is activated? #### How can I check if TSforge ESU is activated?
According to the official [Microsoft documentation](https://learn.microsoft.com/en-us/windows/whats-new/enable-extended-security-updates#install-and-activate-the-esu-key), you can verify the status of a Commercial Key-based ESU activation by running the following command in Command Prompt: According to the official [Microsoft documentation](https://learn.microsoft.com/en-us/windows/whats-new/enable-extended-security-updates#install-and-activate-the-esu-key), you can verify the status of a Commercial Key-based ESU activation by running the following command in Command Prompt:
@@ -281,6 +282,8 @@ For a shorter output, use
You can also run "Check Activation Status" option in MAS script. You can also run "Check Activation Status" option in MAS script.
---
#### What does it mean when the script says, "Windows Update can receive 1-3 years of ESU. 4-6 years ESU is not officially supported, but it might be useful"? #### What does it mean when the script says, "Windows Update can receive 1-3 years of ESU. 4-6 years ESU is not officially supported, but it might be useful"?
Microsoft officially announced that Extended Security Updates (ESU) would be available for only 3 years. However, ESU licenses actually exist for up to 6 years. Microsoft officially announced that Extended Security Updates (ESU) would be available for only 3 years. However, ESU licenses actually exist for up to 6 years.