MistyPE

Yes, exactly, please fix all the download links.  MistyPE isn't the only one having an issue.

http://mistype.reboo....2014.07.06.zip  does not work.  Thanks.

We're working to restore the broken links, sorry about this.

Use the Wayback Machine until links are fixed:
 

https://web.archive....ocs/readme.html

 

Wonko

@sebus and Mr.JoeM
Thanks for reporting the issue. My email notifications (for replies to this and other topics) are not currently working and I hadn't been aware the site(s) were down until today.

 

We're working to restore the broken links, sorry about this.

Thanks Nuno.

Regards,

Misty

P.s. A belated Happy New Year to everyone!!!!

@ Misty

 

Well I perfectly know this tool is not intended to be used with Win10 IP but I didn't resist the temptation to try it.

 

So I made a build in Win7x86 using Win10x86 EN-US Pro Insider Preview last update as source and it worked flawlessly.

 

x64 version didn't so well, not all apps. where included in the build, problems with WOW64 is my guess, not a big deal as x86 build can be booted in UEFI as far as it is supported in UEFI Bios.

 

I just wanted to report my findings and say Hello to you my friend.

 

Best Regards

 

NOTE: You can make an x64 build but using only 64 bits programs in it, and without any 32 bits programs as they don't run in this 10x64PE yet.

Edited by alacran, 10 July 2015 - 07:55 AM.

Hi

I am trying to make a bootable WinPE usb stick with Win 8.1 WinPE environment. I downloaded MistyPE as it has nice GUI skin to make it easy and painless process.

I have Windows ADK for 8.1 installed on my Windows 8.1 64-bit OS. I chose the following directory as the source for this.

C:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\Media

 

When I tried to create the iso, it is failing with the message that it can't find etfsboot.com is missing.

 

I have pasted the last lines from the log section below.

 

What am I doing wrong?

 

I appreciate your help.

 

Thanks

Joe

 

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

      Run - Processing section: [SOURCE.CHECK] From file: [%BaseDir%\Projects\MistyPE\Core\Core.script]
              Checking Source for required files...
              SetVar - Sucessfuly changed the value of [%install.wim%] to: [0]
              IF - File does not exist: [C:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\Media\sources\install.wim] evaluated string: [If,ExistFile,"%SourceDir%\sources\install.wim",Set,%install.wim%,"%SourceDir%\sources\install.wim",GLOBAL]
              SetVar - Sucessfuly changed the value of [%boot.wim%] to: [0]
              IF - File does not exist: [C:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\Media\sources\boot.wim] evaluated string: [If,ExistFile,"%SourceDir%\sources\boot.wim",Set,%boot.wim%,"%SourceDir%\sources\boot.wim",GLOBAL]
              IF - [0] is equal to: [0] evaluated string: [If,%boot.wim%,Equal,0,Set,%ERROR%,1]
              SetVar - Sucessfuly changed the value of [%ERROR%] to: [1]
              IF - [0] is equal to: [0] evaluated string: [If,%install.wim%,Equal,0,Set,%ERROR%,1]
              SetVar - Sucessfuly changed the value of [%ERROR%] to: [1]
              IF - File exists: [C:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\Media\bootmgr] evaluated string: [If,Not,ExistFile,"%SourceDir%\bootmgr",Set,%ERROR%,1]
              IF - File exists: [C:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\Media\boot\BCD] evaluated string: [If,Not,ExistFile,"%SourceDir%\boot\BCD",Set,%ERROR%,1]
              IF - File does not exist: [C:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\Media\boot\etfsboot.com] evaluated string: [If,Not,ExistFile,"%SourceDir%\boot\etfsboot.com",Set,%ERROR%,1]
              SetVar - Sucessfuly changed the value of [%ERROR%] to: [1]
                    IF - [1] is equal to: [1] evaluated string: [If,%ERROR%,Equal,1,Begin]
                    Message: A required source file is missing! Are source files present in the following location? - "C:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\Media" refer to log file
                    IF - [0] is equal to: [0] evaluated string: [If,%boot.wim%,Equal,0,Echo,\sources\boot.wim is missing from source,WARN]
                   \sources\boot.wim is missing from source
                    IF - [0] is equal to: [0] evaluated string: [If,%install.wim%,Equal,0,Echo,\sources\install.wim is missing from source,WARN]
                   \sources\install.wim is missing from source
                    IF - File exists: [C:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\Media\bootmgr] evaluated string: [If,Not,ExistFile,"%SourceDir%\bootmgr",Echo,\bootmgr is missing from source,WARN]
                    IF - File exists: [C:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\Media\boot\BCD] evaluated string: [If,Not,ExistFile,"%SourceDir%\boot\BCD",Echo,\boot\BCD is missing from source,WARN]
                    IF - File does not exist: [C:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\Media\boot\etfsboot.com] evaluated string: [If,Not,ExistFile,"%SourceDir%\boot\etfsboot.com",Echo,\etfsboot.com is missing from source,WARN]
                   \etfsboot.com is missing from source
                   Required file is missing - see warnings above
             Run - Processed section [SOURCE.CHECK] in file: [%BaseDir%\Projects\MistyPE\Core\Core.script]
       Run - Processed section [USECACHE.NO] in file: [%BaseDir%\Projects\MistyPE\Core\Core.script]
        Script time: 9 seconds and 433 milliseconds

        Finished processing script: Core Files

 

 

@ videoguy

 

The source is usually Windows Installation Media - either a CD/DVD, a mounted disk image or the files copied to an accessible folder.

 

Quote from first post:

"There is also an option to collect the necessary files from the host operating system used to run winbuilder - Windows 7/8/8.1 supported. Credit to Erwan.l whose QuickPE project pointed the way to the required commands. This option requires that WinRE be copied from the C: drive - if WinRE was not copied to the C: drive during the Windows install then it won't be possible to use this method."

 

You don't need Windows ADK to make a build, and it is not a suitable source for this project, all you need is Windows Installation Media.

 

Just in case you don't have 8.1 Installation Media, you can download it from Microsoft (select ISO in your download):

http://windows.micro...t-refresh-media

 

Quick Start Guide

 http://mistype.reboo...files/quick.htm

 

It is part of Full documentation from first post: http://mistype.reboo...ocs/readme.html

 

Also included in your download.

Thanks Alacran,

Couldn't have put it better myself
 

...So I made a build in Win7x86 using Win10x86 EN-US Pro Insider Preview last update as source and it worked flawlessly.

x64 version didn't so well, not all apps. where included in the build, problems with WOW64 is my guess, not a big deal as x86 build can be booted in UEFI as far as it is supported in UEFI Bios...

Sorry for the late response. MistyPE will only apply WOW64 settings if one of the following known sources are used -

• 6.1.7600
• 6.1.7601
• 6.2.9200
• 6.3.9600

These builds all have different WOW64 dependancies. If a source over than one of the above is used then no attempt is made to use the WOW64 settings.

I used a hack to apply the WOW64 settings used in WinPE 5.* (build 6.3.9600) in the current Windows 10 download - it didn't work.

Based on the information in the Win10PESE Preview topic at http://theoven.org/it is not currently possible to add WOW64 to Windows 10 based WinPE's - this may change.

If the correct settings and file dependencies are traced then it might be possible in the future - in which case I'll do my best to port it to MistyPE.

Regards,

Misty

Hello misty

It is good to hear from you.

After my post (#155) I found Win10PESE Preview and read it, I am aware they haven't found a way to add WOW64 to PE yet.

Win10 is not released yet and it is too soon to start doing any thing, I just wanted to let you and our forum members know Win10x86 is a suitable source for building a PE. Using Win10x64 source you can get an Iso too, but not adding any x86 program, x64 programs run fine.

Thanks for your comments, I know you will do your best effort to port WOW64 when there is found a way to do it. You can not avoid the challenge, it is in your blood.

Best Regards my friend.

NOTE 1: Two days ago I tried Win10PESE to make a build from IP 10162 x86, It went to the end and I got an ISO, but it didn't boot, need to check if there is a new version of the project and try again.

 

NOTE 2: In fact there is a new version of Win10PESE Preview uploaded today.

 

NOTE 3: Tried last version of Win10PESE Preview, Iso didn't boot, I have Win10 es-MX x86 & x64 versions, perhaps using en-US is the way.

Edited by alacran, 10 July 2015 - 08:15 AM.

@ misty

 

Is it possible you can make an Script to incorporate wofadk.sys and the required registry settings to your project?

It will be greatly appreciated.

 

Best Regards

...Is it possible you can make an Script to incorporate wofadk.sys and the required registry settings to your project?...

It is! And yes I will. Should hopefully have time to do this tomorrow. As I do not have a direct download link to the relevant files it will need to be a simple script with user defined paths to the 32/64-bit WoFadk.sys driver.

If you (or anyone else) knows the link to the relevant .cab file from the Windows 10 ADK (the one(s) containing wofadk.sys) then let me know and I should be able to script automatically downloading it.

Regards,

Misty

If you're looking for a good, free open source file manager that can be integrated, check out Far Manager. My favorite feature is the ability to use plain Lua scripts as plugins. Before finding FM I hadnt yet used any FMs that I deemed really worthy of my time, except maybe Total Commander. I was blown away the first time I used it. Many of you may have heard of it, maybe not, it looks really old school and I like it (think Linux's Midnight Commander, except for Windows). There is also an optional console/CLI addon called ConEmu that is designed to be a supplement to FM. 32 and 64 bit versions are available for both, as well as portable editions. You may want to get permission first if you're considering, but I dont see any reason they would object as long as you obey the relatively loose license. And this would not dramatically increase the size of the PE at all.

 

Edit: There is an x64 version of Opera (v12.xx) but it's at least several yrs old, based on Opera's old Presto engine rather than the newer Webkit engine that Chrome, Safari, etc (it's been this way since version 17/18, I think, and they're now on 30-something). The devs have given no indication of an x64 build for their Webkit-based Opera as of yet. See:

 

 

http://forums.opera....-to-download/p1

 

and

 

ftp://ftp.opera.com/pub/opera/win/1214/en/

@alacran
Wofadk script is attached - please test and feedback. It's not particularly sophisticated, but it will hopefully do the job. Use caution if adding to a source that already contains the WoF.sys driver as I have no idea whether this will cause any issues.

@AnonVendetta
Thanks for the info. I'll check this out when I get some free time.

Regards,

Misty

 WoFADK.script   3.34KB   907 downloads

It is! And yes I will. Should hopefully have time to do this tomorrow. As I do not have a direct download link to the relevant files it will need to be a simple script with user defined paths to the 32/64-bit WoFadk.sys driver.

If you (or anyone else) knows the link to the relevant .cab file from the Windows 10 ADK (the one(s) containing wofadk.sys) then let me know and I should be able to script automatically downloading it.

Regards,

Misty

 

I always use Get WAIK Tool (made by JFX) to download a required Waik/ADK/Dism package http://www.msfn.org/...hl=getwaiktools

 

Or if you use WinNTSetup it downloads only all required files (including WofADK.sys) in Tools folder (x86 & x64) first time you run it.

 

I tested your Script building new Iso's using as source Win7-SP-1 x86 & x64, host OS Win7-SP-1 x86:

 

Both Iso's booted fine from a folder on HDD located in 3trd. primary partition, using grubfordos as boot loader to run the Iso's mapped directly from HDD, not using map -- mem.

 

Then from loaded PEx86 Iso, I ran WinNTSetup 3.85b2 (located in "user added files" on Iso), making a Win7x64 Compact XPRESS8K install to VHD, all working flawlessly.

 

I'm going to make a build using 8.1u1x64 as source (that already contains the WoF.sys driver) to test if there is some issue and report back.

 

EDIT: After building the Iso using 8.1u1x64 as source, and booting it as explained before, from loaded PEx64 Iso, I ran WinNTSetup 3.85b2 (located in "user added files" on Iso), making a Win10x64 Compact XPRESS8K install to VHD, all working without any issue, so I didn't find any conflict between WoF.sys and WofADK.sys drivers.

 

 

Best Regards

 

alacran.

Edited by alacran, 24 August 2015 - 07:06 PM.

Hi alacran

Thanks for testing and feeding back

Nice to know there doesn't appear to be any conflict between wof.sys/wofadk.sys

I'll add the wofadk script to MistyPE when I get around to updating the project. To be honest there's not much else to add - over than updating wimlib.

I'll add the wofadk script to MistyPE when I get around to updating the project. To be honest there's not much else to add - over than updating wimlib.

Thanks for the MystyPe project  !

It's my first PE build and it was fun to do, moreover it will help me to ressurect my "teclast x98 II" since the eMMc drive seem corrupt and I need to access it to repair it ;-)

I was using Hiren's CD/USB before but this tablet is UEFI and UEFI 32 bit, so since 1 week I digged through the web to understand how UEFI/GPT work ...  I found your own questions in a thread about UEFI boot that confirmed a lot of things I've read since many things I've read were conflictual.

Now I had my USB drive with some tools that boot fine with my X98 and moreover I will be able to customize the MystyPE to fit my need and build something better than Hiren's for my needs


One quick question: I'd like to know if it's possible to have more than 1 PE project on a USB Drive (compatible with strict UEFI) ?

Since from my understanding UEFI is only able to book from GPT/Fat32 but is able to use NTFS with some "magic" like this one https://github.com/pbatard/uefi-ntfs.

Have a nice day & Thanks again for this marvelous project !

@ misty

 

yamingw found a solution for Wow64 in Win10PE: http://bbs.wuyou.net...read&tid=371490

 

Attached new plugin developed by JFX for Win10PESE based on yamingw info, maybe you can adapt it, or take ideas for your project, when building 10x64 PE.
 

Best Regards

 

alacran

@mikoul
Apologies for the delay in responding to your message (see below). Many thanks for the positive feedback.

One quick question: I'd like to know if it's possible to have more than 1 PE project on a USB Drive (compatible with strict UEFI) ?

Yes it is - easiest method is to add multiple .wim files (with unique names) with corresponding entries in the BCD store. Some notes can be found here - the Examples - Part 3 page is particularly relevant.

@alacran
This is great news. Many thanks for letting me know. I have limited time at the moment due to an organisational review going on at work (and subsequent job hunting as I'm not happy with the changes being proposed). I will look into porting this to MistyPE/Mini-WinFE as soon as I have the free time to do so. No guarantee that it's possible, however I'm up for the challenge.

Cheers

Misty

Would this be ever upgraded to use Win 10 as source?

 

Thanks

 

sebus

@ misty:
 
Hello my friend, in order to make a little history:
 

@ misty
 
yamingw found a solution for Wow64 in Win10PE: http://bbs.wuyou.net...read&tid=371490
 
Attached new plugin developed by JFX for Win10PESE based on yamingw info, maybe you can adapt it, or take ideas for your project, when building 10x64 PE.
 
Best Regards
 
alacran

 
 

@alacran
This is great news. Many thanks for letting me know. I have limited time at the moment due to an organisational review going on at work (and subsequent job hunting as I'm not happy with the changes being proposed). I will look into porting this to MistyPE/Mini-WinFE as soon as I have the free time to do so. No guarantee that it's possible, however I'm up for the challenge.

Cheers

Misty

 
I saw in the forum a thread about adapting the "Java Winbuilder" to make it capable to buid Win8.x and win10 PE's & make a GUI for it, I really don't see a real need for that and anyway it is going to take long time, your project can do it very fast and always well done, only thing pending is sysWOW64 on 10x64PE's.
 
Today on a Win7x64 Host machine I made new PE's from 8.1U1x86, 8.1U1x64, 10x86 and 10x64 (using as source Win10_1607_Spanish_x32.iso & Win10_1607_Spanish_x64.iso respectively for the last two) all working flawlessly, the only thing is I can only use x64 programs in 10x64PE as there is no sysWOW64 in it.
I use "Pstart" or "PSMenu" (calling one or the other from the PE using batch files located in user.aded.files) to find and run these program launchers and from them run all my portables (located on internal HDD or USB drive), but this two program launchers do not work on a x64PE without sysWOW64, so this is frustrating because there is no x64 alternative for this program launchers.
 
This are my little batch files:

 

I know you are very busy with your new project the Tiny PXE server guide, but please my friend make a little time for this friendly request, anyway it is the last thing required to crown mistyPE & winFE project.

 

Best Regards

 

alacran

@alacran
Message received and understood.

I am working through the most recent 5-wow64 script from the oven .org site and trying to decipher it. With added complications trying to understand my own scripts in order to attempt the additions! It's been so ling since I coded the project I am having to try and remind myself what goes where and why!!

Will no doubt take a week or two before I'm in a position to get a test ready. Will keep you informed. And sorry for the delay - I'm very easily distracted!

Kind regards,

Misty



P.s. Thank you for your kind words about my little project.

Windows 10 based WinPE SysWOW64 support appears to require yamingw's setWOW64.exe - haven't yet been able to find out much about this file and have no idea whether it is redistributable.

Misty

I think this can help, this is yamingw's original post: http://bbs.wuyou.net...ead&tid=371490 (use Google translate)

 

Updates can generate dll lists that support partial virtualization programs, and some virtualization programs require X: \ Windows \ SysWOW64 \ config \ systemprofile.
I tested several virtualization programs, in the normal system can not run the basic, it seems that the virtualization process itself is still limited.
The source code is basically copy the ReactOS smss Lane in the creation of KnwonDlls part, and the normal Win10 generated list is slightly different, but does not affect the use.
Run setwow64 can. Ntoskrnl in the initialization phase 1 detection If it is running in memory in WinPE, do not create KnownDlls32 kernel object. This object content is populated by SMSS. System initialization 32-bit application can not find the path in this object that is being given.
Source is for reference only.

 

After reading it, I see he is using ReactOS code (open source), so it is distributable, I attached both *.7zip files in a single one, to let you take a closer look to them, see my attachment.

 

Best regards

 

alacran

 

 

@alacran
Don't get too excited - some initial good news for Windows 10 (build/version 10.0.10240) - I have managed to get some 32-bit programs running in 64-bit WinPE with SysWOW64 support.

This is some way from full intergration with MistyPE - but it's positive news.

I don't really understand much about the process, however there appear to be two seperate methods that can be used

• loadwow64.exe - running from HKLM\System\ControlSet001\Control\Session Manager - BootExecute key with data loadWoW64.exe
• setwow64.exe - The 5-Wow64 runs the executable from winpeshl.ini. It's also possible to run it at boot before launching any 32-bit apps.

If anyone knows a bit more about these programs and in particular any advantages/disadvantages of each method then please do let me know.

No luck so far with other Windows 10 builds, however it's early days.

Regards,

Misty

P.s. Thanks for the kick up the arse gentle reminder to work on this.

@ misty

Thanks for the good news, about your question I found some info that may help.

This may be usefull: http://reboot.pro/to...app-support-v2/

About: Thanks for the kick up the arse gentle reminder to work on this, no problem, you are wellcome, it was my pleasure.

alacran

P.s. See attached info