Windows Updates
Windows 10
Provides protections against a new subclass of speculative execution side-channel vulnerabilities.
Addresses an issue that causes high CPU usage from SearchUI.exe for a small number of users. This issue only occurs on devices that have disabled searching the web using Windows Desktop Search. (1903 only)
Security updates galore.
1903 – September 10, 2019—KB4515384 (OS Build 18362.356) ***This fixes the Bad Win10 1903 Update aka Search UI issue. I checked it myself and the issue is now gone.
1809 – September 10, 2019—KB4512578 (OS Build 17763.737)
1803 – September 10, 2019—KB4516058 (OS Build 17134.1006)
1709 – EOL, time to update to 1809 or 1903
Windows 8.1
Provides protections against a new subclass of speculative execution side-channel vulnerabilities… and a host of Security updates.
September 10, 2019—KB4516064 (Security-only update)
September 10, 2019—KB4516067 (Monthly Rollup)
Windows 7
Provides protections against a new subclass of speculative execution side-channel vulnerabilities… and a host of Security updates.
September 10, 2019—KB4516033 (Security-only update)
September 10, 2019—KB4516065 (Monthly Rollup)
Software Updates:
O&O ShutUp10 1.6.1403
NEW: Chinese (simplified) language integrated
NEW: Search field in task bar can be deactivated (from Windows 10 1903)
FIX***: Deactivating the Bing search is only recommended reservedly, as there are currently problems with Windows search under Windows 10 1903
FIX: The wording in the English version was changed from passive to active to make it clearer
Available in English, German, French, Italian, Spanish, Russian and Chinese (simplified)
***The fix about Bing is the Bad Win10 1903 Update that was fixed today with today’s Win10 1903 update (see above). So, kinda pointless?
Download | Home Page | Changelog
Nvidia Geforce Game Ready WHQL Driver 436.30
“Provides increased performance and the optimal gaming experience for the Call of Duty: Modern Warfare PC Open Beta, Gears 5, and Borderlands 3”
Download | Release Notes
Dan from Indy says
thanks for the info,Eric
cc says
sfc /scannow still isn’t fixed…
Eric (a.k.a. TweakHound) says
Microsoft is nothing if not consistent.
Eric (a.k.a. TweakHound) says
Run: dism /online /cleanup-image /restorehealth
Results:
C:\WINDOWS\system32>sfc /scannow
Beginning system scan. This process will take some time.
Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection found corrupt files but was unable to fix some of them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
repairs, details are included in the log file provided by the /OFFLOGFILE flag.
C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth
Deployment Image Servicing and Management tool
Version: 10.0.18362.1
Image Version: 10.0.18362.356
[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.
C:\WINDOWS\system32>sfc /scannow
Beginning system scan. This process will take some time.
Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection found corrupt files and successfully repaired them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
repairs, details are included in the log file provided by the /OFFLOGFILE flag.
C:\WINDOWS\system32>