November 2019 Patch Tuesday arrives

Topic

New Reply

Flash: Yes, we’re getting Win10 version 1909 today. See this Windows Insider Blog post from Athima Chansanchai: Along with Tuesday’s release of the Wi
[See the full post at: November 2019 Patch Tuesday arrives]

5 users thanked author for this post.

GreatAndPowerfulTech, lanceboil, CyGuy, abbodi86, Fred

Reply | Quote

Replies

https://twitter.com/WindowsUpdate/status/1194315194983317504

Susan Bradley Patch Lady/Prudent patcher

2 users thanked author for this post.

abbodi86, woody

Reply | Quote

It looks like the 1909 version is out now.
Getting 1909 thru Windows Update will be issued KB4524570 (build 18363.476) but the 1909 ISOs & ESDs will have build 18363.418

Exactly four years ago on Nov. 12, 2015, the 1511 version of Windows 10 (then called the November Update) was released.

Reply | Quote

[PKCano]

Group B Security-only Updates and the IE11 Cumulative Update have been updated for November on AKB2000003.

UPDATE NOTE: According to @abbodi86, the November SOs are telemetry free.

There are new SSUs for Win7 KB4523206 and Win8.1 KB4524445.

• This reply was modified 4 years ago by PKCano.

9 users thanked author for this post.

SueW, LHiggins, abbodi86, Pepsiboy, DrBonzo, samak, lanceboil, woody, AJNorth

Reply | Quote

Assuming the hashes listed on the SSU page are wrong again? Because what I’m seeing has nothing to do with what’s written…

Reply | Quote

Martin Brinkmann now has his excellent overview posted for the November 2019 updates:

https://www.ghacks.net/2019/11/12/microsoft-windows-security-updates-november-2019-overview/

1 user thanked author for this post.

woody

Reply | Quote

First bug: receive MSRT update repeatedly.

2 users thanked author for this post.

Sailor, woody

Reply | Quote

You might try manually downloading, then running, the latest MSRT (v. 5.77):

https://www.microsoft.com/en-us/download/details.aspx?id=9905

(a minute or so after it has completed, you can safely delete the executable).

Reply | Quote

Also getting repeated Malicious Software Updates in Win 10. On Win 7 machines the WU of the Malicious Software Update fails error code 800B0109. Downloaded the file from Microsoft Catalogue and run it which should remove it from updates but it doesn’t, so have hidden it from Win 7 WU.

1 user thanked author for this post.

woody

Reply | Quote

COBKA wrote:

Also getting repeated Malicious Software Updates in Win 10. On Win 7 machines the WU of the Malicious Software Update fails error code 800B0109. Downloaded the file from Microsoft Catalogue and run it which should remove it from updates but it doesn’t, so have hidden it from Win 7 WU.

I ran the delta update from the Update Catalog and then started the search for new updates once again. That solved the failing MRST update on Win 7 (3 machines) and Win 2008 R2 (2 machines): the November update did not re-appear anymore.

Reply | Quote

Same here … ‘Windows Malicious Software Removal Tool x64 – November 2019 (KB890830)’ fails to install.

When I go to the details page for the WU (https://support.microsoft.com/en-us/help/890830/remove-specific-prevalent-malware-with-windows-malicious-software-remo), and click the manual download link for x64:

http://www.microsoft.com/downloads/en/details.aspx?familyid=585d2bde-367f-495e-94e7-6349f4effc74

I get the following message in the browser window instead of a download:

Server Error

404 – File or directory not found.
The resource you are looking for might have been removed, had its name changed, or is temporarily unavailable.

So something is amiss for certain …

 

1 user thanked author for this post.

woody

Reply | Quote

UPDATE:

Downloaded and ran the Win7 x64 November delta for the MSRT from https://www.catalog.update.microsoft.com/Search.aspx?q=KB890830 …

and ran the update manually.

Then, I re-ran WU, which picked and installed the ‘Servicing stack update for Windows 7 SP1 and Server 2008 R2 SP1: November 12, 2019.’

Ran WU again, no pending updates.

Interestingly, the three actual Windows/Office security updates for November installed with no issue without the new SSU.

At any rate, it looks like the issue is with WU trying to install the November MSRT before installing the SSU, and MSRT needed SSU to be installed first.

Definitely a MS issue …

 

2 users thanked author for this post.

COBKA, woody

Reply | Quote

Yes confirm that works for me. Interestingly when I tried this originally I ran the bigger file from the Microsoft Catalogue, not the delta, and maybe its the delta file that needs executing to clear this from WU.

Reply | Quote

Hi All,
I encountered the same problem with the MSRT .

I downloaded both files from the catalog and executed successfully the big file,
but the “delta” file seems to do nothing when executing it, no error and no feedback at all.

Does anybody know whether running the tool manually is supposed to remove the update
from appearing again ?

Thanks & Best Regards,
Iudith

Reply | Quote

The MSRT installation fails even AFTER installing the SSU, so I am not sure that the problem is related to SSU.

Reply | Quote

MSRT is an executable tool, not a real update, SSU has nothing to do with it

1 user thanked author for this post.

woody

Reply | Quote

After repeated reboots and 6 installs, now Windows update no longer reinstalls MSRT and everything looks OK.

Reply | Quote

Can someone please explain why there are so many service stack updates lately?
From what I can gather, not etirely sure, it’s to do with SHA2 and changes to Windows Update? confirmation required, in not too technical format please, thank you old codger homeuser here.
rant/ Bugs and an SSU please for xmas. /rant

1 user thanked author for this post.

WarwickW

Reply | Quote

The SSU is the update for the Windows Update mechanism itself. It is installed exclusively (by itself) for Win7/8.1, so it will appear in the Windows Update Important updates. For Win10, the installation is handled through Windows Update but it is not listed separately from the Cumulative Update.

1 user thanked author for this post.

woody

Reply | Quote

The SANS ISC threat chart for November 2019 Microsoft Patch Tuesday has been posted:

https://isc.sans.edu/forums/diary/November+2019+Microsoft+Patch+Tuesday/25516/

1 user thanked author for this post.

woody

Reply | Quote

Addresses an issue in the Keyboard Lockdown Subsystem that might not filter key input correctly.

Fingers crossed that this is finally gonna close the lid on my intermittent software Windows key sticking. Considering the only workaround I can find to get input back to normal after it happens is loading a UAC prompt, I’m sure it must have something to do with this “Keyboard Lockdown Subsystem.”

Reply | Quote

I hope it does fix your problem, but it’s not likely.  The “Keyboard Lockdown Subsystem” is part of an optional feature of Windows 10 Enterprise / Education only, that allows administrators to configure certain keys or combinations of keys to be disabled, such as ALT+F4 or CTRL+ALT+DEL.  Useful for kiosks or screens intended for use by children.  (Before Windows 10, you usually had to use third-party software to do this sort of thing.)

The fix (which is considered a security fix) actually shipped with every version of Windows 10 older than 1903 last month… not sure why they waited until the November updates to ship it for 1903.

 

Reply | Quote

Figured what the heck and upgraded my 1903 to 1909 through Windows Update. Took all of 4 minutes to update, reboot and log in to desktop. All of my settings appear to have stayed intact.

Never Say Never

Reply | Quote

About the same time for me. No problems that I can detect thus far.

Reply | Quote

Yes, this seems to be the work of KB 4517245:

“Windows 10, versions 1903 and 1909 share a common core operating system with an identical set of system files. Therefore, the new features in Windows 10, version 1909 were included in the latest monthly quality update for Windows 10, version 1903 (released October 8, 2019), but are in an inactive and dormant state. These new features will remain dormant until they are turned on through the “enablement package,” a small, quick-to-install “master switch” that activates the Windows 10, version 1909 features”

I found this on our WSUS, availabe for the few test computers that already run 1903…

Reply | Quote

[galileo]

Smooth update process to 1090 with no issues/problems obvious at this time…

• This reply was modified 4 years ago by galileo.

Reply | Quote

Does the latest update to 1903 as well as 1909 have the fix for “disappearing deferral dialog” bug?

Reply | Quote

The November CU should have the fix for the deferral pulldowns in the GUI

1 user thanked author for this post.

CyGuy

Reply | Quote

“should” – has anyone confirmed it?

Reply | Quote

It was corrected in KB4522355. Win10 updates are CUMULATIE.

3 users thanked author for this post.

CyGuy, woody, sheldon

Reply | Quote

I can confirm it.

1 user thanked author for this post.

CyGuy

Reply | Quote

Has anyone had an issue with the Malicious Software Removal Tool (KB890830)? I’ve released it from WSUS to a test group, manually when into Windows update to install it, it sits at “Installing: 0%” for a couple minutes then goes away. When I hit “Check for Updates” it shows up again and does the same thing.

Reply | Quote

Not on my Windows 7 Pro (x64) test machine.

KB890830-x64, V5.77 was manually downloaded from https://www.microsoft.com/en-us/download/details.aspx?id=9905, then run in its default (recommended) Quick Scan mode (about a minute or so after its completion, it can be deleted).

Reply | Quote

Tried that on one of my Win 7 machines and the update still reappears when you check for updates and the update fails error code 800B0109 if you try to install from there, so I’ve had to hide the update.

Reply | Quote

I have the same problem and we are not aloone :

Loook diz discussion:

https://www.tenforums.com/windows-10-news/144288-kb4524570-cu-windows-10-v1903-build-18362-476-v1909-build-18363-476-a.html

2 users thanked author for this post.

woody, COBKA

Reply | Quote

I can’t help but ask a really dumb question… Is it safe to install version 1909 or should I wait and stay on version 1903? And while we’re at it, is it safe to install the latest cumulative update for 1903?

Reply | Quote

We are on DEFCON-2 which means WAIT to install the November patches.

The Nov updates have not been out long enough (only 2 hours) for anyone to declare them “SAFE” to install yet. (Unless you want to be a Beta-testing Guinea Pig!! 🙂 )

2 users thanked author for this post.

CyGuy, woody

Reply | Quote

I decided to throw caution to the wind and not only install the cumulative update but I also installed 1909, I’m happy to report that my computer didn’t light on fire, explode, and/or otherwise break in any way. All is good.

Reply | Quote

One question for people whose machines are at pre-1903.  Update to 1903 or go directly to 1909  (of course after Woody gives the OK)?  The difference between the two doesn’t seem very large.

1 user thanked author for this post.

CyGuy

Reply | Quote

For now, don’t update anything.

I’ll be watching things closely. When it’s time to update – to either 1903 cumulative update, or to 1909 – I’ll yell loud and clear.

2 users thanked author for this post.

Cee Arr, CyGuy

Reply | Quote

Installed Update “Malicious Software Removal Tool” from November kb890830 and still appears to install in Windows Update MiniTool.

Reply | Quote

I used the show or hide updates troubleshooter to hide the update in Win 10 and that seems to stop the update from repeatedly installing.

https://support.microsoft.com/en-us/help/3183922/how-to-temporarily-prevent-a-windows-update-from-reinstalling-in-windo

 

1 user thanked author for this post.

woody

Reply | Quote

Seeker/cannon fodder report:

Window 10 Version 1909 (OS Build 18363.476)

KB4522742 Cumulative Update for .NET Framework 3.5 and 4.8 for Windows 10 Version 1909 for x64
KB4524101 Cumulative Update for .NET Framework 3.5 and 4.8 for Windows 10 Version 1909 for x64
KB4516115 Security Update for Adobe Flash Player for Windows 10 Version 1909 for x64-based Systems
KB4516115 Cumulative Update for Windows 10 Version 1909 for x64-based Systems

Also got the malicious software removal tool downloaded and installed without issue.

All systems nominal.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We were all once "Average Users". We all have our own reasons for doing the things that we do with our systems, we don't need anyone's approval, and we don't all have to do the same things.

Computer Specs

3 users thanked author for this post.

RetiredGeek, CyGuy, woody

Reply | Quote

I am not sure if this is normal but i did have to install the 1903 CU before it offered me 1909.

As other posters have noticed it was incredibly fast. I would say about a quarter of the time it took to install the 1903 CU.

No apparent problems other than i also am seeing MSRT repeatedly wanting to install.

Last where in the heck do you go to change your signature? I have done it before but cant find it anywhere.

Barry
Windows 11 v22H2

Reply | Quote

Change your signature in your Profile.
Click on your username below you Avatar, then click on Edit.

1 user thanked author for this post.

Barry

Reply | Quote

Upgrade from 1903 to 1909 was as smooth & quick as any monthly CU, although I’m just an ethernet HP desktop.

The Nirsoft WU History App shows – (2) – 1909 Installs 17 min apart (I did see/run a 2-stage Update w/2 MSRT’s — BUT the Control Panel WU history shows just One. SSU shows on the Con Panel History Only as usual.

Surely it matters that my flawless experience with W10 is via a new Feb ’19 desktop shipped with 1709 W10 (smooth 1803-1809-1903 upgrades) VS having to Upgrade from W7 or older. I’ll never look back.

W10 Pro 22H2 / Hm-Stdnt Ofce '16 C2R / HP Envy Desk-Ethernet - SSD-HDD/ i5(8th Gen) 12GB / GP=2 + FtrU=Semi-Annual + Feature Defer = 1 + QU=0

Reply | Quote

For me, 1909 seems to break network discovery similar to 1803. Can’t see other 1903 PCs from 1909 and vice versa. Using IP address either way works fine.

1 user thanked author for this post.

woody

Reply | Quote

Not seeing that here on a mix of 1809, 1903 and now 1909. All machines can browse and see networked machines.

Never Say Never

Reply | Quote

Thanks. Had to reboot the 1903 that was on prior to a 1909 update and now all OK. Whew! Had the worst case of deja vu for a few minutes there.

1 user thanked author for this post.

woody

Reply | Quote

Make sure your network is still private on the 1909 machine. If that ok try enabling SMBv1 on both machines. HTH 😎

May the Forces of good computing be with you!

RG

PowerShell & VBA Rule!
Computer Specs

Reply | Quote

RetiredGeek wrote:
If that ok try enabling SMBv1 on both machines.

Yes, you could do that, but maybe you shouldn’t. With respect, SMB1 is old and insecure and most systems are probably better off not running it.

https://techcommunity.microsoft.com/t5/Storage-at-Microsoft/Stop-using-SMB1/ba-p/425858

Hope this helps.

1 user thanked author for this post.

b

Reply | Quote

Agreed completely. But as RG notes, sometimes it’s the only way you can get the dern things to talk to each other….

Reply | Quote

woody wrote:

Agreed completely. But as RG notes, sometimes it’s the only way you can get the dern things to talk to each other….

Since most Microsoft products use DNS to resolve this sort of thing (and the OP stated that access via IP is still working), I wonder if fixed IP addresses and a quick entry or two in the hosts file wouldn’t be the better way to do this on the typical cheap home network?

(I’m assuming they have inadequate local DNS services.)

Reply | Quote

[TheOwner]

I am also unable to install  November 2019 Malicious Software Removal Tool  trough Windows Update with error 800B0109 on Win 7 64bit. It not download and in my download folder is nothing about this. (I know  it has code name)

• This reply was modified 4 years ago by TheOwner.

1 user thanked author for this post.

rontpxz81

Reply | Quote

November 2019 Malicious Software Removal Tool did not appear in the WU today- only the monthly security roll up.

Reply | Quote

Guidance for disabling Intel® Transactional Synchronization Extensions (Intel® TSX) capability

is this related to CPU vulnerabilities mess?

1 user thanked author for this post.

woody

Reply | Quote

anonymous wrote:

For me, 1909 seems to break network discovery similar to 1803. Can’t see other 1903 PCs from 1909 and vice versa. Using IP address either way works fine.

Networking is working normally for me.  Only one PC on 1909, but it and all the others can look both ways.

One minor annoyance is that 1909 re-installed those useless (for me) Libraries and Special Folders again.  I had to import my reg files into the registry for each user to get rid of them one more time.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We were all once "Average Users". We all have our own reasons for doing the things that we do with our systems, we don't need anyone's approval, and we don't all have to do the same things.

Computer Specs

Reply | Quote

One minor annoyance is that 1909 re-installed those useless (for me) Libraries and Special Folders again. I had to import my reg files into the registry for each user to get rid of them one more time.

I didn’t have that issue on this machine. Weird.

Never Say Never

Reply | Quote

Bbearen,   could you please post the reg file? 😁

May the Forces of good computing be with you!

RG

PowerShell & VBA Rule!
Computer Specs

1 user thanked author for this post.

woody

Reply | Quote

The upgrade from 1903 to 1909 set the default app for Pictures to Paint 3D for me.

I’ve had the ‘awful’ Photos app removed with the Tools option of CCleaner for a while now and ‘restored’ Windows Photo Viewer with a reg file.

The upgrade to 1909 obviously removed the registry change and tried to restore the default app to Photos but because Photos wasn’t there it chose Paint 3D instead.

After running my reg file again the default app is back to Windows Photo Viewer.

Can’t see any other default app changes so far from the upgrade to 1909, I’ll be keeping an eye out though.

PC1: Gigabyte B560M D2V Motherboard, Intel i5 11400 CPU, 16GB RAM, NVIDIA GeForce GTX 1650 Graphics Card, 1x Samsung 870 EVO 250GB SSD, 1x Samsung 860 EVO 250GB SSD, Windows 10 Professional 22H2 64bit.
PC2: Asus H81M-PLUS Motherboard, Intel i3-4160 CPU, 16GB RAM, NVIDIA GeForce GTX 1050 Graphics Card, 1x Samsung 870 EVO 250GB SSD, 1x Samsung 860 EVO 250GB SSD, Windows 10 Home 22H2 64bit.

Reply | Quote

https://docs.microsoft.com/en-us/windows/release-information/windows-message-center#366

Timing of Windows 10 optional update releases (November/December 2019)

There will be no more optional “C” or “D” releases for the balance of this calendar year. Note There will be a December Security Update Tuesday release, as usual.

2 users thanked author for this post.

CyGuy, woody

Reply | Quote

Son of a gun!

I looked all over and didn’t see any qualifier on that announcement – so I assume it applies to all versions of Win10. Wonder if it applies to Win7 and 8.1 (“Monthly Rollup Preview”) as well.

Reply | Quote

Yes, i believe it applies to all Windows versions

holidays 🙂

Reply | Quote

Well, it does not 🙂

Windows 7 and 8.1 got Preview Rollups:

https://support.microsoft.com/en-us/help/4525252/windows-8-1-kb4525252
https://support.microsoft.com/en-us/help/4525251/windows-7-update-kb4525251

with previews for .NET 4.8 and 4.7.2 too

1 user thanked author for this post.

woody

Reply | Quote

Well, I decided to be an adventurous soul and used the new Media Creation Tool to download 1909 and create an ISO file.

Brought my 1903 Pro installation up to date (I wasn’t offered 1909 via Windows Update) then used the ISO file to upgrade to 1909 – disconnected from the Internet, as always.

Bit of an ‘anti climax’ – everything looks exactly the same as 1903.

A few things I’ve noticed:

Cortana was re-enabled (I had it disabled with O&O’s ShutUp10).

Several other items were re-enabled according to ShutUp10 – particularly telemetry.

Meltdown/Spectre protection was re-enabled (I had it disabled with InSpectre). Disabled it again.

OneDrive icon was re-added to the Start Menu (I have OneDrive and most of the other unwanted apps ‘removed’ with the Tools option of CCleaner). The icon was easily removed but I had to do it from the file location, couldn’t delete it directly from the Start Menu.

Took me a while to figure out (had to Google) how to delete the huge windows.old folder from the root of the C drive – was protected by “TrustedInstaller”. Meh!

Checked Windows Update again and installed the November updates for 1909. I’m now on 1909 (OS Build 18363.476).

Everything is running smoothly so far. Of course, I do have Macrium images to go back to if things go wrong.

PC1: Gigabyte B560M D2V Motherboard, Intel i5 11400 CPU, 16GB RAM, NVIDIA GeForce GTX 1650 Graphics Card, 1x Samsung 870 EVO 250GB SSD, 1x Samsung 860 EVO 250GB SSD, Windows 10 Professional 22H2 64bit.
PC2: Asus H81M-PLUS Motherboard, Intel i3-4160 CPU, 16GB RAM, NVIDIA GeForce GTX 1050 Graphics Card, 1x Samsung 870 EVO 250GB SSD, 1x Samsung 860 EVO 250GB SSD, Windows 10 Home 22H2 64bit.

1 user thanked author for this post.

CyGuy

Reply | Quote

Thanks, a very helpful, detailed post of useful info.

Reply | Quote

Does 1909 come with a full version or is it just an CU update.  Sounds like you installed the full version of 1909.

Reply | Quote

It depends.
If you are on 1809 or anything before, you will get a full version.
If you are on 1903 with the latest CU installed (KB4524570 Build 18362.476) you will only get a small Enablement package that will turn on the 1909 features which are already installed.
1903 and 1909 have the same core. The difference is the Enablement package.

1 user thanked author for this post.

CyGuy

Reply | Quote

Can I get the full version of 1909 if I want to do a clean install

Reply | Quote

Yes, you can download the Media Creation Tool from Microsoft (US English) to any Windows PC. Specify that you want to create the installer for another PC, and it will create an ISO that you can burn onto a DVD or bootable USB drive.

If you boot from the created install media, it will do a clean install. If you access setup.exe on the install media from a running Windows installation, it will do an in-place upgrade.

Reply | Quote

PKCano wrote:

If you boot from the created install media, it will do a clean install. If you access setup.exe on the install media from a running Windows installation, it will do an in-place upgrade.

Whether you boot from USB/DVD or run setup from a mounted ISO, you can select to keep files, settings and apps or to delete everything.

Reply | Quote

Key question: does the 1909 feature update also appear with 365 days of feature deferral configured? If so, I foresee troubles ahead. If only because you’ll never know when a ‘click here to download’ unwantedly changes to ‘downloaded, click to reboot’ 🙁

Reply | Quote

[deadite9]

For me, it did not appear with a 365-day deferral (set via gpedit) on a secondary PC. I decided to give the 1909 update a spin on that machine (which was already running 1903) since it’s configured almost exactly like my primary, just to see how it went. The upgrade link didn’t appear, even after installing this month’s 1903 CU, so I set the deferral back to zero to see if that would make it magically appear. It still didn’t, but the 1909 Feature Update did show up in the list when I ran wushowhide. Checking for updates found and installed the 1909 update, the same as it’s been for previous releases (i.e., no prompts to update— just an immediate download and install). Maybe if I’d left it sitting for a while, I would’ve gotten the advertised link to download/install at my leisure.

• This reply was modified 4 years ago by deadite9.
• This reply was modified 4 years ago by deadite9.

1 user thanked author for this post.

CyGuy

Reply | Quote

Isn’t CVE-2019-1419 (OpenType Font Parsing Remote Code Execution Vulnerability) pretty bad?

“A remote code execution vulnerability exists in Microsoft Windows when the Windows Adobe Type Manager Library improperly handles specially crafted OpenType fonts….

There are multiple ways an attacker could exploit the vulnerability, such as by either convincing a user to open a specially crafted document, or by convincing a user to visit a webpage that contains specially crafted embedded OpenType fonts.”

Since it’s the Type Manager Library, that makes it sound like any browser that reads the embedded font will trigger the vulnerability. CVE-2019-1441 seems similar but instead through the Windows font library.

Moderator note: Please provide source for quoted material.

Reply | Quote

Isn’t CVE-2019-1419 (OpenType Font Parsing Remote Code Execution Vulnerability) pretty bad?

It is rated “critical”; however, it remains unexploited — and is considered as “less likely” to be exploited.

Please see: https://isc.sans.edu/forums/diary/November+2019+Microsoft+Patch+Tuesday/25516/

Reply | Quote

Can confirm that, no 1909 for me indeed! On one laptop here we got some weird error in the logs AFTER updating and the first login. WindowsWcpOtherfailure3 type 5 in the logs, with an error report send to MS, regarding Windows Modules Installer worker. Plus an error that the service Delivery Optimation wasn’t correctly shut down. But all is fine, no failed updates or anything. And after a reboot just to be sure no weird other effects. So guess we’ll leave that as it is, impossible to find the cause of such cryptic one-shot fun anyway. Oh and of course I am talking about NOT the updgrade to 1909, but the regular monthly patch round for 1903 😉

Reply | Quote

For those who may be interested, Brian Krebs (Krebs on Security) has posted his overview of this month’s updates: Patch Tuesday, November 2019 Edition — https://krebsonsecurity.com/2019/11/patch-tuesday-november-2019-edition/.

 

1 user thanked author for this post.

CyGuy

Reply | Quote

Any one that uses an SD card for File History, or other backups, should remove the card before updating v.1909. I, again, experienced corruption of my SD card, which happened  before when a feature update also changed the drive letter. I’ll need to let my shops customers know that there is a risk of data corruption, again, with an SD card in a Realtek reader, and to remove the card before updating,

GreatAndPowerfulTech

Reply | Quote

Adobe Flash Player has been updated to version 32.0.0.293; as their Security Bulletins and Advisories site has not yet been updated, it is not known whether this is security related (https://helpx.adobe.com/security.html).

Reply | Quote

Cannon Fodder Volunteer Unscathed

First I let Windows Update install KB4524570 and got it succesfully installed on 13 Nov 2019.
Then I let it download and install Feature Update v.1909, which I also got succesfully installed on 13 Nov 2019.

So now I have Windows 10 Home x64 v.1909 build 18363.476.
Though PC Settings/System/About still says “Installed on 4 July 2019”.

1 Desktop Win 11
1 Laptop Win 10
Both tweaked to look, behave and feel like Windows 95
(except for the marine blue desktop, rgb(0, 3, 98)

Reply | Quote

Presumably because, via Windows Update, the 1909 feature upgrade from 1903 was delivered via a CU, it advanced the build numbers (so all the various ways you can check show 1909 18363.476) but the system installation date stays at whenever 1903 was installed and there is no windows.old folder created. That means there is no restore previous version available (in Settings- Update & Security- Recovery) where you have been running your existing version for more than a few weeks.

So the new version 1909 would just be “reversed” via Uninstall Updates? (Seems odd to reverse a “version upgrade” that way! – not really c’mon MS – 1909 is just a name before big changes next year isn’t it)

Did anyone who has gone from an earlier version than 1903 to 1909 get a windows.old folder created for 1903 on the way through to 1909? What did other upgrade methods do?

Reply | Quote

You should not get a Windows.old folder between 1903 and 1909 because both have the same system core. You are not installing a new altered OS.
If you have 1903, the difference is a “Master Switch” that turns on the 1909 features that are already there. I’m guessing that going back to 1903 (if possible) is simply turning the feature switch back off.

1 user thanked author for this post.

Carl D

Reply | Quote

Thanks, PKCano.

Actually, what I’ve just done is go back to 1903 (with a Macrium image) and then tried Windows Update again… I didn’t realize that I had ‘Activate deferring of upgrades’ turned on in O&O’s ShutUp10.

After turning that off I was then offered the upgrade to 1909 (after the regular monthly updates) which took only a couple of minutes to install. No change of settings or app defaults and no ‘windows.old’ folder this time.

PC1: Gigabyte B560M D2V Motherboard, Intel i5 11400 CPU, 16GB RAM, NVIDIA GeForce GTX 1650 Graphics Card, 1x Samsung 870 EVO 250GB SSD, 1x Samsung 860 EVO 250GB SSD, Windows 10 Professional 22H2 64bit.
PC2: Asus H81M-PLUS Motherboard, Intel i3-4160 CPU, 16GB RAM, NVIDIA GeForce GTX 1050 Graphics Card, 1x Samsung 870 EVO 250GB SSD, 1x Samsung 860 EVO 250GB SSD, Windows 10 Home 22H2 64bit.

Reply | Quote

No, the transition between 1903 and 1909 is delivered via small update KB4517245

to return to 1903, go to Installed Updates and uninstall it
“Feature Update to Windows 10 Version 1909 via Enablement Package (KB4517245)”

warning, running any disk cleanup after installing KB4517245 may make it permanent
i.e. the only way to remove is via restore point, if possible

2 users thanked author for this post.

woody, PKCano

Reply | Quote

Hello all,

Is there any sign of the Compatabilty Appraiser in this month’s Security Only update for Windows 7? There seems to have been a pattern since July with each alternate month including it…

 

Reply | Quote

FYI: Tthat the latest security updates for Office are causing Access database access error 3340 ‘Query is corrupted’

https://borncity.com/win/2019/11/13/office-november-2019-updates-are-causing-access-error-3340/

Ex Microsoft Windows (Insider) MVP, Microsoft Answers Community Moderator, Blogger, Book author

https://www.borncity.com/win/

1 user thanked author for this post.

woody

Reply | Quote

lightbulb wrote:

Hello all,

Is there any sign of the Compatabilty Appraiser in this month’s Security Only update for Windows 7? There seems to have been a pattern since July with each alternate month including it…

 

Word of warning said on November 12, 2019 at 10:53 pm

I noticed that “Microsoft Compatibility Appraiser” scheduler was re-enabled after this update

https://www.ghacks.net/2019/11/12/microsoft-windows-security-updates-november-2019-overview/

Reply | Quote

You are referring to having installed the Monthly Rollup, of course.
The Security-only Update for November is telemetry-free.

Reply | Quote

[AussieBoy]

Still learning my way around here – had to click ‘reply’ to this post as I could not find anywhere an icon for a NEW post to be made. probably just ol’ fella’s disease 🙂 Anyway, I’m posting to ask about November Win7 patch KB4525235 (311mb) as it is the sole patch showing up in MS Updates for Nov for me. It is described as a ‘Quality Rollup’ x64 patch. I searched absolutely everywhere on Woody’s Forums and every link on the page but nothing – only about some other Win7 patch number (KB4523206) which isn’t showing up for me. What does SSU stand for BTW? Anyone know why there’s nothing written or reported on this patch here? Thanks all!

• This reply was modified 4 years ago by AussieBoy.

1 user thanked author for this post.

acemorgan

Reply | Quote

KB4525235 is the Monthly Rollup Update for Win7. It is the cumulative Security Update for November.

KB4523206 Is the Servicing Stack Update (SSU). It is the update for the Windows Update mechanism itself. It has to be installed exclusively (by itself) and will not show up in the Windows Update Important update list until there are no other pending updates (checked or unchecked) in the queue. So, after you have installed (or hidden) all the other updates, go back and check for updates again and KB4523206 should show up. Install it.

You can create a new post in the box at the bottom of the thread, and then “Submit.”
If you want to reply to a post, click the “Reply” button at the top of the post you want to reply to. Then in the entry box at the bottom, type your message. That will nest your reply under the original post.

2 users thanked author for this post.

z-quirp, AussieBoy

Reply | Quote

[AussieBoy]

Thank you very, very much PKCano. That is a very impressive reply – seriously – it covers all the points I was asking about perfectly, succinctly. Much appreciated! Bonus: perfectly punctuated as well – a rarity on the web these days. Yes, so thank you for your prompt response, all is clear to me now and I know what to do with our ‘wonderful’ patches from MS. I also now know how to post new posts 🙂 Cheers from Australia!

• This reply was modified 4 years ago by AussieBoy.
• This reply was modified 4 years ago by AussieBoy.

1 user thanked author for this post.

warrenrumak

Reply | Quote

Okay, one W10 1809 (Pro 64) box installing KB4523204 and KB4523205 without being told to. As in policy-managed, not approved.

… BUT apparently another third-party tool that can trigger updates WAS run today.

Sheesh, herding cats and all…

At least nothing seems to have broken yet.

Reply | Quote

I have some questions and comments about the Windows 7  MSRT patch.  I, too, could not get it to install on my 32-bit system. – 800B0109.  I went to the MS Catalog, as per a reply above, and I saw two files I could download.  One had “delta” in its name, and the other did not.  What is the difference between the two?  I downloaded and ran the non-delta executable.  It ran without problems.  A number of years ago I ran mrt.exe manually, but it had an error; one site I visited said, essentially, do not worry about it.

As for these 8-hexadecimal digit error codes – Are the codes common across the MS software platforms? Does this code from WU have the same reason as the same code produced by another piece of MS code?  A search for that error code pointed to one article about a patch not signed properly, but another pointed to a “fix Windows Update” URL.  When I started with IBM mainframes in 1967, IBM had a manual “Messages and Codes” which explained all of the error codes produced by the mainframe operating system.  Instead of a WU “Get help for this error” hyperlink, why can’t MS produce a web page that has all of these error codes with a detailed explanation?

Reply | Quote

bsfinkel wrote:

Instead of a WU “Get help for this error” hyperlink, why can’t MS produce a web page that has all of these error codes with a detailed explanation?

MS does have some:

Windows Update error codes by component

Windows Update common errors and mitigation

Get help with Windows 10 upgrade and installation errors

1 user thanked author for this post.

AJNorth

Reply | Quote

I looked at the first two Windows Update error codes hyperlinks, and NEITHER has the 800B0109 code that I received.  The third hyperlink pertains to Windows 10, which I am not yet running.

Reply | Quote

0x800B0109 = A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider

do you have sha2 support patches installed?
and i remember MSRT had issue and got rereleased later

Reply | Quote

My complaint was that the hexadecimal error codes were NOT documented.  You proved my point by pointing me to two Windows Update URLs, and neither contains the Windows Update error code that I received.  I rest my case.

I have to assume that these error codes are chosen “out of the blue” at random by the code developers,  I think that there must be a central MS error code repository, and the contents of that repository need to be placed on a web site.

 

Reply | Quote

Update kb4525235 came in and I hid it, checked again for updates and kb4523206 came in and it was hidden. Didn’t receive the MRST. Will wait for the dust to settle before installing the SSU first.

Edition Windows 11 Pro
Version 23H2
Installed on ‎10/‎19/‎2022
OS build 22631.2715

Reply | Quote

I’m confused:

Group B Security-only Updates and the IE11 Cumulative Update have been updated for November on AKB2000003.

UPDATE NOTE: According to @abbodi86, the November SOs are telemetry free.

But:

Word of warning said on November 12, 2019 at 10:53 pm

I noticed that “Microsoft Compatibility Appraiser” scheduler was re-enabled after this update

So does that mean it’s safe to install this month’s SO (from the avoiding telemetry point-of-view)?

Reply | Quote

We are on DEFCON-2. It is not time to install any Nov. update. WAIT.

But when the DEFCON go-ahead is given, it’s @abbodi86 ‘s information you want to listen to. The Nov. SO is telemetry-free.

Reply | Quote

RetiredGeek wrote:

Bbearen, could you please post the reg file? 😁

Actually, it’s not a reg file, it’s a bunch.  I have them assembled into the particular Libraries/Special Folders, so you can leave whatever you want to use intact.  Use right-click-Edit to see what’s inside each one.

Important Note: Before importing the “Remove Quick Access” reg file, go to Control Panel > File Explorer Options and make sure “Open File Explorer to:” is set for This PC.  If “Open File Explorer” is set for Quick Access, it won’t open after the reg file is imported.

Also, some of the registry keys/values are owned by TrustedInstaller.  To get around that I use Process Hacker and the plugin “Run as trusted installer” to open regedit.exe, then it’s just File > Import, one at a time.

And here’s a zip file with all of them:

Completely-Remove

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We were all once "Average Users". We all have our own reasons for doing the things that we do with our systems, we don't need anyone's approval, and we don't all have to do the same things.

Computer Specs

Reply | Quote

[dportenlanger]

I am confused.  I added a couple of 1903 machines to my domain last month for testing.  In WSUS, I only have Windows 10 checked in Products and Classifications, not every specific version.  When the sync would run, it would get the updates required for every version of Windows through 1809

Last month, none of the 1903 updates were listed.  I thought that was odd, so I checked Windows 1903 in WSUS and Windows 10 in Products and Classifications.  No other versions were checked.  WSUS listed all the updates for every version including 1903.  Then I went and unchecked the specific 1903 option.

This morning I checked what updates were synchronized.  Again, every version of Windows except 1903 is listed in updates.

Do we now have to explicitly check 1903 in Products and Classifications to get the 1903 updates?  Is this a requirement I missed?

Thank you in advance.

• This reply was modified 4 years ago by dportenlanger.
• This reply was modified 4 years ago by dportenlanger.

Reply | Quote

A colleague found the answer.

https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/Updating-Windows-10-version-1903-using-Configuration-Manager-or/ba-p/639100

 

1 user thanked author for this post.

b

Reply | Quote

bbearren wrote:

Networking is working normally for me. Only one PC on 1909, but it and all the others can look both ways. One minor annoyance is that 1909 re-installed those useless (for me) Libraries and Special Folders again. I had to import my reg files into the registry for each user to get rid of them one more time.

Yesterday I used a mounted ISO to run the in-place upgrade to 1909.  That’s where the Special Folders came in.  Today I restored my OS drive image from 11/11 (took all of 3:05) and then ran through Windows Update.  I was offered to download and install 1909 on the second round.  No Special Folders this time.

Networking is still normal.  When I open File Explorer, there is about a five second delay before the Network folder populates, but that is normal behavior, so no real changes.

My NAS and my laptop were both offered to download and install 1909 today, and that went very quickly and smoothly.

All systems are nominal.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We were all once "Average Users". We all have our own reasons for doing the things that we do with our systems, we don't need anyone's approval, and we don't all have to do the same things.

Computer Specs

Reply | Quote

Group A,  Win7X64,  Home Premium,  AMD.   KB4525235  roll up,   KB4523206 service stack,  so far no MSRT received .  No problems.

1 user thanked author for this post.

fernlady

Reply | Quote

Windows 7 x64 Home Premium Group A

I also was able to install the monthly rollup KB4525235 yesterday. At that time I was offered the MSRT update KB890830 which failed to install. Accordingly, I had hid the MSRT update.

Today, however, when WU checked for updates, I noticed that the hidden MSRT update was removed. Therefore, it appears that Microsoft has pulled the MSRT update and I would imagine that it will be offered again once Microsoft has fixed it.

1 user thanked author for this post.

Pierre77

Reply | Quote

Yes, it is gone. MSRT KB890830 has been pulled like a puff of smoke.

Reply | Quote

That is interesting, as I just now downloaded it (for Windows 7 x64) from https://www.microsoft.com/en-us/download/details.aspx?id=9905 (version 5.77, with a digital time stamp of Nov 7, 2019); I’ve now successfully installed it on eleven Win 7 x64 machines (with zero failures).

Reply | Quote

there’s a new cumulative update for 1703 this November – KB4525245

however, since 1703 was already EOL’ed on PCs, this new update is for 1703 on Surface Hub devices only

Current status of Windows 10, version 1703

Windows 10, version 1703 has reached end of service for all editions. To continue receiving security and quality updates, Microsoft recommends updating to the latest version of Windows 10.

Surface Hub devices remain in support. Starting on November 12, 2019, updates for Windows 10, version 1703 will be available only for Surface Hub devices. Update information and Surface Hub known issues will be listed on this page.

Reply | Quote

I got the Tuesday updates for 1903 Home on Tuesday with no problems, and no recurring MSRT update. On Wednesday, I decided to install the 1909 update. It shows it installed twice in the update history, but other than that, no issues or problems thus far.

For some reason, the last couple of cumulative updates have installed twice, but they don’t show as installed twice in the update history. Only the 1909 Feature update is shown as installing twice. Anyone experiencing the same or know why that is the case?

Reply | Quote

I was happy to see that Microsoft released an “enablement package” for 1909 in WSUS so that our 1903 people can be upgraded (when approved) without another major install occurring. More like a service pack from the old days which I think Woody already mentioned.

A step in the right direction and my thanks to Microsoft for the way this upgrade was handled. Especially for making this available in WSUS.

Red Ruffnsore

Reply | Quote

anonymous wrote:

For some reason, the last couple of cumulative updates have installed twice, but they don’t show as installed twice in the update history. Only the 1909 Feature update is shown as installing twice. Anyone experiencing the same or know why that is the case?

Until I updated to 1903, every cumulative update was installing twice (first time “failed” and second time “successful”). So far I haven’t seen that with the pair of .NET updates that I installed on 1903.

Windows 10 Home 64-bit

Reply | Quote

[EP]

woody

new preview Rollups for November 2019 released Tue. 11/19:

KB4525251 for Windows 7
KB4525252 for Windows 8.1

edit: no new “C” or non-security updates for older Win10 versions today, maybe either later this week or next Tuesday Nov. 26

• This reply was modified 4 years ago by EP.

1 user thanked author for this post.

woody

Reply | Quote

Happy Thanksgiving to all!

it seems MS will skip releasing the optional, non-security or “C” / “D” patches for Windows 10 as the month of November is nearly over

Reply | Quote

We aren’t expecting C or D week patches next month either, as Microsoft announced earlier this month:

abbodi86 wrote:

https://docs.microsoft.com/en-us/windows/release-information/windows-message-center#366

Timing of Windows 10 optional update releases (November/December 2019)

There will be no more optional “C” or “D” releases for the balance of this calendar year. Note There will be a December Security Update Tuesday release, as usual.

1 user thanked author for this post.

woody

Reply | Quote

I covered that announcement here.

What’s weird is that we still haven’t seen the fixes for the Access error in anything but Office 2016.

Reply | Quote

They are already out

November 27, 2019, update for Office 2013 (KB2965317)
November 27, 2019, update for Office 2010 (KB2986256)

2 users thanked author for this post.

woody, columbia2011

Reply | Quote

Information on fix for Access error.

https://support.office.com/en-us/article/access-error-query-is-corrupt-fad205a5-9fd4-49f1-be83-f21636caedec

Reply | Quote

Is it safe to install kb4525243, kb4525252, and kb4524743 in a Windows 8.1 format?

Reply | Quote

We are still on DEFCON-2 (see top of page) which means the Nov. Rollup has not been approved by Woody yet. When the DEFCON number is 3 or greater, Woody will publish instructions for safe patching.

We do not recommend installing the Preview patches as they are UNCHECKED Optionals.

1 user thanked author for this post.

woody

Reply | Quote

I installed Win 7 November patch KB4525235 this morning.  After the reboot, EventVwr no longer works because the MMC plug-in crashes.  I do not know anything about the internals of the Event Viewer, so I have no idea why the MMC plug-in is required nor do I know what it does.  It appears that the Event Viewer will not work without the MMC plug-in.  I have no proof, but I have to assume that something in the November patch broke the MMC.  I have a list of changed files that were backed up during my incremental backup, but I do not know the filename(s) associated with the Event Viewer.

Reply | Quote

bsfinkel wrote:

I have no proof, but I have to assume that something in the November patch broke the MMC.

I have no proof, but I believe it’s far more likely that your ongoing issues are attributable to your hard drive’s need for a chkdsk after every reboot.

Reply | Quote

Did you install the Nov. Servicing Stack Update KB4523206?

Reply | Quote

The patch KB4523206  was never offered via Windows Update, and I almost never go searching for patches.  Also, I have no idea if that patch was included in a subsequent cumulative patch.

Reply | Quote

KB4523206 is the Servicing Stack Update (SSU). It was/is offered by Windows Update.

BUT
SSUs have to be installed exclusively (by themself). They will not show up in the Windows Update Important queue unless/until there are NO OTHER PENDING UPDATES (checked or unchecked) in the Important list. SO, you have to install or hide anything in the Important list, then check for updates – until there is nothing left (except the SSU, which will then show up).
After installing the SSU, you can unhide anything you have hidden that you want to restore.

2 users thanked author for this post.

Fritz, woody

Reply | Quote

I dd see the SSU update by itself when I checked Windows Update.  I did install it.  After the installation, I again ran EventVwr, and it worked fine.  I cannot conclude that the SSU update fixed the EventVwr problem, as I assume that the SSU update pertains to the Windows Update process.

Reply | Quote