Had try this way(https://forums.mydigitallife.net/threads/windows-10-hotfix-repository.57050/page-65#post-1154312). When save modified Package_for_KB4537829.mum,It has been note that not right.All operation run with admin. Had try to modfiy and save in safe mode(F8).But the prompt is not right to save,too.
Thank you for your work on this project. I was able to successfully apply the February updates using BypassESU. I was also able to apply one additional update after installing KB4537829, so I do not believe that this update killed the Bypass on my system. I believe that one of the Jan 14 updates caused the Bypass to fail if it was executed after the Jan 14 updates were installed. I tested this by installing images before and after 1/14 and found that the Bypass will only work prior to installilng the Jan 14 updates. I even tried to purchase the ESU but could not find a source except for one company that wanted to charge me $70 per ESU license (instead of $50) with a 5 license purchase minimum, so it would have cost me $350 to continue receiving updates. Thank you again for working on this ! Hope this feedback is helpful.
Is there a goto page/post for finding out what security updates I need to install? Asking because of the February KB release. Best I could find was this post: https://forums.mydigitallife.net/th...pdates-eligibility.80606/page-62#post-1577571
wow this thread is now really crowded with endless noob-palaver, sorry +_+ and why the hell suddenly almost everyone installs Monthly Rollup and Security Only?! everyone who wanna "enjoy" additional MS "features", selects the first one. Nevertheless security updates are already included there. anyone else who can do without this additional MS-stuff, selects the "security-only" KB either ... or
Those July and September (2019) security-only updates you're referring to were aberrations, and signs of the increasing desperation of MS to wean users off of Windows 7 as their end of support deadline beckoned. But let's be real, 2 out of 40 (security-only) isn't like potentially 40 out of 40 (rollups). And in both those surreptitious cases, the fixes/corrections were relatively easy to perform, well, if you knew where to look (admittedly many would not have known this though). With that said, your point that this telemetry issue doesn't spin around security-only versus rollup patches alone is valid. A series of further, non-security related patches had to be avoided also, ones that MS regularly regurgitated at varying points. Certain tweaks needed to be implemented on each user's system to boot. So yes, a bit of education was/is required on this maddening issue. All of which underlines Microsoft's seeming inability to be candid and straight with their customers, and begs the question I asked in my last post but again: How much should you trust MS? One rule remains fixed and unchanged: the less telemetry you agree to, the better. Let those who can't be bothered learning how to avoid it be their hapless dupes. Why off topic? It's part of the clamor of why so many are looking to avoid Windows 10 - and heading here. That, and not wanting their computers turned into big screen smartphones that Microsoft controls!
I install the monthly rollups every time they're available. I was suspecting that MS might want to overwrite the new updates so even if i had the ESU installed, these re-appearing patches would make the pc non-updated. I did what you suggested, hid them.
Had the same problem. You have to manually install the January SSU KB4536952 which many of us did not receive through the normal WU.
According to what I also understood, your statements are correct. Personally, I will follow an advice from this thread : "It is urgent to wait for next month second Tuesday updates" ;-).
---↓--- Ianpac beat me to it. ↑ You should be golden after that. Back when you were on v.3, KB4490628, KB4474419, KB4523206 were the ones to be concerned with.
I had exactly the same experience. However, since I had already successfully installed everything I wanted, I used PowerRun 1.3 to re-edit the three .mum files back to their original form. Now KB4537829 is back in both locations, as it was before I used PowerRun. Sorry I can't be of any more help.
I'm not sure, but I assume that in regard to the comment I've marked in red, this explains why I was able to install all the Feb 2020 Updates correctly, even though I had already installed KB4537829.
You only need the bypass for the test KB. after that you can remove the bypass. Then, you can install the ESU updates including SSU. We will have to wait and see how long this trick will work before MS does a 'FIX' for it.
I was never offered KB4537829 (the ominous SSU that breaks the bypass) for my Win64Pro System, nor can I find it in Windows Update history. No Idea why this is so but it possibly saved me from not being able to install the February 11 rollup update, which went through flawlessly. BTW, I was probably one of the last to install the test update on using bypass v3. It seems that for those who successfully ran v3 before MS plugged the hole are not in need to run v4. Not sure, however, how long this state will persist as MS seems to be willing to break bypasses in short succession of their appearance.
You didn't get it on WU because you won't get ESU stage updates by WU. When you want to install all ESU updates you can do it this way: https://forums.mydigitallife.net/th...pdates-eligibility.80606/page-63#post-1577626
I got it neither offered via WU (which ist logical to me because bypass-ESU updates don't come with WU) nor can I see KB4537829 on the MS Windows Update history home page (I should have made clear that I was not referring to my personal Windows update history). So, what I see on Windows Update home page seems to be different from what some other user see. Not sure why this is so.