A new problem: wowexec.exe

jlafferty wrote on 3/14/2005, 7:37 AM
I've suddenly got problems with Vegas hanging on launch -- this only started happening recently, and it only happens every other launch. When I ctrl+alt+del, I noticed for the first time an .exe called "wowexec.exe" and, forcing it to end, Vegas becomes unhung. Searching for the exe, I found it in my system32 folder, which sends up some red flags, though it looks as if it's a legit app -- in the Properties window it's described as "Windows Win16 Application Launcher," "Copyright © Microsoft Corp. 1981-1996," so I'm hesitant to try removing it.

Thanks,

- jim

Comments

Orcatek wrote on 3/14/2005, 7:43 AM
wowexec.exe is a valid program and is part of the OS. It is used to run old 16-bit applications.

I remember someone else had a very similar issue and there is a long thread on it in the archives. Don't remember the result.

Spot|DSE wrote on 3/14/2005, 7:44 AM
it's also used by many UPS's as part of the "golden parachute" that safely closes your system. I don't recall the results of the other thread either, it's a fairly old one, a search will likely show up.
BillyBoy wrote on 3/14/2005, 7:47 AM
Perhaps you'll find this useful:

http://www.coordinated.co.za/discussions/viewtopic.php?t=101

scroll down several posts until you hit a detailed explination.
dcrandall wrote on 3/14/2005, 8:05 AM
I had this exact problem back in May 2004. The solution has to do with the version of "TWAIN_32.DLL" that is located in the "Windows/System32" directory.
See this thread:

Wow.exe problem

-Dan
  • Velocity Micro Z55 Desktop Computer
  • ASUS Prime Z270M-Plus Motherboard
  • Intel(R) Core(TM) i7-7700K CPU @ 4.2GHz
  • Memory: 16GB DDR4-2400MHz
  • 4GB NVIDIA GeForce GTX 1050 Ti Driver Version: Studio Driver 452.06
  • Windows 10 Home 64bit v1909
  • Vegas Pro 18.0 Build 284
RafalK wrote on 3/17/2005, 12:12 PM
If you haven't gotten over this problem yet, this is what I do. I open the task manager, highlight the wowexec task and end it. Does the trick everytime.
jlafferty wrote on 3/17/2005, 12:31 PM
Thanks to Dan the problem's solved -- there are two twain_32.dll files, and I replaced the older one with the newer one and I'm all set.

Sorry I hadn't searched before posting, though -- and thanks again!

- jim