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

bobad said:

Still nothing, maybe they pulled it because of problems reported here.

It showed up here this morning. It downloaded and installed without incident.

The way I finally overcame this snafu about KB4512941 with error 0x800f081f was by doing a repair install using UUPDump .iso for this build. I didn't try to reinstall .NetFramework 3.5 and some other steps suggested in articles found around the web. I considered that to be too much downtime for me.

Now everything seems to be working fine:

Here I installed the 4 patches above and had no problem with MSWindows, such as BDOS or other error during use. I noticed only a CPU usage by CORTANA and SearchUI, but it was gradually increasing, and to go back as before (CPU ~ 0%), I did what some articles read here and internet: Search tip in Registry and "completely deleted" the folder "Cache" .... without pity. Now CPU ~ 0% usage and no errors ... by the way, I had already disabled CORTANA long before because I hate annoying people near me ....

summary: build 329 ok

- - - Updated - - -

New KB4515530 Servicing Stack Update for Windows 10 v1903 - August 30

Cumulative Update KB4511555 .NET Framework 3.5, 4.8 Windows 10 Aug. 30

KB4497165 Intel microcode updates for Windows 10 v1903 - August 29

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

jallenhayslett said:

Another CU, another failed auto update, and another Repair Install. To compound matters, all the aforementioned Cortana/search screwups showed up after the Repair and made me think my profile was corrupted. Spent nearly all weekend setting up a new profile, app settings, etc., only to find out after I spent all that time that I could've fixed it by removing the disabled web search registry tweak. Good thing it was a holiday weekend. Shame I had to waste it on that though, but I needed it done and back in a working state by Tuesday. I usually only make a Macrium image after I finish my monthly maintenance routine, I guess I'll be adding yet another step to the process by making a pre-maintenance image as well. Stuff like this is precisely why I clear my schedule for a full day at the end of every month for device maintenance.

Upside is, I fixed a few other issues in the process. In lieu of disabling web searching in the search UI via a registry tweak, I just went into the firewall and blocked all incoming and outgoing Cortana connections. Web tab is still there, but it connects to nothing and comes up blank. The only way I can see them breaking that in a future update is if they somehow manage to break the Windows Firewall and/or start forcibly removing rules. If it actually gets that bad, I think it's probably time to ditch the Surface and find something with good support for some flavor of Linux.

I just tried blocking the single inbound and outbound Cortana rule and that does work, web searches say "isn't available right now" so it works.

Also Bing search still works in MS Edge.

Faith said:

I see it in my WU list, but I will wait until patch tuesday. No reason to rush it.

Same here.
With the high CPU issues being reported I'll take a pass on this one.

kado897 said:
Have you tried Mael's fix. Cumulative Update KB4512941 Windows 10 v1903 build 18362.329 - Aug. 30

Mutoidi said:

I had not, so I did.. DL'd Update again & re-nstalled.. issue still present.
Will un-install and await developments.. thanks anyway.

Update:

Had some spare time so executed the temporary Cortana/cache fix.. all appears good on .329 - for now!

I do not use Cortana. My desktop runs well after this update. Could not using Cortana make the difference?