Adding syswow64 to Win10PE

Trying to work back through this script: http://w8pese.spam.net/Projects/Win8PESE/Build/5-Wow64.script

So far I've added all the regkeys, copied the entire syswow64 folder from a fully working Win10PE SE image to my the image I'm working on, copied the patched smss.exe into system32, copied the syswow64 three core files into system32, copied all the entries from winsxs, and copied all the entries from system32\catroot.

Unfortunately when trying to boot the image it crashes early in boot with "PROCESS1_INITIALIZATION_FAILED". Which some people say is related to bootcat.cache under system32\codeintegrity but this file does not exist in either of the PE images.

Have I missed something from the script?

EDIT: Just copied the original smss back, no luck, so it's not related to that in any way.

Edited by spleenharvester, 06 February 2016 - 04:54 PM.

Last time I checked it was NOT found a way to add WOW64 to 10 based x64 PE's (unlike what was successful with 7 and 8 based x64 PE's), see:

http://reboot.pro/to...e-2#entry196249

(as said in the post above this piece of info is not actually up-to-date)

Anyway if there is some recent progress on the matter, it is more likely to be found on the actual support board for Win10PE (and Win8PESE), which is here:

http://tinyurl.com/zpjns8s

and where it is more likely that you will find people interested in the matter and knowledgeable on the specifics.

Wonko

P.S.:I just checked and in the meantime a "WoW64 Basic" script has been added to Win10PESE project, possibly it is what you actually need.

Last time I checked it was NOT found a way to add WOW64 to 10 based x64 PE's (unlike what was successful with 7 and 8 based x64 PE's), see:

http://reboot.pro/to...e-2#entry196249

(as said in the post above this piece of info is not actually up-to-date)

 

Anyway if there is some recent progress on the matter, it is more likely to be found on the actual support board for Win10PE (and Win8PESE), which is here:

http://tinyurl.com/zpjns8s

and where it is more likely that you will find people interested in the matter and knowledgeable on the specifics.

 

 

 

Wonko

 

P.S.:I just checked and in the meantime a "WoW64 Basic" script has been added to Win10PESE project, possibly it is what you actually need.

Thanks for the reply - Wow64 basic is indeed what I need, I only need it to run paraglider's RunScanner on one of my own images in development. Have made a thread on The Oven, hopefully someone will know what I'm doing wrong (or how to make winbuilder act on a pre-made WIM, which I'm not sure is possible)

So it seems The Oven don't want to help me, to say the least.

I think I've figured out the problem eitherway - image the Syswow64 is coming from is version 10.0.10586, the target image is 10.0.10240.

If I ever figure out how to do this I'll make sure to let you all know. Cheers.

So it seems The Oven don't want to help me, to say the least.

I am not sure to understand, you made a post asking for assistance/support with the issue and noone replied or did someone post that you are on your own or something similar?

Where is this post?

Wonko

I am not sure to understand, you made a post asking for assistance/support with the issue and noone replied or did someone post that you are on your own or something similar?

Where is this post?

 

Wonko

The post is under the 'plugins' section. They One of their members responded with one of the most needlessly abrasive 'we're not going to help you' posts I've seen in all my years on the internet. So I figure the best response to that is try and figure it out myself and share it on here!

Edited by spleenharvester, 07 February 2016 - 01:33 PM.

Ahhh, I see, you managed to accidentally touch some still exposed nerve. by posting the "botched by reboot.pro ©" link and naming this board .

I guess a few people on BOTH boards won't ever get over it, after what? 4 or 5 years?

Wonko

Ahhh, I see, you managed to accidentally touch some still exposed nerve. by posting the "botched by reboot.pro ©" link and naming this board .

I guess a few people on BOTH boards won't ever get over it, after what? 4 or 5 years?

 

Wonko

Haha yeah I could tell there was some history there when he referred to it as the 'wrong' forum. I had no idea before as I've only really got into WinPE modding over the past couple of months! Ah well, was worth a try.

spleen

Okay progress - I updated my base WinRE version to match the target (both 10.586 rather than 10.240) and it is now booting! - instead of the no subsystem error it tell me the side-by-side configuration is incorrect. I've definitely copied \Windows\WinSxS in properly though. More progress to follow hopefully.

edit - missed some regkeys from the original script

Edited by spleenharvester, 07 February 2016 - 03:15 PM.

Finally got round to working on this more (university side tracking me). I finally managed it and here is how I added syswow64 to a stock WinRE 10586 image. (Requires you to create a Win10PESE image with Wow64 basic)

Obviously full credit goes to everyone at The Oven/Win10PESE team, all I did was go back through their script. Thankyou to all who originally figured this out! 

1) Mount your desired image, and delete \windows\syswow64 and \windows\winsxs

• Note you will probably need a program like Unlocker to delete them as they are very resistant to security options usually

2) After finishing deletion, copy in those folders from the Win10PESE image

3) Copy \windows\system32\catroot from your Win10PESE image and merge with the same folder in your target image

4) Copy hiderun.exe, setwow64.exe, wow64.dll, wow64cpu.dll and wow64win.dll from your Win10PESE image's \windows\system32 directory to your desired image

5) Set your winpeshl.ini to call setwow64.exe upon startup using hiderun.exe

6) Load \windows\system32\config\SOFTWARE hive from your desired image into regedit under the name tmp_software

7) Extract 10000_SxS reg file from 5-Wow64.script and run it - it will add everything to your tmp_software key.

8) Add the keys specified under the RegWrite section of the 5-Wow64 script

9) Load \windows\system32\config\SOFTWARE from your Win10PESE image under the name tmp_software2

10) And this is what I was missing before, export everything from your Win10PESE tmp_software2\microsoft\windows\currentversion\sidebyside to a reg file. Replace all tmp_software2 to tmp_software and then use this to add the keys to your desired image.

Haven't tested extensively but the three apps I've tried so far have worked beautifully, finally no side-by-side errors! 

(also while I'm here - shellstyle.dll is causing memory read errors with open/save prompts, deleting it fixes this issue. But I need it for the file copy progress bar. Only happens in 10586 and not 10240, any ideas?)

Okay so further testing, a few apps are behaving unpredictably, seems there are still some dependencies missing. But it's a start, at least.

EDIT: Tried about 20 different apps now, 3/4 of them are working, I think some of them aren't just due to the nature of SysWOW64 basic.

Edited by spleenharvester, 22 February 2016 - 06:34 AM.

hello,

i see that you use setwow64.exe. This program was made by a chinees developper in C++. i translate it in c# that i put in a PowerShell script. If you Google microWinpeBuilder perhaps it help you. It's in french but with a translator ...

Regards.

Yeah, I had a similar reception when I posted an issue that I was running into when trying to manually create a Windows 10 PE x64 - not using winbuilder and using only MS files.   

At my work, we use Windows PE as a recovery tool.  We are currently on Windows 7 and will be migrating to windows 10 in the near future.  When we went to Windows 7, I did a manual build of Windows 7 PE without 'patching' files or changing the files from the install dvd.  (ie all files in the build came from the Windows 7 install disc, the MS WinPE disc & Windows AIK ).   After I got the OS working, I added a few 3rd party utilities that our ship permits to the disc and it has saved our shop thousands of man hours over the last few years.

I posted that I was doing a manual build for my company and got quizzed on who I work for, etc... and so I quit posting.

Currently, I have a fair amount working somewhat but am stuck on WinSXS aka SideBySide issues.  I have been using the Win10PE project files for reference to see what I need, but beyond that, just the AIK tools.   I can import the SideBySide from Win10SE using the instructions that you listed here and it will launch some 64bit apps (Internet explorer for example) but the 32bit apps are not working.  Get error 0xc000034 error... still trying to trace that down a bit.

The other issue that I am running into is that DWM is not working.  If I include the system32\DWM*.DLL files in the build, it boots to a solid black screen.  if I put them in a "System32\_Removed"  and then boot up, I get the command prompt and blue screen and can start working with the OS to get the shell started, etc.   Explorer still isn't 100% right but I have made some progress.  I think that in Win 10, you have to find a way to force integration of some of the 'AppsX" programs before it will work, but still am playing with it.    The other thought that I have but haven't been able to test is trying to create a new 'local' account  on the VM via startnet.cmd, add that to the local admin group & then try to use psexec to launch the explorer process as the newly created local user - to see if that gets around some of the issues....

anyone try something like that or have any ideas on the DWM or 32bit SXS stuff?

Thanks

Dan

Yeah, I had a similar reception when I posted an issue that I was running into when trying to manually create a Windows 10 PE x64 - not using winbuilder and using only MS files.   

 

At my work, we use Windows PE as a recovery tool.  We are currently on Windows 7 and will be migrating to windows 10 in the near future.  When we went to Windows 7, I did a manual build of Windows 7 PE without 'patching' files or changing the files from the install dvd.  (ie all files in the build came from the Windows 7 install disc, the MS WinPE disc & Windows AIK ).   After I got the OS working, I added a few 3rd party utilities that our ship permits to the disc and it has saved our shop thousands of man hours over the last few years.

 

I posted that I was doing a manual build for my company and got quizzed on who I work for, etc... and so I quit posting.

 

Currently, I have a fair amount working somewhat but am stuck on WinSXS aka SideBySide issues.  I have been using the Win10PE project files for reference to see what I need, but beyond that, just the AIK tools.   I can import the SideBySide from Win10SE using the instructions that you listed here and it will launch some 64bit apps (Internet explorer for example) but the 32bit apps are not working.  Get error 0xc000034 error... still trying to trace that down a bit.

 

The other issue that I am running into is that DWM is not working.  If I include the system32\DWM*.DLL files in the build, it boots to a solid black screen.  if I put them in a "System32\_Removed"  and then boot up, I get the command prompt and blue screen and can start working with the OS to get the shell started, etc.   Explorer still isn't 100% right but I have made some progress.  I think that in Win 10, you have to find a way to force integration of some of the 'AppsX" programs before it will work, but still am playing with it.    The other thought that I have but haven't been able to test is trying to create a new 'local' account  on the VM via startnet.cmd, add that to the local admin group & then try to use psexec to launch the explorer process as the newly created local user - to see if that gets around some of the issues....

 

anyone try something like that or have any ideas on the DWM or 32bit SXS stuff?

 

Thanks

Dan

0xc34 is the error you get when setwow64.exe has not been launched, have you appended it to your winpeshl.ini? (For a test, try just launching it from system32 while booted into WinPE, your 32-bit apps should start working).

As for DWM, I have no idea - I have never been able to get explorer/DWM working properly. Probably could with enough time but I don't care enough to figure it out lol. FreeCommander w/one pane launching into our toolset directory is working brilliantly for our needs. Someone else probably can fill in here.

Let me know how it goes.

Edited by spleenharvester, 23 April 2016 - 06:41 PM.

​Hello,

I don't understant very well English, i'm french. On the site 'the oven' i post a microwinpebuilder. I write a pdf for explain how to make its  own winpe10 from ADK without .EXE, only with scripts PS. I write some scripts PS to make this winpe10 customised. It contains explorer DWM, Syswow64 ( but i don't explain SXS because i launch no 32bits ), MMc, modify FWB.sys with script PS....

I use many explanations from the ite 'the oven'. Without their work,i can't make my scripts.

My scripts PS are text, so no surprise if you read the text. Even setwow64 is translate in PS ( in C# in PS, so text ).

I am working for  new version with Session ADM, BITS, WinRm and i post it soon. The actual version include wow64.

You can find it here http://noel.blanc.fr...WinpeBuilder.7z

Perhaps it can help you or give some idea.

@ spleenharvester, thanks for the like

Regards.

Just a bit of an update to this:

1) Not sure how I missed this, but the keys in [HKLM\software\classes\wow6432node] are necessary for a lot of 32-bit apps to work properly. Exporting these keys from 10PESE and adding them to my own image fixed a lot of common dialog issues.

2) I also recommend removing the keys from your image before adding them from the 10PESE image. That way you have a 'clean' WoW64 install that (should!) be a replica of that in 10PESE.

3) The 10PESE WoW64-Basic script now uses \system32\loadwow64.exe instead of setwow64.exe by the looks of it. If you transfer loadwow64.exe to your image's system32, and then export the "BootExecute" key at [HKEY_LOCAL_MACHINE\tmp_system\ControlSet001\Control\Session Manager] from 10PESE to your own image, this will make WoW64 work.

Setwow64.exe called from winpeshl.ini still works fine to me in the newer image, but they probably have a good rationale for making the change.

Edited by spleenharvester, 21 June 2016 - 11:42 AM.

2) I also recommend removing the keys from your image before adding them from the 10PESE image. That way you have a 'clean' WoW64 install that (should!) be a replica of that in 10PESE.

Just as follow up to this, doing this made one of my WinPE language packages fail to install with a component store corruption error, so maybe best leave the current keys alone.