No practical difference,C stands for channel & B stands for branch.I guess channel sounds more professional nowadays.
I think I will stick with Pro for a month or so and then go for 2019, when all/most of the bugs are gone, KMS tools have been updated, and tools like Winaero and WDP have had a chance to catch up. Is Defender really that bad in this relase? I hate using third party AVs, most are terrible.
as a gamer, who updates his hardware regularly, you will be forced to use the newer windows 10 versions anyway.. e.g. NVIDIAs pascal generation does not work on LTSB 2015 and NVIDIAs new turing generation does not work on LTSB 2016. -andy-
That's even better. Speaking of powerrun, I just checked the registry of my freshly installed Windows LTSC x86, and noticed that a lot of tweaks weren't present. I'm using a firstlogon script to install programs and set registry entries. Before, this worked fine because firstlogon runs as admin so no problems with permissions. But 1809 seems different. Can someone (who uses firstlogon.cmd) confirm that it now needs special permissions? Programs install just fine, but some registry entries, mainly policies, don't get imported. I could try to launch the script by means of powerrun or nsudo, but perhaps that is overkill. I'd rather understand why this happens and if MS made changes to this method of unattended installation. Edit: I may be onto something here. My "firstlogon.cmd" contains abbreviations for HKEY_LOCAL_MACHINE: HKLM and HKEY_CURRENT_USER: HKCU. Now I'm reading on technet that when defining a policy, abbreviations are not allowed/supported. Does this mean that MS finally enforces this rule, as the technet document is from a couple of years ago? In short, is it allowed/supported to use HKLM and HKCU in a cmd file? Cheers.
not true. they work. maybe you need to install the drivers in compatibility mode, so the check for the windows version doesn't trigger and cancel the setup. but you can install the drivers and the card works. those cards also work on windows 7 and 8.1.
With en_windows_10_enterprise_ltsc_2019_x64_dvd_74865958.iso.(non N) I can't seem to find 'Advanced text settings'. To set the size of fonts. Like in 2016 ltsb.:
I have a license key that can be used for Win 10 Enterprise LTSB 2016. Can I use this key for Win 10 LTSC 2019 edition?
I could test a pascal card on windows 10 v1507, but I was sure that there was no way to make it work. and regarding turing.. have you tested this? I don't have a turing card for testing, because they are too expensive, but the driver inf clearly requires windows 10 v1709 as a minimum. EDIT: also, how would compatibility mode work here? that is normally used to install older drivers on newer windows versions, but in this case it's the other way around.. you need to install a newer driver on an older windows version. -andy-
you are right, i don't got a turing for testing purposes but i did try it with pascal cards and even tho the nvidia driver required a higher windows version then 1511, it still worked to install them. same with some amd drivers on 1607. "oh no it's not supported" "oh no the driver won't install" well try to install them in compatibility mode or directly install them from the device manager and your good to go. of course you won't have any rtx options on lower windows versions then 1809, but the turing cards and drivers WILL work, even on older windows versions, just like they will work on windows 7.
I just had a look through the inf file of driver 416.16 and the pascal IDs are listed under [NVIDIA_Devices.NTamd64.10.0...16299], [NVIDIA_Devices.NTamd64.10.0...14310] and [NVIDIA_Devices.NTamd64.10.0], so this should, indeed, work on v1507/LTSB 2015 (at least by installing the driver manually, if the setup tries to block it). I will try this out. but the newer turing (RTX) card IDs are only listed under [NVIDIA_Devices.NTamd64.10.0...16299], so the driver should not work on lower versions than v1709, even by going through the device manager. sadly, I cannot test this. also, one could modify the inf and install the driver manually with driver signature verification turned off. this would be kind of interesting to try out -andy-
Bro, can you please let me know which version of NTLITE you used to remove windows defender from LTSC 2019 ?. Thank you.
Nope, LTSC 2019 needs new keys. Like you also can't use keys from 2015 on 2016 version, they will always require a new set of keys .