#1 I wasn't criticizing you or your work, NOT AT ALL, just asked to understand the meaning of the word "repack" in such context. I hoped for a completely different installer, just like the one for WMC where one unofficial installer is DISM based, while another is script based (hence works everywhere), it's not the case. I'm fine anyway. #2 You have no idea about who I'm, about my age and about my job. So assuming I'm a "standard user" and even that I currently use the LTSB 2015 is just a your assumption, based on nothing. #3 No matter of point #2, yes I think that not only the standard user should use the LTSB release, but MUST, if he cares a bit about its privacy and about a lean and stable OS. #4 LTSB2016/19/22 are all supported by the latest .net installer, so the distinctions both yours and by MS are just arbitrary. #5 I assume that MS thinks to 2015 as a sort of (supported) beta of 2016, and while most people won't even notice the difference between the two, there are some substantial differences under the hood that in some scenarios can make the 2016 (or later) flavor unusable where 2015 works flawlessly.
At the outset: it's my last answer for you. "Repack" means "repacking of any software", but it does not means that it should be changed at all. You also don't know who I am, you can ask @Mr.X or @mdl052020 or any other user here, so, please don't "jump" with such texts. "standard user" means "standard computer user" who bought the computer/laptop in the market, but not about you. I can can buy LTSB in the market (for one person)? Strange, I didn't know about it... The rest about you are talking is about the Corporation OS you use, so my comment is not needed here.
When you go for the updatepacks, you simply put the .net48 WA addon next to the updatepack and when you run the updatepack it will automatically install the WA addon. All addons can be found here: https://forums.mydigitallife.net/th...-install-wim-esd-creation.79421/#post-1516362 All info about the updatepacks can be found here: https://forums.mydigitallife.net/th...egrate-hotfixes-into-win7-distribution.45005/ And best to rename the pack to:
Same as i suggested already which i also got to know long ago to be very sure from a post of enthy on MDL. So Credits to him But the way he suggested is more clear then mine . User will be confused in my suggestion but crystal cleared in enthy's.
Thank you all if you MDLers Updating the system went flawlessly. Obviously thanks to your knowledge and intelligence. Geez I'm a n00b lately.
You said "windows 7 x86". I would imagine it's a low-spec machine, like less than 4gb RAM, ancient cpu with poor IPC performance. In which case, office 2010-2013-2016/19 would be fine but the newer the version, the heavier it will get. Maybe not too noticeably heavy, but still heavy.