I'm seeing a lot of negative experiences in this thread when using the newest LTSC - so after quite a few days of using it on my primary system, I thought i'd leave my review! Install went without a single issue. System was up and running very quickly. Installed 40~ programs, multiple games, everything launched and performed as expected. No lag, no FPS issues (same FPS as 1607). The task manager bug is kind of annoying. Also the file associations not sticking bug is also annoying. I'm honestly very happy with 2019 LTSC. Everything has just... worked. I haven't had any real issues and everything is smooth. Everyone's experience will vary! You'll have to test on your own systems to see how it works for you. Don't take my word, or anyone elses word, as to how the experience is! Everyone has different configurations. Specs: i7 4790k, 1080 TI, 32GB RAM, SSD / HDD / HDD / HDD / HDD
Maybe I'm just being a bit thick but I can't get 1809 LTSC to see any other PCs on my network. I initially built the en-GB version using the svf file. The SHA1 of the converted ISO matched the published version. Clean installed it in a VM ok and all looked ok. If I set up a shared folder on LTSC, I can see that folder on other PCs, but I can't see any other PCs on LTSC. I've no problem with 1809 pro seeing other PCs so not sure what's going on with LTSC. Equally, I've not had a problem with 1607 LTSB seeing other PCs. Just for an experiment, I tried upgrading a working 1607 LTSB with the LTSC ISO. Upgrade went ok, but still the same network problem. As a last resort, I tried building the EN-US version of LTSC from the svf file. Installed OK but same network problem - can't see other PCs on network. Anyone any ideas - is there a hidden setting I'm missing?
control panel > programs > activate windows feautures > enable SMB 1.0. also didn't worked for me without activating SMB. apparently this was in 1803 already the case, for what ever reason. don't know why they don't activate it right from the start if people need this
Did you leave the planet when there were Hostage virusses around which abused some bugs in smb1.0 and MSFT decided to disable it by default, after they fixed the vulnerabilities by CU?
no i did not. how can they release 1803 with a unfixed security bug and instead of fixing it just disable it? and if it's fixed now in 1809, why is it still disabled by default? what should people do who need to see other computers in their network?
But also SMB 1.0 as protocol is so outdated and unsecured for long time that's why they disabled it. But why they hiding real problem with "solution" as disabling smb 1.0 is very stupid and very ridiculous. @freiwald sorry I maybe double posted your anwser as well, didn't saw it
Well, as I suspected, enabling SMB1 did absolutely nothing. It should only be required if you're trying to talk to old PCs running XP or old NAS boxes which only support SMB1. What I'm seeing is that 1809 Pro works fine - it can see other Win 10 PCs on the network and they can see it. With LTSC 1809 however, other PCs can see a shared folder on LTSC, but the LTSC PC can't see any share on other Win 10 PCs. Even typing \\name-of-PC into the explorer address bar doesn't bring anything up.
First I'd like to thank whoever backed up the media feature pack I needed that ! Also I've updated to the 1809 via upgrade from 1607 LTSB, and suddenly the store (that I added via the script I found on these forums) no longer works, and non of the classic methods fix it. Anyone has an idea?
Thanks for that. It worked! LTSC can now see shares on other PCs. However, it looks like it's a bug, because according to the Group Policy, "This policy setting determines if the SMB client will allow insecure guest logons to an SMB server. If you enable this policy setting or if you do not configure this policy setting, the SMB client will allow insecure guest logons. If you disable this policy setting, the SMB client will reject insecure guest logons." So leaving it unconfigured should be the same as Enabling it. Certainly leaving it unconfigured on 1809 Pro works fine. Anyway, thanks again.