Ladies and gentlemen,

 

A few days ago I wrote a letter to this list regarding Creators Update rollout. In that letter I announced that we have entered Creators Update era and the first 72 hours after a feature update release is critical. Today I would like to send out some follow-up announcements regarding this matter.

 

But first, I’d like to announce that Kelly Ford has left Microsoft, and a couple Microsoft engineers has joined this forum cluster: Jeff Petty, a Narrator developer, and Larry Weiss; I’m sure both will make their intros when they are ready. Please wish Kelly luck as he works on other endeavors, and please show Jeff, Larry and others at Microsoft respect, as they are valuable channels for communication between users, engineers, third-party developers and what not. In addition to staff at Microsoft, please show respect to screen reader representatives such as several JAWS beta testers, Quentin from NV Access and others.

 

With that out of the way, a few announcements regarding Creators Update:

 

• Creators Update rollout has begun. As I and others have stressed, many of you won’t find Version 1703 waiting for you at Windows Update today. At some point, you’ll get a toast notification advising you to check privacy settings, and that’s when you’ll know that Creators Update is not far off. During the upgrade installation, some of you will be asked to check privacy settings at the end of the upgrade. I strongly urge people to use Narrator for this portion, as third-party screen readers might not load during this phase.
• Early flights are for those who are truly prepared: as I wrote recently, early flights (Update Assistant route) is intended for those who can provide technical support on their own, and we did receive reports of people meeting changes the hard way. For this reason, I and others have advised (and will continue to advise) that people wait until feature updates show up on Windows Update, and Creators Update is no exception.
• Critical standby period starts now: the 72-hour critical standby period did not start on April 5^{th; it starts today. That is, the first 72 hours after general availability of a feature update is when we’ll get high traffic regarding upgrades, questions on features and what not. What you saw last week is just a taste of what you’ll see in the next few days, so please sit tight. For Windows Insiders, as I said a few days ago, I’d like to request your help in helping other passengers meet Creators Update (unless you have moved onto Redstone 3).}
• Make sure you back up and update programs you are using, especially screen readers: As I wrote a few days ago, when you install Version 1703, you are effectively installing a new Windows version. Thus, please back up your data somewhere and make sure programs you’re using are up to date, including screen readers. During feature update rollouts, there is at least one person who talks about an issue with Windows 10, only to discover that it was an issue with his or her screen readers not being up to date and compatible. I would like to personally plead with everyone that checking compatibility of your screen reader with Windows 10 releases should now be second nature to you.
• Most importantly, have a great time and a safe upgrade when your computer is ready for Creators Update.

 

Cheers,

Joseph

Ladies and gentlemen,

 

A few days ago I wrote a letter to this list regarding Creators Update rollout. In that letter I announced that we have entered Creators Update era and the first 72 hours after a feature update release is critical. Today I would like to send out some follow-up announcements regarding this matter.

 

But first, I’d like to announce that Kelly Ford has left Microsoft, and a couple Microsoft engineers has joined this forum cluster: Jeff Petty, a Narrator developer, and Larry Weiss; I’m sure both will make their intros when they are ready. Please wish Kelly luck as he works on other endeavors, and please show Jeff, Larry and others at Microsoft respect, as they are valuable channels for communication between users, engineers, third-party developers and what not. In addition to staff at Microsoft, please show respect to screen reader representatives such as several JAWS beta testers, Quentin from NV Access and others.

 

With that out of the way, a few announcements regarding Creators Update:

 

• Creators Update rollout has begun. As I and others have stressed, many of you won’t find Version 1703 waiting for you at Windows Update today. At some point, you’ll get a toast notification advising you to check privacy settings, and that’s when you’ll know that Creators Update is not far off. During the upgrade installation, some of you will be asked to check privacy settings at the end of the upgrade. I strongly urge people to use Narrator for this portion, as third-party screen readers might not load during this phase.
• Early flights are for those who are truly prepared: as I wrote recently, early flights (Update Assistant route) is intended for those who can provide technical support on their own, and we did receive reports of people meeting changes the hard way. For this reason, I and others have advised (and will continue to advise) that people wait until feature updates show up on Windows Update, and Creators Update is no exception.
• Critical standby period starts now: the 72-hour critical standby period did not start on April 5^{th; it starts today. That is, the first 72 hours after general availability of a feature update is when we’ll get high traffic regarding upgrades, questions on features and what not. What you saw last week is just a taste of what you’ll see in the next few days, so please sit tight. For Windows Insiders, as I said a few days ago, I’d like to request your help in helping other passengers meet Creators Update (unless you have moved onto Redstone 3).}
• Make sure you back up and update programs you are using, especially screen readers: As I wrote a few days ago, when you install Version 1703, you are effectively installing a new Windows version. Thus, please back up your data somewhere and make sure programs you’re using are up to date, including screen readers. During feature update rollouts, there is at least one person who talks about an issue with Windows 10, only to discover that it was an issue with his or her screen readers not being up to date and compatible. I would like to personally plead with everyone that checking compatibility of your screen reader with Windows 10 releases should now be second nature to you.
• Most importantly, have a great time and a safe upgrade when your computer is ready for Creators Update.

 

Cheers,

Joseph

Ladies and gentlemen,

A few days ago I wrote a letter to this list regarding Creators Update rollout. In that letter I announced that we have entered Creators Update era and the first 72 hours after a feature update release is critical. Today I would like to send out some follow-up announcements regarding this matter.

But first, I’d like to announce that Kelly Ford has left Microsoft, and a couple Microsoft engineers has joined this forum cluster: Jeff Petty, a Narrator developer, and Larry Weiss; I’m sure both will make their intros when they are ready. Please wish Kelly luck as he works on other endeavors, and please show Jeff, Larry and others at Microsoft respect, as they are valuable channels for communication between users, engineers, third-party developers and what not. In addition to staff at Microsoft, please show respect to screen reader representatives such as several JAWS beta testers, Quentin from NV Access and others.

With that out of the way, a few announcements regarding Creators Update:

• Creators Update rollout has begun. As I and others have stressed, many of you won’t find Version 1703 waiting for you at Windows Update today. At some point, you’ll get a toast notification advising you to check privacy settings, and that’s when you’ll know that Creators Update is not far off. During the upgrade installation, some of you will be asked to check privacy settings at the end of the upgrade. I strongly urge people to use Narrator for this portion, as third-party screen readers might not load during this phase.
• Early flights are for those who are truly prepared: as I wrote recently, early flights (Update Assistant route) is intended for those who can provide technical support on their own, and we did receive reports of people meeting changes the hard way. For this reason, I and others have advised (and will continue to advise) that people wait until feature updates show up on Windows Update, and Creators Update is no exception.
• Critical standby period starts now: the 72-hour critical standby period did not start on April 5^{th; it starts today. That is, the first 72 hours after general availability of a feature update is when we’ll get high traffic regarding upgrades, questions on features and what not. What you saw last week is just a taste of what you’ll see in the next few days, so please sit tight. For Windows Insiders, as I said a few days ago, I’d like to request your help in helping other passengers meet Creators Update (unless you have moved onto Redstone 3).}
• Make sure you back up and update programs you are using, especially screen readers: As I wrote a few days ago, when you install Version 1703, you are effectively installing a new Windows version. Thus, please back up your data somewhere and make sure programs you’re using are up to date, including screen readers. During feature update rollouts, there is at least one person who talks about an issue with Windows 10, only to discover that it was an issue with his or her screen readers not being up to date and compatible. I would like to personally plead with everyone that checking compatibility of your screen reader with Windows 10 releases should now be second nature to you.
• Most importantly, have a great time and a safe upgrade when your computer is ready for Creators Update.

Cheers,

Joseph

Hi,

The following changes are applicable to all screen readers (JAWS included):

• Start menu: hide apps list, organize tiles into folders.
• Cortana: change volume, changed listening mode key.
• Action Center: changes to certain toast notifications.
• Settings: 11 categories, Night Light, Game Mode, choose where to get apps from, up to 18 hours for active hours, many changes.
• Dynamic ducking: allow Windows to dynamically adjust volume if told to do so by software, somehow involved in broken audio ducking functionality in Creators Update in JAWS (this issue does not impact NVDA and Narrator users anymore).
• Dynamic lock: lock a computer when a Bluetooth device is out of range.
• So many changes. See the list archive for details. I will not go into Edge because JAWS does not support it properly at this time.

Cheers,

Joseph

----- Original Message -----

From: Joseph Lee

To: win10@win10.groups.io

Sent: Tuesday, April 11, 2017 2:56 PM

Subject: [win10] Welcome to Creators Update, critical standby period begins, staff changes at Microsoft #BranchProgression #AdminNotice

Ladies and gentlemen,

 

A few days ago I wrote a letter to this list regarding Creators Update rollout. In that letter I announced that we have entered Creators Update era and the first 72 hours after a feature update release is critical. Today I would like to send out some follow-up announcements regarding this matter.

 

But first, I’d like to announce that Kelly Ford has left Microsoft, and a couple Microsoft engineers has joined this forum cluster: Jeff Petty, a Narrator developer, and Larry Weiss; I’m sure both will make their intros when they are ready. Please wish Kelly luck as he works on other endeavors, and please show Jeff, Larry and others at Microsoft respect, as they are valuable channels for communication between users, engineers, third-party developers and what not. In addition to staff at Microsoft, please show respect to screen reader representatives such as several JAWS beta testers, Quentin from NV Access and others.

 

With that out of the way, a few announcements regarding Creators Update:

 

• Creators Update rollout has begun. As I and others have stressed, many of you won’t find Version 1703 waiting for you at Windows Update today. At some point, you’ll get a toast notification advising you to check privacy settings, and that’s when you’ll know that Creators Update is not far off. During the upgrade installation, some of you will be asked to check privacy settings at the end of the upgrade. I strongly urge people to use Narrator for this portion, as third-party screen readers might not load during this phase.
• Early flights are for those who are truly prepared: as I wrote recently, early flights (Update Assistant route) is intended for those who can provide technical support on their own, and we did receive reports of people meeting changes the hard way. For this reason, I and others have advised (and will continue to advise) that people wait until feature updates show up on Windows Update, and Creators Update is no exception.
• Critical standby period starts now: the 72-hour critical standby period did not start on April 5^{th; it starts today. That is, the first 72 hours after general availability of a feature update is when we’ll get high traffic regarding upgrades, questions on features and what not. What you saw last week is just a taste of what you’ll see in the next few days, so please sit tight. For Windows Insiders, as I said a few days ago, I’d like to request your help in helping other passengers meet Creators Update (unless you have moved onto Redstone 3).}
• Make sure you back up and update programs you are using, especially screen readers: As I wrote a few days ago, when you install Version 1703, you are effectively installing a new Windows version. Thus, please back up your data somewhere and make sure programs you’re using are up to date, including screen readers. During feature update rollouts, there is at least one person who talks about an issue with Windows 10, only to discover that it was an issue with his or her screen readers not being up to date and compatible. I would like to personally plead with everyone that checking compatibility of your screen reader with Windows 10 releases should now be second nature to you.
• Most importantly, have a great time and a safe upgrade when your computer is ready for Creators Update.

 

Cheers,

Joseph

----- Original Message -----

From: Alan Robbins

To: win10@win10.groups.io

Sent: Tuesday, April 11, 2017 3:28 PM

Subject: Re: [win10] Welcome to Creators Update, critical standby period begins, staff changes at Microsoft #BranchProgression #AdminNotice

Joseph,
You say to check privacy settings, this is something I have never done and other major updates. What are they supposed to be set and or two?

On Apr 11, 2017, at 14:56, Joseph Lee <joseph.lee22590@...> wrote:

Ladies and gentlemen,

A few days ago I wrote a letter to this list regarding Creators Update rollout. In that letter I announced that we have entered Creators Update era and the first 72 hours after a feature update release is critical. Today I would like to send out some follow-up announcements regarding this matter.

But first, I’d like to announce that Kelly Ford has left Microsoft, and a couple Microsoft engineers has joined this forum cluster: Jeff Petty, a Narrator developer, and Larry Weiss; I’m sure both will make their intros when they are ready. Please wish Kelly luck as he works on other endeavors, and please show Jeff, Larry and others at Microsoft respect, as they are valuable channels for communication between users, engineers, third-party developers and what not. In addition to staff at Microsoft, please show respect to screen reader representatives such as several JAWS beta testers, Quentin from NV Access and others.

With that out of the way, a few announcements regarding Creators Update:

• Creators Update rollout has begun. As I and others have stressed, many of you won’t find Version 1703 waiting for you at Windows Update today. At some point, you’ll get a toast notification advising you to check privacy settings, and that’s when you’ll know that Creators Update is not far off. During the upgrade installation, some of you will be asked to check privacy settings at the end of the upgrade. I strongly urge people to use Narrator for this portion, as third-party screen readers might not load during this phase.
• Early flights are for those who are truly prepared: as I wrote recently, early flights (Update Assistant route) is intended for those who can provide technical support on their own, and we did receive reports of people meeting changes the hard way. For this reason, I and others have advised (and will continue to advise) that people wait until feature updates show up on Windows Update, and Creators Update is no exception.
• Critical standby period starts now: the 72-hour critical standby period did not start on April 5^{th; it starts today. That is, the first 72 hours after general availability of a feature update is when we’ll get high traffic regarding upgrades, questions on features and what not. What you saw last week is just a taste of what you’ll see in the next few days, so please sit tight. For Windows Insiders, as I said a few days ago, I’d like to request your help in helping other passengers meet Creators Update (unless you have moved onto Redstone 3).}
• Make sure you back up and update programs you are using, especially screen readers: As I wrote a few days ago, when you install Version 1703, you are effectively installing a new Windows version. Thus, please back up your data somewhere and make sure programs you’re using are up to date, including screen readers. During feature update rollouts, there is at least one person who talks about an issue with Windows 10, only to discover that it was an issue with his or her screen readers not being up to date and compatible. I would like to personally plead with everyone that checking compatibility of your screen reader with Windows 10 releases should now be second nature to you.
• Most importantly, have a great time and a safe upgrade when your computer is ready for Creators Update.

Cheers,

Joseph

----- Original Message -----

From: Kenny Peyattt jr.

To: win10@win10.groups.io

Sent: Tuesday, April 11, 2017 3:47 PM

Subject: Re: [win10] Welcome to Creators Update, critical standby period begins, staff changes at Microsoft #BranchProgression #AdminNotice

Why will we be asked to check our privacy settings before the creator update arrives to the pcs via windows update?

Kenny Peyatt jr.

 

From: win10@win10.groups.io [mailto:win10@win10.groups.io] On Behalf Of Joseph Lee
Sent: Tuesday, April 11, 2017 2:57 PM
To: win10@win10.groups.io
Subject: [win10] Welcome to Creators Update, critical standby period begins, staff changes at Microsoft #BranchProgression #AdminNotice

 

Ladies and gentlemen,

 

A few days ago I wrote a letter to this list regarding Creators Update rollout. In that letter I announced that we have entered Creators Update era and the first 72 hours after a feature update release is critical. Today I would like to send out some follow-up announcements regarding this matter.

 

But first, I’d like to announce that Kelly Ford has left Microsoft, and a couple Microsoft engineers has joined this forum cluster: Jeff Petty, a Narrator developer, and Larry Weiss; I’m sure both will make their intros when they are ready. Please wish Kelly luck as he works on other endeavors, and please show Jeff, Larry and others at Microsoft respect, as they are valuable channels for communication between users, engineers, third-party developers and what not. In addition to staff at Microsoft, please show respect to screen reader representatives such as several JAWS beta testers, Quentin from NV Access and others.

 

With that out of the way, a few announcements regarding Creators Update:

 

• Creators Update rollout has begun. As I and others have stressed, many of you won’t find Version 1703 waiting for you at Windows Update today. At some point, you’ll get a toast notification advising you to check privacy settings, and that’s when you’ll know that Creators Update is not far off. During the upgrade installation, some of you will be asked to check privacy settings at the end of the upgrade. I strongly urge people to use Narrator for this portion, as third-party screen readers might not load during this phase.
• Early flights are for those who are truly prepared: as I wrote recently, early flights (Update Assistant route) is intended for those who can provide technical support on their own, and we did receive reports of people meeting changes the hard way. For this reason, I and others have advised (and will continue to advise) that people wait until feature updates show up on Windows Update, and Creators Update is no exception.
• Critical standby period starts now: the 72-hour critical standby period did not start on April 5^{th; it starts today. That is, the first 72 hours after general availability of a feature update is when we’ll get high traffic regarding upgrades, questions on features and what not. What you saw last week is just a taste of what you’ll see in the next few days, so please sit tight. For Windows Insiders, as I said a few days ago, I’d like to request your help in helping other passengers meet Creators Update (unless you have moved onto Redstone 3).}
• Make sure you back up and update programs you are using, especially screen readers: As I wrote a few days ago, when you install Version 1703, you are effectively installing a new Windows version. Thus, please back up your data somewhere and make sure programs you’re using are up to date, including screen readers. During feature update rollouts, there is at least one person who talks about an issue with Windows 10, only to discover that it was an issue with his or her screen readers not being up to date and compatible. I would like to personally plead with everyone that checking compatibility of your screen reader with Windows 10 releases should now be second nature to you.
• Most importantly, have a great time and a safe upgrade when your computer is ready for Creators Update.

 

Cheers,

Joseph

----- Original Message -----

From: Kenny Peyattt jr.

To: win10@win10.groups.io

Sent: April 11, 2017 15:47

Subject: Re: [win10] Welcome to Creators Update, critical standby period begins, staff changes at Microsoft #BranchProgression #AdminNotice

Why will we be asked to check our privacy settings before the creator update arrives to the pcs via windows update?

Kenny Peyatt jr.

 

From: win10@win10.groups.io [mailto:win10@win10.groups.io] On Behalf Of Joseph Lee
Sent: Tuesday, April 11, 2017 2:57 PM
To: win10@win10.groups.io
Subject: [win10] Welcome to Creators Update, critical standby period begins, staff changes at Microsoft #BranchProgression #AdminNotice

 

Ladies and gentlemen,

 

A few days ago I wrote a letter to this list regarding Creators Update rollout. In that letter I announced that we have entered Creators Update era and the first 72 hours after a feature update release is critical. Today I would like to send out some follow-up announcements regarding this matter.

 

But first, I’d like to announce that Kelly Ford has left Microsoft, and a couple Microsoft engineers has joined this forum cluster: Jeff Petty, a Narrator developer, and Larry Weiss; I’m sure both will make their intros when they are ready. Please wish Kelly luck as he works on other endeavors, and please show Jeff, Larry and others at Microsoft respect, as they are valuable channels for communication between users, engineers, third-party developers and what not. In addition to staff at Microsoft, please show respect to screen reader representatives such as several JAWS beta testers, Quentin from NV Access and others.

 

With that out of the way, a few announcements regarding Creators Update:

 

• Creators Update rollout has begun. As I and others have stressed, many of you won’t find Version 1703 waiting for you at Windows Update today. At some point, you’ll get a toast notification advising you to check privacy settings, and that’s when you’ll know that Creators Update is not far off. During the upgrade installation, some of you will be asked to check privacy settings at the end of the upgrade. I strongly urge people to use Narrator for this portion, as third-party screen readers might not load during this phase.
• Early flights are for those who are truly prepared: as I wrote recently, early flights (Update Assistant route) is intended for those who can provide technical support on their own, and we did receive reports of people meeting changes the hard way. For this reason, I and others have advised (and will continue to advise) that people wait until feature updates show up on Windows Update, and Creators Update is no exception.
• Critical standby period starts now: the 72-hour critical standby period did not start on April 5^{th; it starts today. That is, the first 72 hours after general availability of a feature update is when we’ll get high traffic regarding upgrades, questions on features and what not. What you saw last week is just a taste of what you’ll see in the next few days, so please sit tight. For Windows Insiders, as I said a few days ago, I’d like to request your help in helping other passengers meet Creators Update (unless you have moved onto Redstone 3).}
• Make sure you back up and update programs you are using, especially screen readers: As I wrote a few days ago, when you install Version 1703, you are effectively installing a new Windows version. Thus, please back up your data somewhere and make sure programs you’re using are up to date, including screen readers. During feature update rollouts, there is at least one person who talks about an issue with Windows 10, only to discover that it was an issue with his or her screen readers not being up to date and compatible. I would like to personally plead with everyone that checking compatibility of your screen reader with Windows 10 releases should now be second nature to you.
• Most importantly, have a great time and a safe upgrade when your computer is ready for Creators Update.

 

Cheers,

Joseph

----- Original Message -----

From: inamuddin khan

To: win10@win10.groups.io

Sent: Tuesday, April 11, 2017 6:30 PM

Subject: Re: [win10] Welcome to Creators Update, critical standby periodbegins, staff changes at Microsoft #BranchProgression #AdminNotice

Dear friends,

Before creater’s update whenever I wanted to go to control panel, I just use to press control+x using down arrow until control panel and use to press enter key and that’s all!

Now the question is where is the control panel in creater’s update?

Thanks and regards from Inamuddin with the Skype ID:

Charlsdarwin1

 

 

Sent from Mail for Windows 10

 

From: Brian Vogel
Sent: Wednesday, April 12, 2017 3:12 AM
To: win10@win10.groups.io
Subject: Re: [win10] Welcome to Creators Update, critical standby periodbegins, staff changes at Microsoft #BranchProgression #AdminNotice

 

If you, any you, have never cruised through the privacy settings in Windows 10 you should.  Many would not be pleased with all of the defaults as they are set up.  This is on any of the releases of Windows 10.

Reporting for myself, I did not get anything from Windows 10 regarding checking Privacy Settings except as part of the Creators Update, and then there is a dialog presented for the specific Privacy Settings that may have been changed by the update.  I can't say, "were changed," because it depends on what you had them set to to begin with.   There were a great many complaints, and legitimate ones in my opinion, about previous major updates of Windows 10 changing settings, and particularly privacy settings, that a user had reset themselves and had every reason to believe would remain as they'd set them until they changed them again.  This is not necessarily so and, for myself, I have no problem with an update changing settings so long as part of the update is presentation of a dialog identifying said settings and asking me to tweak those as I see fit.

It is not incumbent on anyone here to be the one and only messenger about changes to Windows 10 Creators Update.  There are thousands of pages already written on Microsoft's site and in the technical press regarding the changes to Windows 10 with the Creators Update.  It is not unreasonable not only to ask, but to expect as standard operating procedure, members on a technical forum to do web searches to get answers that everyone knows, or should strongly suspect, are out there.  I am using the following not to call out Mr. Gilland, but because it is convenient:  A search in any web search engine on "Windows 10 Night Light" (or nightlight as one word) returns article after article after article on what it is and how to use it.  Likewise a search on "Windows 10 Creators Update New Features".

--
Brian

    . . . it misses the point that even if you eliminated all cultural biases, human beings would still form stereotypes.  It's simply how the brain works.

            ~ Scott Safier,  March 10, 2004

 

---

If you, any you, have never cruised through the privacy settings in Windows 10 you should.  Many would not be pleased with all of the defaults as they are set up.  This is on any of the releases of Windows 10.

Reporting for myself, I did not get anything from Windows 10 regarding checking Privacy Settings except as part of the Creators Update, and then there is a dialog presented for the specific Privacy Settings that may have been changed by the update.  I can't say, "were changed," because it depends on what you had them set to to begin with.   There were a great many complaints, and legitimate ones in my opinion, about previous major updates of Windows 10 changing settings, and particularly privacy settings, that a user had reset themselves and had every reason to believe would remain as they'd set them until they changed them again.  This is not necessarily so and, for myself, I have no problem with an update changing settings so long as part of the update is presentation of a dialog identifying said settings and asking me to tweak those as I see fit.

It is not incumbent on anyone here to be the one and only messenger about changes to Windows 10 Creators Update.  There are thousands of pages already written on Microsoft's site and in the technical press regarding the changes to Windows 10 with the Creators Update.  It is not unreasonable not only to ask, but to expect as standard operating procedure, members on a technical forum to do web searches to get answers that everyone knows, or should strongly suspect, are out there.  I am using the following not to call out Mr. Gilland, but because it is convenient:  A search in any web search engine on "Windows 10 Night Light" (or nightlight as one word) returns article after article after article on what it is and how to use it.  Likewise a search on "Windows 10 Creators Update New Features".

--
Brian

    . . . it misses the point that even if you eliminated all cultural biases, human beings would still form stereotypes.  It's simply how the brain works.

            ~ Scott Safier,  March 10, 2004

----- Original Message -----

From: Brian Vogel

To: win10@win10.groups.io

Sent: Tuesday, April 11, 2017 7:45 PM

Subject: Re: [win10] Welcome to Creators Update, critical standby period begins, staff changes at Microsoft #BranchProgression #AdminNotice

On Tue, Apr 11, 2017 at 03:45 pm, Christopher-Mark Gilland wrote:

I am not getting bent out of shape, so don't even go there.

If you have to explain it . . .

I'll go wherever I please.  You, of all people, are capable of doing a web search.  It's not a matter of asking for help, it's a matter of not lifting a finger before doing so.
--
Brian

    . . . it misses the point that even if you eliminated all cultural biases, human beings would still form stereotypes.  It's simply how the brain works.

            ~ Scott Safier,  March 10, 2004

Whatever. I'm not arguing this. Enough said.
---
Christopher Gilland
Co-founder of Genuine Safe Haven Ministries

http://www.gshministry.org
(980) 500-9575
----- Original Message -----
From: Brian Vogel
To: win10@win10.groups.io
Sent: Tuesday, April 11, 2017 7:45 PM
Subject: Re: [win10] Welcome to Creators Update, critical standby period
begins, staff changes at Microsoft #BranchProgression #AdminNotice


On Tue, Apr 11, 2017 at 03:45 pm, Christopher-Mark Gilland wrote:

I am not getting bent out of shape, so don't even go there.
If you have to explain it . . .

I'll go wherever I please. You, of all people, are capable of doing a web
search. It's not a matter of asking for help, it's a matter of not lifting
a finger before doing so.
--
Brian

. . . it misses the point that even if you eliminated all cultural
biases, human beings would still form stereotypes. It's simply how the
brain works.


~ Scott Safier, March 10, 2004

----- Original Message -----

From: Austin Pinto

To: win10@win10.groups.io

Sent: Tuesday, April 11, 2017 11:49 PM

Subject: Re: [win10] Welcome to Creators Update, critical standby period begins, staff changes at Microsoft #BranchProgression #AdminNotice

ok.
let me answer 1 major question.
when should you use narrator?
the answer is a bit long.
depending on the root you take to upgrade from windows update or update tool.
the update downloads.
at this time your screen reader should work.
once you press restart now or if update tool root install now.
it will ask you to reboot your computer.
just wait for 10 seconds and then press ctrl windows enter.
keep narrator on and keep checking the progress.
the best way to do this is press narrator and space that is capslog
and space to turn scan mode on and use up and down arrows to read the
screen.
every time your computer reboots there should normally be 3 reboots
for the entire update you will have to restart narrator.
you will have to check privacy settings after the update goes to 75%
which means your system has entered oob faze.
you will have to do that cause there are some changes to privacy settings.
another thing is the upgrade will reset all of your apps to defaults.
like edge for web browser music for audio files and so on.
so you will have to change that also.
i would advise to just have a look at the settings and sub settings
after your pc settels after the upgrade

On 4/12/17, Christopher-Mark Gilland <clgilland07@...> wrote:
> Whatever. I'm not arguing this. Enough said.
> ---
> Christopher Gilland
> Co-founder of Genuine Safe Haven Ministries
>
> http://www.gshministry.org
> (980) 500-9575
>   ----- Original Message -----
>   From: Brian Vogel
>   To: win10@win10.groups.io
>   Sent: Tuesday, April 11, 2017 7:45 PM
>   Subject: Re: [win10] Welcome to Creators Update, critical standby period
> begins, staff changes at Microsoft #BranchProgression #AdminNotice
>
>
>   On Tue, Apr 11, 2017 at 03:45 pm, Christopher-Mark Gilland wrote:
>
>     I am not getting bent out of shape, so don't even go there.
>   If you have to explain it . . .
>
>   I'll go wherever I please.  You, of all people, are capable of doing a web
> search.  It's not a matter of asking for help, it's a matter of not lifting
> a finger before doing so.
>   --
>   Brian
>
>       . . . it misses the point that even if you eliminated all cultural
> biases, human beings would still form stereotypes.  It's simply how the
> brain works.
>
>
>               ~ Scott Safier,  March 10, 2004
>
>
>


--
search for me on facebook, google+, orkut..
austinpinto.xaviers@...
follow me on twitter.
austinmpinto
contact me on skype.
austin.pinto3

Awesome, and yes. It looks like I got through the update with success. I
never was asked about privacy settings, however, I did manually go through
and make sure they were correct.

I also got all my default apps back like I like them.

Thank you for your help, Austin. Greatly appreciate it, bro.
---
Christopher Gilland
Co-founder of Genuine Safe Haven Ministries

http://www.gshministry.org
(980) 500-9575
----- Original Message -----
From: Austin Pinto
To: win10@win10.groups.io
Sent: Tuesday, April 11, 2017 11:49 PM
Subject: Re: [win10] Welcome to Creators Update, critical standby period
begins, staff changes at Microsoft #BranchProgression #AdminNotice


ok.
let me answer 1 major question.
when should you use narrator?
the answer is a bit long.
depending on the root you take to upgrade from windows update or update
tool.
the update downloads.
at this time your screen reader should work.
once you press restart now or if update tool root install now.
it will ask you to reboot your computer.
just wait for 10 seconds and then press ctrl windows enter.
keep narrator on and keep checking the progress.
the best way to do this is press narrator and space that is capslog
and space to turn scan mode on and use up and down arrows to read the
screen.
every time your computer reboots there should normally be 3 reboots
for the entire update you will have to restart narrator.
you will have to check privacy settings after the update goes to 75%
which means your system has entered oob faze.
you will have to do that cause there are some changes to privacy
settings.
another thing is the upgrade will reset all of your apps to defaults.
like edge for web browser music for audio files and so on.
so you will have to change that also.
i would advise to just have a look at the settings and sub settings
after your pc settels after the upgrade

On 4/12/17, Christopher-Mark Gilland <clgilland07@gmail.com> wrote:
> Whatever. I'm not arguing this. Enough said.
> ---
> Christopher Gilland
> Co-founder of Genuine Safe Haven Ministries
>
> http://www.gshministry.org
> (980) 500-9575
> ----- Original Message -----
> From: Brian Vogel
> To: win10@win10.groups.io
> Sent: Tuesday, April 11, 2017 7:45 PM
> Subject: Re: [win10] Welcome to Creators Update, critical standby
period
> begins, staff changes at Microsoft #BranchProgression #AdminNotice
>
>
> On Tue, Apr 11, 2017 at 03:45 pm, Christopher-Mark Gilland wrote:
>
> I am not getting bent out of shape, so don't even go there.
> If you have to explain it . . .
>
> I'll go wherever I please. You, of all people, are capable of doing a
web
> search. It's not a matter of asking for help, it's a matter of not
lifting
> a finger before doing so.
> --
> Brian
>
> . . . it misses the point that even if you eliminated all
cultural
> biases, human beings would still form stereotypes. It's simply how the
> brain works.
>
>
> ~ Scott Safier, March 10, 2004
>
>
>


--
search for me on facebook, google+, orkut..
austinpinto.xaviers@gmail.com
follow me on twitter.
austinmpinto
contact me on skype.
austin.pinto3