Why Windows-on-Windows acts like this ?
Run windows-on-windows by typing "wowexec.exe" in Run dialog.
Now open taskmaneger.
1. Notice that there there is no memory usage shown.
2. Also there is a space before the process name.
3. You'll see another process, ntvdm.exe, has started with it.
When you arrange the processes by name/cpu usage/mem usage etc by clicking the columnheaders, both processes move together.
4. Now try to kill wowexec.exe. - It can't be killed.
Kill ntvdm.exe, then that process will exit.
Why this is happening ? :confused:
http://img265.imageshack.us/img265/7170/wowii4.jpg
Re: Why Windows-on-Windows acts like this ?
Re: Why Windows-on-Windows acts like this ?
Somewhere I heard you can solve this problem by setting HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WOW\DefaultSeparateVDM key to "yes".
But that didn't work. :(
Re: Why Windows-on-Windows acts like this ?
Re: Why Windows-on-Windows acts like this ?
Ya, I feel an issue like this before on a process name ante.exe. But it is not make any damage to me. After few days automatically it removed.