I personaly use Windows 10 pro even as an insider. But i have blocked a lot and if i like to i use Ghostery to disabel all cookies , spy stuff, adds cokies, even social meda stuff at my browsers. https://www.ghostery.com
Then additional addblock plus https://adblockplus.org
Bloth together. This is the emanyest combo for blcoking all stuff. Even adds.
But only if i like to.
Else i am participating at MS Insider a bit and sharing my machine - data and some not activity/position -relateed Stuff anonymous with them and others to making Windows better. Alos each crahs of Lotro is getting auto reported meanwhile.
It's decent, but it doesn't block telemetry back to Microsoft. For blocking that, one would need to set specific registry keys and other changes.
I deploy Windows 10 at work via Microsoft MDT and wrote this script to disable all of that telemetry. Copy and paste specific sections as needed (or just edit the file) and run it in Powershell.
Just some general info about how I have to log into the forums. I've got two bookmarks: one for the login page and one for the forums. I always start with the Login bookmark and then use the Forums bookmark to perform any retries.
If I get an error when I attempt to login to the forums I do not bother retrying. I just click on my Forums bookmark and go directly to the forums. I pretty much always find that I'm successfully logged in when I do this.
Sometimes the main Forums page is stuck waiting for TLS handshake, so I click the X and then select the Forums bookmark and I usually get right in.
I hope this is helpful to others.
(Yeah, Win 10. I use O&O software's freeware utility Shutup10 to eliminate most of the spying.)
Nice, that it is working for you. For me it wont. Thank the new Smart - System. Even this pages at Google for the Lotro forum barely are working. The suggested ones for the german forum never are showing the login. But better then having got some trojans later.
ps.: if it realy is my net then my provider is looking for a new server for me and disconnecting all of my internet - stuff.
It will not response at submittig datas.
I go back to the 1st page and puh f5 crossing fingers that my login came through. if not: i repeat trying tologging in at this 1st link.
We live in 2019 And even at 2008 it would be the only page which is using souch an "self ruining" system.
Why the login - buttons have to be loaded extra and are not at an secured part of the page??
Chrome announces there will be no more XP updates from 2016
Chrome drops XP support 2017.
So XP support by Chrome (one single vendor), was dropped 12 years after it's replacement came out.
Meantime, AMD and NVidia have dropped support for Vista, Win8 and Win8.1, but still support Win7 - because - market share.
In other words, as long as there is a big enough market, they will still produce products for it.
MicroGit have been trying to kill off Win7 since 2012, using all the same tricks they used to try and kill off XP, yet here we are with the market share for Win7 being within a couple of percentage points of Win10 - if you average the results of the various large net stat surveys.
I would put good money on Win10 being replaced before Win7 support stops, as it seems to become more difficult to update, and more unstable with every release.
The LATEST Win10 SNAFU it bricking millions of PCs running AVAST - which apparently has the worlds LARGEST AV install base; so no biggie there then. Do they actually DO any testing??
It's decent, but it doesn't block telemetry back to Microsoft. For blocking that, one would need to set specific registry keys and other changes.
I deploy Windows 10 at work via Microsoft MDT and wrote this script to disable all of that telemetry. Copy and paste specific sections as needed (or just edit the file) and run it in Powershell.
I had corrected my post and thanks for this infos. I just do no want to disable all of it because of my system needs to run a lot to even being able to boot without being asked to re verify each time. Or even to being able to offline - boot.
Since my license is secured at an online - Acount.
Some datas are neccesary to even detecting crashes or bugs /malfunctions. So it is a verry bad idea for me personaly to disabling all of it.
But a lot i already had disabled at the Windows - Installation. Like Cortana etc. "She" is only a bar like the google bar for Windows now.
Like i had written: it was my personal choiche to making my account online at the step where i had logged in my live - account at Windows 10.
Thats how you link this Windows to your live - account.
1 thing which is bad: The user name shall never being changed to preventing not working licenses.
With logging i meant logging in at the windows- installation or the Windows -Account. And then activating/migratig the liceses you have got.
In other words, as long as there is a big enough market, they will still produce products for it.
I completely agree.
Originally Posted by Yarbro
I would put good money on Win10 being replaced before Win7 support stops, as it seems to become more difficult to update, and more unstable with every release.
Microsoft is ending patch/update support for Windows 7 in January of next year. That's typically when most third party developers stop officially supporting it as well. However, if the market share is still high, they often don't block updates or installs on that platform. But if that platform requires additional work to maintain their programs, then a developer would typically drop support at that time.
Originally Posted by Yarbro
The LATEST Win10 SNAFU it bricking millions of PCs running AVAST - which apparently has the worlds LARGEST AV install base; so no biggie there then. Do they actually DO any testing??
Be careful throwing around that term "bricked". It's not accurate in this case. The conflict didn't screw up firmware on systems, so there is no "bricking". But it did screw up the operating system, requiring an offline fix. Pretty nasty one. Both Microsoft and Avast screwed up on this one. Microsoft for not testing a major developer in terms of antivirus market share, and Avast for not testing the latest Microsoft updates with their software. Developers typically have early access to updates from Windows Insider/Technet.
Ok: 1 Extra for you: Windows 10 1903 Launched 2019. About 1 week ago and is like a new system.
Self repairing but still for Insiders only. I use the safest branch so it is ok. With my license of course.
1606/1609 and soon 1703/1709 are not supported anymore. 1803/1809 still are a bit supported. The 09er longer.
The payed update - versions are keeping the support of course.
Microsoft is ending patch/update support for Windows 7 in January of next year. That's typically when most third party developers stop officially supporting it as well. However, if the market share is still high, they often don't block updates or installs on that platform. But if that platform requires additional work to maintain their programs, then a developer would typically drop support at that time.
Be careful throwing around that term "bricked". It's not accurate in this case. The conflict didn't screw up firmware on systems, so there is no "bricking". But it did screw up the operating system, requiring an offline fix. Pretty nasty one. Both Microsoft and Avast screwed up on this one. Microsoft for not testing a major developer in terms of antivirus market share, and Avast for not testing the latest Microsoft updates with their software. Developers typically have early access to updates from Windows Insider/Technet.
Sorry, I thought I had put "temporarily" in front of "bricked", but my 6 y/o was pestering me and I must have missed it out. Sometimes my brain thinks one thing and hand hands type something shipshape dandelion.
The report I read about the problem suggested Avast hadnt had access to the final version of the update; bearing in mind much of this update has been through a bazillion "fixes" since Microgit initially launched it - and (temporarily) bricked millions of PCs - back last Autumn.
Another software package was also involved in the recent bjorking, but I forget who, although my brain is screaming "Adobe - something".
Another software package was also involved in the recent bjorking, but I forget who, although my brain is screaming "Adobe - something".
Adobe is always getting into hot water with something and needing to release patches all the time.
Don't get me wrong, I love plenty of Adobe's apps, but they're so darn bloated and suffer from development issues. They have too many 'cooks in the kitchen' when they make too many things modular across all their apps.
I have read all comments and like what I read. Was going to reply but must head out to buy groceries.
First I wanted to ask WHAT IS GOING ON ACROSS THE ATLANTIC IN US RIGHT NOW ???
This site took ages to load and I decied to make a trace router and basically it's a black out and * * * Timeouts all the way after my 9th hop. After hop with IP Adress 4.31.43.210. Anything after that is just Timeouts. So somewhere close to SSG servers, since the move I usually have 10 max 11 hops before I hit SSG servers. At least via the route I usually get nowdays.
Now time to rush out to buy groceries. Hope hitting Submit on this one will even work and not take too long. I hope this "thing"/problem, whatever it is, clears up soon.
...and I decied to make a trace router and basically it's a black out and * * * Timeouts all the way after my 9th hop. After hop with IP Adress 4.31.43.210. Anything after that is just Timeouts. So somewhere close to SSG servers, since the move I usually have 10 max 11 hops before I hit SSG servers. At least via the route I usually get nowdays.
What are you using to test the trace route? Try the latest WinMTR for more accurate results.
Also, a lot of network hardware is configured to either not respond to pings when there's a lot of traffic, or just not respond to pings at all. They're still working, but just to responding to ping requests. It's the dropped packets and long timeouts you want to focus on, such as replying to a ping a second or more later.