Vegas won’t start twice

[Gary Kleiner]

You may have to reinstall Vegas.

Gary Kleiner

Learn Vegas and DVD Architect

http://www.VegasTrainingAndTools.com

[Edward Troxel]

My guess would be an old scanner (twain) driver that isn’t closing when Vegas exits. After exiting Vegas, see if there’s a “wow32” still running. If there is, kill it and then try starting Vegas.

The ultimate solution would then be to get rid of the old driver.

Edward Troxel

[Alan Kushnir]

Edward,
Wow. I am duly impressed. Thank you.
There was a process running called “wowexec.exe”. As soon as I killed it, Vegas starts up. I renamed the “wowexec” file, and now the issue is resolved.
Thanks so much.
My curiosity is working overdrive right now. Can I ask how you knew this, ie the specific file name? I guessed it was caused by something left behind after Vegas exited, but why should Vegas have initiated “wowexec.exe” in the first place? What application put “wowexec” in my system?
thanks again.
Alan

[Edward Troxel]

Wowexec is a windows file. You need to rename it back as it is needed to keep older programs compatible with newer versions of Windows. Vegas started it probably because it inialized your scanner which required 16bit compatibility.

Instead, you need to locate what is causing wowexec to start. Odds are it’s an old “twain32.dll” file. If you do a search, I’ll bet you find several twain files. Here’s a quote from someone else who had this problem:

It would appear that I have just solved this problem for my own system. I discovered that I had a different version of the twain_32.dll in my WINDOWS/SYSTEM32 folder than in my Windows protected DLL cache and WINDOWS folders. The first one was 76K bytes and was listed as “TWAIN_32.DLL” ( all caps). The other 2 files were 46K bytes, listed as “twain_32.dll” (small letters), and have a more recent date associated.

I have a Cannon scanner and found the 76KB “TWAIN_32.DLL” in the CanoScan folder. I replaced the 76KB TWAIN_32.DLL in the WINDOWS/SYSTEM32 folder with the 46KB twain_32.dll. You will probably need administrator rights if you try this yourself.

And now for more information than you ever wanted to know:

wowexec.exe
“Windows on Windows Executable environment process, or more specifically Win16 on Win32

[Alan Kushnir]

>>And now for more information than you ever wanted to know:

Edward,
No, its not more. I also found on my system the two versions of twain_32.dll, and replaced the old one (dated 1996) with the new (smaller) one (2004).
This seems to be the real problem, because notwithstanding my renaming the “wowexec.exe” file, windows went and re-created it and it again starts up. But now, vegas has no problems starting even though wow is running.
I do appreciate greatly the references to the 2004 thread where this same problem was originally worked through.
I hope this thread helps somebody else solve this in the future.
Thanks again.
Alan

[Gary Kleiner]

[Alan Kushnir] “Wow. I am duly impressed”

Me too 🙂

Gary Kleiner

Learn Vegas and DVD Architect

http://www.VegasTrainingAndTools.com

[Alan Lacey]

Me too, it’s just this sort of background info that you need to file away in the grey matter. You never know when you’ll need it.

Alan

[Edward Troxel]

Thanks, guys. Glad I could help.

Edward Troxel

[Fatih Sanane]

I Have had the same problem with you and here is the solution for it .

you guys having TWAIN manager error, probably you have disabled Windows Image Acquisition Service. Set it to manual and everything will be ok. That is (in case you don’t know how to do it):

* Goto Start -> Administration Tools -> Services
* Double click “Windows Image Acquisition (WIA)”
* Set “Start type” to “Manual”, press “OK”