Cumulative Update KB4512941 Windows 10 v1903 build 18362.329 - Aug. 30 Win Update

Bree said:

This is an odd 'error' reported by SFC after installing KB4512941. With SFC /VerifyOnly it reported that there were errors, but none are shown if you view the CBS.log as per Option Five in the SFC tutorial.

sfc /scannow Finds and Repairs after Storage Sense Temp Clean

Code:

Microsoft Windows [Version 10.0.18362.329]
(c) 2019 Microsoft Corporation. All rights reserved.

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>

I've been getting this on both my machines whenever I do a cleanup with Storage Sense.

It started with .297 a month ago. Then again with .329 and I'm not sure if it's just Clean Up or Clean Up after Update files appear, which for me I see in Storage Sense only after ever other CU for some odd reason and are about 2.5 G worth.

Last month I'd thought it might be related to the Defender hash corruption, but for me there's been no Defender Platform updates yet since 7/25/2019 with 4.18.1907.4-0

@Brink so basically if u never messed with windows search and left it default then you can safely install this??

maurice naggar said:

a ) Where and how are you trying to execute a search ?

b)
Can you just export out the whole content of this key ( in the registry )
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Search

You´re right, the sub-key was present and it can be deleted.

Anibor said:

You´re right, the sub-key was present and it can be deleted.

I think all these problems are caused by people using custom software to shutdown various windows functionalities like spying. This leads to further problems during windows updates.

arifkarim said:

I think all these problems are caused by people using custom software to shutdown various windows functionalities like spying. This leads to further problems during windows updates.

O&O ShutUp10 in my case, which I used for a short time several years ago.

Hi folks

I seem to be finding less and less of these problems with Windows as these releases get updated etc -- OK there's the odd niggle like Language / keyboard issues but liveable with.

Perhaps it's because the only 3rd party software I use is pretty standard -- Mozilla Firefox, Thunderbird (sometimes) although I use Office 2019, Photoshop, Macrium, and a hardware video capture device -- no 3rd party reg cleaners, Anti-virus software, custom mods, and have no eseoteric graphics hardware or "extreme" type of CPU's so no drivers likely to break the system.

I don't use cortana or those audio search things either -- so to all intents and purposes a pretty vanilla and probably to a lot of people a boring system -- but it's a computer and it does what I need it to do.

If I'm surfing dubious places or using torrents to grab video / audio content I always do it via Linux so the chances of getting any malware for those types of torrents is pretty well zero. The video / audio content gets stored on my NAS nyway -- doesn't go near the Windows machines. So my conclusion is that for pretty standard systems the releases are doing OK -- but of course I'm probably not the best person to use for testing these releases although if someting is breakable I usually find it pretty quick. I also tend to use UUPDUMP for installing the insider releases (all the rings) and have found that using UUDUMP always seems to work for me whether installing clean or updating.

Cheers
jimbo

neveready said:

I give up. My HP laptop currently has 18362.327 on it and fails every try to update to KB4512941. I didn't even have "BingSearchEnabled" in the registry so I put it in. Same problem. Update fails. Have 2 desktops on Insider 18970.1005 that are working perfectly. Think I will just update laptop to 18970.1005 and be done with it.

Do an in-place upgrade using the Windows 10 ISO, this is the only way it worked for me