Failed attempt. While Windows was snappy as heck, as if it was Windows 7 on steroids, most my drivers failed to install with a message that the driver doesn't support this OS. Heck I couldn't even install the latest nCrapia Drivers! This Windows 10 BS is horrid. It's like you're installing an entirely different OS not Windows 10 with these driver compatibilities. Now every build of 10 requires its own set of drivers. Imagine the poor n00bs who don't kow all this stuff when their brand new laptop stops working properly after a Windows Build update due to drivers
Exactly You only forgot that you are behaving that way I'm installing the latest January/2018 patch on a Pro-N 1511 w/o any problem, while I'm writing. Check by yourself if you don't trust me, I'm not going to post any screenshot to proof the obvious.
If the sku is not mentioned in the aplicability list of the update (update,mum) it won't install. Just like with Pro-WS 16299.15 won't get updates.
Here's "ApplicabilityInfo" for KB4075200 (latest update for 1511): "Windows 10.0 Client;Windows 10.0 Server Core;Windows 10.0 Server;Windows 10.0 WinPE;" It does install on 1511 Pro.
I used abbodi1406's installer script to install KB4075200 and it seemed to have installed it. At least, I see a lot of .mum and .cat files from KB4075200 in \Windows\servicing\Packages and .cat files in \Windows\System32\catroot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE} after running it. But you are right Enthousiast- now that I look closer, I don't see that the update is installed. The lack of errors/warnings from the installer script and seeing the files listed in the above folders led me to think it was installed. Apologies for the confusion.
It can be "integrated" to Pro or Home, because they can be upgraded to Education (and Enterprise for Pro) so the update package is "staged" for upgrade Spoiler my script is innocent
Getting back to the ApplicabilityInfo of the update- you were right about that, Enthousiast. My knowledge of updates is apparently getting outdated now with Win10. abbodi1406 gave me some great info that I'll share so others can benefit from his knowledge as well: --------- pkgProperties.txt [where I got that ApplicabilityInfo above from] is guidance. It correctly defines the applicable product type, but not the editions. The actual applicability is update.mum (and the sub-packages). [as Enthousiast said also] Since first Windows 10 version 1507, cumulative updates are restricted by parent editions in update.mum (and some sub-packages like Edge). That makes it easy to cut support of certain editions (EOL or unofficial edition like EnterpriseGN). In version 1709, all updates are now restricted by edition, including Flash and servicing stack, and even tiny updates like KB4058043. --------- Credit for the above goes to @abbodi1406. I appreciate him passing along this great info. --Edit: put an @ sign in name
Myself I'm on 1511, i have tested later releases but none were as good as 1511. Security updates don't really bother me There 1gb iso difference between 1511 and 1709, Microsoft are just adding more and more s**t into Windows. I have paid for my pro version of wibdows 10 and its filled up with so much s**t spying some junk apps I would never use. Actually 1511 is the latest windows version I will ever use and won't do any upgrades anymore, had enough of it. The moment 1511 will be to old that's the moment I will upgrade my pc to Linux. Atm my 1511 uses only 500mb of ram and 30 windows processes running in the background and thatst how it should be.
