I am on english 17763.2237 64 bit, I'm trying to update the build so i'm on at least 1903 but from what you've said I'm assuming even 21H1 will work without deleting anything? I guess i'd go with an english 64x 21h1 build 19043.1237 assuming the upgrade will work correctly.
It does, since 16299.125 ESDs but you must use undocumented parameters Code: MediaCreationTool /Eula Accept /Retail /MediaLangCode en-us /MediaArch x64 /MediaEdition Enterprise
I know this (@mxman2k and i even started creating the original MCT tool for this a few years back, based on your info) but the average user doesn't.
Has there ever been a fix for Windows (always encountered this in LTSC, but wouldn't surprise me if it was just a 1809 bug overall) automatically changing default app associations every time it encounters a new file extension? It's always made installing a fresh LTSC 2019 system a pain because I need to wait forever for Windows to stop doing it's thing and leave my default apps alone.
That is an Enterprise 2019 LTSC overview post, providing all content info, download links, checksums (for all three officially released ISOs, not only the latest) and guidance how to create an uptodate Enterprise 2019 LTSC ISO.
I understand this but question is why so complicated/complex? Most people aren't OS geniuses and need basic Windows so a simple link with latest version and checksum would be perfect.
The post services all, techy users and newbe users. Not all want only the latest, not every post needs to contain already provided info and linking to the existing posts works fine for most.
Orange8756 I agree with you . Its over complicated and makes things dificult . Your not the first person to say it .
I get why the link to an "information" thread, but also understand his "complaint". When you have not been following those threads, and are just looking for an ISO, and get sent to one, it just looks like chain of links to unrelated or loosely related things. I follow most of it and still get lost in those convoluted info link to a link to link to another posts.
Hello, I am on the verge of losing my mind trying to fix my Nvidia drivers. Since I randomly started to get blue screens and memory failures related to it I decided to wipe my drivers and reinstall them. This brought me back to two years ago when I first installed LTSC and had to deal with the exact same hell of reinstalling drivers about 30 times and sifting through countless fruitless solutions. Every single attempt leads to the same thing - the installer fails due to "incompatibility" or I get the Microsoft Store Control Panel which does not open, even with the store manually enabled. I have tried every single route I could think of: Experience drivers -> store app; DDU -> Nvidia standard driver (newest/older/ancient); DDU -> Windows std. driver -> Nvidia std. driver; DDU -> Windows std. -> manual pnputil driver uninstall -> std. driver; DDU -> Windows std. -> Manual update through devmgr with .inf files (there are enough variants for my card there to go through one by one for at least two weeks); And probably countless more variations, with new/older versions, online/offline, safe/normal mode, with/without Experience. I cannot for the life of me remember what I did two years ago to actually fix this as I didn't update my post here. Please, someone give me hope, because I did enjoy the stability of using LTSC. But this process has taken ten years off my life and I am about to drop everything and just move onto a normal Windows installation. I am on a dual GTX 1060 (notebook) and Intel UHD 630 setup. Windows version 1809. Edit: This is a hardware problem exclusive to the Lenovo Legion Y530 line. There is no software fix.
Shot in the dark: Get the standard version (old style not dependent on the store) of the nvidia driver, not the DCH one?