Date   

Re: Zoom with nvda

Sarah k Alawami
 

Hello. I have a podcast highlighting the good, the bad and the inaccesibal on zoom rom a mac side but you can perhaps take some of it and convert it into pc stuff. Go to my podcast site in the sig and search for the keyword, zoom.

Sarah Alawami, owner of TFFP. . For more info go to our website. This is also our libsyn page as well.
For stuff we sell, mac training materials and  tutorials go here.
and for hosting options go here
to subscribe to the feed click here

Our telegram channel is also a good place for an announce only in regard to podcasts, contests, etc.

Our discord is where you will know when we go live on youtube, twitch and mixer. Thanks Restream staff.

Finally, to become a patron and help support the podcast go here

On 1 Oct 2019, at 13:53, hurrikennyandopo ... wrote:

Hi


I went to there you tube channel from off the website of theres and I could only find it for the zoom magnifier not the zoom conferencing software. Maybe I missed it.


I think I will also sign up later on today or tomorrow for a free account then do it from the side of it been hosted the basics and lay out etc when I got it worked out.


Also will check out training material from the zoom website etc which I have been doing.


I will do it more on the audio side not all the other stuff I think I will point to videos for that.


Would I have any takers who would like to read the tutorial after it has been typed up especially those who have done it from both sides? to make sure it is right before posting to the website of mine for others to use or follow.

If so I can contact you off list for that or the other way around.


Gene nz


Gene nz




On 2/10/2019 7:02 AM, Samuel Villa wrote:

Hey.

This may be off topic, but on the Freedom Scientific YouTube channel, there is an instructional video on how to use Zoom with JAWS.

Let me know if this was helpful.

--
Check out my website for NVDA tutorials and other blindness related materials at http://www.accessibilitycentral.net

To find out which library networks in New Zealand have a copy of the NVDA screen reader on them and there library locations please go to http://www.accessibilitycentral.net/nz%20libraries%20with%20nvda.html
To find a NVDA certified expert near you, please visit the following link https://certification.nvaccess.org/. The certification page contains the official list of NVDA certified individuals from around the world, who have sat and successfully passed the NVDA expert exam.


Re: Zoom with nvda

hurrikennyandopo ...
 

Hi


I went to there you tube channel from off the website of theres and I could only find it for the zoom magnifier not the zoom conferencing software. Maybe I missed it.


I think I will also sign up later on today or tomorrow for a free account then do it from the side of it been hosted the basics and lay out etc when I got it worked out.


Also will check out training material from the zoom website etc which I have been doing.


I will do it more on the audio side not all the other stuff I think I will point to videos for that.


Would I have any takers who would like to read the tutorial after it has been typed up especially those who have done it from both sides? to make sure it is right before posting to the website of mine for others to use or follow.

If so I can contact you off list for that or the other way around.


Gene nz


Gene nz




On 2/10/2019 7:02 AM, Samuel Villa wrote:

Hey.

This may be off topic, but on the Freedom Scientific YouTube channel, there is an instructional video on how to use Zoom with JAWS.

Let me know if this was helpful.

--
Check out my website for NVDA tutorials and other blindness related materials at http://www.accessibilitycentral.net

To find out which library networks in New Zealand have a copy of the NVDA screen reader on them and there library locations please go to http://www.accessibilitycentral.net/nz%20libraries%20with%20nvda.html
To find a NVDA certified expert near you, please visit the following link https://certification.nvaccess.org/. The certification page contains the official list of NVDA certified individuals from around the world, who have sat and successfully passed the NVDA expert exam.


NVDA and hackerrank?

Sally Kiebdaj
 

Hello all,

I am not a programmer so in a poor position to judge this for myself but am curious about the compatibility of NVDA and tests put out by hackerrank.com

A job to which I  am applying has a test for non-programmers to see how quickly we pick up on rules of a fake computer language. I am trying to determine if I can actually take this test independently and am not getting a response from hackerrank customer service yet. 

Does anyone have experience with them and NVDA?

Warmly,
Sally 


Re: Virtual Viewer

 

Hi,

If I’m getting this thread correctly, the answer is yes and no: yes, it exists as a form of an add-on.
Cheers,

joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of tim
Sent: Tuesday, October 1, 2019 1:06 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Virtual Viewer

 

Ok, I can live with it as a toggled feature. However, running all the time makes the screen reader load up your graphic buffer to cause crashing, and that was a hidden crash bug they would not fix.

On Oct 1, 2019, at 3:58 PM, Sarah k Alawami <marrie12@...> wrote:

 

Actually I'd love a virtual viewer like thing at least make it a toggl.

Sarah Alawami, owner of TFFP. . For more info go to our website. This is also our libsyn page as well.
For stuff we sell, mac training materials and  tutorials go here.
and for hosting options go here
to subscribe to the feed click here

Our telegram channel is also a good place for an announce only in regard to podcasts, contests, etc.

Our discord is where you will know when we go live on youtube, twitch and mixer. Thanks Restream staff.

Finally, to become a patron and help support the podcast go here

On 1 Oct 2019, at 12:54, tim wrote:

I haven’t found one and hope it never comes. That was part of the problem with Jaws crashing.

On Oct 1, 2019, at 2:11 PM, kelby carlson kelbycarlson@... wrote:

Is there anything like the virtual viewer in JAWS that NVDA has? It
would be amazing to be able to easily bring up a list of footnotes in
Word.

-- 
Kelby Carlson

 

 


Re: Virtual Viewer

tim
 

Ok, I can live with it as a toggled feature. However, running all the time makes the screen reader load up your graphic buffer to cause crashing, and that was a hidden crash bug they would not fix.

On Oct 1, 2019, at 3:58 PM, Sarah k Alawami <marrie12@...> wrote:

Actually I'd love a virtual viewer like thing at least make it a toggl.

Sarah Alawami, owner of TFFP. . For more info go to our website. This is also our libsyn page as well.
For stuff we sell, mac training materials and  tutorials go here.
and for hosting options go here
to subscribe to the feed click here

Our telegram channel is also a good place for an announce only in regard to podcasts, contests, etc.

Our discord is where you will know when we go live on youtube, twitch and mixer. Thanks Restream staff.

Finally, to become a patron and help support the podcast go here

On 1 Oct 2019, at 12:54, tim wrote:

I haven’t found one and hope it never comes. That was part of the problem with Jaws crashing.

On Oct 1, 2019, at 2:11 PM, kelby carlson kelbycarlson@... wrote:

Is there anything like the virtual viewer in JAWS that NVDA has? It
would be amazing to be able to easily bring up a list of footnotes in
Word.

-- 
Kelby Carlson




Re: Virtual Viewer

Sarah k Alawami
 

Actually I'd love a virtual viewer like thing at least make it a toggl.

Sarah Alawami, owner of TFFP. . For more info go to our website. This is also our libsyn page as well.
For stuff we sell, mac training materials and  tutorials go here.
and for hosting options go here
to subscribe to the feed click here

Our telegram channel is also a good place for an announce only in regard to podcasts, contests, etc.

Our discord is where you will know when we go live on youtube, twitch and mixer. Thanks Restream staff.

Finally, to become a patron and help support the podcast go here

On 1 Oct 2019, at 12:54, tim wrote:

I haven’t found one and hope it never comes. That was part of the problem with Jaws crashing.

On Oct 1, 2019, at 2:11 PM, kelby carlson kelbycarlson@... wrote:

Is there anything like the virtual viewer in JAWS that NVDA has? It
would be amazing to be able to easily bring up a list of footnotes in
Word.

--
Kelby Carlson


Re: Virtual Viewer

tim
 

I haven’t found one and hope it never comes. That was part of the problem with Jaws crashing.

On Oct 1, 2019, at 2:11 PM, kelby carlson <kelbycarlson@gmail.com> wrote:

Is there anything like the virtual viewer in JAWS that NVDA has? It
would be amazing to be able to easily bring up a list of footnotes in
Word.

--
Kelby Carlson



Re: tracking down NVDA triggers

tim
 

I have to go with John on this one.
If you have any third party virus or malware hunters. Then you can have screen notifications pop up and go . With those any screen reader acts the same way.
So I would look for notifications and maintenance software that came with the laptop. All have some type for updating drivers.

On Oct 1, 2019, at 1:33 PM, Joseph Lee <joseph.lee22590@...> wrote:

Hi,
I’m thinking not – as in debugging steps didn’t take place from what I can tell.
To Giles, can you try running NVDA in debug mode, and as soon as you hear NVDA repeat an info you don’t want to hear, send a log (press NVDA+F1 to open the log and copoy and paste everything as an email) to me and Quentin so we can diagnose what’s up? I’m requesting logs in private because it may contain sensitive information. Be sure to CC info@... with the precise description of the problem when sending the log to us.
Cheers,
Joseph
 
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Brian Vogel
Sent: Tuesday, October 1, 2019 10:29 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] tracking down NVDA triggers
 
On Tue, Oct 1, 2019 at 01:23 PM, Joseph Lee wrote:
Only after trying to figure out what’s up with NVDA should we look into SFC.
Joseph, given what was offered in the original message, I am willing to presume that NVDA debugging, including a possible uninstall/reinstall, has already taken place.  Perhaps it hasn't, but then I'd hope that might be tried as a step.

I stand by my advice, which does not include doing a completely clean reinstall unless all other methods fail.  Doing an SFC and DISM as "good housekeeping" hurts absolutely nothing, and can also serve as a diagnostic step.

There are multiple ways to come at any problem, and I am not about to allow my advice to be grossly mischaracterized.   It's a fairly simple matter to do some significant "Windows 10 Health Checks" to see if something could be wrong.  It has been my experience that when uncharacteristic behaviors such as those described are occurring it's generally not the application program that's at fault.
 
-- 
Brian - Windows 10 Pro, 64-Bit, Version 1903, Build 18362  
The color of truth is grey.
           ~ André Gide

 

 



Re: Announcement: changes coming to NVDA 2019.3 compatibility announcements page based on latest community feedback

Afik Souffir <afik.souffir@...>
 

hello Joseph and all!
Joseph, thank you for this info.


-------------------------------------------

cordialement,
Afik Souffir
Israel


2019-10-01 21:05 UTC+03:00, Joseph Lee <joseph.lee22590@gmail.com>:

Hi NVDA users,



As you may know, there exists a website on community add-ons page that
lists
add-ons considered compatible with upcoming NVDA 2019.3/Python 3:

https://addons.nvda-project.org/addons/nvdapy3.en.html



Over the last few days, NVDA developers and add-on authors had a discussion
regarding what is considered "compatible". Currently, add-ons with source
code compatibility are considered compatible with NVDA 2019.3/Python 3, and
some authors expressed concerns about compatibility range statements
provided by add-ons via their manifests. Specifically, while some add-ons
were source code compatible, they haven't been updated in a long time and
thus do not either come with compatibility statements or assume old NVDA
releases. The overall conclusion from our discussion is that, while source
code compatibility is a good indicator, this information isn't friendly to
users, and users would look at compatibility range specified by add-ons as
an indicator of whether add-ons are compatible with future NVDA releases.



Based on this, the following change will be made to the above website:



Any add-on that is deemed source code compatible yet do not show manifest
updates will be marked as "incompatible" for purposes of record keeping. In
other words, although an add-on may pass checks based on source code, if it
cannot be installed on latest NVDA stable releases (or for that matter, if
it fails to install on NVDA 2019.3 in any form) due to outdated
compatibility range statements in the manifest, it will be marked as
"incompatible". Exceptions include add-ons marked as "planned" or "work in
progress" - authors are planning to get add-ons ready for NVDA 2019.3 or
work is under way to support NVDA 2019.3 technologies, respectively.



This change will take effect on October 2, 2019. As a result, the following
will happen (some will have to wait for a while to be implemented):



1. The community will be asked to contact authors of add-ons that are
failing compatibility check (source code is ready but cannot be installed
on
NVDA 2019.3). I advise waiting until 2019.3 beta 1 comes out before
initiating this.
2. In the future, when add-ons are going through review process for
registration on community add-ons website, manifest information
(specifically, compatibility statements) will be checked. Details will be
announced when it is time to implement this change (hopefully before end of
this year).
3. For every add-on listed on community add-ons website, compatibility
range statement will be encouraged. This will become mandatory after
details
of compatibility check review (see above) is finalized, hopefully by
January
1, 2020.



Thank you.

Cheers,

Joseph





Re: So what will happen to my favorite add-ons in the future: September 2019 update

kelby carlson
 

Will the Eloquence synthesizer ad-ons be compatible with NVDA 2019.3?

On 9/18/19, Joseph Lee <joseph.lee22590@gmail.com> wrote:
Hi NVDA users,



At least I'm back in action (slightly reduced workload, but working on NVDA
coding here and there) and some news to share with you regarding what will
happen to your favorite add-ons in the future.



First, a bit of a background for people who don't know what I'm talking
about:



This past summer (winter for some), I and other NVDA developers worked on
preparing NVDA for the future. Specifically, with the impending end of life
of Python 2 (the original language NVDA is coded in), the developers felt
it
is time to shift gears and move onto a more modern way of providing equal
access to technology: Python 3. In addition to some exciting enhancements,
it brought many changes under the hood that will make NVDA a viable option
for all of you in the long term, including some performance enhancements,
smooth internationalization, and much more.



One of the questions we received in recent weeks has been about your
favorite add-ons and the upcoming NVDA 2019.3, the first version to be
powered by Python 3. Although there were initial bumps, I'm delighted to
announce that majority of add-ons that you know and love will work with
NVDA
2019.3. Take a look at the following items:



* 63 percent of add-ons hosted on community add-ons website
(addons.nvda-project.org) are compatible with NVDA 2019.3.
* Several authors have indicated plans to introduce Python 3 support
to their add-ons soon, and others are working hard on porting their add-ons
to make them future-proof.
* Notable add-on developers, including makers of Vocalizer series and
DictationBridge, have committed to releasing Python 3 compatible versions
of
their add-ons in the future. In case of Vocalizer series, an alpha version
of old Vocalizer Direct (2.x) is being tested, and a public beta of Python
3
compatible DictationBridge is scheduled to be released shortly after NVDA
2019.3 beta 1 is released.



The add-ons community expects more add-ons to join the ranks of
future-proof
add-ons as NVDA 2019.3 release approaches. Until then.

Cheers,

Joseph




--
Kelby Carlson


Virtual Viewer

kelby carlson
 

Is there anything like the virtual viewer in JAWS that NVDA has? It
would be amazing to be able to easily bring up a list of footnotes in
Word.

--
Kelby Carlson


Announcement: changes coming to NVDA 2019.3 compatibility announcements page based on latest community feedback

 

Hi NVDA users,

 

As you may know, there exists a website on community add-ons page that lists add-ons considered compatible with upcoming NVDA 2019.3/Python 3:

https://addons.nvda-project.org/addons/nvdapy3.en.html

 

Over the last few days, NVDA developers and add-on authors had a discussion regarding what is considered “compatible”. Currently, add-ons with source code compatibility are considered compatible with NVDA 2019.3/Python 3, and some authors expressed concerns about compatibility range statements provided by add-ons via their manifests. Specifically, while some add-ons were source code compatible, they haven’t been updated in a long time and thus do not either come with compatibility statements or assume old NVDA releases. The overall conclusion from our discussion is that, while source code compatibility is a good indicator, this information isn’t friendly to users, and users would look at compatibility range specified by add-ons as an indicator of whether add-ons are compatible with future NVDA releases.

 

Based on this, the following change will be made to the above website:

 

Any add-on that is deemed source code compatible yet do not show manifest updates will be marked as “incompatible” for purposes of record keeping. In other words, although an add-on may pass checks based on source code, if it cannot be installed on latest NVDA stable releases (or for that matter, if it fails to install on NVDA 2019.3 in any form) due to outdated compatibility range statements in the manifest, it will be marked as “incompatible”. Exceptions include add-ons marked as “planned” or “work in progress” – authors are planning to get add-ons ready for NVDA 2019.3 or work is under way to support NVDA 2019.3 technologies, respectively.

 

This change will take effect on October 2, 2019. As a result, the following will happen (some will have to wait for a while to be implemented):

 

  1. The community will be asked to contact authors of add-ons that are failing compatibility check (source code is ready but cannot be installed on NVDA 2019.3). I advise waiting until 2019.3 beta 1 comes out before initiating this.
  2. In the future, when add-ons are going through review process for registration on community add-ons website, manifest information (specifically, compatibility statements) will be checked. Details will be announced when it is time to implement this change (hopefully before end of this year).
  3. For every add-on listed on community add-ons website, compatibility range statement will be encouraged. This will become mandatory after details of compatibility check review (see above) is finalized, hopefully by January 1, 2020.

 

Thank you.

Cheers,

Joseph


Re: Zoom with nvda

Samuel Villa <Saleena81@...>
 

Hey.

This may be off topic, but on the Freedom Scientific YouTube channel, there is an instructional video on how to use Zoom with JAWS.

Let me know if this was helpful.


Re: tracking down NVDA triggers

 

Hi,

I’m thinking not – as in debugging steps didn’t take place from what I can tell.

To Giles, can you try running NVDA in debug mode, and as soon as you hear NVDA repeat an info you don’t want to hear, send a log (press NVDA+F1 to open the log and copoy and paste everything as an email) to me and Quentin so we can diagnose what’s up? I’m requesting logs in private because it may contain sensitive information. Be sure to CC info@... with the precise description of the problem when sending the log to us.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Brian Vogel
Sent: Tuesday, October 1, 2019 10:29 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] tracking down NVDA triggers

 

On Tue, Oct 1, 2019 at 01:23 PM, Joseph Lee wrote:

Only after trying to figure out what’s up with NVDA should we look into SFC.

Joseph, given what was offered in the original message, I am willing to presume that NVDA debugging, including a possible uninstall/reinstall, has already taken place.  Perhaps it hasn't, but then I'd hope that might be tried as a step.

I stand by my advice, which does not include doing a completely clean reinstall unless all other methods fail.  Doing an SFC and DISM as "good housekeeping" hurts absolutely nothing, and can also serve as a diagnostic step.

There are multiple ways to come at any problem, and I am not about to allow my advice to be grossly mischaracterized.   It's a fairly simple matter to do some significant "Windows 10 Health Checks" to see if something could be wrong.  It has been my experience that when uncharacteristic behaviors such as those described are occurring it's generally not the application program that's at fault.
 
--

Brian - Windows 10 Pro, 64-Bit, Version 1903, Build 18362  

The color of truth is grey.

           ~ André Gide

 

 


Re: tracking down NVDA triggers

 

On Tue, Oct 1, 2019 at 01:23 PM, Joseph Lee wrote:
Only after trying to figure out what’s up with NVDA should we look into SFC.
Joseph, given what was offered in the original message, I am willing to presume that NVDA debugging, including a possible uninstall/reinstall, has already taken place.  Perhaps it hasn't, but then I'd hope that might be tried as a step.

I stand by my advice, which does not include doing a completely clean reinstall unless all other methods fail.  Doing an SFC and DISM as "good housekeeping" hurts absolutely nothing, and can also serve as a diagnostic step.

There are multiple ways to come at any problem, and I am not about to allow my advice to be grossly mischaracterized.   It's a fairly simple matter to do some significant "Windows 10 Health Checks" to see if something could be wrong.  It has been my experience that when uncharacteristic behaviors such as those described are occurring it's generally not the application program that's at fault.
 
--

Brian - Windows 10 Pro, 64-Bit, Version 1903, Build 18362  

The color of truth is grey.

           ~ André Gide

 

 


Re: tracking down NVDA triggers

 

Hi Brian,

Actually, for this one, I think John’s advice is a bit better – I myself have experienced it on my ThinkPad, and it appears to be an event-related problem. To truly find out what’s up, you need to run NVDA in debug mode (restart NVDA with debug logging enabled) and capture the log output (it’ll print all sorts of things). Only after trying to figure out what’s up with NVDA should we look into SFC.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Brian Vogel
Sent: Tuesday, October 1, 2019 10:16 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] tracking down NVDA triggers

 

On Tue, Oct 1, 2019 at 12:33 PM, John Isige wrote:

I'm sorry, but WTF? Some dude's getting a program's title read to him
periodically, and the conclusion is, yeah dude you might want to more or
less reinstall Windows.

No, it isn't.   I cannot help if you cannot be bothered to read, and comprehend, the advice given.  You might want to think about that before spouting off garbage like this again.
 
--

Brian - Windows 10 Pro, 64-Bit, Version 1903, Build 18362  

The color of truth is grey.

           ~ André Gide

 

 


Re: tracking down NVDA triggers

 

On Tue, Oct 1, 2019 at 12:33 PM, John Isige wrote:
I'm sorry, but WTF? Some dude's getting a program's title read to him
periodically, and the conclusion is, yeah dude you might want to more or
less reinstall Windows.
No, it isn't.   I cannot help if you cannot be bothered to read, and comprehend, the advice given.  You might want to think about that before spouting off garbage like this again.
 
--

Brian - Windows 10 Pro, 64-Bit, Version 1903, Build 18362  

The color of truth is grey.

           ~ André Gide

 

 


Add-on Updater 19.10.1 and Windows 10 App Essentials 19.10, an important notice on Version 1809 support from WinTenApps #addonrelease

 

Hi all,

 

Add-on Updater 19.10.1 and Windows 10 App Essentials 19.10 are now available. Add-on Updater can now check for updated versions of Beep Keyboard and Synth Ring Settings Selector from David CM (newly declared stable), and Windows 10 App Essentials adds support for various 20H1 features, most notably the new Cortana user interface and modern Chinese, Japanese, and Korean IME.

 

IMPORTANT: if you are using Windows 10 App Essentials on Windows 10 October 2018 Update (Version 1809), please keep the following in mind:

 

Support for Version 1809 from Windows 10 App Essentials is coming to a close soon. The sunset date is set for January 2020. People using development releases will see this come sooner – as soon as NVDA 2019.3 stable version is released, development channel will drop support for Version 1809. Don’t worry, it won’t affect stable channel users for a while longer.

 

Cheers,

Joseph


Re: In-Process 1st October

molly the blind tech lover
 

Hi.

This is a wonderful in process

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Quentin Christensen
Sent: Tuesday, October 1, 2019 1:20 AM
To: nvda@nvda.groups.io
Subject: [nvda] In-Process 1st October

 

Hi everyone,

This week in In-process, a great milestone for NVDA, a new beta, a shout-out to our friends at Intopia and heaps more!

https://www.nvaccess.org/post/in-process-1st-october/

 

--

Quentin Christensen
Training and Support Manager

 


Re: tracking down NVDA triggers

John Isige
 

I'm sorry, but WTF? Some dude's getting a program's title read to him
periodically, and the conclusion is, yeah dude you might want to more or
less reinstall Windows. That's like, option number one? I also notice
there's no explanation whatsoever as to how we're supposedly concluding
this is a Windows issue worthy of some sort of reinstallation. I'm
sorry, this just seems irresponsible, even with things like the Windows
10 reset where you can reinstall but preserve files and data.


I don't know the answer, about how to chase it down from the logs, but
it seems to me a much more readily apparent answer is that another
program is running in the background and stealing focus, or making NVDA
think focus has changed. I don't see how it automatically means that
Windows itself has been corrupted in any way whatsoever.


Suppose for instance, there's a download manager running in the
background, and it flashes its window or such to get your attention. It
seems entirely possible to me that such a benign event could be
temporarily stealing NVDA's focus. I've had this occur before, often it
will repeatedly read the first item on the desktop, both with NVDA and
under NVDA remote. So far as I know, both of my machines are good in
terms of Windows, I'm not noticing any other issues whatsoever. It
happens so infrequently that I've never worried about it.

On 10/1/2019 9:17, Brian Vogel wrote:
Giles,

            There is likely some corruption in your Windows 10
installation itself that needs to be remedied.  The probability of
this being an NVDA-based issue is very small indeed, particularly if
you've already tried uninstalling NVDA and reinstalling it.


My standard advice, in virtually all cases, (and presuming any
potential infection has already been addressed, first) is trying the
following, in the order specified.  If the issue is fixed by option
one then there's no need to go further.  Stop whenever your issue is
fixed:

1. */Using SFC (System File Checker) and DISM (Deployment Imaging
Servicing and Management) to Repair Windows 8 & 10/*
<https://drive.google.com/uc?export=download&id=0B98uELZbPFnOc2l4M0Y1V3pkcGM>


2. */Doing a Windows 10 Repair Install or Feature Update Using the
Windows 10 ISO file/*
<https://drive.google.com/uc?export=download&id=1RZiHlLVtXewYBgoSvJNm9_08hj1tALPK>


3. Doing a completely clean reinstall (options *a* & *b* are
downloadable PDF files):

           a) */Completely Clean Win10 (Re)install Using MCT to
Download Win10 ISO File/*
<https://drive.google.com/uc?export=download&id=1hHoEnSz2YWHyztOO3ZjXtV2y4gQASoMR>

           b) */Completely Clean Win10 (Re)install Using MCT to Create
a Bootable USB Drive/*
<https://drive.google.com/uc?export=download&id=1cvsT64KAwz5ZJmiPfBQlUDBOoskb9dDO>

           c) */How to do a CLEAN Installation of Windows 10/*
<https://forums.tomshardware.com/faq/how-to-do-a-clean-installation-of-windows-10.3170366/>(/Tom’s
Hardware Forums/, with screen shots)

I */_never_/* choose the “/thermonuclear option/,” the completely
clean reinstall, until it's clear that this is the only viable option.
I hate having to go through all the work of reconfiguring a machine
from scratch if that can reasonably and safely be avoided.

__


--

Brian *-*Windows 10 Pro, 64-Bit, Version 1903, Build 18362

*The color of truth is grey.*

           ~ André Gide

19521 - 19540 of 85149