Jump to content











Photo
* * * * - 2 votes

MistyPE

winpe10 winpe5 winpe4 winpe3 winpe2 winpe

  • Please log in to reply
377 replies to this topic

#376 XenonKilla

XenonKilla
  • Members
  • 3 posts
  •  
    United States

Posted A week ago

@XenonKilla

 

I haven't tested a MistyPE build from Win10 April 2018 update v1803.17134.  At the moment I'm not able to make a test build from the source you used. The more recent source I have used is Win10 Fall Creator Update 1709 from Dec. 2017, and it works flawlessly.

 

I suggest to make a test build using as source any one confirmed. And then if all your Applications are working fine we may say there is a problem using as source Win10 April 2018 update v1803.17134.

 

As you don't clarify if your Applications are working in previous sources (all applications included in project download do not require this fixes).  In case you have missing dependencies for your 32 bits portable aplications, you may edit syswow.USER.ADDED.txt when making a build from 64 bits Windows source, And/or dependencies.USER.ADDED.txt, when making a build from 32 bits Windows source, both files located on MistyPE\Projects\Tools\wimlib.file.lists\

 

alacran

 

Yes everything is working fine using Win10 v1709 files. I've been using WinPE & MistyPE since WAIK 2.0, now so this is nothing new to me. The issue is definitely something to do with the SysWOW64 script as none of the 32-bit apps are working when building with 64-bit arch.

 

I also did a file comparison between a MistyPE created v1709 boot.wim and a v1803 boot.wim, and there are definitely a lot of .dll's and SysWOW64 files missing.

 

It's fine, I'm not really looking for any help on getting it to work, using the v1709 build files works fine for me. Just wanted to give everyone a heads up. I'm sure Misty will get it updated eventually. :)


Edited by XenonKilla, A week ago.

  • alacran likes this

#377 alacran

alacran

    Silver Member

  • Advanced user
  • 611 posts
  •  
    Mexico

Posted A week ago

Yes everything is working fine using Win10 v1709 files. I've been using WinPE & MistyPE since WAIK 2.0, now so this is nothing new to me. The issue is definitely something to do with the SysWOW64 script as none of the 32-bit apps are working when building with 64-bit arch.

 

I also did a file comparison between a MistyPE created v1709 boot.wim and a v1803 boot.wim, and there are definitely a lot of .dll's and SysWOW64 files missing.

 

It's fine, I'm not really looking for any help on getting it to work, using the v1709 build files works fine for me. Just wanted to give everyone a heads up. I'm sure Misty will get it updated eventually. :)

 

Thanks for your quick answer, so according with your info we may say without any doubt Win10 April 2018 update v1803.17134 x64 is not a suitable source for making a MistyPE build wich include x86 applications.

 

Once again thanks, it was good you share this info with all of us, to help other people know about this issue.

 

EDIT: Just made a build, I can also confirm what our friend XenonKilla said: using Win10 v1803.17134 x64 as source, x86 programs do not run, (even those included in project).

 

alacran


  • XenonKilla likes this

#378 alacran

alacran

    Silver Member

  • Advanced user
  • 611 posts
  •  
    Mexico

Posted A week ago

I think it is good to make clear for new users it doesn't matter wich RTM version of Win10 (on x86 or x64 arch.) you use as source, you always get a MistePE 10 (x86 or x64) wich has same capabilities and programs as MistyPE project version has, so there is not any improvement or advantage using the very last RTM (or actual equivalent) as source for your build.

 

I assume our good friend Misty will make a new version/revision of MistyPE Project whenever he consider it is the right time.

 

alacran







Also tagged with one or more of these keywords: winpe10, winpe5, winpe4, winpe3, winpe2, winpe

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users