Replies

[Mark]

I think he’s correct.  I have my system set to metered connection and also blocked via policy and registry and I do believe I have not been getting the definition updates due to this.  Yes, I have trust issues…specifically with Microsoft.
I have found the best way is to go to the Defender definitions download and just download and install them myself.  The link to the downloads is: https://www.microsoft.com/en-us/wdsi/defenderupdates

Windows 10 Pro x64 v1909, Windows 7 Home Premium x64, Windows Vista Home Premium x64

• This reply was modified 4 years, 8 months ago by Mark.

2 users thanked author for this post.

BigFatBoy, KP

In Microsoft’s case the wood they get…balsa.

Windows 10 Pro x64 v1909, Windows 7 Home Premium x64, Windows Vista Home Premium x64

Just thought I’d add that we didn’t see any problems with Outlook 2016 MSI on our isolated systems (v1809), nor did I see it on my home laptop (v1909) which is running Office 2016 C2R.  Obviously our isolated systems never get to “phone home” to MS, so probably why it wasn’t bothered.

Ditto for my home laptop.  I have it locked down so no updates get applied unless I want to have updates run. I use the metered connection and also double-down by locking out updates through the registry.

Windows 10 Pro x64 v1909, Windows 7 Home Premium x64, Windows Vista Home Premium x64

Ah…so that would explain why I see Satan right in the middle of that “upgrade” group photo!

Windows 10 Pro x64 v1909, Windows 7 Home Premium x64, Windows Vista Home Premium x64

1 user thanked author for this post.

Cybertooth

Just keep thinking that.  They can track with or without the phone being on.

https://slate.com/technology/2013/07/nsa-can-reportedly-track-cellphones-even-when-they-re-turned-off.html

Also, even if they don’t use this method, by using your phone they can triangulate where you are from cell tower data.  Now, supposedly as of last year they said they stopped tracking phones (yeah, right).  We’ll see how that goes.

It reminds me of a line in the movie “Sneakers”…”Too many secrets”.

Windows 10 Pro x64 v1909, Windows 7 Home Premium x64, Windows Vista Home Premium x64

1 user thanked author for this post.

Mr. Austin

Yeah, mine is disabled by default, because…well, it’s Microsoft.

Windows 10 Pro x64 v1909, Windows 7 Home Premium x64, Windows Vista Home Premium x64

1 user thanked author for this post.

rontpxz81

Well, all I can say is I haven’t seen this bug in v1809.  But then again I don’t let my PCs talk to Microsoft.  I have the connection set to “metered” and then I really locked it down in the Policy and registry.  I recently did patches for January and Office 365 a week ago.  Then I locked the connection back down so Office couldn’t phone home.  You could say I have “trust issues” with Microsoft.

Windows 10 Pro x64 v1909, Windows 7 Home Premium x64, Windows Vista Home Premium x64

Who says it has to be an “official” policy?  If it was it would have to be written down (or in company emails) making them even more at risk for an anti-trust suit.

Windows 10 Pro x64 v1909, Windows 7 Home Premium x64, Windows Vista Home Premium x64

1 user thanked author for this post.

Moonbear

This is what I stated further up the thread.  The EU and US is going to have a field day with MS over this.  This is the stuff anti-trust lawyers live for.  I’m sure they’re salivating over this right now in anticipation.
I’m pretty sure you still can’t extricate IE from Windows without breaking the system (at least from what we’ve seen here at work).  At least you can tell the system which browser you want to use.  Now we’ll have to go through the same gyrations to get their search engine out of our browser.  I’m sure there is going to be some way to do it, but it’ll probably be buried deep in the bowels of the Registry.

Windows 10 Pro x64 v1909, Windows 7 Home Premium x64, Windows Vista Home Premium x64

You know the EU is going to eat Microsoft’s lunch with this one…and lets not forget the case back in 2001, United States v. Microsoft Corp.  Which by the way MS lost.  Trying to make it so you couldn’t separate IE from Windows (sound familiar?).

I’ll bring the popcorn…

Windows 10 Pro x64 v1909, Windows 7 Home Premium x64, Windows Vista Home Premium x64

3 users thanked author for this post.

jburk07, GreatAndPowerfulTech, Moonbear

Running Win 7 Enterprise at work, patched to the most recent.  Google Chrome Version 78.0.3904.87 (Official Build) (64-bit), Firefox Version 72.0.1 (64-bit), and IE 11 Version 11.0.9600.19540, all give the “You Are Vulnerable” message.

Windows 10 Pro x64 v1909, Windows 7 Home Premium x64, Windows Vista Home Premium x64

EP, you can fix it to permanently not take updates (unless you want it to).  This is what I’ve done to mine.  You can do it in Win 10 Pro, Ent, and probably Ed.  I’m using Pro, so I know it works with that.  I locked mine down through Group Policy and in the Registry.  I have yet to have anything try to load up.  I also did the normal set the metered connection setting as well.  Here is a pretty good look at the way to do the Group Policy and Registry settings.  I was at v1709 until I decided to upgrade to v1809 (with my own media…not MacroSloths).

https://www.windowscentral.com/how-stop-updates-installing-automatically-windows-10

Windows 10 Pro x64 v1909, Windows 7 Home Premium x64, Windows Vista Home Premium x64

WildBill, you’re getting way to worked up about Win 10 upgrades.  I was on v1607 until I was ready to upgrade…ditto with v1709.  Now I’m on v1809 and I double-dog dare MS to even try to upgrade without my say-so.  I’ve got my PC so locked down, the only upgrades or updates it gets  are the ones I want it to have.

So don’t sweat it…move to Win 10, lock it down, and then just smile and have a cup of coffee!

Windows 10 Pro x64 v1909, Windows 7 Home Premium x64, Windows Vista Home Premium x64

I don’t understand why they don’t just drop the whole YYMM format for the Version and stick with the Build number as the Version.Build.  They’ve stuck with the same Build prefix since v1803 (17134), v1809 (17763), etc.  It would be so much easier to say it’s Version 17134, Build 864 (17134.864).

Windows 10 Pro x64 v1909, Windows 7 Home Premium x64, Windows Vista Home Premium x64

1 user thanked author for this post.

b

I’ve had the opportunity to use all versions of Windows from the very first released version which was 1.01.  Of course I also had the chance to use all versions of DOS as well, so I guess that sort of dates me! 

Windows 10 Pro x64 v1909, Windows 7 Home Premium x64, Windows Vista Home Premium x64

4 users thanked author for this post.

Pierre77, Noel Carboni, woody, Fred