Windows 10 version 1809 advances to build 17763.165 – with no documentation, of course

Topic

New Reply

I’m reading between the tea leaves here, but it appears as if KB 4469342 was released to the Insider Release Preview ring, then to the Win10 1809 mass
[See the full post at: Windows 10 version 1809 advances to build 17763.165 – with no documentation, of course]

6 users thanked author for this post.

abbodi86, ch100, b, Fred, GreatAndPowerfulTech, Mr. Natural

Reply | Quote

Replies

KB4469342 installed with no apparent issues for 17763.165.

I think it’s Release Preview only so far.

(Ed Bott corrected his tweet.)

Reply | Quote

I see where Ed recanted, but then Barb posted that she had seen it on the RTM branch. (Edit: Barb has verified that she only saw it on RP.)

Wonder what’s up? This is important, no matter which is true.

If it’s being distributed to the Release Preview ring, that’s EXACTLY what  should be done — new cumulative updates for a released version go into Release Preview before they’re pushed out to everybody. That’s never been done before, in my experience.

If true, the person at MS who decided to use RP in the way it was intended should be canonized.

Reply | Quote

I don’t see it as being made public, but installed manually and it works well.
The correct order to install is:
SSU – KB4470788
CU – KB4469342

1 user thanked author for this post.

abbodi86

Reply | Quote

Apparently there was also a corresponding SSU to go with it. Did you get the double download issue (first pass fails and then second pass with SSU)? Please check your Update History and let us know. Thanks!

1 user thanked author for this post.

woody

Reply | Quote

I believe there is an SSU that is needed. I have found KB4470788 listed on some sites, but it is not currently in the Catalog (10:30am CDT US 11/16).

1 user thanked author for this post.

woody

Reply | Quote

… and just confirming here … you’re all seeing this problem inside the Release Preview ring, yes?

Reply | Quote

It is not in the Catalog, it is in Preview only.

Reply | Quote

Good point. Yes, I did get failed first. Installed updates lists the SSU installed today as KB4470788, which is also not documented yet.

1 user thanked author for this post.

woody

Reply | Quote

Unless its a bug, I really don’t understand this first pass failover strategy for getting the 1809 SSU. Why can’t the SSU be a separate item in WU that gets installed first?

Reply | Quote

It has worked right before the Nov updates. It’s something MS did to change the install sequence.

Reply | Quote

Since first release of 1809, it has failed for me on each of the two subsequent Patch Tuesday’s (10/9 and 11/13). I am not in the RP ring, but 4469342 would make it three times. Would love to know why 1809 is different from past Feature Updates in this particular regard.

Reply | Quote

Your system has a problem, 1809 is just fine and has been fine for “normal” people from the very start. Only those misconfiguring their systems had the file loss issue, although Microsoft should have been more diligent with that issue.

Reply | Quote

I think the last time Release Preview Ring was actively used is with 1607

good to see they back on track 🙂

Reply | Quote

17763.165 (KB4469342) is supposed to fix the “file association” bug – can anyone with this v1809 specific patch confirm?

Reply | Quote

I have that installed, but what’s a good test?

Where did you see this patch may have fixed it?

EDIT: I installed Notepad++ and was able to set that to always open .txt files, which stuck.

So as far as I can tell the file association bug probably is fixed in 17763.165 for Release Preview.

Reply | Quote

I saw a case where I tried to open a .png file by double-clicking it, and I got some kind of Windows viewer instead of the IrfanView application I have (and have had) configured for the purpose.

I was focused on getting something else done, but after seeing that problem I right-clicked the file, chose Open With, picked “Choose another app”, then chose IrfanView and checked the box “[ ] Always use this app to open .png files”. Immediately thereafter I tried double-clicking the .png file again in Explorer and it failed to open Irfan View. I then went on to get the task done another way (dragging the file to the Irfan View icon on the desktop).

Here’s the thing… Now – a day later and on a fresh bootup – double-clicking a .png file DOES open IrfanView.

I do NOT have the aforementioned KB installed – my Win 10 is still at 17763.134.

I’m thinking this means that either a) something before 17763.165 fixed the issue, or b) it’s intermittent.

-Noel

Reply | Quote

What is all this Servicing Stack Update stuff all about lately?

Isn’t “cumulative” supposed to cover everything with one easy peasy update?

Why shouldn’t a “cumulative” update be fully and truly cumulative?

-Noel

Reply | Quote

How an update is supposed to update the same engine that handle the update itself? 😀

Reply | Quote

Same way it updates everything else: By putting boot-time instructions in place to swap files so that next time new software is run. This is not a new problem.

-Noel

Reply | Quote

17763.165 fixes the file association bug with .134

Reply | Quote