Cumulative Update KB4515384 Windows 10 v1903 build 18362.356 Sept. 10 Win Update

Bree said:

No. I didn't. In Pro x64 I had the default SmartScreen settings (on, all set to 'warn') and no group policies in place.

Change Windows SmartScreen Settings in Windows 10

Yeah, I never touched mine either and have the same settings as you. Odd. I get a little nervous when ever I get a warning an app may be problematic, especially since said app is from Microsoft.

Farvatten said:

I guess what really surprised me was this statement under the MSRT link in Details - Use this tool:
MSRT targets prevalent malware families only. For comprehensive malware detection and removal, consider using Microsoft Safety Scanner.

The difference is that MSRT only scans for those malware that are though by MS to to be active at the moment, while the Microsoft Safety Scanner uses the same full definitions database that Defender uses. I guess it's a compromise so that the MSRT scan doesn't take too long.

Each release of the tool helps detect and remove current, prevalent malicious software. This malicious software includes viruses, worms, and Trojan horses. Microsoft uses several metrics to determine the prevalence of a malicious software family and the damage that can be associated with it.

https://support.microsoft.com/en-us/...mo#releaseinfo

I use Open Shell so hadn't noticed this until now but when I tried to access the Windows start menu I got the message "Critical Error, your Start menu isn't working. We'll try to fix it next time you sign in." Signing out and back in didn't fix it.

On the off chance it might be a conflict with Open Shell I uninstalled it but that didn't work. Neither did running SFC scan (shows no corruption). Even tried DISM Restore Health, same result.

I may revert back to latest Macrium image and try a repair install later.

Bree said:

...while the Microsoft Safety Scanner uses the same full definitions database that Defender uses. .

Ahhh, thanks.. makes sense, especially with MSS being time sensitive as it says:

"Safety Scanner only scans when manually triggered and is available for use 10 days after being downloaded. We recommend that you always download the latest version of this tool before each scan."

Bree said:

... I guess it's a compromise so that the MSRT scan doesn't take too long.

I would imagine MSS's longer scan time is why it's not pushed religiously every month like MSRT has. ( I do seem to remember over the years it's skipped months like yesterday before). I know the inconvenience of MSRT's added travel and run time to these monthly CU Updates already is not appreciated by many users.

Clearly MS is relying more and more on it's real time protection seeing even Defender Quick Scans kind of taking a back seat now. Defender stopped bothering to remind me to do full scans for a while now, like it use to.

I wonder if a manual MSRT will eventually follow suit? I'm sure they're keeping stats on what it's been finding, and over the years with problems dwindling, it will get to a point where they won't burden 99.999% of the Windows community for the .001% that might benefit.

Bottom line - I guess unless you've got serious symptoms, they won't recommend this harsher manual MSS medicine.

How to fix Windows 10's Start menu and search after installing the KB4515384 update | Windows Central

Actually I reverted back to an image from before a day or two before the update. Everything's fine now. Also deferring CU's until this gets fixed.

Thought I'd point this out in case anybody else wanted to try it.

OldGuyFromCdn said:

I use Open Shell so hadn't noticed this until now but when I tried to access the Windows start menu I got the message "Critical Error, your Start menu isn't working. We'll try to fix it next time you sign in." Signing out and back in didn't fix it.

On the off chance it might be a conflict with Open Shell I uninstalled it but that didn't work. Neither did running SFC scan (shows no corruption). Even tried DISM Restore Health, same result.

I may revert back to latest Macrium image and try a repair install later.

what version of Open Shell do you have installed?

erpster4 said:

what version of Open Shell do you have installed?

4.4.138