MS says there’s no Start/Search bug in this month’s Win10 1903 cumulative update

Topic

New Reply

The official Release Status Info page was recently updated to say: Some users report issues related to the Start menu and Windows Desktop Search Micro
[See the full post at: MS says there’s no Start/Search bug in this month’s Win10 1903 cumulative update]

Reply | Quote

Replies

woody wrote:

MS says there’s Start/Search bug in this month’s Win10 1903 cumulative update

Did you omit “NOT a” from the headline?

MS says there is NOT a Start/Search bug in this month’s Win10 1903 cumulative update, which I confirm.

1 user thanked author for this post.

woody

Reply | Quote

YIKES.

You’re absolutely right. Change made.

Reply | Quote

[pHROZEN gHOST]

The comment page and the article heading on the main page are not the same 

Byte me!

• This reply was modified 5 years, 8 months ago by pHROZEN gHOST.

Reply | Quote

I’m a Seeker, so if the update is available for my PC, I’ve got it.  I don’t use the Windows Start Menu, I use StartIsBack++ v2.8.5, and I haven’t had any issues with it.

I’ve had Search and Indexing disabled for I can’t remember how long, so I wouldn’t notice any issues there, and I don’t have any other performance issues.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

Reply | Quote

Our users on 1903 were having issues with Start and Search up until a week or so ago. After checking with several others it appears all the issues we had are now gone.

Two things I attribute to the fix was to apply all the current 1903 patches and changing our Group Policy to “allow apps to run in the background” in privacy settings.

I had read when 1903 was coming out that disabling background apps from running would affect Cortana search going forward. Wrumak reminded me of that fact in another thread a week or so ago. A few days after that discussion I removed the prevention of background apps from running in group policy. Making that change does appear to help fix the issues we were previously having.

 

Red Ruffnsore

2 users thanked author for this post.

woody, b

Reply | Quote

@b

Yeah, this is a non-acknowledgement. They’re just acknowledging that there are some reports of issues, but they haven’t found enough evidence to definitively say there’s an issue. I think that this is a good thing, and it’s much better than maintaining radio silence like they did on the high CPU issue. Even if it turns out to be nothing, good to give a heads up and encourage users to report.

@bbearren

I’m a Seeker, so if the update is available for my PC, I’ve got it. I don’t use the Windows Start Menu, I use StartIsBack++ v2.8.5, and I haven’t had any issues with it.

I’ve had Search and Indexing disabled for I can’t remember how long

Of course you don’t have issues if you don’t use the affected software. And of course you couldn’t be affected by the SearchUI redlining bug a few weeks ago either because you had the software disabled (and you would have no reason to disable web search if you didn’t use it anyway). I don’t think it’s terribly constructive to post on all of these threads that you have no issues with an update when you don’t use the affected software.

@Mr. Natural

I have group policy set to not allow any apps to run in the background. I also have the search Indexer disabled. No issues here after patch Tuesday (and an SFC scan to undo the temporary cache fix). The reports don’t seem to be as widespread as with the redlining bug, so this could turn out to be nothing. Good on MS for being transparent though.

I’ve had issues with the Start Menu before due to DISM permissions issues, which were due to third-party software. This could be something similar; the new start menu is a complicated piece of software and is more fragile than the classic one.

1 user thanked author for this post.

b

Reply | Quote

Our I.S. Director was one the the folks complaining the most about the issue which prompted me to apply 1903 patches whenever they were released. I pushed the 2 1903 updates released on September 10th and he and I both still had some start menu quirks but the situation was better after the updates.

It was after those patches were applied I decided to make the group policy change. I did so and afterward I told my boss to reboot again. That was last week. After seeing Woody’s post here I decided to check back with the chief and he confirmed what I was also experiencing, no more start menu issues after the policy change from last week.

So that’s the background on my reasoning of my previous post. 

 

Red Ruffnsore

Reply | Quote

I’m certainly not saying you’re wrong about the group policy, it may have an impact in certain scenarios but not others, just reporting that it isn’t as simple as that alone. If it was that simple to replicate they probably would’ve caught it. Windows can be complicated and there are many interleaving parts.

For example, not too long ago I had the start menu search not work in a completely clean new local user profile, but after switching users back and forth it was working. This stuff is complicated and fragile. I certainly can understand people who want to rip it out and replace it with a classic shell, but that’s not really an option for organizations.

Start menu breakage isn’t all that uncommon, that’s why there’s a troubleshooter after all, but I don’t think it’s terribly common for this to be a straight up Microsoft problem rather than a combination of their complicated system and bad interactions with third-party software. We’ll see if they figure it out. If it’s like the last issue maybe someone in the community will figure it out first and publish a workaround.

Reply | Quote

Not quite sure how they say there is no issue (or no significant issue) when many on Reddit, including myself, have experienced it first hand.

“Wipe it under the rug, nothing to see here” I guess.

Reply | Quote

anonymous wrote:

I don’t think it’s terribly constructive to post on all of these threads that you have no issues with an update when you don’t use the affected software.

From the heading of this thread, “this month’s Win10 1903 cumulative update”.  The cumulative update covered more than just Start/Search.

bbearren wrote:

and I don’t have any other performance issues.

I’m a Seeker, a member of the cannon fodder to whom Woody refers in his wait-and-see approach on updates.

I’ll continue to report from the front lines, even though I run a fully updated Windows 10 Pro installation and have had no issues so far.

When I do, AskWoody will be the first to know.  When I don’t, I’ll report on that “to our unique respite from the madness.” as well.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

2 users thanked author for this post.

geekdom, woody

Reply | Quote

Well, Microsoft planted the bug (erratic navigation pane popups) into the upcoming Windows 10 1909 version. And the clowns at Microsoft also messed with Windows Explorer causing its search option no longer working for those blocking www[.]bing[.].com or having no Internet connection at all.

Edit for content

Reply | Quote

Sorry Woody, here I think the “update” proces was disturbed perhaps by other active applications ((ofcourse this is my fault)),

Was so frustrated that these faults happened that I reinstalled immediately to the backup image

It wears out always being used as guineapig

* _ ... _ *

Reply | Quote

[SonicMojo]

I will be able to confirm this in about 5 minutes.

I have changed the Group Policy setting mentioned here (allow apps in to run in background) as a test.

I have 18362.295 in a test 1903 VM and have just installed 4515384 (for a third time).

Will reboot and see what is happening.

Stay tuned.

EDIT: Nope

Sonic

• This reply was modified 5 years, 8 months ago by SonicMojo.
• This reply was modified 5 years, 8 months ago by SonicMojo.

Reply | Quote

I uninstalled KB4515384 and reverted back to 18362.295 – all is working fine.

So despite what MS wants to say about this update – it is breaking something fairly substantial. And is unusable in this case. Clearly they are looking at this from the aspect of a base install where nothing has been modified in any way.

For all the possible group policy and registry keys that can be set, altered or changed – I feel for them in some small way – but they need to address this from the angle that many things can be customized and many things can change.

I am certain I am not the only one.

Sonic.

Reply | Quote