[phpBB Debug] PHP Warning: in file [ROOT]/phpbb/session.php on line 574: sizeof(): Parameter must be an array or an object that implements Countable
[phpBB Debug] PHP Warning: in file [ROOT]/phpbb/session.php on line 630: sizeof(): Parameter must be an array or an object that implements Countable
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 370: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 370: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 370: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 113: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 370: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 113: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 113: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 113: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 5348: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3937)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 5348: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3937)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 5348: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3937)
Win10 notifier/download, How To STOP it - FrankForum (Frankness IS Forum)

FrankForum (Frankness IS Forum)

No ads, no mods, Frankly Anonymous (you can join w/fake name/email, are not tracked)!
It is currently 06 Mar 2021, 01:03

All times are UTC


Forum rules


GUESTS AND MEMBERS can post here. Extra Smileys: http://forums.mydigitallife.info/misc.p ... _Editor_QR

Not moderated, so you are on your own. Spambots, stalkers and anti-semites will be banned without notice. Else, POLICE YOURSELF.



Post new topic  Reply to topic  [ 15 posts ]  [phpBB Debug] PHP Warning: in file [ROOT]/vendor/twig/twig/lib/Twig/Extension/Core.php on line 1266: count(): Parameter must be an array or an object that implements Countable
Author Message
PostPosted: 20 Aug 2015, 16:14 
Site Admin
User avatar

Joined: 10 Aug 2015, 16:03
Posts: 1845


Report this post
Top
   
PostPosted: 07 Sep 2015, 08:26 
Site Admin
User avatar

Joined: 10 Aug 2015, 16:03
Posts: 1845
Here's the latest rehash of how to stop Windows 10 popups in Windows 7, in light of the latest warning that MSFT is trying to foist privacy-robbing snooping on earlier Windows versions:

Most important thing you can do, is turn Windows 7 updates OFF: .. :bustedcop:

1. Type 'Windows Update' in search box of Start Menu.

2. Pick the 'Windows Update' at top left which is higlighted in blue, as a result.

3. The resulting window has at left, 'Change settings'. Click on that.

4. The resulting window then has in the middle, a dropdown list, one of which says 'Never check for updates'. Click on that, then click OKay at the right bottom.

5. There's now a red shield which is supposed to scare you. As if you didn't know anything. But as a result, after clicking the OK, the screen changes and you'll see a button in middle right which says 'Check for Updates'.

6. So now it's a MANUAL process, which YOU control.

7. So when YOU are ready to check for updates, you again repeat steps #1-2, and you'll immediately see the result in #5.

8. So BEFORE you click on 'Check for updates' again, you CLONE or backup your entire hard drive (clone is better, it's a live bootable replica of your machine, and you can get for cloning).

9. So after doing step #8, when you click on 'Check for updates' you'll have a delay.

10. After the delay, you'll have a list of updates which at right give you a link of the 'KB' you can click on, to see what it is.

11. If you don't understand what the update says, or it says 'telemetry' or 'experience', AVOID IT; instead of getting it, right-click and HIDE the update, so it won't come again.

12. If instead it says 'security' update, and you read the KB article, and you see keywords like 'kernal' or 'fault' or 'elevated privileges', then yeah it's a security update, and you're safe to accept it. Else, ignore it or hide it. Point is, not to accept what you don't understand.

13. Some of the optional updates relate to your hardware, extra software, or to the Intel stuff on your machine. Read the KB articles and if you understand them, accept those updates, too. Don't accept what you do not understand.

. Now, these might change. Or, even after you hide them, later versions of the same ones might come down as updates.

14. As for the CEIP stuff, it depends on what MSFT software you have. The generic setting can be accessed by typing 'Customer Experience' in the Start Menu search Box. At upper left you will then see 'Customer Experience.. Settings'. Which, technically you click on and then turn off. But that only turns off the reporting for Windows crashes or problems.

Per Microsoft programs, there are addtional CEIP defaults to turn off. Usually in Help there is some option about how to configure the help, whether to get help online 'web'. THERE is where they stash the CEIP option (i.e., in Microsoft Word 2003, I don't do later Word, so you'll have to hunt for the new location). That's an estimate of where it will be. Each program you have will have its own CEIP.

But the point of the Forbes article is that it won't matter what you select. Nor will it matter if you do a registry hack or state 'hosts' file to avoid the phoning home. MSFT will just ignore your preferences, and slurp the data anyway.

How true is that article? Not sure, really. But since you can't tell what data of yours is being sent back to MSFT, the smartest thing is to avoid the 'updates' which alter what is sent home, in the first place. If the KB numbers mentioned above are already installed, then you have to go through Uninstall updates (type that in the Start Menu search box) and uninstall the highest number first, backwards. You might not be able to uninstall.

Does this help? Yell at me if not.


Report this post
Top
   
PostPosted: 11 Sep 2015, 03:01 
Site Admin
User avatar

Joined: 10 Aug 2015, 16:03
Posts: 1845
Be sure to get rid of those updates soon. :drinkcompute:

Two articles here and one reaction, help explain why. How true they are for the States, I don't know, but why take chances. The initial BC post re the articles (for added perspectives), is here.




and


The reaction, . I had to use the 'reply' function to get the permalink, sorry.

If you've an domain or Active Directory network and you need hints on how to block those creepy updates, .


Report this post
Top
   
PostPosted: 17 Sep 2015, 21:45 
Site Admin
User avatar

Joined: 10 Aug 2015, 16:03
Posts: 1845
In the lead post, the video shown is what I actually ran. So far, so good. Since somehow prior updates wiped out my list of hidden updates, this latest KB 3050265 which promises to stop GWX altogether, better dang well work!


Report this post
Top
   
PostPosted: 22 Sep 2015, 03:55 
User avatar

Joined: 14 Sep 2015, 13:11
Posts: 383
I will have to rescind my belief of Windows 7 to 10 upgrades being seamless in an 'ideal' environment (that I claimed) due to correspondence that was thrown at me from a colleague out of the blue.


Report this post
Top
   
PostPosted: 02 Oct 2015, 07:00 
Site Admin
User avatar

Joined: 10 Aug 2015, 16:03
Posts: 1845


Report this post
Top
   
PostPosted: 04 Oct 2015, 19:25 
User avatar

Joined: 14 Sep 2015, 13:11
Posts: 383


Report this post
Top
   
PostPosted: 10 Oct 2015, 22:08 
Site Admin
User avatar

Joined: 10 Aug 2015, 16:03
Posts: 1845
Apparently MSFT is breaking its promise re KB 3050265, on which I did a video. That video and 'Private One' comments in reply to explain that 3050265 is no longer stopping GWX notifiers, are

So you may have to hide the updates all over again:
3035583
2952664
2976978
2977759
3083710
3083711


Report this post
Top
   
PostPosted: 16 Oct 2015, 22:29 
Site Admin
User avatar

Joined: 10 Aug 2015, 16:03
Posts: 1845
Latest forced attempt to make Win10 go on your machine, PRE-TICKED BOX for Windows Update to 10, make it a regular update!! Not kidding, read here:

Tandem articles and discussion are going on,


Report this post
Top
   
PostPosted: 19 Oct 2015, 01:05 
Site Admin
User avatar

Joined: 10 Aug 2015, 16:03
Posts: 1845


Report this post
Top
   
PostPosted: 20 Oct 2015, 23:50 
Site Admin
User avatar

Joined: 10 Aug 2015, 16:03
Posts: 1845
Article is . Take it slow, there's a lot of material covered, and not all the suggested steps will be useful/beneficial. Depends on your system and proclivities.


Report this post
Top
   
PostPosted: 29 Oct 2015, 23:57 
Site Admin
User avatar

Joined: 10 Aug 2015, 16:03
Posts: 1845
, who got her news from MSFT's Terry Myerson, that the (hitlerian disgusting) forced Win10 nagware/ransomware notice will continue. They didn't listen at all to the problems. So all those hapless grandparents and children and casual users who didn't have the money to get the nagware removed by a professional, are now going to be continually harrassed.

And the updates for Win7 and 8, being bypassed until you click on Win10, means they can't be patched for Win7 and 8, either. So then they can't get the security updates they need, or have to shell out money to computer geeks to get the Win10 nagware/ransomware removed -- if they even know the CAN do that.

It's no longer moral to buy anything MSFT sells. Sorry. Hitlerian describes MSFT now in EVERY WAY.

Boycott them and anyone who praises Win10, until all this is over. Better still, PRAY that God smack down those fostering this, for the sake of protecting those who are victims. For this IS a form of terrorism.

Since we don't know who's truly guilty and what kind of redress should be employed, prayer rather than human action is the better option, so that real justice will be done. God better knows what's required, than we do.

Parallel articles coming out afterwards: then and .

But avoid commenting at ArsTechnica. If you tell the truth about how bad Windows 10 is, or reply to others, you get banned as if you were a troll, even if you use citations and substance. Even ZDnet is not that bad. So 'shake the dust' at ArsTechnica.


Report this post
Top
   
PostPosted: 02 Dec 2015, 16:02 
Site Admin
User avatar

Joined: 10 Aug 2015, 16:03
Posts: 1845
Since Win10 adoption is going so badly, MSFT has come up with new ways to wreck our lives, with new KBs, .

The KBs come through Windows Update, so I hope you've turned them off to make update manual.

The one TO HIDE/REFUSE for Win7 is https://support.microsoft.com/en-us/kb/3112343
The one to HIDE/REFUSE for Win8 is https://support.microsoft.com/en-us/kb/3112336

Now you are forewarned.


Report this post
Top
   
PostPosted: 03 Dec 2015, 01:39 
User avatar

Joined: 14 Sep 2015, 13:11
Posts: 383
Also just to re-iterate, the GWX remover, removes and prevents Windows 7/8 switching to Windows 10:
http://ultimateoutsider.com/downloads/G ... lSetup.exe


Report this post
Top
   
 Post subject: Win10 notifier MORPHING?
PostPosted: 07 Dec 2015, 15:07 
Site Admin
User avatar

Joined: 10 Aug 2015, 16:03
Posts: 1845
Now, MSFT is changing its nagware for GWX to ignore or reset your specs against it, from off (don't want), to on (do want) -- automatically. Apparently it's checking as often as several times during an hour. That should slow down your operation, no? :killcomp: :smashcomp: :hammer: :typing: :crying:

. Opine, please?


Report this post
Top
   
Display posts from previous:  Sort by  
Post new topic  Reply to topic  [ 15 posts ]  [phpBB Debug] PHP Warning: in file [ROOT]/vendor/twig/twig/lib/Twig/Extension/Core.php on line 1266: count(): Parameter must be an array or an object that implements Countable

All times are UTC


[phpBB Debug] PHP Warning: in file [ROOT]/vendor/twig/twig/lib/Twig/Extension/Core.php on line 1266: count(): Parameter must be an array or an object that implements Countable
You can post new topics in this forum
You can reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
cron
Powered by phpBB® Forum Software © phpBB Limited