If i integrate KB3105514 in my offline image and enable dotnetfx3 via dism, unmount/commit, and install it, wu will download KB3097617 (expected behaviour before kb3105514 whas released) but that triggers an error (also if KB3097617 is integrated alongside kb3105514).
today... Security Update for Internet Explorer Flash Player for Windows 10 Insider Preview October Update for x64-based Systems (KB3105216) Update Windows 10 Insider Preview October Update for x64-based Systems (KB3106638)
notepad.exe It's interesting that flash update KB3105216 have coreos-revision 10.0.10565.41736 (seems a mistake) but the later (newer) one KB3106638 updates notepad (and coreos-revision) to 10.0.10565.16384 rtm candidate? usually, insider builds updates have small delta versions (i.e. 10.0.10565.3) Spoiler coreos-revision = UBR value in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion
I will test it again but I doublechecked it with abbodi1406's w10 updates list and he didn't mark kb3097617 as "removed" and added kb3105514 to his list (check his sig). My findings were: /resetbase doesn't remove/deinstall it and when dotnetfx3 is enabled after installing both kb's it will try to redownload 3097617 because 3105514 isn't downloadable via wu.
What are u talking about? As you can see he doesn't discard the old one. I make releases for other people. That's not about what i want but what they need (after installation a usable and complete uptodate windows install).
The newer 16393 iso contains 2 updates extra: 1452 (servicing stack) and 1455 (cumulative sept. 5), this is done by ms itself so they are "permanent". It's the same case if you use 8.1 update 1 or 8.1 update 1 november rollup iso. /resetbase normally does the removing of superseeded updates for you and it can only be done on the offline mounted wim if 1452 and 1455 are integrated. The same as when the zdp (683) whas released and it made the pre-release > "rtm", at that time you also could resetbase the wim, the later cu's could not be resetbased because they set the pending flag. Edit: Adding only 1452 and 1455 to the 16384 build wim does not have the /resetbase option, it's only possible on the new 16393 builds.
By consulting the history of Windows updates (10.0.10240.16384), I find attempts last days of Office 2013 while I have the 2016 version of VLSC whose days have been installed update. Yet there are no traces of Office 2013 that I uninstalled a month ago. What's the problem ? Thank you.
Am I to understand that if I did a clean install of Build 1693 and went straight to the list of installed updates, these two updates (1452 & 1455) would not be visible.. I understand the concept of ResetBase and the need for it in Windows 8 for the maintaining of an up to date image. But with windows 10, things currently appear to be a little different... in so much, that.. One only needs the installation media and access to current Required Updates (2, maybe 3, depending on ones needs). When dealing with one or two machines it hardly constitutes a great deal of effort, or time for that matter. Obviously, Horses for courses....
The two mentioned updates are still visible in the list of installed updates but all updates after those 2 can be resetbased. If you release win iso's to the public (of all kind of intelligence levels) it's (to me) best to have all updates integrated, a release with the txt: "Mwah, i didn't see the need to integrate update xxx and xxx because i decide that for you". kb..1449, 687 and 686 are automaticly downloaded during OOBE. What people want to do after installing windows is not my problem but it, what ever they do, is mostly the cause of many angry windows users when it goes wrong (it's never their own fault/usage but always windows' fault).
I completely agree, in my experience the vast majority of people DO tend to abdicate responsibility... but I would think that this Forum aims to meet the needs of those..with at least a modicum of comprehension of what they are doing. As much as I know, there is still more to know (and as much as I'd like to think otherwise, I will never Know it all)