Despite the message, i am still getting windows defender updates at least through windows update (just checked now and it updated the security definitions) which means THE MESSAGE IS PROBABLY JUST A NAG we will be seeing for the entire run of the ESU program (Microsoft being Microsoft). I am running W10 22H2 Enterprise 19045.6456, activated with TSForge. (Sorry for the off-topic post)
I realize we won't really know if TSforge is actually working until next month. In the meantime, could someone clarify what should be shown on the Windows Script Host window that appears after running the 'slmgr.vbs /dlv' command in Win10 Pro? Should it mention something about ESU add-ons? I have run the TSforge powershell ESU activation but when I run the 'slmgr.vbs /dlv' command, there is no mention of ESU in the Windows Script Host popup. I saw what @Enthousiast posted for his Win10 Enterprise install and his Script Host popup has an entry for each year of ESU Add-ons but mine has nothing like that. Thanks
Well, that was easy. It looks like it didn't stick the first time around. After running it again, the Windows Script Host popup has all the ESU confirmations. Thanks
Can the TSforge ESU work for domain-joined PCs? Works great on standalone PCs, but when I tried it on domain PCs - nothing.
I think question could (also) be: Can it be used in a business domain environment? That would turn into a legal question i'm sure a company's IT departement would not be to happy about.
I agree - not talking about a business environment, they can afford to pay for the licenses. This is for non-commercial environments.
It only activates ESU for various Windows 10 editions. There are still upgrades such as W11 24H2, 25H2 ...
Windows 23H2 will not get ESU, as you can simply upgrade to a supported branch like 24H2 or 25H2. MS does not care for CPUs without SSE4.2/POPCNT.
CPUs without SSE 4.2 go earlier than 2010 and below 1st gen Core Intels and AMD Bulldozer, why would they even get Windows 11, they will be at 100% utilization just browsing anyway. Those legacy CPUs should be using Windows 10, preferably LTSC
Tested Serwer 2008 R2 activated ESU and and... Monthly October 2025 WU downloaded without problems. IE I saw has updated too automatically in that, but... Net 4x ESU isn't detect via WU. I will check Windows serwer 2012 R2 too. Actually I try fix to detect net. I think still need ESU prep + bypass 13f.
To me only net don't detect. Can you tell me, how WU detected you net ? Sorry for my ask but maybe i didn't made something or I don't know. I made updates , turned on net 3.5 because mas need that, activate ESU and monthly update was detected but net no. With net stopped after December 2022. If I can one please. You can give steps how you made to update that all from clean installed Server 2008 R2 ? Me with bonus install newest SCEP for have AV too. But I am sure any policies or he to block if only net didn't updated.
Question ... For what I read ... you can install "normal" Windows 10 (Pro) and with some modification tohe the registry, do a in place upgrade to Windwos 10 LTSC IoT, giving updates up to 2032 while keeping the latest build of the OS + Microsoft store. But I also found that TsForge can change the actuall installation licence to the same version. So ... Can I just install Windows 10 Pro + switch licence with TsForge for Windows 10 LTST IoT + Activate with either HWID or KMS and then have the OS updated until 2032 with the lates build + Windows store, all without having to do a inplace upgrade from Windows 10 Prod to LTSC IoT ? Thanks!
I run a AD at home (my kid hates me for putting GPO, account lockout, logon time and all - lol) and I have a few Windows 10 PC that all had the ESU activation from TSForge on them and it sems to works!