Windows 10 Enterprise LTSC 2019/2021

Download = Windows 10 Enterprise LTSC 2019 (x64) - DVD (English) = en_windows_10_enterprise_ltsc_2019_x64_dvd_5795bb03.iso

Code:

Name: en_windows_10_enterprise_ltsc_2019_x64_dvd_5795bb03.iso
Size: 4330432512 bytes (4129 MiB)
CRC32: D68A78C3
CRC64: E113A663485137B4
SHA256: B570DDFDC4672F4629A95316563DF923BD834AEC657DE5D4CA7C7EF9B58DF2B1
SHA1: 615A77ECD40E82D5D69DC9DA5C6A6E1265F88E28
BLAKE2sp: C696B98C2CDD3999470C9B735E00319C98B2ACF8299382E7E3903CFC39491197

Verify ISO by Hashtag = https://www.heidoc.net/php/myvsdump.php


Download Windows 10 Enterprise LTSC 2021

Mirror

Download Windows 10 Enterprise LTSC IoT 2021

Other languages download links


==========================================================
To add the Microsoft Store, simply download the below ZIP file, ensure that the file is not blocked by right clicking on it, go to Properties, then look at the bottom if it says this file came from the internet bla bla bla, just hit the UNBLOCK button then Apply then OK. Then extract it and run Add-Store.cmd as Admin

Store-LTSC2019-2021-11-17

Store-LTSC2021-2021-11-17

How To:

Right-click and run Add-Store.cmd as administrator (do not run from powershell prompt)

Remarks:

- If you don't want (Store Purchase/App Installer/Xbox Identity), remove its Bundle before running Add-Store.cmd

- To install latest Microsoft Store bundle
Add-Store-Dynamic

- Store require Media Feature Pack for Enterprise LTSC N edition

- To remove Store and/or all apps:

Spoiler

execute in powershell as administrator

All apps

Code:

Get-AppXPackage | Foreach {Remove-AppxPackage $_.PackageFullName}
Get-AppxProvisionedPackage -Online | Remove-AppxProvisionedPackage -Online

Specific (Store)

Code:

Get-AppXPackage -Name "*WindowsStore*" | Foreach {Remove-AppxPackage $_.PackageFullName}
Get-AppxProvisionedPackage -Online | Where DisplayName -eq Microsoft.WindowsStore | Remove-AppxProvisionedPackage -Online

Xbox
Xbox Identity Provider
Xbox Console Companion
Xbox Game Bar
Xbox Game Bar Plugin

 

Yup. All part of the arm-twisting bastards' scam. I wonder how much the asshats at Micro$lop paid the Kool-Aid drinking shills at UL/3DMark to do that?

Anyhoo, now you know why I waste drive space for a cancer version of Windows OS X and why I am slowly working my way toward Linux and giving up benching. I am getting closer to telling them to kiss my hind end. Not there yet, but that day is coming. They've just about ruined everything related to computers that I care about.

 

And you get no points on the bot. Wasted energy being angry on the paid shills at UL/3DMark. Let them have it. Less people who spend time on it just mean this test will go in the history books as a failed product.

 

UL/Futuremark still can't fix own flawed software. It's on level with the new and shiny OS from Redmond HQ.

https://www.3dmark.com/fs/22807470

 

Do you still recommend following the 'Clean Install' and 'Tweaks & Fixes' thread even with LTSC?

 

Yes

 

Unless you're down with the sickness. The lyrics are very fitting for the Windows 10 feces invasion.

 

well at least LTSC 2019 feels better (and slightly faster) than using LTSB 2015/2016

 

I almost spit coffee all over my laptop while reading this! hahaha

 

Hi, is this version 1809 ?
I know there is these iso file, which is Windows 10 2004 enterprise, which is nearly the same as LTSC lacking long term support as far as I understand :
https://techjourney.net/windows-10-enterprise-version-2004-evaluation-released-for-90-days-trial/
I need to try one of these of a VM.

 

Yes, it is 1809, which is far superior to 2004 (which is garbage). I haven't found anything (not even one thing, sorry to say,) that is good about 2004.

LTSC has zero bloat. No Store and app crap. No Edge or Cortana trash. Just Windows. You can manually add the UWP filth, but that is kind of like adding just a little bit of feces to a batch of brownies. You might not smell it or taste it, but you know it's in there and the brownies are corrupted even though it may not be obvious to everyone eating them.

 

Yes I know, I'm looking for a more recent LTSC than 1809, the "xbox game pass" application need at least 1903 to launch :/
I'm running LTSC 1809 for more than a year on my Precision M6700 with no other issue so far.
You should update your OS, 17763.107 is a build from november 2018

 

It is unfortunate that you need the XBOX Game Pass and even more unfortunate (and evil) that they manipulate customers in that manner. I will no longer purchase Micro$oft Studios game titles because of that. If it is not available on a Steam, Origin, GOG, Uplay, Epic or Bethesda game client then I can live without it.

No need to update my OS. I am running LTSC with no updates and Windows 7 SP1 with no updates after 2014. I prefer having a stable system that delivers higher performance and one that I am in control of. Updates result in the exact opposite of that. Newer and "more secure" (tongue in cheek) Windows builds offer me nothing of value and I have lost my appetite for Micro$lop's nonsense. They do nothing right in my eyes.

 

Keep in mind that the LTSC Trial ISO is just a trial and cannot be activated using a genuine key if you later on decide to keep it. The ISO in the OP is the full edition which can be activated.

 

Latest official version is Windows 10 Enterprise LTSC 2019 (1809). And this is a smart move. At least Microsoft is able to understand that thei just can't throw out a new LTSC version each year. All know that if they pushed out one or two versions a year, it would water it down to a huge unstable mess as the regular versions... https://www.windowslatest.com/2020/06/22/whats-next-for-windows-10/

 

yeah even the Area-51m that I have came with Build 1809. one of the most stable builds.

 

After 1809 we got 1903 and with some candy the small 1909 package. And now 2004. And coming fall edition (small package) is in short same version as May Update. Doomed to fail. Even 1809 failed at release but have worked ok the latest months. Latest and greatest may work ok at end of life.

Of course Windows won't be stable as long they move on after release of the latest. They should stop with this "Windows as a service" nonsense.

" Microsoft has already started working on the next two versions" of Windows 10 and a new variant called ‘ Windows 10X‘. It’s all part of what Microsoft is referring to as ‘Windows as a service’, which basically means that there won’t be a new operating system every year to get new features, security patches or support for modern hardware.

 

Once I installed Windows 10 Threshold 1 build 10.0. 10240, felt like I bought a new taptop on steroids! It was nothing like today, it was even faster than Windows 7 due to the support for newer hardware BUT with nothing of telemetry compared to today's builds. Unfortunately it needs its own set of drivers because even though it is Windows 10, as we know each new build needs its own drivers thank to Microsoft's stupid way of making these updates.

Have you a Threshold?

 

Yeah. Never update directly to new and flawed. Hold on to old as long as possible. And always do a clean install.


Windows 10 update addresses a fundamental flaw in Windows Setup Windowslatest.com | July 12, 2020

When you upgrade Windows to the next version, sometimes Windows may create a new recovery partition if it detects that there is no sufficient space on your recovery partition. Windows is not able to extend

 

I wonder which build will come on my Area-51m R2, 1909 or 2004?

For the R1:

 

I don't think they dare release it with 2004.

 

The fact that this even exists as a download from a third party is as scary as hell and emphasizes the fact that Dell is the least trustworthy manufacturer in the world. Not only do they embed their own filth from the factory, they have a plan in place to keep that feces embedded even with a clean install. Building a product that relies on its proprietary garbage or UWP trash apps to function is also deplorable. People should be running another direction as fast as they can and never looking back.

 

The Dell images come pre-installed with Dell/Alienware Update and SupportAssist! The perfect disaster combo!

 

Exactly. Pre-installed viruses. That kind of behavior is exemplary of why everything they do should be questioned and second-guessed, and any promises they make should be taken with a pinch of salt. Both companies (Dell and MSI) are really messed up.

 

"SupportAssist", really? Can't wait for SupportAssistHelpTotallyUseful -_-

 

If only you'd seen Alienware Support's Twitter Account. Everything can be solved by the Voodoo Magic SupportAssist!

"Computer feeling slow? SupportAssist can help"

"Having slow network? SupportAssist will fix it!"

"Run SupportAssist to ensure you have the latest driver and BIOS to cripple your machine!"

"Feel lethargic?No Problem! Run SupportAssist it will make you a Cappuccino"

 

Yeah....

 

My best advice to anyone considering a Dell product:

 

Me reading this after ordering a 6.5K Dell taptop:



Poopoosan =

 

I know. Not my cup of tea. You have been warned before.

 

That thing better run as cool as a cucumber with a price tag like that.

 

That's more than I spent for my nice low-mileage used car a couple of years ago. And, two of them are just a little bit less than what I paid for my wife's brand new car in December.

Edit: That's also substantially more than what I spent on my desktop and Tongfang turdbook combined. Even if I include the three monitors, keyboards, mice, etc.

 

Really puts things in perspective when looking at it that way

 

Are you facing dead screen pixels? Update your BIOS to fix it!

https://twitter.com/i/status/1282360382267547648

 

Is that an official video? That's really "helpful"... Surprised they didn't recommend turning it off and on again

 

New updates for 1809 (17763.1339):

SSU (https://support.microsoft.com/help/4558997):
Version: 17763.1337.1.1

Code:

http://download.windowsupdate.com/d/msdownload/update/software/secu/2020/07/windows10.0-kb4558997-x64_9c9a7137d609ef46898bba95e204e6c867a9aa12.msu

CU (https://support.microsoft.com/help/4558998):

Code:

http://download.windowsupdate.com/c/msdownload/update/software/secu/2020/07/windows10.0-kb4558998-x64_6da68fe659dacb747458ab3a431c3546ce7765b5.msu

DotnetCU 3.5 & 4.8:
Info: http://support.microsoft.com/kb/4566516
Version:

Code:

http://download.windowsupdate.com/c/msdownload/update/software/secu/2020/06/windows10.0-kb4565632-x64-ndp48_dbab0773d0b336c20b095d9144120d487992066c.msu

Flash (http://support.microsoft.com/kb/):

Code:

No Updates

 

Cancer-free stability is hard to beat. Stability and performance always trump "security" for me. I cannot identify the last time a cumulative update improved stability or performance, so I ignore them.

 

I took the liberty to rewrite your nice post. Not that you're right about Dell. You were right on point But the pict also reminds me about Microsoft's latest and greatest. Hence my post.


[Updated] And It Begins… All the Windows 10 v2004 Known Issues as Confirmed by Microsoft Itself wccftech.com

It is unclear why Microsoft had to wait until after the launch to release this list of known issues and why they couldn't be addressed when Windows 10 version 2004 was being tested. Since the list is already live, it cannot be due to customer complaints either as it's too early for that process to start. We can only hope that process doesn't end up revealing even more bugs in the just-released Windows 10 May 2020 Update.

 

Posted this earlier 'hidden' in another topic, maybe useful to revive it here for those evaluating ltsc. A more or less informative MS blog, but the very interesting user comments are worth a read (imo).

https://techcommunity.microsoft.com...-is-it-and-when-should-it-be-used/ba-p/293181

 

July 21, 2020—KB4559003 (OS Build 17763.1369) Preview

As usual a very long list with fixes!

Highlights

• Updates an issue that might cause the Magnifier to stop working in Microsoft Excel in certain scenarios. As a result, Microsoft Excel might also stop working.

Improvements and fixes

• Addresses an issue in Microsoft Edge IE mode that occurs when you open multiple documents from a SharePoint site.
• Addresses an issue in Microsoft Edge IE mode that occurs when you browse using anchor links.
• Addresses an issue that might cause the Magnifier to stop working in Microsoft Excel in certain scenarios. As a result, Microsoft Excel might also stop working.
• Addresses an issue that might cause apps that use the custom text wrapping function to stop working in certain scenarios.
• Addresses an issue that prevents you from opening documents in SharePoint in certain scenarios.
• Addresses a reliability issue in dxgkrnl.sys that might cause stop error 0x50 PAGE_FAULT_IN_NONPAGED_AREA.
• Addresses an issue that might increase the number of handles when using Microsoft Outlook.
• Addresses an issue that causes an application to flicker or stop responding when sharing the application using Microsoft Teams.
• Addresses an issue that incorrectly calculates long path addresses that have Unicode characters outside of the current system.
• Addresses an issue that prevents Windows 8.1 apps from projecting to a secondary display when those apps use the StartProjectingAsync API.
• Addresses an issue that prevents Event Viewer from saving a full set of filtered events when you filter by the date.
• Addresses an issue that continues to display the previous username hint in the smart card sign in box after a different user has used the machine with domain credentials.
• Addresses an issue that causes lsass.exe to stop working on a terminal server when you enable Remote Credential Guard. The exception code is 0xc0000374.
• Addresses an issue that prevents Microsoft Defender Advanced Threat Protection (ATP) from applying file exclusions in some cases, which leads to application compatibility issues.
• Addresses an issue that causes automatic investigations to fail in Microsoft Defender ATP.
• Improves Microsoft Defender ATP's ability to identify malicious code injection activities.
• Addresses an issue that causes the network controller (NC) host agent to incorrectly report that a virtual machine (VM) has moved.
• Addresses an issue that might cause a deadlock in the Wired AutoConfig (dot3svc) service.
• Addresses an issue that might prevent applications from running as expected on Active Directory Federation Services 2019 (AD FS 2019) clients. This occurs when applications use an iFrame during non-interactive authentication requests and receive X-Frame-Options set to DENY.
• Addresses an issue that incorrectly reports Lightweight Directory Access Protocol (LDAP) sessions as unsecure sessions in Event ID 2889. This occurs when the LDAP session is authenticated and sealed with a Simple Authentication and Security Layer (SASL) method.
• Updates the message users receive that tells them to check their phone for notifications from the Microsoft Authenticator application. This message only appears when authentication is done using the AD FS Azure Multi-Factor Authentication (MFA) adapter.
• Updates dcpromo.exe to remove the "Network access: Restrict clients allowed to make remote calls to SAM" policy on member servers when they are promoted to domain controllers. This allows clients to make Security Accounts Manager (SAM) connections to these domain controllers.
• Addresses an issue that might cause Windows 10 devices that enable Credential Guard to fail authentication requests when they use the machine certificate.
• Addresses an issue that might cause stop error 7E in nfssvr.sys on servers running the Network File System (NFS) service.
• Addresses an issue that discards the Remote Desktop Gateway Secure Sockets Layer (SSL) Bridging settings and resets them to the default.
• Addresses an issue that prevents you from updating the port number for HTTPS or the User Datagram Protocol (UDP) settings in the Remote Desktop Gateway Manager.
• Addresses an issue that occurs when a standalone Remote Desktop Session Host (RDSH) server allows multiple sessions per user. After disconnecting from a session, if you attempt to reconnect to the original session, the server creates a new session instead.
• Addresses an issue that causes the Windows Management Instrumentation (WMI) Provider Host (WmiPrvSE.exe) to leak registry key handles when querying Win32_RDCentralPublishedDeploymentSettings.
• Addresses an issue that logs a Distributed Component Object Model (DCOM) error in the System event log when the Distributed File System (DFS) Replication service is started.
• Addresses an issue that might cause the Microsoft Remote Assistance process (msra.exe) to stop working when a user is receiving assistance during a computer session. The error is 0xc0000005 or 0xc0000409.
• Addresses an issue that causes Server Message Block (SMB) to incorrectly use the original, cached non-Continuous Available handle to a file, which becomes invalid after a network error or storage failover. As a result, applications to fail with errors such as STATUS_UNEXPECTED_NETWORK_ERROR.
• Addresses an issue in SMB that causes Windows Server 2019 to stop working when using 100 GB network interface cards (NIC). This only applies to Storage Spaces Direct (S2D) and SMB Daemon (SMBD) scenarios.

If you installed earlier updates, only the new fixes contained in this package will be downloaded and installed on your device.

Manual download link KB4559003


July 21, 2020 - KB4562901 Cumulative Update Preview for .NET Framework 3.5 and 4.8 for Windows 10 Version 1809 and Windows Server 2019

Manual download link KB4562901

 

Has anyone here done anything to show that there is an advantage to these higher tier versions of windows over standard editions? I would be curious what benefit windows enterprise or workstation has to a more casual power user such as myself. Stability maybe?

 

There is no "microsoft garbarge" in enterprise/LTSC version like every consumer version got

 

This (below)

Well said, Brother @TheQuentincc

 

Amen to that.

 

Hey guys, thanks to you i also made the jump to Windows 10 LTSC and i am quite satisfied without the M$ crap apps. I purchased an LTSC key from ebay (did the same for M$ Office 2019) and all good so far. Now i tried to do a fresh install of Windows 10 LTSC and i am getting an error message during Windows activation (the key is already used, same for Office).
I read somewhere that i have to 'un-license' the prior install first using the commands slmgr /upk and slmgr /cpky then i can re-enter the key in a fresh install. Can anyone please confirm if this is the correct procedure? (i just don't want to go through another fresh install and end up with the same error again).
As for Office, is there a way to 'un-license' so that i can use the key on the fresh install?
Thank you in advance folks.

 

You need to do a phone activation.

For Windows, type slui4 in the run dialogue box and hit enter

For Office, I also got a Professional Plus 2019 key but I haven't tried it yet as I am waiting for my new laptop, see if there is anything like troubleshoot activation where you can select phone activation.

 

Congrats and welcome to the LTSC elitist family. This is the only edition of Windows 10 that is worth a damn, and you're super-smart for recognizing that.

Yes, that is correct. Phone activation is the way to go. Before installing Office, back up the Windows activation with Micro$oft Toolkit. As long as you avoid updating the BIOS (which is the smart thing to do) you should be able to restore it if you ever clean install again. You can still do phone activation again later, but it's easier to not have to deal with any of that nonsense. If you install Office it will back up that activation as well, but the chance is good that the Windows activation restore will fail, so just don't do it. Back it up first, then install Office.

For Office activation, I like to do it this way. Run this command: setup.exe /configure config.xml using this file in the same folder as the 64-bit Office setup.exe

Code:

<Configuration>
<Add OfficeClientEdition="64" Channel="Targeted">
    <Product ID="Proplus2019Retail" PIDKEY="XXXXX-XXXXX-XXXXX-XXXXX-XXXXX">
      <Language ID="en-US" />
      <ExcludeApp ID="Groove" />
      <ExcludeApp ID="Lync" />
      <ExcludeApp ID="OneNote" />
      <ExcludeApp ID="OneDrive" />
    </Product>
    <Product ID="ProofingTools">
      <Language ID="en-US" />
    </Product>
</Add>
<Display Level="Full" AcceptEULA="TRUE" />
<Updates Enabled="TRUE" Channel="Targeted" />
</Configuration>

Save as config.xml and replace the X's with your product key. This will omit the totally worthless feces (Groove, Lync/Skype, OneNote, and OneDrive) and install only the meaningful applications in the Office Suite (Word, Excel, Access, Outlook, PowerPoint, Publisher, etc.).

 

Pretty neat stuff there, thanks @Spartan@HIDevolution and @Mr. Fox . I can confirm that the phone method works for windows activation (still i tried to unregister the previous Windows install but still got the error with key already used, phone activation solved that).

 

But also no feature updates until the next LTSC release, which is years away. I *need* individual DPI app scaling for apps that don't play nicely with 4k screens. And sadly that feature is not in the LTSC release yet as far as I know. Same with HAGS/WDDM 2.7 for GPUs. While not beneficial yet, Ampere may change that and it's only available on the latest consumer version update.

 

Yeah, it's a Choice between the Plague and Cholera. None of them is tempting.