Error when initiating Windows setup while NVDA screen reader is running

When I attempt to start Windows setup from within Win10PE SE, after choosing "Next" on the initial language selection screen, I receive the following error.

setup.exe - Application Error The exception unknown software exception (0xe0000100) occurred in the application at location 0x00007FFC215B1F08.

The problem occurs with both Windows 7 and Windows 10 setup.  I would appreciate assistance resolving this issue since one of the more useful purposes of a PE with a screen reader for the blind is being able to install Windows with speech.

Thanks and regards.

Thoughts?  Comments?  I suspect the problem is related to missing dependencies, but I have no idea which ones.  I am not sure that I know the WinBuilder scripting language well enough to import the necessary files, but I am willing to try if I at least have an idea where to begin.

With Win8.1PE SE, I receive a different error when running Windows setup.

Windows encountered an internal error while initializing COM.

About a year ago I remember we had this problem in Win7PE SE with 64 bit installation sources while the NVDA screen reader was running and it gave the same error.  I believe it may have been related to UI Automation.  The problem seems to have been resolved in Win7PE SE.  So the question is what do I need to change in
2-Config.script
to resolve this problem in Win8.1PE SE?

Works here with both x86 and x64.
You can try to find the dependencies with Sysinternals Process Monitor.

Do you mean in Win10PE SE or Win8.1PE SE?  If you mean Win8.1PE SE, I believe the error only occurs when the NVDA screen reader is running so if it is not running on your build, you may not experience this problem.  I am not even sure if UI Automation is the cause of the problem in Win10PE SE since the error is completely different.  I would really appreciate some input from the developers or someone who understands all of this better since I am mostly lost here.

Well, in your first post you talk about Win10PE SE,
so I tried Win10PE SE with Win10 1511 source using default setting, plus NVDA plugin.

If you can not solve your problem on your own, than at least provide enough details to reproduce it.

I have also discovered that this problem does not occur if you run setup from the
sources
subfolder while NVDA is not running.  This definitely seems to be related to the problem discovered in Win7PE SE about a year and a half ago.  There is even a note about this in
2-Config.script

// Text Input Processor Language Bar (Enable=1), Reset to 0: problem with NVDA (one example) on x64 build to install a Windows x64 (teststed with Win7x64), problem COM

However, the problem does not exist in Win7PE SE, but it does in Win8.1PE SE and Win10PE SE.  All three projects have the same comment in
2-Config.script

I provided all of the information I had at the time.  I did not initially realize that the problem might be related to NVDA as it was in Win7PE SE a year and a half ago since it was a completely different error.  I only realized after I tested on Win8PE SE and ran setup  from the
sources
subfolder in Win10PE SE.  At that point in both cases, I received the

Windows encountered an internal error while initializing COM.

error which is when I first realized that the problem might be related.

Disabling the
PowerShell
and
Logon as Admin
scripts seems to have mostly resolved this issue when using a 64 bit source.  I'm not sure what that's all about.  However, on 32 bit builds I still receive the

Windows encountered an internal error while initializing COM.

message while NVDA is running.

I saw your message zimmy and I tried with NVDA.
With Win10pese x64, I have the same results as JFX, no problem here to install windows 10 64-bits 

But with x86 to install win10 x86, I reproduce your problem with the same COM message. I do not know more
I can get around by closing NVDA on the Install screen, after the  language selection +next. Than, after 2, 3 seconds, we can restart NVDA with Win key to get the Menu, shortcuts.
Also, I know that you know, you have the great WinNTSetup, ready to use, with a cmd line shortcut, it should be quite easy to use for blind peoples.
Do you really need  a Windows 10 32 bits installation ? except some tablets, almost all PCs are 64-bits now.

#
In Nvda log, I have this, seems related with the COM error:

Code: [Select]

IO - speech.speak (00:56:14):
Speaking [LangChangeCommand ('fr_FR'), u'Fran\xe7ais']
DEBUGWARNING - RPC process 328 (setup.exe) (00:56:14):
Thread 2460, build\x86\remote\ia2Support.cpp, installIA2Support, 86:
Error registering class object, code -2147221008

Perhaps, you can send the log here  Win10PEx86_NVDA_Setup_Win10x86.zip (3.84 kB - downloaded 156 times.)
and send it to the English users' mailing List https://github.com/nvaccess/nvda-community/wiki/Connect

To join the users' list, send a blank email to: nvda-request@freelists.org with the word "subscribe" in the subject line.

they can probably help to understand the IA2 support error

#
There is a new Nvda version, 2015.4. I will update the plugin when I have some free time.
To take it, use "Custom version from this folder (with your settings)" button with Nvda portable install and your settings.

Hi Chris,

Thanks for the reply.  Sorry I did not see your message until now or I would have responded sooner.

Yes I was able to eliminate the issue with 64 bit sources as well by disabling the
PowerShell
and
Logon as Admin
scripts.  I don't quite understand why disabling those two scripts stopped the error, but it definitely did make a difference.  I was aware that closing NVDA before the error and then restarting it works since we had a similar problem with Win7PE SE a couple of years ago.  As you say, most machines in general are likely to be 64 bit capable.  It is just useful to have access to a 32 bit Windows 10 based PE for the sake of completeness.

I will see about passing the error in the log on to the NVDA developers.