Replies

Thanks for your suggestion Paul T,

I have downloaded, installed and run WUmgr as you suggested and clicked the search button, but it doesn’t come up with anything that I cannot already see and know via Windows Update (WU).

I’m thinking, perhaps that’s not so surprising because WU is persistently telling me that I’m currently up to date and as I understand it, WUmgr is really only running WU anyway so why would it be any different?  So far as I know, I am up to date . . . so actually I should not be expecting any new 21H2-related updates to be delivered at this point, only that WU should surely be offering me the option to upgrade to 22H2.  Is my thinking correct?

(One thing that WUmgr’s update history tells me that WU’s update history does not is an event that happened two days ago: “9PB1QWVW0R95-Microsoft.WindowsAppRuntime.1.4 Update;ScanForUpdates Failed (0x80240034)” but perhaps that was a transient error that has now been overcome – or could it be relevant?).

 

Thanks for that suggestion Susan.

However, I have today installed and run InControl by “taking control”, changing the Win11 release box from 21H2 to 22H2, and then using Windows Update to “Check for updates”, however WU continues to say “You’re up to date” and is still not offering me the option of upgrading to 22H2.  I have tried this both in the “You’re in control” and “Release control” states to no effect.

Am I doing this right, and should I expect an immediate reaction from WU do you think? – I assume I should be leaving it in the “You’re in control” state from now on (?).

Is there some way of interrogating the WU system (a log perhaps) so that a reason (if any) for not being offered 22H2 may be revealed?

Thanks and all ideas gratefully received.

 

 

Thanks Susan,

I look forward to seeing what you dig up.

I think the two things that are odd are:-

(1) that the 2021-05 CU Preview for .NET comes out after the 2021-05 CU (non-Preview) for .NET – surely it should be called the 2021-06 CU Preview for .NET ?

(2) that .NET Preview updates are automatically installed at all for users who are either not registered Windows ‘insiders’ or who have chosen not to optionally install them if offered – I would expect only the most recent non-Preview .NET updates to be installed automatically for such users, such as myself.

These two behaviours for .NET Preview updates are inconsistent with the way Windows Preview updates are installed vs. optionally offered, and doesn’t achieve the desired outcome for monthly updating when un-pausing at the appropriate point in the month.

Thank you, b AskWoody MVP, I must have missed seeing that valuable 10 April post from Susan at the time.

Another thought – are there any reasons for not simply downloading any particular MS365 app update you want from the MS Update Catalog site (providing it’s the relevant ‘channel’ of course), or would that conflict in some way with MS365’s own updating mechansims?

(BTW – I’m a relatively new subscriber to AskWoody, what does your status as an AW MVP mean and what does it stand for?).

 

Thanks for your helpful reply, LH.

I like your approach or method for determining when to do MS365 (aka Ofiice365) monthly updates and will start to do something similar.

However, although as you say, v2104 does mean April, according to MS Update Catalog it was first released in non-preview form on 29 April, not in early April, and in preview form on 19 April, it is the new “Feature Release”.

i.e. I believe each new monthly “Feature Release” tends to come out near the end of the month it relates to, not near the beginning of it?

Thus, as I understand it, the AskWoody Master Patch List’s most recent recommendation (29 April) is to update to the most recent release of v2103 (which was first released in non-preview form on 30 March and has had several revisions “Resolving Issues” not rolling out new features, leading up to the apparently final one on 23 April – which is the one I would have hoped to be able to update to now).  v2105 will probably be released at the end of May as I see it.

Trouble is, final v2103 (stable, issues resolved, widely used & tested) was superseded more-or-less immediately by v2104 (new untested features) so there was no time to catch the last v2103 and defere v2104! – hence my question, is it possible somehow easily to update to v2103 not V2104, which I feel the AskWoody Master Patch List, if it were to be revised as of now, would advise “defer”?

Hope I’m making sense, please let me know if you think I have still got it wrong.

Thanks.

 

Hi Susan, and all.

I’m running Win10 Home 21H02 and MS Office365 Click to Run Current Channel, and normally update Win10 via Windows Update (after un-pausing), and update Office365 in-app from Office Account, by re-enabling updates.  I do not allow receiving of other MS products when updating Windows (which in my experience doesn’t work anyway for Office365 – you have to update it separately now?).

So … I’m all ready to update my paused (‘disabled’) Office 365 Current Channel v2102 to the latest v2103 (now 13901.20462 04/23) per your Master Patch List recommendation, but according to MS that has already(!) been superseded by the first NON-preview v2104 (13929.20296 04/29), for which I guess you would be saying “defer”?

Please would you help me to understand how I can update to that last Office v2103, when I’m almost certain that if I let Office update rip (by re-enabling Office updates) it will give me Office v2104 which is exactly what I was trying to avoid by disabling updates.  I didn’t expect that to appear until the first Tuesday of the month, per previous experience.  Maybe I’m worrying unduly but would welcome your thoughts/knowledge.  v2104 is what we would expect to go for towards the end of May before v2105 comes along, surely?

Thanks so much in advance for any tips you can give.

 

Ah thanks PKCano for that explanation – much appreciated – I did wonder at the time why the release notes for both 19041 & 19042 builds are covered by the same MS KB number.

I downloaded the ISO using the MS <MediaCreationTool20H2.exe> which is why I was so surprised to see the version represented as 2004 in the build information shown by DSIM.

I am currently running 1909, so if I understand you correctly, that means I have the choice to use the same “squirrelled” ISO image to either upgrade from 1909 to 2004 (since AFAIK 2004 is no longer available via Windows Update), or to skip 2004 entirely and upgrade from 1909 to 20H2 (i.e. after 20H2 is replaced soon by 21H1 on Windows Update, which is the reason Susan suggested “squirelling” now) – is that right?

… and if so, at which stage of the ISO installation process am I offered the option to leave the EP (AKA “20H2 Enablement Package” I believe) ON or to switch it OFF, depending on which of the two destination versions I choose (i.e. 20H2 or 2004 respectively)?

Thanks for your continued help.

I don’t want to alarm anyone, but I just downloaded and saved what I though was going to be the Win10 20H2 ISO using the MS Windows Media Creation Tool.

During the download, the <products.xml> file at  $Windows.~WS\Sources apparently correctly showed that the build would be 19042.631 (i.e. the Win10 Home x64 version 20H2 build made available on 19 Nov 2020), however, after the download had completed I decided to check what I had actually received, by mounting the ISO and using the MS DSIM Tool to interrogate the <install.esd> file, only to find that it is actually (according to the DSIM result) 19041.631 **NOTE 19041 NOT 19042** which is the Win10 Home x64 version 2004 build made available on 19 Nov 2020 !

My first instinct is to assume I am doing something wrong, so please someone, put me right here!  Has anybody else double-checked too?  But if what I am seeing is true, this looks to me like a serious drop-off by Microsoft, let’s hope not …

This worried me enough to go and check using the DSIM Tool the Win10 Home x64 version 1909 ISO that I thought I had downloaded at Woody’s suggestion some time ago (27 May 2020), only to find that is actually (according to the DSIM result) build 18362.418 which is version 1903 **NOTE 1903 NOT 1909** made available on 08 October 2019!

So now I’m really confused and seriously concerned, and look forward to others’ views, experiences and findings on this all-important “squirrelling away” topic – thanks in anticipation!

1 user thanked author for this post.

JC Zorkoff