See if you have these two services running: Function Discovery Provider Host Function Discovery Resource Publication For some reason these weren't starting up when browsing for network shares and they were unreachable in my 1803/1809 machines. Set them up to start automatically and these problems went away. SMB1.0 is disabled.
Are there any bugs with the Media Feature Packs? I don't see any other reason for MS to remove them from the official site otherwise. Especially considering they pulled them in less than 24 hours.
They pulled 1809/2019 LTSC2019 and everything related to it. Vanishing Media Feature packs = collateral damage.
All is still available on MVS, techbench and UUP, they only pulled the upgrade by ESD options (WU, UA, MCT), it seems (iirc the products.cab is pulled), and the mediafeaturepacks.
Hello @GodHand I was able to use your script and it works really well, thank you so much. Could you please describe each Powershell parameter? I would like to know which are needed and which are not. Probably you can add this to your github page, I was only able to get some information about the parameter -Registry. Is it possible for you to describe them in short words and tell us which are essential and which are not? -MetroApps "All": This seems to remove metro apps -SystemApps: This gives me the selection to remove System packages like BioEnrollment? -Packages: This gives me the selection to remove System packages like BioEnrollment? (Difference to SystemApps?) -OneDrive: ? -Drivers: ? -Registry "Hardened": Do you recommend to use the hardened setting or not? -DaRT: Is this one for debugging purposes only? -NetFx3 $true: Is it needed? Does this add Dot Net Framework 3 to Windows 10 iso? Not needed I guess? Sorry for asking, but the documentation is lacking for me right there. Best regards and keep up the great work!
I guess, when they pulled, they had the common user in mind, not the MDL Über-Guru. Let's rephrase: "Paused from mass distribution to guinea pigs users."
So it's safe to install the now pulled Media Feature Pack? No one seems to have had issues with it thus far. Edit: Just to add an issue I seem to have with LTSC 2019; I can't extract to replace files when extracting into a folder. I have to extract the file to my desktop and then add the extracted file into the originally intended folder to be able to Replace Files.
Why do people install N editions but must have the mfp's afterwards, just install the non N version from the start. Only people with licenses for N versions should install them, they are crippled by EU law, not a feature version.
So which is the best option LTSB/LTSC 2015/2016 or 2019? (A) Just as a desktop PC (B) For gamers. For me frame rates and game compatibility are of no concern but they will be for others. Historically since the release of XP the best release has been the first one, I suspect that is true with this edition of Windows. To me it seems that 2016 and 2019 are all about added bling at the expense of stability and performance, a deck of cards waiting to colapse. At the moment 2019 sounds very buggy, I am torn between 2015 and 2016 as my ongoing OS. I have used 2016 and liked it but is the original better?
Does the Media Feature Pack have a custom or selective install option? For instance, I need Media Foundation and codecs, but I don't want Skype installed.
i have 2015 on my mother inlaws box because it's good enough for her i would not use it here for mine over 2016.. it's rock solid for me if 2016 is ok on your specs i would use it at this time i have it on an old refurbished box
Definitely go for 2019 after it's stable. I have explained in older posts a lot of issues I have bumped into while running LTSB 2016 on gaming laptops. Haters will swear by it and dismiss any reports stating otherwise calling you names, but that was not my or my friends experience on multiple devices - from keyboard lights and buttons not working, to bluetooth headsets functioning intermittently, to external displays stutters or failing to pair, to wireless speed and drop issues on gigabit connection, to phantom micro-stutters in games, plus not having the patience anymore to deal with that outdated crap. But "muh, I got bloat on my pro startmenu" - "bitch, please". Just fire up a powershell/regedit and get rid of that pronto, or even better, use the best windows edition aka education and enjoy a modern os for better and for worse.
At the very top of the script is full list of parameters, what they do, any options assigned to them, examples of how to execute, notes, etc.
Yesterday I received a rather vintage system to experiment with. It's a Lenovo, Pentium D LGA775, Intel 945 chipset with 2GB of ram. Decided to put LTSC 1809 x86 on it. Already on the imaging state (I never use the normal setup, image manually from PE) I was surprised to see that it was way faster than normal. On this old system it took less than 3 minutes. After imaging, the footprint for x86 LTSC on the drive was less then 5GB. WTF?? After setting up complete office 2019 suite, a bunch of other programs, the footprint is still only 12GB. I´ve checked and double checked from PE and it's consistent. This is a pleasant surprise. There where some pitfalls of course, I'll name some of them. - Need latest KMS VL ALL (by abbodi) else it won't activate - Have to kill defender and it's nasty, I hope to remove it when MSMG comes out - Bunch of reg tweaks are not working anymore. Like "HideSCAHealth" systemwide (HKLM hive) is a no-go. Now you can only set it on the CU hive and with "DisableActionCenter" dword. - Background apps are still running even though the "DisableGlobalUser" reg key has been set - Show "This PC" on desktop reg tweak is not working anymore - Filetypes associations is a mess. I still couldn't choose the complete list of filetypes for a given app like in 1607. It requieres some manual work to get it setup right, but in the end it's worth it. I've encountered no serious issues. It feels even faster than 1607. For me it's worth it. Cheers.
LTSB was my OS for years, all other builds I tried were unstable. LTSC so far is as stable as LTSB but it's quicker in almost every way for me (1950x, 32GB RAM etc).
I've only one minor issue: Is there any way to set Windows Photo Viewer as the default image viewer in LTSC 2019? It's stuck on Paint and no way to choose Windows Photo Viewer, it stays on "Paint". It worked on LTSB 1607. Cheers.
Working fine here, after importing PhotoViewer.reg during setup https://forums.mydigitallife.net/posts/1382080/
Worked perfectly, somehow I missed your post Abbodi. Sorry about that. I imported the reg file with nsudo, TI all privileges enabled. Cheers.
