Patch lady – fourth Tuesday release for 1803

Topic

New Reply

The fourth Tuesday of the month is “clean up” day.  When the odd non security update comes out.  Of course lately that fourth Tuesday schedule has bee
[See the full post at: Patch lady – fourth Tuesday release for 1803]

Susan Bradley Patch Lady/Prudent patcher

3 users thanked author for this post.

Elly, woody, Mr. Natural

Reply | Quote

Replies

It appears KB4284848 does indeed address the SMBv1 issue. I just got a call from a user who was unable to map a network drive to an alpha server running samba with smbv1 after updating to 1803. I was anticipating some issues with this. I guess I got lucky. I manually applied the patch and the drives reconnected properly after a reboot. One thing to note was that drive letter no longer had a name when viewing in Windows Explorer. It just had a drive letter. So I gave the drive letter the appropriate name on the client pc and everything is back in order. Our WSUS has not synced yet so that patch is not in WSUS. Since I’ve been diving head first into this 1803 push I’m going to go ahead and approve this tomorrow.

This patch is brand new and not yet approved so I don’t recommend applying just yet. In my situation it appears to address an issue we have so I’m approving tomorrow it if it is still available late tonight when WSUS syncs.

 

Red Ruffnsore

Reply | Quote

I hope i am the only one going through this, but it seems 1803 feature update is pushed toward the ones that haven’t updated yet to 1803. it seems this update was used as an opportunity to shove that update.

ironically, I want to actually install this update, but I am going to wait for it to become stable

Just someone who don't want Windows to mess with its computer.

Reply | Quote

Yes I was offered 1803 again today (currently on 1709).
With 1803 updates apparently coming out weekly, hopefully it wont be too long before 1803 is a viable upgrade.

Reply | Quote

I am not sure, if the frecuent patches  are a good sign that 1803 will be stable soon. I mean that happened back then with 1709 and Woody never blessed that upgrade.  At least I ignore if he ever blessed it.

In my Opinion its too soon to upgrade, it has been out for just two month.

(I am currently in 1703)

Just someone who don't want Windows to mess with its computer.

Reply | Quote

Me, too. See https://www.askwoody.com/forums/topic/was-1709-ever-blessed-by-woody/#post-199981

Reply | Quote

In addition to the latest Cumulative Update (LCU), there is also a Servicing Stack Update (SSU) for 1803.  However, in looking at the SSU article, it says it only applies to Enterprise 1803.

Interesting because the LCU article has the usual warning for manual installers to do the SSU first.  I assume that warning only applies to Enterprise and that it is OK to manually install just the LCU if one is not using Enterprise version.

Reply | Quote

If you manually install updates you need the Servicing stack before the normal cumulative update.

Susan Bradley Patch Lady/Prudent patcher

1 user thanked author for this post.

Elly

Reply | Quote

But KB article for SSU says it applies to Enterprise 1803.  If I have Pro and do manual installation, do I not need to install the SSU?

Reply | Quote

Never mind.  Microsoft updated the SSU KB article on June 27th to include all editions of 1803 not just Enterprise as they originally posted.

Reply | Quote

If you manually install updates you need the Servicing stack before the normal cumulative update.

Out of curiosity, why before?

I have apparently missed some key piece of information here on this subject.

As a test, and since I missed this bit of advice before I installed KB4284848, I have installed the SSU after. Windows seems happy. It passed an SFC check both before and after…

-Noel

Reply | Quote

I think the advice is from the KB articles themselves. Quite often at the bottom of a quality update, when a servicing stack update has also been released, there is a message along the lines of:

“Important When installing both the servicing stack update (SSU) KB4132650 and the latest cumulative update (LCU) from the Microsoft Update Catalog, install the SSU before installing the LCU.”

Reply | Quote

So Microsoft says “when installing both” install the SSU first.  I suppose that means if I’m only manually installing the LCU, I should be good.  No?

Reply | Quote

No.
If you are manually installing the LCU you need to manually install the SSU first.

Reply | Quote

Has Microsoft thrown out their patching scheduling because Windows 10 is “Windows as a Service” and therefore Microsoft does whatever they want?

Reply | Quote

Technically this is the proper day for these no new security/bug fixes only updates for the semi-annual targeted channel.  I still consider 1803 as IN the semi-annual targeted updates.  The fourth Tuesday (NOT last week’s Thursday releases) are proper.

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote

the 4th Tuesday should have been the time when non-security fixes are released for ALL supported releases of Win10, not just the current release (1803) of Win10. I don’t understand why Microsoft released different patches for different releases of Windows 10 on different days, which makes my head hurt that I need to take some headache medicine like advil or tylenol.

Reply | Quote

Our WSUS server picked up the servicing stack update, but not this cumulative.  I’ve even manually synced this morning, but it’s not there yet.  Are they letting the home users beta test again before inflicting^H^H^H^H^H^H^H^H^H^H releasing this to business users?

Reply | Quote

Same here. The only new update showing in WSUS after last night’s resync is KB4338853, Service stack update for 1803.

Red Ruffnsore

Reply | Quote

Day two, and our WSUS server still hasn’t pulled down this patch.  Only the 1803 servicing stack update was made available so far.   Very strange!

Reply | Quote

I have an Alienware 17R4 laptop.  The system disk is SSD.  There is a second, rotating, 1TB drive.  The laptop has sat on a table undisturbed for 8 months (est), the battery uncharged, wifi and ethernet locked-down so it didn’t wake-up on it’s own and try to update unattended during thos months.  Last week, I tried to use it.  It should have been ready to go, except for charging.  Once charged, it would not boot.  Error codes were tracked and confirmed by Dell as a bad SSD.  Still under warranty, Dell sent a tech with a replacement SSD.  Old SSD was Samsung 240GB.  New SSD is Toshiba 140GB, so new SSD is smaller by 100GB.  New SSD install reverted Windows to factory settings.  Not much data loss as not much was on it.  Tech repaired laptop on Tuesday.  The updates on Wednesday bricked the computer.  Apparently, even though I have a backup image of both drives and carefully included all partitions, even unmarked partitions, to my Linux-based NAS using Macrium Reflect, I cannot effect a restore.  It seems I still need to use another computer and download an entirely new ISO image of Windows 10 and install it somehow.  Here goes another week away from doing productive work to fix a mess!  Laptop seems to be a lemon and should be bought-back at full retail price plus cash compensation at this point.  Windows 10 is complete and utter ******.

Reply | Quote