Get answers from your peers along with millions of IT pros who visit Spiceworks.
Join Now

I noticed the VLSC site now shows that Windows 10 1803 media shows as "Updated June '18."

So, does that mean that it now contains the June 2018 cumulative update?

Will WSUS feature update files installed via WSUS ever get updated so that when the 1803 Feature Update is installed on a system, it isn't full of unpatched vulnerabilities requiring another separate round of updates?

We have had an issue with users applying the feature update via WSUS, restarting to complete it and then thinking they are done.  They end up being more vulnerable after the update than before becaus their workstation is now 3 months behind in patches unless they know and remember to manually check for updates again to complete a second round of updates.


Da_Schmoo
Ghost Chili
OP
Da_Schmoo

The "June" release on VLSC - SW_DVD9_Win_Pro_Ent_Edu_N_10_1803_64BIT_English_-4_MLF_X21-87129.iso .


Also noticed it made me do the 3 security question nonsense which it never did before but that was probably because the network was disabled.

Learn windows powershell
With tons of resources, progress tracking, and achievement badges you're bound to improve your IT skills.
TEST YOUR SMARTS
Which of the following retains the information it's storing when the system power is turned off?
  • GPU
  • RAM
  • CPU
  • ROM
88% of IT pros got this right.

20 Replies

· · ·
Big Green Man
Mace
OP
Big Green Man

Joe9493 wrote:

I noticed the VLSC site now shows that Windows 10 1803 media shows as "Updated June '18."

So, does that mean that it now contains the June 2018 cumulative update?

Install it and look at the build number. :)

Joe9493 wrote:

Will WSUS feature update files installed via WSUS ever get updated so that when the 1803 Feature Update is installed on a system, it isn't full of unpatched vulnerabilities requiring another separate round of updates?

It'll always be the RTM for $FeatureUpdate, and they will need to do a second round of updates afterward to bring up to date.

Joe9493 wrote:

We have had an issue with users applying the feature update via WSUS, restarting to complete it and then thinking they are done.  They end up being more vulnerable after the update than before becaus their workstation is now 3 months behind in patches unless they know and remember to manually check for updates again to complete a second round of updates.

Is Windows Update not automatically checking?

0
· · ·
Da_Schmoo
Ghost Chili
OP
Da_Schmoo

I haven't installed it anywhere yet but the June release on VLSC is a different size than then one I downloaded May 8th. 

Just looking at the file name, it appears to be 1803, Build 17129.

1
· · ·
Joe9493
Chipotle
OP
Joe9493



Big Green Man wrote:

Joe9493 wrote:

I noticed the VLSC site now shows that Windows 10 1803 media shows as "Updated June '18."

So, does that mean that it now contains the June 2018 cumulative update?

Install it and look at the build number. :)


I thought that maybe this has been out for a few days or weeks and someone else has already installed it and knows the status.

0
· · ·
Da_Schmoo
Ghost Chili
OP
Da_Schmoo

I'm going to be installing it on a machine later today or tomorrow.  I can confirm the build but I'm not sure how to tell if it has the June update on it - Win10 does some sort of update during install and once it's installed Windows update will be offering up the July CU anyway.

0
· · ·
Joe9493
Chipotle
OP
Joe9493

Big Green Man wrote:


Is Windows Update not automatically checking?

Windows Update may check, but the user won't know unless they proactively take it upon themselves to go look for more updates after they apply the feature update.

Most users are not going to do this.

I have had to send email reminders to people who applied the feature update via WSUS because they didn't go back and install 1803 cumulative updates.

I can set a backdated deadline for the current 1803 updates so they get installed automatically, but the deadline reboots are disruptive to users.

0
· · ·
OverDrive
Mace
OP
OverDrive

Joe9493 wrote:

Big Green Man wrote:


Is Windows Update not automatically checking?

Windows Update may check, but the user won't know unless they proactively take it upon themselves to go look for more updates after they apply the feature update.

Most users are not going to do this.

I have had to send email reminders to people who applied the feature update via WSUS because they didn't go back and install 1803 cumulative updates.

I can set a backdated deadline for the current 1803 updates so they get installed automatically, but the deadline reboots are disruptive to users.

Polices to install daily and check every 4-8 hours will minimize the time a system is out of date for.

https://www.ajtek.ca/wsus/how-to-setup-manage-and-maintain-wsus-part-4-creating-your-gpos-for-an-inh...

2
· · ·
Big Green Man
Mace
OP
Big Green Man

Da_Schmoo wrote:

I'm going to be installing it on a machine later today or tomorrow.  I can confirm the build but I'm not sure how to tell if it has the June update on it - Win10 does some sort of update during install and once it's installed Windows update will be offering up the July CU anyway.

Do the install without a network connection so it can't update. Build numbers for 1803 are:

17134.1 - RTM (4/30)

17134.48 - May Update (5/8) - KB4103721

17134.81 - Second May Update (5/23) - KB4100403

17134.83 - June Update (6/5) - KB4338548

17134.112 - Second June Update (6/12) - KB4284835

17134.137 - Third June Update (6/26) - KB4284848

17134.165 - July Update (7/10) - KB4338819

0
· · ·
Da_Schmoo
Ghost Chili
OP
Da_Schmoo

" Do the install without a network connection so it can't update."

I'll do that if FedEx will ever arrive with my SSD drive.  :( 

0
· · ·
Big Green Man
Mace
OP
Big Green Man

Da_Schmoo wrote:

" Do the install without a network connection so it can't update."

I'll do that if FedEx will ever arrive with my SSD drive.  :( 

I've got some downtime right now. Let me grab the ISO and install quick. Need to download it so I can start testing anyway.

0
· · ·
Da_Schmoo
Ghost Chili
OP
Da_Schmoo

I'm installing it in a VM right now because I'm bored.

1
· · ·
Big Green Man
Mace
OP
Big Green Man

Da_Schmoo wrote:

I'm installing it in a VM right now because I'm bored.

But I already have 2 GB downloaded!

0
· · ·
Da_Schmoo
Ghost Chili
OP
Da_Schmoo

Big Green Man wrote:

Da_Schmoo wrote:

I'm installing it in a VM right now because I'm bored.

But I already have 2 GB downloaded!

HAHA.  I was already installing it before I saw your post!

1
· · ·
Da_Schmoo
Ghost Chili
OP
Best Answer
Da_Schmoo

The "June" release on VLSC - SW_DVD9_Win_Pro_Ent_Edu_N_10_1803_64BIT_English_-4_MLF_X21-87129.iso .


Also noticed it made me do the 3 security question nonsense which it never did before but that was probably because the network was disabled.

1
· · ·
Big Green Man
Mace
OP
Big Green Man

Da_Schmoo wrote:

The "June" release on VLSC - SW_DVD9_Win_Pro_Ent_Edu_N_10_1803_64BIT_English_-4_MLF_X21-87129.iso .

Also noticed it made me do the 3 security question nonsense which it never did before but that was probably because the network was disabled.

So it's already 2 updates behind. Guess that means OP will be updating post install.

0
· · ·
Joe9493
Chipotle
OP
Joe9493

I knew we would still need to do updates since July updates are out now, but at least the worst 1803 bugs are now patched in the base install.

Too bad the same isn't true applying the feature update with WSUS.

1
· · ·
NathM
Thai Pepper
OP
NathM

Joe9493 wrote:

I knew we would still need to do updates since July updates are out now, but at least the worst 1803 bugs are now patched in the base install.

Too bad the same isn't true applying the feature update with WSUS.

as for the media, you can always inject whichever CU you like and make your own media, rather than waiting for Microsoft to make it available

1
· · ·
Joe9493
Chipotle
OP
Joe9493

I thought slipstreaming update packages was no longer supported.

0
· · ·
NathM
Thai Pepper
OP
NathM

Joe9493 wrote:

I thought slipstreaming update packages was no longer supported.

not that I'm aware of

Get a Windows update package. For example, grab the latest cumulative update listed in Windows 10 update history from the Microsoft Update catalog. Extract the .msu file update to a folder, for example, C:\WindowsUpdates\windows10.0-kb4016871-x64_27dfce9dbd92670711822de2f5f5ce0151551b7d.msu.
Dism /Add-Package /Image:"C:\mount\windows" /PackagePath="C:\WindowsUpdates\windows10.0-kb00001-x64.msu" /PackagePath="C:\WindowsUpdates\windows10.0-kb00002-x64.msu" /PackagePath="C:\WindowsUpdates\windows10.0-kb00003-x64.msu" /LogPath=C:\mount\dism.log
DISM /Cleanup-Image /Image:"C:\mount\windows" /StartComponentCleanup /ResetBase /ScratchDir:C:\Temp
Dism /Unmount-Image /MountDir:"C:\mount\windows" /Commit

0
· · ·
Da_Schmoo
Ghost Chili
OP
Da_Schmoo

"Also noticed it made me do the 3 security question nonsense which it never did before but that was probably because the network was disabled."

Well, I've confirmed that the new build does require you to answer the three security questions regardless of whether the network is attached.  Without network access it simply makes you create a local user account and bypasses all the prompting to use a Microsoft account and all that but either way requires answering the questions.

More annoyances.

0
· · ·
Joe9493
Chipotle
OP
Joe9493

There has been a recent update to the 1803 Feature Upgrade in WSUS, it looks like it also will upgrade directly to to 17134.112.

You will need to approve the new upgrade and decline the new older version.

0
Oops, something's wrong below.