Automatic Sample Submission is Off?

Josey Wales · Jul 18, 2021

Just Ignore it, not much one can do, one would think that a company like KS would be concerned with something dealing with security???

PerpetualCycle · Jul 18, 2021

Josey Wales said:
Just Ignore it, not much one can do, one would think that a company like KS would be concerned with something dealing with security???

TBH, I actually disabled this in Windows 10. I did not expect much benefit. Then I re-enabled it because you get that yellow triange/bang and have to look each time to see if it is something else. Typical making it painful or inconvenient for customers to knuckle down and not do what MS wants.

It is listed as a known issue in the Windows 11 .71 release notes.

Dru2 · Jul 18, 2021

geneo said:
It is listed as a known issue in the Windows 11 .71 release notes.

I started out with .65 and it was there as its there in .71

Josey Wales · Jul 19, 2021

This seems to be Fixed, I got a new Feedback Hub This Morning and I just restarted and all is OK with this.

plat · Jul 19, 2021

The yellow mark is still there for me, even after a restart. One recent thread on this at Feedback Hub has a comment "Working on it."

I'm wondering if there's a connection between this issue and the Device Security one/s saying "Standard hardware security not supported." Wouldn't be surprising if there wasn't, though. but it would knock out two issues at the same time.

Josey Wales · Jul 19, 2021

plat said:
The yellow mark is still there for me, even after a restart. One recent thread on this at Feedback Hub has a comment "Working on it."

I'm wondering if there's a connection between this issue and the Device Security one/s saying "Standard device security not supported." Wouldn't be surprising if there wasn't, though. but it would knock out two issues at the same time.

View attachment 3472

I did Remove Open Shell Plus that TB app and I did get a new Feedback Hub this morning. I will Restart again and see what happens?

Josey Wales · Jul 19, 2021

OK, it is still fixed after the RS. I also got a new version of Firefox, Notepad++ and REVO installer Pro, as well as the updated Hub. No windows updates either. I am good to go I guess.:)

AndreTen · Jul 19, 2021

plat said:
The yellow mark is still there for me, even after a restart. One recent thread on this at Feedback Hub has a comment "Working on it."

I'm wondering if there's a connection between this issue and the Device Security one/s saying "Standard hardware security not supported." Wouldn't be surprising if there wasn't, though. but it would knock out two issues at the same time.

View attachment 3472

It's known issue, listed in the release notes. MS will fix it

Josey Wales · Jul 19, 2021

They must have for me.

plat · Jul 19, 2021

AndreTen said:
It's known issue, listed in the release notes. MS will fix it

Yes, this is already understood and I was actually commenting on Josey Wales' post with a contrasting experience.

My Feedback on FH on these two problems is already from two weeks ago. It must be a little more complex than one would assume.

plat · Jul 22, 2021

Today, Automatic Sample Submission was enabled at machine start. Restarted a few times, it stayed enabled.

MS telemetry at work maybe. I ain't complaining this time.

Edit: There's a new version of the Platform: 1.1.18400.4. Could that have been the fix? Anyone know where a changelog would be?

plat · Jul 22, 2021

Microsoft Update Catalog

Is this the platform update in question? Not sure as there's no changelog. The date is July 9, 2021 which is almost two weeks ago. All I can say is just now I restarted and started machine via a cold boot and the Virus sample submission is enabled every time. It's remaining fixed on here for now.

Not looking a gift horse in the mouth. :)

Dru2 · Jul 22, 2021

plat said:
Today, Automatic Sample Submission was enabled at machine start. Restarted a few times, it stayed enabled.

Same here - Yellow triangle in Windows Security (Defender)

plat · Jul 22, 2021

The thing is: the vss bug is still listed as a "known issue" in the list for cumulative update KB5004300. So, this is very mysterious. Here are the version numbers for Defender at this point in time. Again, not complaining since it's seemingly fixed on here. I just don't know how it got to that point, only when it did: overnight last night sometime.

Bree · Jul 22, 2021

plat said:
The thing is: the vss bug is still listed as a "known issue" in the list for cumulative update KB5004300. So, this is very mysterious. Here are the latest version numbers for Defender. Again, not complaining since it's seemingly fixed on here. I just don't know how it got to that point, only when it did: overnight last night sometime.

View attachment 3816

What I don't understand is how you got the antimalware engine update. Mine is still on 1.1.18300.4, even after KB5004300 installed 22000.100 - and I still have the yellow triangle after every Restart.

plat · Jul 22, 2021

@Dru2 : Is your Engine version the same as mine?: 1.1.18400.4

If you look at the Feedback Hub under the filters Problems/Security and Privacy, there are a number of posts claiming this VSS issue was fixed for various uses since the last one or two days--by a Defender update, or an antimalware platform update but there's no consensus.

Hmmmm.

Dru2 · Jul 22, 2021

plat said:
@Dru2 : Is your Engine version the same as mine?: 1.1.18400.4

I'm sorry, but where am I looking for that info at?

Bree · Jul 22, 2021

Dru2 said:
I'm sorry, but where am I looking for that info at?

Open Windows Security. Click the Settings cogwheel, bottom left. In Settings, click the blue 'About' link.

Dru2 · Jul 22, 2021

plat said:
@Dru2 : Is your Engine version the same as mine?: 1.1.18400.4

Bree said:
Open Windows Security. Click the Settings cogwheel, bottom left. In Settings, click the blue 'About' link.

Thanks. Don't know where my mind was on that

Anyway...

Mine is 1.1.18300.4. Plat shows 1.1.18400.4.

plat · Jul 22, 2021

OK, thanks Dru2--so it seems you're one version behind on the Engine, but notice that the Antimalware Client Version is the same and Bree's is one behind. So, maybe that updated Client version contained the fix? This is such speculation but it really is baffling, esp. how I got one version ahead on the Engine.

Same client: 4.18.2107.4