Replies

Thank you, Paul T.  I failed to find this problem under the AskWoody Knowledge Base, but did verify your response from the software author’s WUMgr Issues list on GitHub.

From Issue #59,  https://github.com/DavidXanatos/wumgr/issues/59

“The problem is the Windows Update API returns a update size based on ‘maximum size’ and how MSFT calculated this is unknown. If you were to use something like PSWindowsUpdate Powershell Module for comparison you’d see the same size.

If you actually download the update via the API or tools that use it, it will only download the 839MB it actually needs.

So sadly its not something that can probably be fixed in this tool as its an issue or limitation of the upstream data”

Mr. Austin wrote:

In this case, with 0Patch, I first created the online account, and then from my password management/form filling utility I copied and pasted the password into the 0Patch client software.

I had created my 0Patch account, stored my user/PW into my Norton Password Manager, logged out, then came back later to download the agent installation .msi file.  My NPWM would not supply autofill data, and manual Copy/Paste did not work either, including pasting with Control-V.  I manually typed in the user/PW to access the site.

However, I just logged onto 0Patch 24 hours later and NPWM autofilled my login with no problem.

Susan Bradley wrote:

Let me reach out to the vendor. The servers could be overloaded with all the requests. Hang loose.

Just when I had studied this post enough to think I understood 0Patch enough to jump in and install it, I hit a server problem when I first tried to download the 0Patch Agent .msi file on 6/11/2022.  I tried again later that evening and the download was successful.

For future reference, 0Patch has a Service Status page at https://status.0patch.com/

Wouldn’t you know it, “Calendar View” shows their server problem on 6/11/2022 was the first such incident since 2/10/2022.

This “Guest” reply 2442413 should be from STBC Mapper; I forgot to log in before making the reply.

Thank you, b.

When I checked online for Office 2016 C2R Update History at around 7:30 PM EDT yesterday, Microsoft listed “April 20, 2022   Version 2203 (Build 15028.20228)” as the latest version.  I see now that the list has been updated, so it’s business as usual: When a C2R update gets deemed safe by the Woody group and entered into the Master Patch List, Microsoft has already made one to two additional updates, and I have no choice but to use the latest one.

At any rate, I guess I don’t need to worry about the”Preview” status I had found in the very limited search results last night.

Issue: Office 2016 Retail (C2R) updated to Preview version

Windows 10 21H2 Build 19044.1586, Office 2016 Retail (C2R) V2203 Build 15028.20160, updated 3/25/2022, one version newer than the approved version in the Master Update List (MPL) because C2R updates are restricted to “Enable Updates” and “Update Now”, which is a typical issue every month.

The MPL approved update as of today (04/26/2022) is V2203 Build 15028.20204, but after performing the same update procedure “About Outlook” tells me I now have Version 2204 Build 15128.20178 C2R.  The only info I could find is that this is a “Current Channel (Preview) update.

I have no experience nor interest in testing a preview update, so where do I go from here?  What could possibly go wrong?

1 user thanked author for this post.

LH

The Windows 10 Download page (aka Susan’s Favorite Method) reads “Windows 10 May 2021 Update”, which I successfully used a month ago for the April 2021 Update on my device 1 of 2, which for me was a feature update from v1809 to 20H2.  (Thank you very much, Susan; this was the FIRST time I have had a successful feature update after trying other methods month after month since August 2020!)

I want to repeat this same process now for the May 2021 Update on device 2 of 2, but I want to remain at 20H2 for now and not advance to 21H1. What will this page download now, and does my TargetReleaseVerson registry setting of 20H2 protect me from the unwanted 21H1 using this method?

FYI: I posted this text at around 10 AM EDT today and have since been off the PC.  It is now nowhere to be found and I received no email notifications.  I was in a hurry, so it could have been operator error on my part, although I do remember selecting the Notify me and Submit buttons.

I’m surprised to see a go-ahead for the January Windows Updates given they include KB4598242 and KB4598229 per my next-up Feature update from v1809 (don’t yell at me, I’ve had issues with Feature Updates!) to v1909, my current limit set by TargetReleaseVersion.

My hesitation is driven by the dire warnings given in this report: “Windows 10: PCs not booting up after latest update” (i.e. KB4598242 and KB4598229),
https://www.komando.com/downloads/windows-pcs-not-booting/774835/?utm_medium=nl&utm_source=windows&utm_content=2021-01-22

I see in the previous replies in this thread that others have similar concerns, so how about some good words to boost our confidence? My slow Internet connection leads to a 5 hour download for a feature update plus another hour or so to install, so I am reluctant to bite the bullet and risk having to recover to my earlier version.

Susan Bradley wrote:

What if you search for OfficeC2RClient.exe on your computer?

I used Windows Search and Windows Explorer Search and did not find OfficeC2RClient.exe.   The closest I found was OfficeC2RClient.exe.db and OfficeC2RClient.exe_Rules.xml.

The Office App About reports Office Pro 2016 C2R Retail v2006 build 13001.20266, as I stated above.

Also, About does not include a string identifying the current update channel.

It’s 1 AM local time here, time to shut down for the evening.

Susan Bradley wrote:

To start the switch Channel process, run “OfficeC2RClient.exe /update user” from the cmd prompt path ‘C:\Program Files\Common Files\Microsoft Shared\ClickToRun>” This should be followed by a series of windows which will take you through the process of downloading and installing updates for the new channel that you have switch to.

This all sounds straightforward, but as with many other similar issues with Office Pro 2016 C2R Retail, there is no “\ClickToRun” folder under my “C:\Program Files\Common Files\Microsoft Shared” folder and I did not find a file “OfficeC2RClient”.exe installed on my PC.

The OP noted he purchased a retail version of Office Home & Business 2016 C2R.

My Sys: Win 10 Pro v1809, Office Pro 2016 C2R Retail v2006 build 13001.20266

I have a similar setup as the anonymous Guest of post 2268981, and today (June 6)  I enabled my Office 2016 Retail C2R to update, and now have v2005 12827.20268 (June 02).  When I look at the Office Update History this version is listed for Office 365, but the latest version for Office 2016 C2R is v2004 12730.20352 (May 21).  Am I to assume that somebody at MS is still out to lunch?

Ref: https://docs.microsoft.com/en-us/officeupdates/update-history-office-2019

Susan Bradley wrote:

You should be able to independently do updates for Office as compared to Windows 10.

Sorry again, the anonymous reply at 10:45 PM is from me.  I thought I had logged in.
I also just noticed the “quote” button.

If I am interpreting the 2020-01-27 Office Master Update file correctly, those of us with Office 2016 C2R retail versions should not be making updates after the 12/10/2019 Release, Version 12228.20364, which I had done earlier.  Is this correct?

The Master list also shows a

1/14/2020 Release, Version 1235.20298 without an update recommendation,

and the Microsoft Update History page shows additional updates on

01/22/2020, Version 12325.20344, and

01/30/2020, Version 12430.20184.

Needless to say, I am very conflicted regarding just WHEN to toggle my Office update switch, since it will update the Microsoft’s latest updates.

—————————————————————————–

Win 10 Pro 1809 x64 Dell Inspiron i7

MS Office Pro v1911 Build 12228.20364 2016 Click-to-Run

—————————————————————————–

Thanks for the 2019 Table of Contents.  I was about to create one myself, but you saved me the effort.

This article says to go ahead with the January 2020 Windows updates, but it also makes indirect reference to the latest Patch Watch Column at

https://www.askwoody.com/newsletter/closing-the-book-on-windows-7/#patch-watch-0

and Master Patch list at

https://www.askwoody.com/wp-content/uploads/2020/01/2020-01-14-Windows10-Updates.xlsx

which have not been updated since 01/20/2020 and 01/14/2020 respectively and indicate that consumers should defer updates.

Am I missing something here?

Win 10 Pro 1809 x64 Dell Inspiron i7

 

1 user thanked author for this post.

Marcus Weldby