JFX

Tranngocyd, I'm not really sure I understand you. This version is not experimental, it just have a new and still not completed feature. Only reason for using it would be the new command line switch. Everyone else should wait for the next final version, which is coming soon.

Hi Joseph, There shouldn't be such a problem with The EFI loader on MBR disks. But actually very EFI seems to following it's own will. I don't want to add check boxes for everything, so for now I added just a new switch run it like this WinNTSetup_x86.exe NT6 -nombrefi and it will not create EFI on MBR disks https://onedrive.live.com/?cid=0053f5d45a736673&id=53F5D45A736673%21219&action=Share

Yes, sadly that's normal or "windows 8 normal". Makes sense, if you removed app packages or have them updated already. There's no need to update them at end of setup.

Hmm, only if the pc is online, you said. Don't tell me you mean the app updates on end of setup? If so you need to disable the update options:

Hope I got them all tweaks.zip

Hmm, wasn't the devcon sourcecode not available somewhere? So compiling it with another name should be enough to have a redistributable one. Also, I could properly add devcon download to GWT Done! Run GetWaikTools -devcon

Yes, it's as simple as it looks on the picture. Bootice will subtract 100MB for the EFI and 32MB for MSE partition.

Yeah, next version will accept the new names. Thanks reminding about the name changes. WinNTSetup v3.3 - fixed sfc disable patch did not delete *.cat in dllcache folder - removed dll dependencies: imagehlp, netapi32, psapi - removed all deprecated win32 API's - fixed xp user creation, when setup an x64 OS from WinNTSetup_x86.exe - accepts bootice???.exe names in Tools folder and appdir - fixed swm files where detected by extention instead of attributes - fixed updating bootsector could use wrong tool

Bootsect.dat is not used anymore, it was a useless trouble maker. Setupldr is now renamed to ntldr, the text mode phase cleans this up. EDIT: Version 3.2.2 uploaded! this just a small bugfix version, the last subst fix could effect iso/vhd mounting

My, my it's just gone from the zip file, not killed or made it impossible to use it anymore. Users can still download and put it in the tools folders themselves. But it saves me same minutes uploading a new version. Why don't you have reported that bootsect.exe is not working for you, before? There is always a WinNTSetup.log file in the new Windows folder that contains bootsect's stdout. If you discover this problem again please upload the log.

Well even bootice can do this:

A good partition program should help creating one. But you can also use classic diskpart tool. http://technet.microsoft.com/en-us/library/hh825686.aspx

xcv150, it's no real difference to normal BIOS. Just make sure you create a EFI system partition and select this one as boot drive.

Okay done, you now can run it like this: "WinNTSetup_x86.exe download". It will silently download the adk tools and close with exitcode 0 if successful. WinNTSetup v3.2.1 - reduced ADK download size by 600KB - new download command line option to download ADK silently - added links to about gui - removed bootice from tools

Ah, that evil first page, I always forgot there something. I'll add a download command line, with the next version

You can't change the Windows folder path since Vista. Doing it manually will only break your windows installation.

@jaclaz With an x86 recovery environment you can't do some things on an x64 windows - access all hardware due to lack of drivers available - servicing with dism - sfc checking/repairing - using offline system restore - remove a troublesome hotfix - reinstall windows without 3rd party apps

Ok, so this took a while but should adress all problems. WinNTSetup v3.2 - fixed problem with "subst" drives - fixed drive label still not displayed on some systems - new support for esd files - command line accept relative pathes - on windows 8.1 system32 wimgapi.dll will be preferred - admin check now token based - updated offreg library to latest version

Yes, it will be useful if one still burn a setup DVD, with it's limited space. I mostly use fast compression, only for winpe maximum compression seems useful. Don't forgot if you not run winntsetup on XP host, you can update wimgapi.dll in the tools folders. The 8.1 ADK api saves also a bit time while applying.

Seems Microsoft had the idea to call LZMS compressed wim files esd, too. So I will add support for esd files created by dism, but not the ones downloaded by ms store . @click-click Nothing changed, all *.reg files will be applied during setup. Temp files in the folder are just not delete, but will be in next version.

After reading a topic on MDL forum about esd creation, I think there is a misunderstanding about esd files. People started to call recovery compressed wim files now install.esd instead of install.wim. Well adding support for such files shouldn't be a problem. However this compression type is not thought as a replacement for maximum compression and will have much slower applying times.

@click-click Next version will accept relative paths to winntsetup.exe like version 2 did. @conty9 Sorry forgot language while moving software to a new PC, but re-uploaded now. Could reproduce your subst problem and it's really a bug. This will take some time to fix as I'm a bit busy these days and there is different behavior between NT5 and NT6 windows versions (as well as WinPE).

@tranngocyd Complete change log for 3.0 to 3.1 fixes and first page now

Oh, so you have not noticed that you can click on the OEM and Runafter labels to get file select dialogs, my bad for not mention that. Well honestly I have nothing to do with PESE progress anymore. ChrisR puts all his time in development. I'm just enjoy beta testing these great WinPE's.

@datanfsm Maybe there will be more improvements for XP installs, but not soon. Currently there is only 1 easter egg planed for NT5 installs, but maybe if there is more time avalible. Let's see. Anyway there are enough fixes since the 3.0 release, so here's a small update. Update WinNTSetup v3.1 - fixed splited wim (swm) files could not be applied - using vista style folder browse dialogs if available - new runafter program selection on Ready GUI - fixed existing cmdlines.txt became corrupted - minor bugfixes