79 replies to this topic

[misty]

Shameless self promotion. MistyPE is capable of building a Window 10 based WinPE from source files (.iso media is recommended). Depending on the system setup it may also optionally build from a local installation - this option will only work if WinRE is located on the Operating System partition.

• Download portal - see here
• Support thread - see here

Misty

[Brito]

I really enjoy that option to build from the local media. Congratulations on the release!

[misty]

Thanks Nuno. Have you tried the project BTW?

[Tokener]

Dear Misty

This is really GREAT work.

Had to try it immediately.

It works

Host-PC is Win7x64 and MistyPE-Build x86 as well as -x64 bootet successfully.

Thanks a lot for sharing.

 

Sincerely T.

[sagonzal]

GREAT work. I will try it immediately. Thanks.

[红毛樱木]

Hi,Can Win10  15063 works?

[misty]

Hi,Can Win10  15063 works?

It should do. Not sure if all features will work as I haven't tested this build. I did a quick test with build 10.0.15042.0 a few weeks ago and it seemed to perform similarly to 10.0.14393.0 with SysWoW64 functioning.

Only way to know for sure is to test. Preferably using a mounted .iso as source.

Language support may or may not work depending on your source files. If you are using Chinese language builds as source then please report back to confirm if the project works - my own tests have been limited mainly to using en-US and en-GB sources.



Misty

[nguyentu]

Thank you, I think it's great. I'm using Vietnamese keyboard, I think this is the reason for the error in the build process. Right?

 

[misty]

@nguyentu
Your Vietnamese keyboard should not result in this error.

The script in your error message has been replaced in the latest beta. Which version of MistyPE are you using (in the format 2012-03-22 (year-month-day))?

I will do a full upload of the latest beta later today and will post back here when it's done.

Misty

[nguyentu]

I'm using MistyPE.2017.03.08.zip, I will wait to test the new version ...

[misty]

Please download the latest build from the download portal (see link in post #1).

Misty

[nguyentu]

Thanks, but I got new issue

 

[misty]

@nguyentu
Can you please PM me your log file and I'll take a look later.

Misty

[nguyentu]

Sent it, check your inbox. Thank you!

[misty]

Based on the log file, the error appears to be triggered by line 47 of \Projects\MistyPE\Core\syswow64.files.from.wim.script

The line reads -

If,Not,ExistRegSection,HKLM,_WinPE_SOFTWARE,RegHiveLoad,_WinPE_SOFTWARE,"%SysWow64_Registry%\software"

Do you have the necessary permissions to mount registry hives on your host OS?

Misty

[genetix]

Hmm, not sure should I say nice work or give this project a "why".

 

(Personal note: I just think it makes more sense to include all(scripting, powershell, WMI, etc) and code an personal app that can modify, create and dump at detected media from UFD or networked from iPXE or even better EFI based concept. Building such at the moment here with C#/C++ without any batch style scripting.)

[genetix]

Hi,Can Win10  15063 works?

 

I'd say no as 10.0.15063.x would need new PE tools or dump PE directly from official boot.wim which doesn't exist as far I've looked only WinRE is available from fast ring.

[nguyentu]

@Misty

 

Yes, I use the user created first when installing Windows 10. My computer has only one account.

[misty]

@nguyentu
The project seems to run fine until an attempt is made to mount a registry hive.

Some information from the winbuilder help file -

RegHiveLoad
Load an external registry hive onto your local registry system.

Syntax
RegHiveLoad,<SectionName>,<HiveFilename>

Remarks
This command is based on Windows 32bit API and works under any Windows platform - under Vista/Windows7 it is necessary to disable the UAC (User Account Control) or Run as Administrator.

Try temporarily disabling UAC.

Misty

[nguyentu]

UAC has disabled but has not made any changes.

[misty]

I can't replicate the problem at the moment. I'll give it some thought and will get back to you. Sorry.

[misty]

Hmm, not sure should I say nice work or give this project a "why".
 
(Personal note: I just think it makes more sense to include all(scripting, powershell, WMI, etc) and code an personal app that can modify, create and dump at detected media from UFD or networked from iPXE or even better EFI based concept. Building such at the moment here with C#/C++ without any batch style scripting.)

Adding powershell, WMI, etc, significantly increases build time and may not be required - I haven't required these Optional Components for any of the programmes that I regularly use in WinPE. This is a minimalist build and is designed to be fast (in terms of the build process).

Sadly, Coding in C#/C++ (or any programming language) is beyond my abilities.

Misty

[misty]

@nguyentu
WinBuilder has an option to continue despite errors - the project is set to use "Stop Build on Error".

I seriously doubt that the build will complete successfully if registry files cannot be mounted - which appears to be the problem.

It's worth seeing if you get any further by disabling this option though. Click on the Tools icon (top right near to the Play and Refresh buttons) and uncheck the "Stop Build on Error" option (bottom right of the tools screen).

I'm off out now, but will check back in later.

Misty

[genetix]

Adding powershell, WMI, etc, significantly increases build time and may not be required - I haven't required these Optional Components for any of the programmes that I regularly use in WinPE. This is a minimalist build and is designed to be fast (in terms of the build process).

Sadly, Coding in C#/C++ (or any programming language) is beyond my abilities.

Misty

 

Including those to your PE you could get quite a bit more out of it which is, all I am saying. It's a damn nice PE thanks for updates and hard work.

 

Minimal is also nice idea, but not including support for languages or shell tools is kinda shooting over it.

 

- 256MB(x86, current with official packages: 287,9MB)

- 512MB(x64, current with official packages: 380,6MB)

 

both of above including WMI, powershell, scripting, dism expansion plus unnessessary .NET 4.5.1 which makes them going over ideal.

[misty]

@genetix
Thanks for the feedback.

Windows 10.0.14393 (32-bit) based WinPE - building from an existing cache in MistyPE with following programs added -
* Q-Dir
* CloneDisk
* DMDE
* ImDisk
* WinHex
* Wprotect

boot.wim file size after optimisation, with all of the above programs and BlackBox Lean shell is 222 MiB

Build time = 48 seconds (including .iso file)

First build (when the Windows files were added to the cache) was longer - 1 minute from start of caching files to the build (with .iso) completing.

An existing 64-bit WinPE that I built earlier today, with SysWoW64 support and the programs listed above, had a boot.wim file size of 330 MiB. I didn't save the log file for this build and cannot recall how long it took. Due to SysWoW64 support I'd guess the build time was around 3-4 minutes.

I'm not disputing the usefulness of the Optional Components you listed - depending on what programs you actually want to run. I was able to get IEF (Internet Evidence Finder) partially working in WinPE a couple of years ago after adding the NetFx package.

BTW, MistyPE can be used to create a WinPE with all ADK Optional Components added - this takes significantly longer and is a bit more complex than just pressing the Play button. This will be covered in the documentation when I get around to updating it all.

Misty