GodHand updated his script to 3.1.2.7. The "regionlanguage" policy is back, means that it will not be possible to change keyboards. Besides that, the policy is duplicated at line 1919 and line 1932. Toast notifications are still being set to 0, means no "safe to remove USB" messages and other important system messages. The *LTSC vs *LTSC* has not been corrected, nor the setupcomplete lines 2750 and 2751, those commands still error out. Cheers.
I just did a quick install of LTSC to check for differences from 2016 and noticed Windows Defender is no longer shown in the control panel. Trying to run a scan in the security settings does nothing. Also, trying to check for virus definitions from the tray icon pops a message about resource not being available. Is this normal? Edit: Nevermind, looking at the Group Policy, nothing was configured, so I assumed it was okay. For some reason the registry for that policy was set to disabled.
Guys, MSMG Toolkit was updated yesterday to version 8.9! Highlights: + Support for Windows 10 Redstone 5 / Server 2019 Source OS. + Windows 10 Insider Preview WADK (v10.0.18272.1000) Tools. + All Apps/Components are now removed fully using the Manual Method (Only for Windows 10 Redstone 5 en-GB and en-US Source Images). For LTSC 2019: Windows Apps : Nothing there to remove System Apps : The below components are not present, the reset can be removed. Edge, OneDrive, PPIProjection, SecureAssessmentBrowser, Store, XboxIdentityProvider
The business iso doesn't contain LTSC. When do you get that message? and be aware that it's better to pre-integrate the most current updates.
Standard message atm when trying to install/upgrade online . Needed to check online myself since my VMs mostly install offline so i didn't notice any of these .
Don't install LTSC, install Enterprise.... kinda defeating the object of running LTSC if you want to install all the store apps lol
Nah! Some still don't seem to get it's the licensing period that matters for a lot of users, not the missing 'bloat' (that actually isn't all bloat, there is indeed some usablity hidden in some apps).
For me the biggest advantage of LTSC is that it doesn't receive feature updates, therefore all my tweaks will not be resetted every 6 months, i also like that LTSC includes some Win32 programs by default, such as the Windows 7's Calculator. I understand that some people want to install Store on LTSC, 1809 is the newest build right now, so they can play UWP games from the Store for example, i think another advantage is that on LTSC the Store won't install sponsored apps by itself and pin them to Start Menu like it does in normal versions (stuff like Candy Crush, Minecraft, Disney Magic Kingdoms and other sponsored adware bloat), but i haven't checked that.
In 1607 store apps required MSA binding so i didn't use them. Now with MSA binding being optional, i tested the mail integration with local account and it works indeed pretty satisfying. Never had similiar results using 3rd party solutions, now they are part of system notifications and therefor easily accessable . Additionally Edge is a way better fall-back browser than IE.
Ah well not for me, reason I ran LTSB and now LTSC is because it is pre-debloated, saves me the hack job later on, nothing in those apps I will ever want, and tbh it is a joke that even Enterprise gets games pre-installed or at least pre-pinned ready for install
My friends, majority uses their riggs for online shooters, also enjoyed this fact when i introduced LTSB/C to them. Matter of taste. For that reason i prefer untouched install media and do all the tweaks (automated) at a later stage according to what the user needs/wants.
Yeah I get so excited when Candy Crush is being installed automatically, so easy and it gets pinned also. Cheers.
Dear fellow LTSB & LTSC Users! Would anyone know how to get LTSC 2019 to open images with Windows Photo Viewer? I like using this photo viewer a lot! However... since installing Windows 10 LTSC 2019 I can't get it to open images. It won't appear in the "Default Programs" list for images... Also, right-clicking an image & selecting "Open With..." & then selecting the Windows Photo Viewer app & then clicking "Apply" doesn't work for me either... Anyone know a workaround? Thanks for your time in reading this post P.S. The Windows Photo Viewer app may be made visible in program lists in Windows 10 via a registry modification.
GodHand's script is so useful that I tend to forgive the *usually* trivial error's I find, like the duplicated 'regionlanguage' code lines (which have been around forever!). Having followed his GitHub project on and off for a year, I notice the errors do eventually get corrected. Still ... I imagine it feels a bit disheartening to have a nontrivial, easy to implement, code solution ignored! I'm not sure if a PM or using GetHub might get a better outcome? It's not very multi-language friendly to leave the the things you've pointed out broken. Don't expect GodHand to change 'personal preferences' like Toast notifications. I also turn Toast notifications back on, but some people hate-hate-hate them! I now make all my 'personal preferences' registry changes online. I used to modify his script directly, but I was having issues getting OO to work with LTSC 2019 so now I severely limit my modifications of his script. I even turn back on things like the duplicated 'regionlanguage' online... maybe i should share my script? Obviously, right now, you *have* to modify the script just to get it to work with your OEM Spanish image! I have added your prior post(s) with your solutions to using his script with a Spanish language OEM ISO and, if you don't mind, I'll add this one as well. FYI, I continue to update my post and have started a script that lets you add new registry changes and update an LTSC pre-treated OO install. For example I've installed to real HW LTSC/OO 3.1.2.6 and my online code will update my PC's registry to OO 3.1.2.7.
@TheStutch: Sure, add what you like and see fit. I'd rather not bother the author, other than posting my findings here on the board. If he doesn't pick it up, that's OK. Either way I'm very grateful that he made it available to the community. It's awesome. Maybe my findings can help others to run and adjust the script so they won't encounter the same issues as I did. Cheers.