Windows 10: 07/23/2019 upgrade to #1903 causing endless "reliability history" failures of "system...

Ever since my 07/23/2019 upgrade to #1903, I've had daily "stopped working" notifications from my reliability monitor on system

settings broker.


Windows 10 Pro #1903 18362.267


Is this already under investigation?

Is this experienced by others?​

My reliability monitor report(s) were clean at #1803, but #1903 has produced several of these failures daily(most recent variety).

These multiple failure report(s) continue daily. I also have a W10 home laptop, serviced at #1903, with a clean reliability monitor.






Here's one of the first errors:


Problem:Stopped Working Date:07/24/2019 12:32 AM Status:Report sent

Description
Faulting application name: SystemSettingsBroker.exe, version: 10.0.18362.1, time stamp: 0x5fc608d5
Faulting module name: ucrtbase.dll, version: 10.0.18362.1, time stamp: 0x5cbddb81
Exception code: 0xc0000409
Fault offset: 0x000000000006d3be
Faulting process id: 0x2114
Faulting application start time: 0x01d541dfc4de058a
Faulting application path: C:\Windows\System32\SystemSettingsBroker.exe
Faulting module path: C:\WINDOWS\System32\ucrtbase.dll
Report Id: 9d25765d-cd7d-4478-acb9-3d4614397a8b
Faulting package full name:
Faulting package-relative application ID:





Here's one of the most recent(today):


Problem:Stopped Working Date:08/09/2019 07:55 AM Status:Report sent

Description
Faulting Application Path: C:\Windows\System32\SystemSettingsBroker.exe

Problem signature
Problem Event Name: BEX64
Application Name: SystemSettingsBroker.exe
Application Version: 10.0.18362.1
Application Timestamp: 5fc608d5
Fault Module Name: ucrtbase.dll
Fault Module Version: 10.0.18362.267
Fault Module Timestamp: 080a13f7
Exception Offset: 000000000006d33e
Exception Code: c0000409
Exception Data: 0000000000000007
OS Version: 10.0.18362.2.0.0.256.48
Locale ID: 1033
Additional Information 1: 89d2
Additional Information 2: 89d21884349785ea9a611f7235e6c095
Additional Information 3: 6b6e
Additional Information 4: 6b6e30fe963bb990d64e60732fc11be0

Extra information about the problem
Bucket ID: fd851b4875ec6165edafaf270f67ed5e (2139120930321329502)

:)

 

MS Jigsaw Not working well after 2019-07 1903 updates

-----Windows 10 1903 is currently at version 18362.266

I saved the 1903 ISO file for x64 on 7/10/2019

That installed to 18362.175 on 7/20/2019

On 7/23--the first 2019-07 Updates for 1903 showed up and installed.

KB4507453 which is supposed to be version 239 installed, but I was still at vers 175

On 7/25--Kb4507453 was saved and installed again. This time I had vers 239

I did check the detail for that package which stated it was released 7/9/2019, which was a day before I saved the 1903 ISO.

Why was the KB4507453 not correct at this point?

It should not have taken two D/L and Installs of that KB package to get up to 239.

 

MS Jigsaw Not working well after 2019-07 1903 updates

Hello--I successfully installed 1903 from USB Media created from the ISO saved 7/10/2019

The version installed is 18362.175

MS Jigsaw continued to work well without problems. I have 39 Puzzle Packs, which I do have backups saved for each.

On 7/23 the first 1903 Updates installed for 2019-07

And I was still showing 18362.175.

MS Jigsaw started taking a long time to load. I am able to open puzzle packs, but only get to make a few moves before MS Jigsaw closes. It does save the progress.

What do I need to do in order to fix MS Jigsaw so it does not close after a few moves?

 

MS Jigsaw Not working well after 2019-07 1903 updates

I did not need to use Taskkill because Windows Update has continued to find and save updates. It was not stuck like early in 2018.

Update did successfully install 2019-07 KB4507453 on 7/23 but stayed at ver 175

On 7/25 Updated installed a second version of KB4507453 which bought it up to ver 239.

I looked at the KB detail and that KB package was released on 7/9. I got the 1903 ISO on the next night.

Why did Windows Update not just get and install the second version of that package.

It was a Cumulative so the previous should not have mattered.

On 7/27 Updated installed 2019-07 Kb4505903, which brought it up to ver 267.