October 2019 Patch Tuesday problems

[woody]

I see remarkably few reported problems with the October 2019 incarnation of Patch Tuesday. Looks like the printer problems have been resolved (only to
[See the full post at: October 2019 Patch Tuesday problems]

1 user thanked author for this post.

Fred

Reply | Quote

[amidieus]

Hi. Long time, first time here. Silly questions, but wondering if the DEFCON 1 also applies to servers?  I only patch servers and not workstations, and I know issues like printing bug do not really apply to Server OS, but curious to know if the posts in this site apply to Server OS as well.

 

Thanks.

1 user thanked author for this post.

woody

Reply | Quote

[PKCano]

Yes, the postings also apply to Servers. Patch Lady Susan Bradley’s Master Patch List is aimed at the business environment, while the Woody’s DEFCON rating mostly applies to the consumer audience. The Master Patch List is accessible from the menu button at the top of the page, but requires a Plus Membership (see the notes at the top right of the page under the login).

A one-year Plus Membership is based on a donation of your choice.

1 user thanked author for this post.

woody

Reply | Quote

[woody]

Just found a note on Reddit frompyork211099 

who says that they’re still getting a “Critical error” when trying to use the Start menu in 1903, after the latest cumulative update:

Finally found an error message about it though (2 actually one for StartMenu and one for Shell):

Activation for Microsoft.Windows.StartMenuExperienceHost_cw5n1h2txyewy!App failed. Error code: This app does not support the contract specified or is not installed.. Activation phase: No phase defined

and

Activation for Microsoft.Windows.ShellExperienceHost_cw5n1h2txyewy!App failed. Error code: This app does not support the contract specified or is not installed.. Activation phase: No phase defined

Reply | Quote

[Kobold Curry Chef]

I can corroborate. I built a new Win10 Pro v1903 VM earlier this week, using the current v1903 ISO, and experienced the Start menu critical error after KB4524147 was installed. (But not the printer spooler crash that I saw on other, newly upgraded to 1903 boxes.)

After applying KB4517389 and rebooting, the Start menu critical error persists. Hooray!

1 user thanked author for this post.

woody

Reply | Quote

[schwabel_ronald]

I also was seeing the start menu search problem along with the action center refusing to open after installing the patches from before the October patch Tuesday.  removing the cumulative updates allowed the task bar search and action center to run again.

I probably wasn’t very prudent, but I did decide to let Windows Update install the October Patch Tuesday update.  My task bar search, Cortana and Action Center all failed after reboot so I removed the latest patch.

Reply | Quote

[PKCano]

What version of Win10 are you running? 1803, 1809, 1903, or 1909?

Reply | Quote

[schwabel_ronald]

I am running 1903 build 18362.295 – every update I have tried to install since then has  caused my failures.

I just realized that everyone is referring to a ‘Start Menu’ Problem.  My Start Menu is working fine after every one of the updates.  What I am seeing is when I try to use the Task Bar Search box, the Cortana icon and the Action Menu.  They all refuse to respond to any actions.

1 user thanked author for this post.

woody

Reply | Quote

[willie.nilley]

Hello there, my first time here.

I have exactly the problem you describe.

I am on 1903 build 18362.239

cannot install updates without losing search, jumplists, action centre.

start menu works

Have used windows update and MS update catalog.

have run DISM repair, sfc /scannow

each time I try, I have to uninstall or revert to a backup.

I have Kaspersky Free virus checker, just for info, I turn this to ‘paused’ when allowing update to run. Have tried update repeatedly same result. Nothing telling that I can see in event logs.

Cortana is disabled, local login only, user is admin, bing search is allowed in registry.

 

1 user thanked author for this post.

woody

Reply | Quote

[cogx]

I’ve found that doing in-place Windows 10 upgrades will sometimes result in Cortana/Search not working – Start menu comes up fine, just not the search functionality.  The fix I found is to delete the settings.dat file under each of these user folders:

c:\users\%username%\appdata\<wbr />local\packages\microsoft.<wbr />windows.cortana_cw5n1h2txyewy\<wbr />settings\settings.dat

 

Reply | Quote

[woody]

schwabel_ronald wrote:

Task Bar Search box, the Cortana icon and the Action Menu.  They all refuse to respond to any actions.

Have either of you done anything to disable web search in the Cortana Search box?

 

Reply | Quote

[schwabel_ronald]

Of course I have tried to block web searching! I don’t think the web should be involved when I do a search on my local machine.  If I want information from the web I have a web browser (or three) to do that when it is appropriate.

Anyhow, that is a good thought.  I just checked and I have the

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Search “BingSearchEnabled” registry entry set to 0.

Do you think it would be worth setting it to 1?

It never seemed to make any difference the last time I had search problems and I had it set to 1.

1 user thanked author for this post.

Indoda

Reply | Quote

[PKCano]

There have been reports that enabling Edge/Cortana may be a workaround.

1 user thanked author for this post.

woody

Reply | Quote

[schwabel_ronald]

I’m a little bit of a glutton for punishment and I decided to try a few more things.  I did find 3 Group Policy entries that dealt with preventing the task bar search bof from using the Internet.  I disabled them and tried KB4517389 again.  Still no Cortana, Task Bar Search or Action Center.  I don’t ever use Cortana but I do use the Task Bar Search and Action Center frequently so I removed KB4517389 (again)

I’m beginning to think that Microsoft has no clue about what is causing  my problems and might not ever do anything to fix them.

Reply | Quote

[chaloots]

As per previous recommendations provided here I’d paused Windows Updates in Settings a few weeks ago. Updates paused has them currently set to resume on 10/10/2019. Problem is that the pause option in Settings is grayed out and not available, preventing any further delay. Will this mean that the accumulated previous updates will all be installed? How could I re-establish or extend the waiting period?

The duration of a minute depends on which side of the bathroom door you're on.

1 user thanked author for this post.

ashfan212

Reply | Quote

[PKCano]

You will not be able to use the Pause again until the pending updates have been installed. That is the down side of using Pause, although that probably prevented you from getting the bad Sept. patches.

2 users thanked author for this post.

chaloots, woody

Reply | Quote

[chaloots]

Thanks for clearing that point of confusion up for me. Am guessing that many others who also tapped “delay” a few times in Update Settings will also be dealing with what’s been simmering in the background, waiting to be set free.

Once that’s done, presumably this forum will be revising/advising on future slumber settings?

The duration of a minute depends on which side of the bathroom door you're on.

• This reply was modified 1 year, 8 months ago by chaloots.

Reply | Quote

[woody]

I have rigorous instructions at least twice a month, in Computerworld – what to click and how many times. 🙂

As a Plus Member, you’ll get an email Alert the next time the situation changes.

1 user thanked author for this post.

chaloots

Reply | Quote

[woody]

Mayanik Parmar at Windows Latest reports on more Start menu problems:

Users have reported on Microsoft community forum and Reddit that Windows 10 KB4517389 also breaks the Start menu with a critical error, and it’s still unclear what is causing Start menu problems.

(The Reddit link points back to the discussion I noted here.)

Reply | Quote

[numike]

Windows update lets you answer Android calls on a PC
You can now answer, decline and make calls on your Android phone from your PC.
https://www.cnet.com/news/windows-update-lets-you-answer-android-calls-on-a-pc/

Reply | Quote

[b]

Windows Insiders in Fast Ring only, as it’s coming in version 20H1.

Windows 10 Pro version 21H1 build 19043.1081 + Microsoft 365 (group ASAP)

1 user thanked author for this post.

WildBill

Reply | Quote

[woody]

I just tried to get it working and failed miserably. Might be just me, but I couldn’t use my Android phone to make a call after installing it.

MS says the feature is rolling out to anyone with Build 18362.356 or later. That’s the first September cumulative update for Win10 version 1903 . You have to install the Your Phone app on your PC from the Win10 MS Store, and install the companion app on your Android or iPhone.

I discovered – the hard way – that once you’ve installed the Win10 Your Phone app, the only way to get rid of it is to nuke it with a PowerShell command in admin mode.

• This reply was modified 1 year, 8 months ago by woody.

1 user thanked author for this post.

WildBill

Reply | Quote

[b]

Your MS says link there is weird.

The Your Phone app is a standard “in-box” app on versions 1809/1903.

I think you misread something about Android calling, but if you have a link that works I’d like to see it.

Richard Hay has it working, but on Insider build 18363.418 for 1909:

Look at what just showed up in Your Phone for one of my Windows 10 (19H2) Release Preview devices – Build 18363.418. Your Phone app is at Build 1.19092.399.0. There is a toggle in Settings to enable Calls feature. Looking forward to trying this out later! pic.twitter.com/yNHf1S6Du9

— Richard Hay (@WinObs) October 9, 2019

So now testing incoming calls via the Your Phone app. No BT headphones attached – call comes to both the phone and desktop – can answer and hear the call on main desktops speakers. If BT headphones are connected – call does not come through headphones. Must be a BT conflict.

— Richard Hay (@WinObs) October 9, 2019

One nice aspect – Your Phone does not have to be open to receive calls via the Calls feature.

— Richard Hay (@WinObs) October 9, 2019

So – I just decided to try the Your Phone Calls feature again on my main desktop but not using my Surface Headphones – and the call audio came across the main PC speakers!

— Richard Hay (@WinObs) October 9, 2019

Windows 10 Pro version 21H1 build 19043.1081 + Microsoft 365 (group ASAP)

2 users thanked author for this post.

woody, WildBill

Reply | Quote

[b]

I eventually figured out that you’d reversed the “MS says” and Powershell command links.

The WindowsClub link say, “Currently the Your Phone app supports sharing photos and SMS texts only.” which is how it’s been for the last year.

Only Insider builds get Android calls/calling via Your Phone so far.

Windows 10 Pro version 21H1 build 19043.1081 + Microsoft 365 (group ASAP)

2 users thanked author for this post.

woody, WildBill

Reply | Quote

[b]

woody wrote:

MS says the feature is rolling out to anyone with Build 18362.356 or later.

Yes, you’re right. I’m now confused about which part of Your Phone Calls, if any, requires being an Insider.

Windows 10 Pro version 21H1 build 19043.1081 + Microsoft 365 (group ASAP)

Reply | Quote

[616c]

Spinny thing and a Sophos Safeguard logo.

Vacation request looks good right now.

Reply | Quote

[616c]

After 4 hours of waiting, and two forced power cycles, I’m up and running.

The user population should not be the only quality check.  I know they fired those people a while ago, and it saves them a ton of money to just roll things out and patch the patches.

This is the 21st century:  Don’t wast time testing.  Force things to fail fast.  Then fix it.

Reply | Quote

[GoneToPlaid]

All of my computers are Windows 7 x64 Group B. I did a full backup of my primary computer’s OS partition two days ago. Yesterday I installed the 2019-10-08 KB4520003 security only update. This is one of those updates which reboots twice in order to fully install. The installation actually was rather quick, and there appear to be no issues. No disabled telemetry was reactivated. Then I installed the 2019-10-07 IE11 KB4519974 cumulative update. IE opens and works. I haven’t done any further testing, other than simply using my computer.

2 users thanked author for this post.

SueW, Myst

Reply | Quote

[anonymous]

Did you have all the latest SSU and SHA-2 updates installed as well? And that looks like some good news for Windows 7 Security Only folks but Telemetry not turned on is different from Telemetry not installed.

So I’m wanting for there to be verification of no Telemetry code at all present on the Windows 7 Oct 2019 Security Only update. I have skipped the Telemetry Included “Security Only” W7 updates entirely and do not want that code on my system, disabled or not.

Reply | Quote

[GoneToPlaid]

Yes. The latest SSU and SHA-2 updates for Win7 computers which I have installed are the ones released on 2019-09-09. There is a later SHA-2 update for Windows Server 2012 which was released on 2019-10-08. The update catalog erroneously lists this 2019-10-08 update as being for Windows Server 2008 and not for 2008 R2, when in fact the update is for both.

Reply | Quote

[EP]

I will hold off a week until at least next Tuesday October 15 to install the new security updates released Oct. 8.

some people who have installed the out-of-band updates between Sept. 23 & Oct. 4 may have gotten burned

btw woody – the KB4519338 cumulative update for v1809 is build 17763.805, not .806 as listed in Microsoft support KB article 4519338 (that article lists that CU as .805).

See this post from the NotebookReview forums – KB4519338 is 17763.805 as shown in the About Windows dialog box.

Edit: I almost forgot to mention – the KB4520010 cumulative update is the very last update for the Windows 10 Creators Update version (1703) as the 1703 release is fully out of support on 10/8/2019.

• This reply was modified 1 year, 8 months ago by EP.
• This reply was modified 1 year, 8 months ago by EP.
• This reply was modified 1 year, 8 months ago by EP.

Reply | Quote

[E Pericoloso Sporgersi]

I requested the October 8 update(s).

I got KB4517389, and the usual anti-malware and AV updates.

They installed flawlessly. No issues at all. 

All that on a Clevo P17SM-A, Windows 10 Home x64 v.1903

What’s keeping v.1909? Or will that be skipped in favour of v.2003? 

Reply | Quote

[Kirsty]

E Pericoloso Sporgersi wrote:

What’s keeping v.1909? Or will that be skipped in favour of v.2003?

No, it’s not being skipped, based on this:

 
What’s new in Windows 10, version 1909
October 8, 2019

The next feature update for Windows 10 (known in the Windows Insider Program as 19H2) will be a scoped set of features for select performance improvements, enterprise features, and quality enhancements. To deliver these updates in a less disruptive fashion, we will deliver this feature update in a new way, using servicing technology (like the monthly update process) for customers running the May 2019 Update who choose to update to the new release. … When 19H2 is officially released, it will be referred to as “version 1909.”

Read the full blogpost here from the Windows Insider Program docs.

1 user thanked author for this post.

E Pericoloso Sporgersi

Reply | Quote

[EP]

read this recent Tweet from Zac Bowden, Kirsty

GA or public release of 1909/19H2 possibly late October 2019 or November 2019
sorry folks…public must wait longer for official 1909 release

Reply | Quote

[woody]

An odd report from @KristoferA on Twitter:

Have you heard anything about an increase of Win10 BSODs with error code INTERNAL_POWER_ERROR after the September patches for Win10 1809?

Unfortunately, I don’t have any details, just empirical observations; I have just noticed an increase in BSODs over the past week or two. The only recent changes to the affected systems is that they got the Sept patches around 2 weeks ago.

Which means it isn’t due to this week’s Patch Tuesday patches. Anybody else see this?

Reply | Quote

[anonymous]

Edge is broken for me.  Out of Band patches already applied: 4522014 and 4524149.  After application of 4520008, Edge will not launch.

Reply | Quote

[woody]

So you’re on version 1803.

If you uninstall the patch, what happens?

Reply | Quote

[anonymous]

I am on 1809 and having the same issue with Edge not loading after installing October 8, 2019—KB4519338 (OS Build 17763.805).

Uninstalling KB4519338  restores Edge’s functionality.

I pushed out KB4519338 and KB4521862 (Servicing Stack Update) at the same time so I thought it may have been related to the install order so I tried removing KB4519338  and then re-installing KB4519338.  That did not help.

Reply | Quote

[anonymous]

My nephew has an HP Pavillion laptop running Windows 10 v1903 – assuming home version.

it automatically downloaded and installed three updates on 10-9-19:
KB4517389
KB4515871
KB4521863 – security patch

After the pc rebooted, once the desktop icons loaded, the pc started flashing on and off – like a strobe effect.  A restart did not clear this up.
Some programs launched, others wouldn’t.
I was able to finally, uninstall the first 2 updates , didn’t think the security patch would have messed things up, restart the pc and all was fine.
I looked up both those KBs, but did not see anything glaring that might cause this issue.

Anyone else see anything similar?

thanks,
George

Reply | Quote

[smcabery]

Observation,

Just manually installed KB4517389 on a VM and the printing issue does seem to be fixed however Edge would not run. Outlook would not run. Upon further review there were several processes suspended.  Uninstalled KB4517389 and VM was working perfectly with no processes suspended.  VM is currently sitting at 18362.357

1 user thanked author for this post.

woody

Reply | Quote

[anonymous]

Many comments in Günter Born’s Blog state that Edge is not starting anymore after applying the recent 1903 Update.

Reply | Quote

[mark.busby]

Hi there,

Is anyone aware of issues/a fix for the symptoms below please.  Desperate for a fix asap !

– Windows 10 (1903 latest version/updates as on today) or Windows 7 32-bit
– After installing KB4517389 on these Windows systems, when opening 16-bit applications an error message is displayed “unexpected error; quitting”
– After removing the update the application works fine once more.

I’d like to establish what is causing this error so I can prevent it from crashing my 32-bit apps, or how to prevent this single update from installing automatically as part of the Windows Updates process in the future.

Thank you,
Mark Busby
Moderator Edit: Removal of email address

2 users thanked author for this post.

fixnstuff, woody

Reply | Quote

[PKCano]

There are third-party apps that block Windows Update.

Reply | Quote

[E Pericoloso Sporgersi]

PKCano wrote:

There are third-party apps that block Windows Update.

There’s also Winaero Tweaker (recommended by Deanna McElveen).

Among many others interesting tweaks, Winaero Tweaker can block Windows Update indefinitely.

Reply | Quote

[woody]

If you’re running 1903, just click to delay updates for 7 days. Click it four or five times.

Reply | Quote

[anonymous]

https://answers.microsoft.com/en-us/windows/forum/all/windows-update-kb4517389-causing-vbrun300dll-to/efdb6817-2af8-4d4b-acc5-7ef745b687c2

1 user thanked author for this post.

woody

Reply | Quote

[woody]

Microsoft really has a thing about VB, yes?

Reply | Quote

[anonymous]

There’s an update on that microsoft thread, 10/26/2019 that says Microsoft released a fix for Windows 10.. no news yet for Win7

“After installing KB4522741 and KB4522355 the problem at my Machine Win10Pro 32bit with old 16-bit programs (unexpected error;quitting) is gone.”

James

Reply | Quote

[EP]

could you try the preview rollup for win7 – KB4519972?
maybe the VB fix for Win7 is in that preview rollup

1 user thanked author for this post.

bassmanzam

Reply | Quote

[fixnstuff]

mark.busby wrote:

Hi there,

Is anyone aware of issues/a fix for the symptoms below please.  Desperate for a fix asap !

– Windows 10 (1903 latest version/updates as on today) or Windows 7 32-bit
– After installing KB4517389 on these Windows systems, when opening 16-bit applications an error message is displayed “unexpected error; quitting”
– After removing the update the application works fine once more.

I’d like to establish what is causing this error so I can prevent it from crashing my 32-bit apps, or how to prevent this single update from installing automatically as part of the Windows Updates process in the future.

Thank you,
Mark Busby
Moderator Edit: Removal of email address

A similar issue is with KB4519338 (OS Build 17763.805) for 1809. My 16 bit apps now throw an odd error. External XVT error. Removing KB4519338 resolves the issue but I need to know how to work around this so all security updates are installed.

Reply | Quote

[EP]

did you try the KB4520062 update for 1809 (build 17763.832)?

• This reply was modified 1 year, 7 months ago by EP.

Reply | Quote

[Speccy]

Reporting from a managed set of Virtual Machines (VMs) and physical systems (including a couple of Win7 legacy dual core workhorses) backed up and updated as described below.

Previous notes:
1. I skipped August updates (moved from July to September).
2. For those systems where .NET Framework is required (not all do) I stick with v4.6.2 on Win7 (had issues in the past with v4.7.x) and I’m currently using (when needed) v4.7.1 on Win8.1 (v4.7.2 might be OK but I haven’t had time and opportunity yet to assess that properly) as I find these versions to be the most stable ones for my particular needs (third-party software being used and how/what these systems are used for). Other users might have different needs (or no need for .NET Framework at all): Microsoft has helpful information here and here.
3. All systems appear to be “stable” (as in “no noticeable/obvious bugs or negative impacts so far”) – meaning that, overall, everything seems to be working just fine and normally, as expected. That assumption is further confirmed by executing the SFC /VERIFYONLY and DISM /Online /Cleanup-Image /CheckHealth commands (both successful, no errors returned).
4. The three sum-ups below refer to
4.1) my previous stable “BASELINE” (Jul 13);
4.2) a “baseline candidate” (stable update) I was preparing a few days back (Oct 3) while we got caught up between the MS-DEFCON 1 and MS-DEFCON 3 change (this might be yet another helpful feedback report for worried, confused users out there) and
4.3) a currently, apparently “stable” BETA TESTING (Oct 10) – which, incidentally, is NOT yet endorsed by Woody or by any of the other MVPs here: it’s just *my* particular feedback (one, adding to many others). Things worked well for me, but be warned: proceed at your own risk (we’re at MS-DEFCON 1, which means: ***WAIT!***).

Windows 7 x64 SP1 (Group A)

DATE     INSTALLED UPDATES                         DESCRIPTION/NOTES
-------- ----------------------------------------- -----------------
20190713 KB4490628 (2019-03 SSU)                   Stable BASELINE
         KB4474419 (2019-03 SHA-2)                 (Jul 13, 2019)
         KB4507449 (2019-07 Monthly Rollup)
          ->Includes KB4507434 (IE11 Rollup)
         KB4507420 (2019-07 .NET Framework Rollup)
          ->KB4507004 (3.5.1) + KB4506997 (4.6.2)
-------- ----------------------------------------- -----------------
20191003 KB4516655 (2019-09 SSU)                   Stable UPDATE
         KB4474419 (2019-09 SHA-2 v3)              (Oct 3, 2019)
         KB4516065 (2019-09 Monthly Rollup)
          ->Includes KB4516046 (IE11 Rollup)
         KB4514602 (2019-09 .NET Framework Rollup)
          ->KB4507004 (3.5.1) + KB4511516 (4.6.2)
-------- ----------------------------------------- -----------------
20191010 KB4524102 (2019-10 .NET Framework Rollup) Stable BETA TEST*
          ->KB4507004 (3.5.1) + KB4515854 (4.6.2)  (Oct 10, 2019)
         KB4519976 (2019-10 Monthly Rollup)
          ->Includes KB4519974 (IE11 Rollup)
-------- ----------------------------------------- -----------------

*No observable bugs so far.

Windows 8.1 x64 (Group A)

DATE     INSTALLED UPDATES                         DESCRIPTION/NOTES
-------- ----------------------------------------- -----------------
20190713 KB4504418 (2019-07 SSU)                   Stable BASELINE
         KB4507448 (2019-07 Monthly Rollup)        (Jul 13, 2019)
          ->Includes KB4507434 (IE11 Rollup)
         KB4507422 (2019-07 .NET Framework Rollup)
-------- ----------------------------------------- -----------------
20191003 KB4512938 (2019-09 SSU)                   Stable UPDATE
         KB4516067 (2019-09 Monthly Rollup)        (Oct 3, 2019)
          ->Includes KB4516046 (IE11 Rollup)
         KB4514604 (2019-09 .NET Framework Rollup)
-------- ----------------------------------------- -----------------
20191010 KB4521864 (2019-10 SSU)                   Stable BETA TEST*
         KB4524104 (2019-10 .NET Framework Rollup) (Oct 10, 2019)
         KB4520005 (2019-10 Monthly Rollup)
          ->Includes KB4519974 (IE11 Rollup)
-------- ----------------------------------------- -----------------

*After reboot, KB4521864 (2019-10 SSU) came up again (a second time) on WU as an Important update: just clicked ‘Check for Updates’ to make it go away (no need to re-install it).

Windows 10 x64 (Version 1803)

DATE     INSTALLED UPDATES                         DESCRIPTION/NOTES
-------- ----------------------------------------- -----------------
20190713 KB4509094 (2019-07 SSU)                   Stable BASELINE
         KB4507435 (2019-07 Monthly Rollup) b885   (Jul 13, 2019)
-------- ----------------------------------------- -----------------
20191003 KB4512576 (2019-09 SSU)                   Stable UPDATE
         KB4516058 (2019-09 Monthly Rollup) b1006  (Oct 3, 2019)
-------- ----------------------------------------- -----------------
20191010 KB4521861 (2019-10 SSU)                   Stable BETA TEST*
         KB4520008 (2019-10 Monthly Rollup) b1069  (Oct 10, 2019)
-------- ----------------------------------------- -----------------

*No observable bugs so far.

• This reply was modified 1 year, 8 months ago by Speccy.
• This reply was modified 1 year, 8 months ago by Speccy. Reason: Corrected (clarified) Win7 Stable BETA TEST section information (.NET Framework)

4 users thanked author for this post.

rexr, GoneToPlaid, Lars220, woody

Reply | Quote

[gborn]

schwabel_ronald wrote:

I also was seeing the start menu search problem along with the action center refusing to open after installing the patches from before the October patch Tuesday.  removing the cumulative updates allowed the task bar search and action center to run again.

I probably wasn’t very prudent, but I did decide to let Windows Update install the October Patch Tuesday update.  My task bar search, Cortana and Action Center all failed after reboot so I removed the latest patch.

Concerning the start menu, search and action center issues in Windows 10 Version 1903 (and probably older Win 10 build) I wrote a blog post Windows 10 October 2019 Patchday (Start menu) issues. It seems not isolated cases. Here’s the beef derived with the help from my German blog readers and some MS Answers users confirmed that.

Addendum: Startmenu issues are not fixed! German blog reader Janami25 left this comment for Windows 10 Version 1903 (I’ve translated it):

My original guess with the first problem update KB4524147 has been confirmed here [within my German blog post]. Once you have installed this first “problematic” update, you will notice that you have issues with the start menu. If you only uninstall this update, newer patches can’t fix the issues.

In my opinion, it mandatory to restore a system backup made BEFORE installing KB4524147 for the first time. And then install the very latest patch [from October 8, 2019]. Only then the issues with the start menu was solved. At least with me. So, before installing the KB4517389 (18362.418) restore a much older Windows version.

Janami25 postet also a link to this Microsoft Answers forum post, where user Al McNaught also reported a broken start menu and user mirovb confirmed the obervation zited above. I’ve made a few suggestions within my article to overcome this situation. Maybe it helps.

Windows 10 is a wonder box – but Microsoft’s position is clear Patching as a social responsibility – year, they force their Windows 10 users to gain high administrator skills and keep them trained at a daily base – we are all weaponed for the challenges of the 21th century ;-).

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

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

2 users thanked author for this post.

Kobold Curry Chef, woody

Reply | Quote

[schwabel_ronald]

I think my search/cortana/action center problems are now solved.  I found something on Reddit that suggested using sfc /scannow immediately after rebooting from the install of kb4522355.

Start Menu and Search broken again for Windows 10 1903? from sysadmin

After following those instructions I again have full use of the task bar search menu, the Action center and Cortana after updating to Windows 10 Pro 1903 (18362.449)

The sfc /scannow command didn’t report any errors to the console screen, but checking the C:/Windows/logs/CBS/CBS.log revealed several warnings that it had changed some of the file ownership rules.

It made some sense that things like search and the action center could get into trouble if they were no longer able to access certain files.  It doesn’t explain why some systems failed and others worked correctly.

 

Reply | Quote

[TJ]

Hi guys,

I’m running Windows 10 Pro – 1809 x64, build 17763.775 on a stand-alone system. (Still got Win7 Pro SP1, Group B running on a secondary HDD, but Win10 is now my daily runner.)
Updates are handled by WuMgr and occasionally I download and install necessary updates through the Catalog. That went well till now:

I now have two updates that either get a ‘not applicable’ or ‘not installed’ result with a 0x8E5E0408 error:
KB 4524099 (4515843 in my case) Cumulative .NET 3.5, 4.7.2, 4.8
KB 4521862 Servicing Stack Update

From what I can find online, this error has to do with Windows Store, which I removed along with other apps immediately after installing 1809.
There seems to be a work-around solution https://social.technet.microsoft.com/Forums/en-US/6d5296db-cc4c-48bb-9a7c-71b3ad23d8c5/store-apps-fail-to-install-with-error-quottry-that-again-something-went-wrongquot-0x8e5e0408?forum=win10itprosetup
but that requires me to create a new user with a MS-account, and I work only with local accounts.

Any other solution/suggestion?
Thx

@moderator: I posted this yesterday as topic “2x update Error 0x8E5E0408” in the Windows 10 version 1809 forum, but nobody reacted so I hope to get some help here (and that topic can be deleted). Thanks

• This reply was modified 1 year, 8 months ago by TJ. Reason: Add. info

Reply | Quote

[anonymous]

Hi,

We received a blue screen this morning on a Windows 2008 R2 RDS server, after applying patches last night and rebooting. Prior to patching the server had shown no issues.

We got a:
Stop error code 0x0000003B (SYSTEM_SERVICE_EXCEPTION)
Has anyone else seen this?

Reply | Quote

[PKCano]

What update(s) did you install? Sept? Oct?

Reply | Quote

[gborn]

Just a brush up. I’ve escalated the shell/start menu/search/action center issues to MS engineers and it’s confirmed. A fix is planned for end of October 2019. See the discussion at https://answers.microsoft.com/en-us/windows/forum/windows_10-start-win_menu/start-menu-showing-critical-error-after-installing/ae473b3c-ae57-4e1a-8c55-c727cd16fabd?messageId=5d035ddd-841c-4569-aaac-eed2c261cd9c&auth=1&page=3 for further details.

For those affected: I’ve outlined some workarounds and the root cause within my blog post https://borncity.com/win/2019/10/12/windows-10-fixes-for-october-2019-start-menu-issues/

Maybe it helps

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

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

2 users thanked author for this post.

willie.nilley, satrow

Reply | Quote

[anonymous]

BleepingComputer confirming issues with KB4517389…

https://www.bleepingcomputer.com/news/microsoft/windows-10-1903-known-problems-in-the-kb4517389-update/

 

Reply | Quote

[plodr]

Four Windows 7 32 and 64 bit Home and Pro computers. I’m a selective group B patcher.

The only patch I installed in July 2019 were .NET security patches. No telemetry on my systems! The only patch I installed in September 2019 was the SHA-2, 4474419 because this affected Win 7. It is released monthly and I usually read what it impacts. Again I skipped the security only patch because of telemetry bundled in it.

October 2019. I installed SSU 4516655 which had a date of September 30th. I didn’t notice it until October.

Yesterday I installed 4520003 on one computer then checked if Diagnostic Tracking Service was added. It wasn’t so I concluded this month’s security update did not include telemetry.

All computers now have: 4516655, 4520003 and 4519974

I have not noticed any problems.

Got coffee?

1 user thanked author for this post.

AJNorth

Reply | Quote

[anonymous]

Windows 10 1803 64 bit.  Installed October SSU and KB4520008 CU updates, installed OK, stable for 3 days.

Reply | Quote

[anonymous]

Probably a good thing we shouldn’t patch. I haven’t been able to find a way to get our laptop and desk top to update since the August patches were okayed. I keep getting error messages. When I do the relevant fix, I get another different error.

We’re running 8.1 on both machines. What is going on, and any suggestions? I’m probably barely above average on tech solutions so no messing with the registries unless that’s the only option!

Reply | Quote

[plodr]

First, you probably need to install the Servicing Stack update that came out in September. https://support.microsoft.com/en-us/help/4512938/compatibility-update-for-installing-windows-8-1-rt-and-server-2012-r2

That’s probably why your systems aren’t receiving any updates since August. Check if KB 4517298 was installed in September. If not, go to the catalog and download and install it. https://www.catalog.update.microsoft.com/Search.aspx?q=KB4512938

 

Got coffee?

• This reply was modified 1 year, 8 months ago by plodr. Reason: space needed

Reply | Quote

[gborn]

anonymous wrote:

Edge is broken for me.  Out of Band patches already applied: 4522014 and 4524149.  After application of 4520008, Edge will not launch.

Concering the Edge issue mentioned from some users: my suspicion has been confirmed by affected blog reader. Have a look at my blog post Windows 10 V1903: Update KB4517389 breaks Edge Browser [Fix]. There I outlines the root cause and a possible workaround. German users has confirmed, that the solution works.

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

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

Reply | Quote

[walker]

@gborn:  This is with reference to the Yahoo suddenly not having a “contacts” list anymore.  Am I the only one who has noticed this?  Yahoo apparently has changed its format without notifying its users?

Crazy question with everything floating around about all of the version “W” problems.  Now to search for a new e-mail sender.   It only gets crazier and crazier.

Reply | Quote

[Guest]

I didn’t install KB3133977 Bitlocker and I am all caught up to October now. Is there still a need to install KB3133977 anyway or that was only needed as a workaround for the August patches for select configurations and I am past that point now?

Reply | Quote

[PKCano]

If updates are working, you don’t need to worry about it.

Reply | Quote

[anonymous]

Any reason why KB4519976 (October Rollup) isn’t showing up on Windows Update anymore? All I see is KB4516065 (September Rollup) instead, as well as KB4474419 and the October MSRT. I didn’t get a chance to install the September Rollup when defcon was at 3.

Reply | Quote

[PKCano]

I would suggest you go ahead and install KB4516065 (September Rollup) and KB4474419 SHA-2 code signing update. Both have passed the DEFCON 3 level and are safe to install.

You may find that KB4516655 Servicing Stack update shows up in Windows Update after you reboot from the other install. In fack, the lack of the Servicing Stack may be why the October Rollup didn’t show.

Reply | Quote

[anonymous]

But the October Rollup appeared before without needing KB4516655. In fact the website mentions I just need the SSU from March. I’m just wondering if anyone else noticed this Rollup missing.

Reply | Quote

[anonymous]

I installed the September Rollup and the SHA-2 update. Everything seems to be running OK. I only have the October MSRT left but I am waiting till we get the OK to install October updates.

Reply | Quote

[PKCano]

Hide the Oct MSRT temporarily and see if anything else shows up. You can always unhide it if there is nothing else.

Reply | Quote

[anonymous]

I checked for updates (without hiding anything) and now the October Rollup appeared! (KB4519976 dated the 17th) as well as the October MSRT. How odd I needed the September Rollup first for the October Rollup to appear. Anyway, not touching either of these at the moment. Thanks for the help!

Reply | Quote

[anonymous]

Supercedence, they have a rule in the patch that X is needed before Y.

Reply | Quote

[anonymous]

I’m also getting the “Unexpected error, quitting” problem on both Windows 10 and 7. Is there any way to avoid this other than not installing the security patch?

Mike

Reply | Quote

[EP]

what version of win10 are you using, mr anonymous?

for win7, try installing the KB4519972 preview rollup (if you want an “immediate fix”)
otherwise wait until next month (November 12) for new updates

• This reply was modified 1 year, 7 months ago by EP.

Reply | Quote

[desertdad]

Windows Updates entry gone from Settings/Update and Security/ after KB4519338. I had the SSU KB4521862 already installed. Update appeared to finish ok, restart ok, Win seems to be running ok. Dell Win10Pro laptop, not using auto Win Update, deferred updates using the recommended settings, ended up with Build 17763.805. Is Windows Updates being gone on purpose? If so, how do I control Updates? I got pretty dependent on manually controlling updates. Advanced Options just gives me some Upload/Download Settings. I’m not on the Insider track. I’m kind of in shock.

 

Win10 Pro, Dell laptop, currently on 1909 build 18363.1256

Reply | Quote

[Author]

Posts