From 27c2c3516c6ee7e14e097d06da6e58142ab94a02 Mon Sep 17 00:00:00 2001
From: WindowsAddict
Date: Thu, 8 May 2025 04:53:32 +0530
Subject: Fix Microsoft links

---
 docs/oem-folder.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

(limited to 'docs/oem-folder.md')

diff --git a/docs/oem-folder.md b/docs/oem-folder.md
index e80d609..0d8dcb1 100644
--- a/docs/oem-folder.md
+++ b/docs/oem-folder.md
@@ -9,7 +9,7 @@ To create a pre-activated Windows installation ISO, do the following:
 
 :::warning
 
--   On Windows 8 and later, [**running setupcomplete.cmd is disabled**](https://learn.microsoft.com/windows-hardware/manufacture/desktop/add-a-custom-script-to-windows-setup?view=windows-11#windows-setup-scripts) if the default installed key for the edition is from the OEM channel, except for Enterprise editions and Windows Server.
+-   On Windows 8 and later, [**running setupcomplete.cmd is disabled**](https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/add-a-custom-script-to-windows-setup?view=windows-11#windows-setup-scripts) if the default installed key for the edition is from the OEM channel, except for Enterprise editions and Windows Server.
 -	However, in Windows 10, IoT Enterprise editions were not included in the Enterprise category list during the installation process. As a result, Enterprise with an OEM key can handle setupcomplete.cmd, but IoT Enterprise (LTSC) cannot. This was fixed in later Windows 11 versions.
 -   In Windows 10 IoT Enterprise (LTSC), you can resolve this issue by using the Non-IoT Windows 10 Enterprise LTSC ISO. In this case, the HWID method in preactivation will install the IoT LTSC key to change the edition and enable HWID activation.  
 -   In Windows 11 IoT Enterprise (LTSC), it works fine as expected by default.
-- 
cgit v1.2.3