Servicing stack updates are needed for security-only updates likewise, not just cumulative updates and monthly rollups. They're recommended to be installed whenever they're released to provide fixes to the servicing stack, the component in the OS which provides the grease for the facilitation and integration of updates. They shouldn't be put off once released, and should be installed before additional cumulative, rollup or security-only updates are incorporated. If not, you may receive installation errors from the latest released updates, or even Windows failing to start properly after assimilating a new one.
Thats it. Hope no changes from MS. There cant be that many of us doing this. There isn't a swarm of people talking about it. The whole western hemisphere knows this post is here. I haven't found many more.
Is the Lite version specific to Windows 7? Tried it on Server 2008 and it said "ERROR: The system was unable to find the specified registry key or value."
And you won't. Read the first post, updates must be downloaded and applied manually. The Lite and normal BypassESU v4 from first post are for Windows 7 and Server 2008 R2 only (aka Windows NT 6.1). Post #2 offers a BypassESU for Windows Vista and Server 2008 (aka Windows NT 6.0).
This was Windows Home Server 2011 which is based on 2008 R2, hmm.... The v4 bypass worked on another system running the same OS. Perhaps the Lite version won't work for me with this OS
So I can just manually do what light would do? What's the point of removing V4 after? Will the updates not install with it present or is it simply housekeeping?
The latter. BypassESUv4 is not required anymore when Lite (or the full test update) is present. Besides, the February SSU blocks BypassESUv4 (but not Lite). So, ATM, Lite > BypassESU v4.
Thanks, man. You were right: I meant online-installer, not offline. I tried what you said, searching for 'KB452' in Installed Updates, and I gave it awhile to run, but only one item came up, not KB4528069. (I also tried it with 'KB453' and several items came up, so I think that makes it look like search in Installed Updates is working at least to some degree. But it can't find KB4528069 for some reason.) I tried running Online-Installer again & I got the same message as before. Do you (or anyone else) have any other ideas as to how to get rid of KB4528069? Thanks.
When i said that it should be tested, i meant on VM because it's not recommanded to use both versions (KB4528069-Lite + original KB4528069) So now that KB4528069-Lite has been installed, uninstall bypass, you don"t need it anymore. You don't have to worry about not seeing KB4528069 in the installed updates list. i cannot explain why the update is not visible in the updates list but what i know for sure is that it is installed in the system as the message that you showed first clearly indicated it.
Works fine when done correctly but not usefull for anything. As explained before, the lite version doesn't install the update, only the captured results of installing it (the actual Lite part of it), to suppress further ESU checks.
Sorry for my incompetence, I have Windows 7 Ultimate, but some things are not clear to me, let's see if I guess: first start online-installer.bat; then I carry out the Offline Integration procedure up to point 4, where I manually install the updates and then go to step 5. Does all this need to be done every time updates arrive? Does the install.wim file refer to the Windows 7 CD? Kindly explain to me the procedure to mount this file? I thank.