I have been experimenting to see how much I can remove of the WOW64 emulator from XP x64.
Here is what I have got up to:
Removed all x86 and WOW64 files from the WinSxS folder
Removed all files from SysWOW64
Removed the 3 WOW64 DLL's from System32
Removed all WOW64, WOW, and X64 entries from the registry
Removed WOW KS thunk driver files
With this I can still boot and seem to have only access to 64 bit code. However there are some more things I want to do:
Remove or disable registry reflection to the WOW6432Node keys
Remove the WOW6432Node completely
Remove the SysWOW64 folder (I get a blue screen if this is removed, even when empty. If the entry to the folder is removed from KnownDLLs key in the registry I also get the blue screen.)
So guys, how much more of the emulator can I 'rip out', without modifying any system files directly? Has anyone tried this before and got far?
Thanks.
2 replies to this topic
#1
Posted 25 March 2013 - 05:38 AM
#2
Posted 25 March 2013 - 11:13 AM
So guys, how much more of the emulator can I 'rip out', without modifying any system files directly? Has anyone tried this before and got far?
May I ask what is the "scope" of the exercise?
I mean, like:
- reducing XP 64 installation size
- increasing security by removing the possibility of execution of Win32 Malware/Viruses/Whatever
- making it faster/more responsive
- for the fun of it
- just because it can be done
A WinPE 3.x (and 4.x) 64 bit has all the WOW64 stuff removed, and there is a list of things that people re-adds to it (in order to add the 32 bit compatibility), maybe those files could represent a reference:
http://reboot.pro/to...ession-winpe-4/
http://reboot.pro/topic/16214-wow64/
Wonko
- Brito likes this
#3
Posted 26 March 2013 - 08:19 AM
May I ask what is the "scope" of the exercise?
I mean, like:A WinPE 3.x (and 4.x) 64 bit has all the WOW64 stuff removed, and there is a list of things that people re-adds to it (in order to add the 32 bit compatibility), maybe those files could represent a reference:
- reducing XP 64 installation size
- increasing security by removing the possibility of execution of Win32 Malware/Viruses/Whatever
- making it faster/more responsive
- for the fun of it
- just because it can be done
http://reboot.pro/to...ession-winpe-4/
http://reboot.pro/topic/16214-wow64/
Wonko
Hi, thanks for the reply.
The reasons are more for number 4 and 5 of your reasons, it's just a hobby really to see how far I can remove WOW64.
I reckon there are some more files related to WOW64 I can remove from the system32 directly, and hope it's as easy as just removing the files without Windows punishing me with a blue screen for it.
I will look into the preinstall environments you mentioned for any clues, thank you.
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users