Getting ready for Windows 10 1909

Topic

New Reply

PATCH WATCH By Susan Bradley Many of us are still pondering Win10 1903 — and now Version 1909 is almost upon us. Here’s how not to be the next release
[See the full post at: Getting ready for Windows 10 1909]

1 user thanked author for this post.

Fred

Reply | Quote

Replies

OK, so back around the beginning of the month I paused (1903, Build 18362.356) updates and later again, but now the pause time has run out and there’s no extra information on the Windows Update screen, just the “You’re up to date” message, which of course is wrong since my history shows the last updates (Flash, NET, and CU) were installed 22 September.

Susan’s listing of individual KB files implies I should download and install the latest updates manually like an IT expert consultant might, but then I read MS saying that I should install the SSU update before the CU updates but there is no advice about when (or if) I should install the .NET patches. I have on rare occasion successfully installed updates manually, but I would rather not. Can I assume that MS will get around to updating me in its own sweet time if I just leave it alone? I’m in Europe and I have the vague impression that the monthly waves of updates reach us here a bit later than in the USA where most (all?) of the regular authors are located even without any pauses being set. For what it’s worth, my definition updates arrive daily, including today, with or very soon after boot-up so can I assume my PC is reaching out for CU updates as well?

Will Defcon move up soon now that Susan is “comfortable”?

Reply | Quote

In the search box tyoe “winver” (without quotes) and verify you are on 1903, Build 18362.356

After that, you can wait for Windows Update to scan again (don’t click “Check for updates”.
Or you can download the Oct. SSU KB4521863 (that is a direct download link for 64-bit) and manually install it.  I suspect the Oct updates will show up in WU if you wait for the next time it scans.

Reply | Quote

[Wayne]

Thanks, PK. I used Winver to check the build I entered above. Will the October SSU increase the likelihood of the October CU arrival if I install it or will everything arrive if I just wait (my preferred option)?

I’m wondering now because the time to pause the November CU is rapidly approaching and it seems safer to have the October CU in place first, Defcon status notwithstanding . . .

How often, roughly, does Win 10 scan for updates?

• This reply was modified 5 years, 6 months ago by Wayne.

Reply | Quote

That’s a bit “how long is a piece of string”. I think it’s between 1 day and a week.

cheers, Paul

1 user thanked author for this post.

Wayne

Reply | Quote

The string wasn’t that long after all. My CU (KB4517389) and .NET (KB4524100) updates arrived by themselves last night (29 Oct) and announced that a restart was needed, which I did, bringing winver up to Build 18362.418.

Of course, MS doesn’t make it simple: I have another .NET update shown (KB4522741) as “pending download” with a “Download” button ready to push AND the Optional updates available band (CU, KB4522355) that I do not intend to touch as per AskWoody constant reminders.

I assume my next move is to just wait until the new .NET update downloads by itself while the Optional CU update just sits there inactive, saving my pauses until just before update Tuesday (Nov 5 or 12?) and the usual AskWoody warning notice so I get the full 35-day benefit.

Is my assumption correct?

Reply | Quote

Patch Tuesday is Nov 12.

1 user thanked author for this post.

Wayne

Reply | Quote

Until the other day my Dragon Professional Individual English Version 15.30 (dictation software) was working perfectly. Then Microsoft pushed Windows 10 Build 1909 on to my work station. Since then Dragon has been unable to recognize my Andrea NC-185VM USB head set. The problem continued after I reinstalled Dragon.

Has anyone else had a comparability problem with Dragon 15.3 and Windows 10 build 1909?

Reply | Quote

Have you tried the Andrea Support website?
Have you updated, or at least reinstalled the drivers for the headset?

Tried running the troubleshooter?
Windows Key+i > Update & security > Troubleshoot > Playing Audio > Run the troubleshooter

Reply | Quote

The big question is, how bad will it be?

I’m delayed and I do a full backup … just in case the sky does fall.

Byte me!

Reply | Quote

Susan,

Your article on using gpedit is excellent.  However, I believe you might have left out a step.  Before setting the number of days you wish to defer the update, don’t you also need to choose:  Semi-Annual channel in the box labeled “Select the Windows Readiness level for the updates you want to receive?

If you fail to select this, on my computer  it defaults to a readiness level of Preview Build-Fast, which is definitely not what I want.

Gary Cahn

1 user thanked author for this post.

b

Reply | Quote

Susan included that step in the Podcast (at 5:40) but not the newsletter.

1 user thanked author for this post.

garycahn

Reply | Quote

I went ahead and grabbed the new 1909 ISO from one of my MSDN accounts, and installed it over top of my 1903 (build 18362.449).

Like others here, I had no idea what on earth 1909 was about, how Microsoft was changing the OS, how they were managing to have the same service packs for two builds, etc.  It was extraordinarily poorly described and documented.

After this upgrade, I have no more questions.  My Win10 “1909” build 18363.449 is virtually the same as 1903.  The only “difference” is that if your registry is stamped with the 18363 moniker, certain features are allowed to be enabled (as MS rolls them out.)  That’s it.  I’ve run a check on all system .DLL files since the update and nearly every last one of them is a flavor of 18362.  (I’m sure there’s a proper 18363 .DLL somewhere in here, for the new Start menu features and whatnot, but I’m not inclined to keep looking; suffice it to say I’ve looked at hundreds and none have showed up yet.)

I’d liken the “1909” release to the old Windows XP Media Center Edition, which was nothing more than XP with some toys bolted on.  No wonder the cumulative update packages were designed to work with “both” operating systems – there’s only one OS here, one of them plain, and the other tattooed to allow new toys.

TL;DR – if 1903 is working, the likelihood of 1909 breaking anything is nearly nil.  1909 IS 1903, but stating that outright isn’t exactly going to get Microsoft the “excitement” they demand.

2 users thanked author for this post.

radosuaf, CraigS26

Reply | Quote

The problem with Dragon Professional Individual English Version 15.30 (dictation software) and Andrea NC-185VM USB head set is not related Windows 10 Build 1909.

It was a problem with my privacy settings.

Sorry Folks

1 user thanked author for this post.

b

Reply | Quote