Error when attempting to run Windows setup from Win8.1PE SE and Win10PE SE
#1
Posted 27 January 2016 - 06:57 PM
#2
Posted 27 January 2016 - 07:59 PM
You can run WinNTSetup from almost any PE and install from XP up to Win10: http://www.msfn.org/...inntsetup-v386/
You need to download it and run it at least once in your PC in order to let it download required files, then just add it to your USB or CD/DVD (it is portable) and run the version according your PE architecture (x86 or x64). Of curse you need also your install ISO that can be on same or other USB or DVD.
About a PE builder, for building a PE bootable in Bios, UEFI, X86 or x64, I suggest MistyPE good to build any PE: http://reboot.pro/fi...le/357-mistype/
alacran
#3
Posted 27 January 2016 - 08:11 PM
#4
Posted 27 January 2016 - 09:23 PM
Only thing WinNTSetup does not do for you is Partitioning and formating the HDD but you can do it using diskpart (command line) or BootIce (Portable, GUI) first, then use WinNTSetup to deploy the selected image in the *.wim or *.esd (when not encripted) to the disired location and apply the boot files (for Bios, UEFI or both) to the desired location too.
It is also able to build a VHD and deploy the system to it, add extra drivers, use unattended.xml file and OEM folder and make a Wimboot (only Win8.1u1) or Compact install of Windows 7, 8.x or 10, (with more compact options than Windows install), in few words it works better and with more options than usuall installs.
About MistyPE, my mistake, it is not made for blind people sorry, but you may ask the developer for a pluginn for the NVDA screen reader, he is a very nice and frienly guy, this is MistyPE thread: http://reboot.pro/topic/18917-mistype/
Best Regards
alacran
#5
Posted 27 January 2016 - 09:32 PM
#6
Posted 28 January 2016 - 03:53 AM
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 as Win8.1PE SE. 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?
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users