That happened also with 10240 and it began cumulating up to 5 updates and then, bam, 10586 was released
I just use WSUS Offline once a month, let it make its iso and then run it on my systems. ping pow dung?
Updated to Windows 10 Build 10586.122 Using BorderSkin 0.3 with Aero Skin, and also using OldNewExplorer 1.1.7.0 they work ok. Transparency and Blur settings work ok in BorderSkin 0.3 as well.
Considering this update includes improvements to stuff like authentication and updates, analyze this to figure out if is it really worth the rest in the update, some updates may just do more bad an good, across the field, like obfuscation of our tweaks to block snooping and other stuff, they could sneak in some additional hosts-bypass DLLs and none would be the wiser, each update has to be decompressed and searched for key strings, and when you install updates you always scan it with Process Monitor and upload the saved PML report. (save only filtered results) Major part is you have to figure out which EXEs are used by the Update install process, i might be talking basics here but just to remind, it's definitely more than the usual ones for program installation and it's already like 5 there - for programs i use: setup.exe - install.exe - trustedinstaller.exe - msiexec.exe - installer.exe - System (sometimes some files/registry are created/modified using the System process not through the program that requested it) - Those are the base ones now each program may have it's own additional ones, for example Visual Studio I had to add vssetup.exe - vscommunity.exe - vbsetup.exe ... etc I'm still yet to finish my other work before I get deep into Win10 tweaking, I will provide such detailed reports when I do my own stuff, It's a lot of stuff I might specialize, we can't expect everyone to do everything but if nobody's going to do it then I will once I get going in a few weeks. Because if updates include all the good stuff with all the bad stuff it gets complicated. And I'm not even a guy trying to get stuff for free, I mean, when I start using Win10 I'm going to get a copy out of spite, so nobody can come to me and tell me I'm, I'm not reselling the mods, im not profiteering of their stuff, just not gonna use their defaults and their good for nothing cert/policy nags, and the registration/upd needs web access too so that falls into the snooping, so there's no point using the original dvd and key, i mean, when snowden came out, it was so funny when companies had to apologize to twitter users how it was all unfortunate and that their TOS/PRIVACY was ALL A JOKE ALL ALONG, they all share and sell data, CISA and other laws were pushed so hard to get this legally covered so they would be easier and no fear of lawsuit.
Analyzing all updates exactly all things they do so this doesn't go on and only found out years later. But I know people around here already doing this, it was just a reminder, I'm just lurking a bit before I get into it myself. I intend to modify a lot of GUI, such as windows, theme, start menu, icons, various registery settings around that, I don't want any update to mess that up or remove a hidden feature in registry, depending on the severity, an update might be a dealbreaker and if they include all the good fixes/improvements in the same update it becomes frustrating. For example, I want to have the "show desktop" button in the right corner of the taskbar, if this get's messed with it is a complete deal braker, I will redirect all my focus on getting this fixed before I continue with any other work in Windows. Also, MS said in future they may get rid of old-style setting dialogs, replacing them with crap-mobile style ones, we also need work on that (kind of a big deal) by either creating an app that restores them or a program that has it's own gui but then modifies the settings through itself. I also intend to remove anything that will bring up any of these weird tablet-themed popups, everything will be old fashioned or modified through batch/desktop shortcuts (for switch-type options) My biggest dillema is wether to wait longer for MS to churn out the updates and get it on when system is more polished (eg SP1) or go at it earlier to get more experience and possibly go through several remakes (as updates come out, when stuff goes wrong prolly have to redoit from a fresh updated install) Ofcourse this is all testing, I don't intend to use any of the installations in practise. And if the whole "windows as a service" thing, they might strategically release updates which work like a Totalitarian Tip Toe, which is you want to go to something which the public doesn't like, you don't go in one big jump, you go in hundred smaller jumps or steps (hence Stepping Stone Tactic), from A to B - from B to C ... from V to Z. So we must identify if some of these updates include something big enough that is contributing to the bad goal Z and already try to fix whatever they messed with and identify it ealier so it's known to others, and it is easier early when it's still a minor move towardy goal Z, because as updates go on, several steps might have already happened behind the scenes when most people will notice a big change, but most people weren't paying attention, just woke up some day and all these little changes over the years accumulated into one big annoying mess. Well I don't want to wait when that happens, and only then start figuring out and going back and I just know it's going to be harder then, not many people will have motivation, it's much easier to keep an eye now along the way and I apprecitate it very much. In other threads I see people already doing similar stuff, but I don't think we have a specific thread for it, well I'm not yet that deep into all, just a reminder, for example in the Telemetry thread it was reported a service name (a long name) was changed in an update to "DiagTrack" to make it seem less suspicious, tricks like that, but also everything else not just privacy ones.
You might want to try MiniTools in my sig, hide the update until you get/ or determine all clear I have mine set to notification mode, it warns me with sound that their are updates, it does not install them, I hide which one's I want, and install the others, the one's hidden stay hidden until you decide to install them.
I think maybe your biggest dillema will be if you ever try and do a repair function, DISM or Sfc, sets everthing back to default, how do you get around that I guess you could make 10 backup images a day