Replies

Tried using the update assistant on a couple home PCs. One computer worked fine. The other (on 1909 Pro) boot looped 3 times and went to “undoing changes”. Don’t feel like chasing down the problem as this is also my WFH PC. Guess I’m stick with 1909 for a while.

Are you looking for someone to do this permanently or just to setup the template and then you can take it from there? I may be able to lend a hand.

2 users thanked author for this post.

Elly, woody

[IndyPilot80]

Hmm. Interesting. KB4541335 just showed up in WSUS. Wonder if this is a “Ohh, come on, just one more before we have to stop”.

Edit: Just saw then are planning to “pause” starting in May.

• This reply was modified 3 years, 6 months ago by IndyPilot80.

[IndyPilot80]

abbodi86 wrote:

No
http://www.catalog.update.microsoft.com/Search.aspx?q=KB4533002

they probably forgot, with all this 1903/1909 confusion they created

That’s kind of what I figured. Thanks for confirming.

• This reply was modified 3 years, 9 months ago by IndyPilot80.
• This reply was modified 3 years, 9 months ago by Microfix.

Not sure if I’m missing something here. I see KB4533002 (.NET Update) in WSUS. The title says for 1903 but in the description it says for 1903 and 1909. My test workstations aren’t getting it from WSUS and it says it isn’t applicable. But, when I use “Check Online for Updates from Microsoft”, it downloads it but it update title says it’s for 1909.

Have they not released it for 1909 in WSUS yet?

Has anyone had an issue with the Malicious Software Removal Tool (KB890830)? I’ve released it from WSUS to a test group, manually when into Windows update to install it, it sits at “Installing: 0%” for a couple minutes then goes away. When I hit “Check for Updates” it shows up again and does the same thing.

“Microsoft set out to understand why some customers weren’t applying cybersecurity hygiene, such as security patches, which would have helped mitigate this threat.”

I mean, is this a joke? To me, just shows they aren’t listening to their customers at all. If they want to understand why people aren’t patching, it’s quite simple. Just Google “Microsoft Update Breaks”.

6 users thanked author for this post.

doriel, Sessh, Canadian Tech, Fred, Nibbled To Death By Ducks, Charlie

So, unless I’m reading it wrong, it sound like if we’ve already patched for CVE-2019-1367 and we don’t have any .NET 3.5 or print spooler issues, we can safely skip this and wait until Oct 8?

Clicking Search (the magnifying glass) and clicking start and typing the first few letters of a program do absolutely nothing. Cloud searching is enabled.

Unfortunately, there is no rhyme or reason to it. Originally, I thought I screwed something up with our image. But, KB4517211 installed just fine on some of them, and on others we get the menu issue.

[IndyPilot80]

Regarding .NET 3.5 not installing.

I dont know if this will help anyone, but, I had to re-image a few computers due to still having start menu issues. .NET 3.5 would fail to install if those machines were in WSUS groups. Once I pulled them out, I was able to install .NET 3.5, then I put them back in.

EDIT: Just noticed someone posted “change the registry key UseWUServer to 0”.

• This reply was modified 4 years ago by IndyPilot80.

I tried installing the CU for the heck of it on the test computer to see if search was fixed (even though it wasn’t mentioned in the notes). Nope, still broken.

1 user thanked author for this post.

woody

I received this in my WSUS notification e-mail last night:

Update for Windows 10 Version 1903 (KB4516421) Install this update to resolve issues in Windows. For a complete listing of the issues that are included in this update, see the associated Microsoft Knowledge Base article for more information. After you install this item, you may have to restart your computer.

But when you click the KB link,  it goes to “page not found”. Also, it doesn’t actually show up in WSUS (for me at least). It only showed up in the notification e-mail.

 

1 user thanked author for this post.

woody

Confirmed on my end. Installed on a workstation, search broken. Uninstalled, search was fine. Tried installing again from a direct download instead of our WSUS server and after a sfc /scannow, search broken. Uninstalled, but, this time clicking the start button gave a “Critical Error: Your Start menu isn’t working. We’ll try to fix it the next time you sign in.” after it was uninstalled.

Had to do a restore on the workstation from a recent backup.

2 users thanked author for this post.

Microfix, woody

PKCano wrote:

Please provide the links when you are posting information from other sites. It prevents us from waisting our time duplicating efforts/investigation.

https://www.reddit.com/r/sysadmin/comments/d2cqf0/kb4515384_anyone_else_having_start_menu_issues/

https://www.reddit.com/r/Windows10/comments/d2m2ue/i_installed_kb4515384_and_search_is_completely/

3 users thanked author for this post.

woody, Microfix, PKCano