Topics

Critical advisory: do NOT update to Fall Creators Update if you plan to use JAWS 2018 with Edge due to performance problems #jaws #ADVISORY #wintendev


 

Hi everyone,

 

The below advisory is rated “critical” as it will affect ALL JAWS 2018 users who plans to use Microsoft Edge in Fall Creators Update. Thus, I recommend folks to forward this to other forums, mailing lists and what not, as well as raise a red flag with MS and VFO:

 

CRITICAL ADVISORY: major performance issues found when using JAWS 2018 with Edge under Fall creators Update builds, with one report stating JAWS and/or Edge crashes:

 

JAWS 2018 adds support for Microsoft Edge, the browser that ships as part of Windows 10. Support for Microsoft Edge, especially the new EdgeHTML rendering engine, is crucial when it comes to supporting certain universal apps, as they will use the rendering engine used by Edge to display web content. However, some users have reported performance problems when trying to use JAWS 2018 with Edge under Fall Creators Update preview builds, ranging from delay in feedback to at least one report of JAWS and/or Edge crashing, with performance issues confirmed in subsequent testing. Although these are possible due to beta status of JAWS 2018, part of this is due to changes to Edge code introduced in several Windows Insider Preview builds for the upcoming feature update to Windows 10.

 

Reason for rating this advisory “critical”:

 

  • Windows 10 is a service, therefore feature updates are sent to users and organizations on a semi-annual basis. The latest stable build (Version 1703) will be replaced by upcoming Fall Creators Update (Version 1709) in a few weeks, and soon or later, most users will be asked to update to the new version. Although enterprises can delay the upgrade for a time, they will be asked to upgrade to a future release at one point or another. For those running Windows 10 Home, you CANNOT defer updates.
  • The time to deploy Fall Creators Update can range from several weeks to several months. This means that, unless users tell Windows 10 to defer updates, they’ll be updated to the new release. If told to defer updates, Windows 10 will present the new release by early next year.
  • The delay period (between the day Fall Creators Update is released and January 2018) is a period of bug fixing, and if MS and/or VFO misses this, people will face issues with Edge in the upcoming release after upgrades, further compounding the problem. Thus, it is critical that a fix (both short-term and long-term) is in place before end of 2017 to allow people to test this for a few weeks before Fall Creators Update comes to everyone.

 

Recommended actions:

 

  1. Raise a red flag (feedback) with Microsoft and VFO to make sure this is addressed as soon as possible.
  2. Avoid upgrading to Fall Creators Update until issues with JAWS and Edge are ironed out to an extent that users can use Edge for basic tasks.
  3. Optionally, if you absolutely need to use Edge and/or universal apps that display web content via Edge’s rendering engine, use other screen readers known to support Edge (such as Narrator).
  4. If you need to use a web browser for any task, do NOT use Edge until major problems are resolved.

 

Thanks.

Cheers,

Joseph


kavein thran
 

thanks joseph,

On 9/1/17, Joseph Lee <@joslee> wrote:
Hi everyone,



The below advisory is rated "critical" as it will affect ALL JAWS 2018
users
who plans to use Microsoft Edge in Fall Creators Update. Thus, I recommend
folks to forward this to other forums, mailing lists and what not, as well
as raise a red flag with MS and VFO:



CRITICAL ADVISORY: major performance issues found when using JAWS 2018 with
Edge under Fall creators Update builds, with one report stating JAWS and/or
Edge crashes:



JAWS 2018 adds support for Microsoft Edge, the browser that ships as part
of
Windows 10. Support for Microsoft Edge, especially the new EdgeHTML
rendering engine, is crucial when it comes to supporting certain universal
apps, as they will use the rendering engine used by Edge to display web
content. However, some users have reported performance problems when trying
to use JAWS 2018 with Edge under Fall Creators Update preview builds,
ranging from delay in feedback to at least one report of JAWS and/or Edge
crashing, with performance issues confirmed in subsequent testing. Although
these are possible due to beta status of JAWS 2018, part of this is due to
changes to Edge code introduced in several Windows Insider Preview builds
for the upcoming feature update to Windows 10.



Reason for rating this advisory "critical":



* Windows 10 is a service, therefore feature updates are sent to users
and organizations on a semi-annual basis. The latest stable build (Version
1703) will be replaced by upcoming Fall Creators Update (Version 1709) in a
few weeks, and soon or later, most users will be asked to update to the new
version. Although enterprises can delay the upgrade for a time, they will
be
asked to upgrade to a future release at one point or another. For those
running Windows 10 Home, you CANNOT defer updates.
* The time to deploy Fall Creators Update can range from several weeks
to several months. This means that, unless users tell Windows 10 to defer
updates, they'll be updated to the new release. If told to defer updates,
Windows 10 will present the new release by early next year.
* The delay period (between the day Fall Creators Update is released
and January 2018) is a period of bug fixing, and if MS and/or VFO misses
this, people will face issues with Edge in the upcoming release after
upgrades, further compounding the problem. Thus, it is critical that a fix
(both short-term and long-term) is in place before end of 2017 to allow
people to test this for a few weeks before Fall Creators Update comes to
everyone.



Recommended actions:



1. Raise a red flag (feedback) with Microsoft and VFO to make sure this
is addressed as soon as possible.
2. Avoid upgrading to Fall Creators Update until issues with JAWS and
Edge are ironed out to an extent that users can use Edge for basic tasks.
3. Optionally, if you absolutely need to use Edge and/or universal apps
that display web content via Edge's rendering engine, use other screen
readers known to support Edge (such as Narrator).
4. If you need to use a web browser for any task, do NOT use Edge until
major problems are resolved.



Thanks.

Cheers,

Joseph


g melconian
 

Thanks for letting us know. I actually don’t use ms edge, my default two browsers that work the best and have been using them from windos 7 days ar chrome and firefox . those two have never let me down with any screenreader from supernova, to window eyes to NVDA to jaws .  these ar the three major screenreaders that I have used in 25 years. 

 

From: win10@win10.groups.io [mailto:win10@win10.groups.io] On Behalf Of Joseph Lee
Sent: Thursday, August 31, 2017 10:18 PM
To: win10@win10.groups.io
Subject: [win10] Critical advisory: do NOT update to Fall Creators Update if you plan to use JAWS 2018 with Edge due to performance problems #ADVISORY #JAWS #WinTenDev

 

Hi everyone,

 

The below advisory is rated “critical” as it will affect ALL JAWS 2018 users who plans to use Microsoft Edge in Fall Creators Update. Thus, I recommend folks to forward this to other forums, mailing lists and what not, as well as raise a red flag with MS and VFO:

 

CRITICAL ADVISORY: major performance issues found when using JAWS 2018 with Edge under Fall creators Update builds, with one report stating JAWS and/or Edge crashes:

 

JAWS 2018 adds support for Microsoft Edge, the browser that ships as part of Windows 10. Support for Microsoft Edge, especially the new EdgeHTML rendering engine, is crucial when it comes to supporting certain universal apps, as they will use the rendering engine used by Edge to display web content. However, some users have reported performance problems when trying to use JAWS 2018 with Edge under Fall Creators Update preview builds, ranging from delay in feedback to at least one report of JAWS and/or Edge crashing, with performance issues confirmed in subsequent testing. Although these are possible due to beta status of JAWS 2018, part of this is due to changes to Edge code introduced in several Windows Insider Preview builds for the upcoming feature update to Windows 10.

 

Reason for rating this advisory “critical”:

 

  • Windows 10 is a service, therefore feature updates are sent to users and organizations on a semi-annual basis. The latest stable build (Version 1703) will be replaced by upcoming Fall Creators Update (Version 1709) in a few weeks, and soon or later, most users will be asked to update to the new version. Although enterprises can delay the upgrade for a time, they will be asked to upgrade to a future release at one point or another. For those running Windows 10 Home, you CANNOT defer updates.
  • The time to deploy Fall Creators Update can range from several weeks to several months. This means that, unless users tell Windows 10 to defer updates, they’ll be updated to the new release. If told to defer updates, Windows 10 will present the new release by early next year.
  • The delay period (between the day Fall Creators Update is released and January 2018) is a period of bug fixing, and if MS and/or VFO misses this, people will face issues with Edge in the upcoming release after upgrades, further compounding the problem. Thus, it is critical that a fix (both short-term and long-term) is in place before end of 2017 to allow people to test this for a few weeks before Fall Creators Update comes to everyone.

 

Recommended actions:

 

  1. Raise a red flag (feedback) with Microsoft and VFO to make sure this is addressed as soon as possible.
  2. Avoid upgrading to Fall Creators Update until issues with JAWS and Edge are ironed out to an extent that users can use Edge for basic tasks.
  3. Optionally, if you absolutely need to use Edge and/or universal apps that display web content via Edge’s rendering engine, use other screen readers known to support Edge (such as Narrator).
  4. If you need to use a web browser for any task, do NOT use Edge until major problems are resolved.

 

Thanks.

Cheers,

Joseph


Jeff Kenyon <jkenyon7@...>
 

I know that when 2018 comes Edge is supposed to work with it, provided that you don't have this update?  As far as how to use Edge keyboard command wise I take it it is the same as it is in I.E.?  

Sent from my iPhone

On Sep 1, 2017, at 2:35 AM, g melconian <gmelconian619@...> wrote:

Thanks for letting us know. I actually don’t use ms edge, my default two browsers that work the best and have been using them from windos 7 days ar chrome and firefox . those two have never let me down with any screenreader from supernova, to window eyes to NVDA to jaws .  these ar the three major screenreaders that I have used in 25 years. 

 

From: win10@win10.groups.io [mailto:win10@win10.groups.io] On Behalf Of Joseph Lee
Sent: Thursday, August 31, 2017 10:18 PM
To: win10@win10.groups.io
Subject: [win10] Critical advisory: do NOT update to Fall Creators Update if you plan to use JAWS 2018 with Edge due to performance problems #ADVISORY #JAWS #WinTenDev

 

Hi everyone,

 

The below advisory is rated “critical” as it will affect ALL JAWS 2018 users who plans to use Microsoft Edge in Fall Creators Update. Thus, I recommend folks to forward this to other forums, mailing lists and what not, as well as raise a red flag with MS and VFO:

 

CRITICAL ADVISORY: major performance issues found when using JAWS 2018 with Edge under Fall creators Update builds, with one report stating JAWS and/or Edge crashes:

 

JAWS 2018 adds support for Microsoft Edge, the browser that ships as part of Windows 10. Support for Microsoft Edge, especially the new EdgeHTML rendering engine, is crucial when it comes to supporting certain universal apps, as they will use the rendering engine used by Edge to display web content. However, some users have reported performance problems when trying to use JAWS 2018 with Edge under Fall Creators Update preview builds, ranging from delay in feedback to at least one report of JAWS and/or Edge crashing, with performance issues confirmed in subsequent testing. Although these are possible due to beta status of JAWS 2018, part of this is due to changes to Edge code introduced in several Windows Insider Preview builds for the upcoming feature update to Windows 10.

 

Reason for rating this advisory “critical”:

 

  • Windows 10 is a service, therefore feature updates are sent to users and organizations on a semi-annual basis. The latest stable build (Version 1703) will be replaced by upcoming Fall Creators Update (Version 1709) in a few weeks, and soon or later, most users will be asked to update to the new version. Although enterprises can delay the upgrade for a time, they will be asked to upgrade to a future release at one point or another. For those running Windows 10 Home, you CANNOT defer updates.
  • The time to deploy Fall Creators Update can range from several weeks to several months. This means that, unless users tell Windows 10 to defer updates, they’ll be updated to the new release. If told to defer updates, Windows 10 will present the new release by early next year.
  • The delay period (between the day Fall Creators Update is released and January 2018) is a period of bug fixing, and if MS and/or VFO misses this, people will face issues with Edge in the upcoming release after upgrades, further compounding the problem. Thus, it is critical that a fix (both short-term and long-term) is in place before end of 2017 to allow people to test this for a few weeks before Fall Creators Update comes to everyone.

 

Recommended actions:

 

  1. Raise a red flag (feedback) with Microsoft and VFO to make sure this is addressed as soon as possible.
  2. Avoid upgrading to Fall Creators Update until issues with JAWS and Edge are ironed out to an extent that users can use Edge for basic tasks.
  3. Optionally, if you absolutely need to use Edge and/or universal apps that display web content via Edge’s rendering engine, use other screen readers known to support Edge (such as Narrator).
  4. If you need to use a web browser for any task, do NOT use Edge until major problems are resolved.

 

Thanks.

Cheers,

Joseph


 

Hi,

As long as you stay on Creators Update (Version 1703), JAWS 2018 and Edge will work well. Note that this could change later.

As for commands, most are same as IE but some are not. See a tutorial by David Moore and posts from others regarding this.

Cheers,

Joseph

 

From: win10@win10.groups.io [mailto:win10@win10.groups.io] On Behalf Of Jeff Kenyon
Sent: Thursday, August 31, 2017 11:41 PM
To: win10@win10.groups.io
Subject: Re: [win10] Critical advisory: do NOT update to Fall Creators Update if you plan to use JAWS 2018 with Edge due to performance problems #ADVISORY #JAWS #WinTenDev

 

I know that when 2018 comes Edge is supposed to work with it, provided that you don't have this update?  As far as how to use Edge keyboard command wise I take it it is the same as it is in I.E.?  

Sent from my iPhone


On Sep 1, 2017, at 2:35 AM, g melconian <gmelconian619@...> wrote:

Thanks for letting us know. I actually don’t use ms edge, my default two browsers that work the best and have been using them from windos 7 days ar chrome and firefox . those two have never let me down with any screenreader from supernova, to window eyes to NVDA to jaws .  these ar the three major screenreaders that I have used in 25 years. 

 

From: win10@win10.groups.io [mailto:win10@win10.groups.io] On Behalf Of Joseph Lee
Sent: Thursday, August 31, 2017 10:18 PM
To: win10@win10.groups.io
Subject: [win10] Critical advisory: do NOT update to Fall Creators Update if you plan to use JAWS 2018 with Edge due to performance problems #ADVISORY #JAWS #WinTenDev

 

Hi everyone,

 

The below advisory is rated “critical” as it will affect ALL JAWS 2018 users who plans to use Microsoft Edge in Fall Creators Update. Thus, I recommend folks to forward this to other forums, mailing lists and what not, as well as raise a red flag with MS and VFO:

 

CRITICAL ADVISORY: major performance issues found when using JAWS 2018 with Edge under Fall creators Update builds, with one report stating JAWS and/or Edge crashes:

 

JAWS 2018 adds support for Microsoft Edge, the browser that ships as part of Windows 10. Support for Microsoft Edge, especially the new EdgeHTML rendering engine, is crucial when it comes to supporting certain universal apps, as they will use the rendering engine used by Edge to display web content. However, some users have reported performance problems when trying to use JAWS 2018 with Edge under Fall Creators Update preview builds, ranging from delay in feedback to at least one report of JAWS and/or Edge crashing, with performance issues confirmed in subsequent testing. Although these are possible due to beta status of JAWS 2018, part of this is due to changes to Edge code introduced in several Windows Insider Preview builds for the upcoming feature update to Windows 10.

 

Reason for rating this advisory “critical”:

 

  • Windows 10 is a service, therefore feature updates are sent to users and organizations on a semi-annual basis. The latest stable build (Version 1703) will be replaced by upcoming Fall Creators Update (Version 1709) in a few weeks, and soon or later, most users will be asked to update to the new version. Although enterprises can delay the upgrade for a time, they will be asked to upgrade to a future release at one point or another. For those running Windows 10 Home, you CANNOT defer updates.
  • The time to deploy Fall Creators Update can range from several weeks to several months. This means that, unless users tell Windows 10 to defer updates, they’ll be updated to the new release. If told to defer updates, Windows 10 will present the new release by early next year.
  • The delay period (between the day Fall Creators Update is released and January 2018) is a period of bug fixing, and if MS and/or VFO misses this, people will face issues with Edge in the upcoming release after upgrades, further compounding the problem. Thus, it is critical that a fix (both short-term and long-term) is in place before end of 2017 to allow people to test this for a few weeks before Fall Creators Update comes to everyone.

 

Recommended actions:

 

  1. Raise a red flag (feedback) with Microsoft and VFO to make sure this is addressed as soon as possible.
  2. Avoid upgrading to Fall Creators Update until issues with JAWS and Edge are ironed out to an extent that users can use Edge for basic tasks.
  3. Optionally, if you absolutely need to use Edge and/or universal apps that display web content via Edge’s rendering engine, use other screen readers known to support Edge (such as Narrator).
  4. If you need to use a web browser for any task, do NOT use Edge until major problems are resolved.

 

Thanks.

Cheers,

Joseph


Pradip Chandra Sikdar
 

It is already crashing in windows 10 creator update. JAWS 2018 is crashing 90% of time when using with edge.

On 9/1/2017 10:48 AM, Joseph Lee wrote:

Hi everyone,

 

The below advisory is rated “critical” as it will affect ALL JAWS 2018 users who plans to use Microsoft Edge in Fall Creators Update. Thus, I recommend folks to forward this to other forums, mailing lists and what not, as well as raise a red flag with MS and VFO:

 

CRITICAL ADVISORY: major performance issues found when using JAWS 2018 with Edge under Fall creators Update builds, with one report stating JAWS and/or Edge crashes:

 

JAWS 2018 adds support for Microsoft Edge, the browser that ships as part of Windows 10. Support for Microsoft Edge, especially the new EdgeHTML rendering engine, is crucial when it comes to supporting certain universal apps, as they will use the rendering engine used by Edge to display web content. However, some users have reported performance problems when trying to use JAWS 2018 with Edge under Fall Creators Update preview builds, ranging from delay in feedback to at least one report of JAWS and/or Edge crashing, with performance issues confirmed in subsequent testing. Although these are possible due to beta status of JAWS 2018, part of this is due to changes to Edge code introduced in several Windows Insider Preview builds for the upcoming feature update to Windows 10.

 

Reason for rating this advisory “critical”:

 

  • Windows 10 is a service, therefore feature updates are sent to users and organizations on a semi-annual basis. The latest stable build (Version 1703) will be replaced by upcoming Fall Creators Update (Version 1709) in a few weeks, and soon or later, most users will be asked to update to the new version. Although enterprises can delay the upgrade for a time, they will be asked to upgrade to a future release at one point or another. For those running Windows 10 Home, you CANNOT defer updates.
  • The time to deploy Fall Creators Update can range from several weeks to several months. This means that, unless users tell Windows 10 to defer updates, they’ll be updated to the new release. If told to defer updates, Windows 10 will present the new release by early next year.
  • The delay period (between the day Fall Creators Update is released and January 2018) is a period of bug fixing, and if MS and/or VFO misses this, people will face issues with Edge in the upcoming release after upgrades, further compounding the problem. Thus, it is critical that a fix (both short-term and long-term) is in place before end of 2017 to allow people to test this for a few weeks before Fall Creators Update comes to everyone.

 

Recommended actions:

 

  1. Raise a red flag (feedback) with Microsoft and VFO to make sure this is addressed as soon as possible.
  2. Avoid upgrading to Fall Creators Update until issues with JAWS and Edge are ironed out to an extent that users can use Edge for basic tasks.
  3. Optionally, if you absolutely need to use Edge and/or universal apps that display web content via Edge’s rendering engine, use other screen readers known to support Edge (such as Narrator).
  4. If you need to use a web browser for any task, do NOT use Edge until major problems are resolved.

 

Thanks.

Cheers,

Joseph


--
Regards,
Pradip Chandra Sikdar
Director of Clavier Productions
Founder of Project Sonic Electronica
Keyboard Player, Composer & Sound Engineer of X-RaF
Catch me on Facebook
Follow me on Twitter
E-mail: pradeepsikdar@...
Skype: pradeep.sikdar
Mobile: +91-9883669711


Shannon
 

How do you  defer the updates? Just in case, I’d like to make that my choice to install it now or later.

 

If one does not choose to go to the MS appstore and use universal apps, and the user does not use Edge for a browser, is Jaws 2018 going to work with the Fall Creaters version?

 

Thanks

Shannon

From: win10@win10.groups.io [mailto:win10@win10.groups.io] On Behalf Of Joseph Lee
Sent: Friday, September 1, 2017 12:18 AM
To: win10@win10.groups.io
Subject: [win10] Critical advisory: do NOT update to Fall Creators Update if you plan to use JAWS 2018 with Edge due to performance problems #ADVISORY #JAWS #WinTenDev

 

Hi everyone,

 

The below advisory is rated “critical” as it will affect ALL JAWS 2018 users who plans to use Microsoft Edge in Fall Creators Update. Thus, I recommend folks to forward this to other forums, mailing lists and what not, as well as raise a red flag with MS and VFO:

 

CRITICAL ADVISORY: major performance issues found when using JAWS 2018 with Edge under Fall creators Update builds, with one report stating JAWS and/or Edge crashes:

 

JAWS 2018 adds support for Microsoft Edge, the browser that ships as part of Windows 10. Support for Microsoft Edge, especially the new EdgeHTML rendering engine, is crucial when it comes to supporting certain universal apps, as they will use the rendering engine used by Edge to display web content. However, some users have reported performance problems when trying to use JAWS 2018 with Edge under Fall Creators Update preview builds, ranging from delay in feedback to at least one report of JAWS and/or Edge crashing, with performance issues confirmed in subsequent testing. Although these are possible due to beta status of JAWS 2018, part of this is due to changes to Edge code introduced in several Windows Insider Preview builds for the upcoming feature update to Windows 10.

 

Reason for rating this advisory “critical”:

 

  • Windows 10 is a service, therefore feature updates are sent to users and organizations on a semi-annual basis. The latest stable build (Version 1703) will be replaced by upcoming Fall Creators Update (Version 1709) in a few weeks, and soon or later, most users will be asked to update to the new version. Although enterprises can delay the upgrade for a time, they will be asked to upgrade to a future release at one point or another. For those running Windows 10 Home, you CANNOT defer updates.
  • The time to deploy Fall Creators Update can range from several weeks to several months. This means that, unless users tell Windows 10 to defer updates, they’ll be updated to the new release. If told to defer updates, Windows 10 will present the new release by early next year.
  • The delay period (between the day Fall Creators Update is released and January 2018) is a period of bug fixing, and if MS and/or VFO misses this, people will face issues with Edge in the upcoming release after upgrades, further compounding the problem. Thus, it is critical that a fix (both short-term and long-term) is in place before end of 2017 to allow people to test this for a few weeks before Fall Creators Update comes to everyone.

 

Recommended actions:

 

  1. Raise a red flag (feedback) with Microsoft and VFO to make sure this is addressed as soon as possible.
  2. Avoid upgrading to Fall Creators Update until issues with JAWS and Edge are ironed out to an extent that users can use Edge for basic tasks.
  3. Optionally, if you absolutely need to use Edge and/or universal apps that display web content via Edge’s rendering engine, use other screen readers known to support Edge (such as Narrator).
  4. If you need to use a web browser for any task, do NOT use Edge until major problems are resolved.

 

Thanks.

Cheers,

Joseph


 

On Fri, Sep 1, 2017 at 05:13 am, Shannon wrote:
How do you  defer the updates?
If you have Windows 10 Pro I believe that the Defer option is either under the Advanced Options on the Windows Update pane or else one level below that using Choose how updates are delivered.

It's been a couple of weeks since I was last dealing with Win10 Pro but I am certain that it is under the Advanced Options of the Windows Update pane of Update & Security settings somewhere.

Not that I would not use the defer option if possible, but I have absolutely no expectation that the roll out of Version 1709 is going to be much different than the earlier roll outs.  That means that it could be months after release until any given Windows 10 Home user gets the update, though it is, of course, a roll of the dice.  Were I a Windows 10 Home user this would push me to obtain an external backup drive and be taking system image backups on a far more regular basis than I might so if Version 1709 does install earlier than wanted one could restore back to 1703 using that system image.
 
--
Brian  Windows 10 Home, 64-Bit, Version 1703, Build 15063  (dot level on request - it changes too often to keep in signature)

Like all weak men he laid an exaggerated stress on not changing one's mind.
   ~ Somerset Maugham

 


 

Hi,

As for the other question about using Edge: no, not entirely. You will eventually come across Edge at one point or another, especially through Start menu searches.

Cheers,

Joseph

 

From: win10@win10.groups.io [mailto:win10@win10.groups.io] On Behalf Of Brian Vogel
Sent: Friday, September 1, 2017 9:14 AM
To: win10@win10.groups.io
Subject: Re: [win10] Critical advisory: do NOT update to Fall Creators Update if you plan to use JAWS 2018 with Edge due to performance problems #ADVISORY #JAWS #WinTenDev

 

On Fri, Sep 1, 2017 at 05:13 am, Shannon wrote:

How do you  defer the updates?

If you have Windows 10 Pro I believe that the Defer option is either under the Advanced Options on the Windows Update pane or else one level below that using Choose how updates are delivered.

It's been a couple of weeks since I was last dealing with Win10 Pro but I am certain that it is under the Advanced Options of the Windows Update pane of Update & Security settings somewhere.

Not that I would not use the defer option if possible, but I have absolutely no expectation that the roll out of Version 1709 is going to be much different than the earlier roll outs.  That means that it could be months after release until any given Windows 10 Home user gets the update, though it is, of course, a roll of the dice.  Were I a Windows 10 Home user this would push me to obtain an external backup drive and be taking system image backups on a far more regular basis than I might so if Version 1709 does install earlier than wanted one could restore back to 1703 using that system image.
 
--
Brian  Windows 10 Home, 64-Bit, Version 1703, Build 15063  (dot level on request - it changes too often to keep in signature)

Like all weak men he laid an exaggerated stress on not changing one's mind.
   ~ Somerset Maugham

 


Randy Barnett <randy@...>
 

As Joseph keeps saying MS is useing the Edge rendering engine for UWP apps and more and more of the OS. So you have probley used it even if you werent aware you were.
So without Edge support you will eventually get to a point that windows and UWP apps will no longer be Fully accessible with Jaws...

On 8/31/2017 11:35 PM, g melconian wrote:

Thanks for letting us know. I actually don’t use ms edge, my default two browsers that work the best and have been using them from windos 7 days ar chrome and firefox . those two have never let me down with any screenreader from supernova, to window eyes to NVDA to jaws .  these ar the three major screenreaders that I have used in 25 years. 

 

From: win10@win10.groups.io [mailto:win10@win10.groups.io] On Behalf Of Joseph Lee
Sent: Thursday, August 31, 2017 10:18 PM
To: win10@win10.groups.io
Subject: [win10] Critical advisory: do NOT update to Fall Creators Update if you plan to use JAWS 2018 with Edge due to performance problems #ADVISORY #JAWS #WinTenDev

 

Hi everyone,

 

The below advisory is rated “critical” as it will affect ALL JAWS 2018 users who plans to use Microsoft Edge in Fall Creators Update. Thus, I recommend folks to forward this to other forums, mailing lists and what not, as well as raise a red flag with MS and VFO:

 

CRITICAL ADVISORY: major performance issues found when using JAWS 2018 with Edge under Fall creators Update builds, with one report stating JAWS and/or Edge crashes:

 

JAWS 2018 adds support for Microsoft Edge, the browser that ships as part of Windows 10. Support for Microsoft Edge, especially the new EdgeHTML rendering engine, is crucial when it comes to supporting certain universal apps, as they will use the rendering engine used by Edge to display web content. However, some users have reported performance problems when trying to use JAWS 2018 with Edge under Fall Creators Update preview builds, ranging from delay in feedback to at least one report of JAWS and/or Edge crashing, with performance issues confirmed in subsequent testing. Although these are possible due to beta status of JAWS 2018, part of this is due to changes to Edge code introduced in several Windows Insider Preview builds for the upcoming feature update to Windows 10.

 

Reason for rating this advisory “critical”:

 

  • Windows 10 is a service, therefore feature updates are sent to users and organizations on a semi-annual basis. The latest stable build (Version 1703) will be replaced by upcoming Fall Creators Update (Version 1709) in a few weeks, and soon or later, most users will be asked to update to the new version. Although enterprises can delay the upgrade for a time, they will be asked to upgrade to a future release at one point or another. For those running Windows 10 Home, you CANNOT defer updates.
  • The time to deploy Fall Creators Update can range from several weeks to several months. This means that, unless users tell Windows 10 to defer updates, they’ll be updated to the new release. If told to defer updates, Windows 10 will present the new release by early next year.
  • The delay period (between the day Fall Creators Update is released and January 2018) is a period of bug fixing, and if MS and/or VFO misses this, people will face issues with Edge in the upcoming release after upgrades, further compounding the problem. Thus, it is critical that a fix (both short-term and long-term) is in place before end of 2017 to allow people to test this for a few weeks before Fall Creators Update comes to everyone.

 

Recommended actions:

 

  1. Raise a red flag (feedback) with Microsoft and VFO to make sure this is addressed as soon as possible.
  2. Avoid upgrading to Fall Creators Update until issues with JAWS and Edge are ironed out to an extent that users can use Edge for basic tasks.
  3. Optionally, if you absolutely need to use Edge and/or universal apps that display web content via Edge’s rendering engine, use other screen readers known to support Edge (such as Narrator).
  4. If you need to use a web browser for any task, do NOT use Edge until major problems are resolved.

 

Thanks.

Cheers,

Joseph



 

On Fri, Sep 1, 2017 at 01:04 pm, Randy Barnett wrote:
As Joseph keeps saying MS is useing the Edge rendering engine for UWP apps and more and more of the OS. So you have probley used it even if you werent aware you were.
So without Edge support you will eventually get to a point that windows and UWP apps will no longer be Fully accessible with Jaws...
Which is why VFO needs to get off its proverbial duff.  In the eight years I've now been working very actively with JAWS it is astounding just how far behind the current curve of Windows development JAWS has very often been.   This is not generally the fault of Microsoft, though there have been a couple of times where they've thrown complete curve balls and deserved the blame.

Windows 10 has been here now and using the evolving Edge rendering engine since July 2015.  Over two years should have been more than enough time for a commercial software house to play catch-up.  Other non-commercial ones certainly have.
 
--
Brian  Windows 10 Home, 64-Bit, Version 1703, Build 15063  (dot level on request - it changes too often to keep in signature)

Like all weak men he laid an exaggerated stress on not changing one's mind.
   ~ Somerset Maugham

 


Randy Barnett <randy@...>
 

Yes, I totally agree.

On 9/1/2017 1:40 PM, Brian Vogel wrote:
On Fri, Sep 1, 2017 at 01:04 pm, Randy Barnett wrote:
As Joseph keeps saying MS is useing the Edge rendering engine for UWP apps and more and more of the OS. So you have probley used it even if you werent aware you were.
So without Edge support you will eventually get to a point that windows and UWP apps will no longer be Fully accessible with Jaws...
Which is why VFO needs to get off its proverbial duff.  In the eight years I've now been working very actively with JAWS it is astounding just how far behind the current curve of Windows development JAWS has very often been.   This is not generally the fault of Microsoft, though there have been a couple of times where they've thrown complete curve balls and deserved the blame.

Windows 10 has been here now and using the evolving Edge rendering engine since July 2015.  Over two years should have been more than enough time for a commercial software house to play catch-up.  Other non-commercial ones certainly have.
 
--
Brian  Windows 10 Home, 64-Bit, Version 1703, Build 15063  (dot level on request - it changes too often to keep in signature)

Like all weak men he laid an exaggerated stress on not changing one's mind.
   ~ Somerset Maugham