SoundPackager Crashes At Installation & Startup But Found A Fix [Win7, x64]

I upgraded to Object Desktop from WB7 yesterday and everything installed fine excpet SoundPackager.

During installation, I got two error messages that's got to do with "regsvr32". After the installation, when

I ran SP, it just crashed. Since I know a little programming, I know that "regsvr32" is used to register DLL's

and OCX'es so I went into SP's installation directory and tried to find some problem DLL's or OCX'es. Apart

from the .NET DLL's, I found the DirectSkin control wbocx32.ocx. Since I remembered seeing it in the Impulse

folder too, I checked the version of the ocx in the SP folder (5.0.0.0) and found it to be lower than the one

in the Impulse folder (5.0.6.1) or the one in the Tweak7 folder (5.0.6.3). So I renamed the ocx in SP folder

to "wbocx32.ocx.bak" and copied the one from Impulse folder into the SP folder. Now, I can run SP without any

crashes. I hope this will help those facing similar problems. I'm running Windows 7 x64.

131,475 views 32 replies +5 Loading…
Reply #1 Top

Good find! I've been trying figure out what was wrong with mine for months. Thanks!

Reply #2 Top

Glad to know it helped someone!

+1 Loading…
Reply #3 Top

An excellent solution!  Now mine works (Win 7 64 bit), so perhaps someone at stardock will incorporate the relevant file in an update.

Reply #4 Top

Yeah, an update is what we need. Maybe Stardock's not giving SP as much attention as other products cause it's not as popular.

Reply #5 Top

Thanks for the info.  This should be fixed in an update soon.

Reply #6 Top

You Are Awesome I Was About To Go Ballistic $49 Bucks & It Doesn't Work?? Thanx Alot Sir U Saved The Day!!

Reply #9 Top

2 support tickets......over a  year of not being able to use soundpackager or only having it work for about a week after a reformat.......then i find this thread.......THANKYOU!!!!!!! 

 

Worked like a charm.....why the heck isnt the stardock support team offering this information to people with the same problem? they never mentioned anything like this to me, just a bunch of basic uninstall reinstall reboot run arounds that never worked.  thankyou

Reply #10 Top
Thanks guys!! Maybe Stardock support couldn't pinpoint the problem 'cause it doesn't occur on every machine. From what I've read on the forum, some people with Win7 x64 are using SP without any problems.
Reply #12 Top

Thanks guys!! Maybe Stardock support couldn't pinpoint the problem 'cause it doesn't occur on every machine. From what I've read on the forum, some people with Win7 x64 are using SP without any problems.

Yes, this seems to only affect certain machines.  My own machine running 7 x64 is not affected by this.

Reply #13 Top

unfortunatly mine stopped working again after the last impulse update. i repeating this trick and noticed the wbox32.ocx is now at version 5.0.7.6 and i think it automaticly updated the one in my sound packer folder to the new one during the impulse update....this new version of the .ocx file seems crashes soundpacker again when applying a sound package.

Reply #14 Top

Absolutely fantastic. The only app I could not get to work on my new W7 build. Thanks ChillChan!

Reply #15 Top

Thank you so much for posting this fix. I looked in a lot of places that suggested that I change my DEP settings, but my 64 bit Windows 7 machine wouldn't let me make the recommended changes. Replacing the file worked like a charm.

Reply #16 Top

Quoting fern420, reply 13
unfortunatly mine stopped working again after the last impulse update. i repeating this trick and noticed the wbox32.ocx is now at version 5.0.7.6 and i think it automaticly updated the one in my sound packer folder to the new one during the impulse update....this new version of the .ocx file seems crashes soundpacker again when applying a sound package.

Try deleting the "wbocx32.ocx" from the Sound Packager folder. SP runs fine with or without the ocx file

(at least on my PC). The only difference is without the ocx file, the buttons inside SP are no longer

skinned by SP but by Windows (or WindowBlinds if you're using WB). If the problem still persists, can you

please post the error message you get in detail? If SP loads but only crashes when applying packages,

it may not be a problem with the ocx.

Reply #17 Top

Quoting chillychan, reply 16

Quoting fern420, reply 13unfortunatly mine stopped working again after the last impulse update. i repeating this trick and noticed the wbox32.ocx is now at version 5.0.7.6 and i think it automaticly updated the one in my sound packer folder to the new one during the impulse update....this new version of the .ocx file seems crashes soundpacker again when applying a sound package.
Try deleting the "wbocx32.ocx" from the Sound Packager folder. SP runs fine with or without the ocx file

(at least on my PC). The only difference is without the ocx file, the buttons inside SP are no longer

skinned by SP but by Windows (or WindowBlinds if you're using WB). If the problem still persists, can you

please post the error message you get in detail? If SP loads but only crashes when applying packages,

it may not be a problem with the ocx.

 

tried it but still no go.....SP only crashes when trying to apply a sound package however i can apply sound packs just fine from the windows control panel but ofcourse there's no option there for the advanced sound package option so it's definitely not a corrupt package or anything like that. here's the error:


Problem signature:
  Problem Event Name:    CLR20r3
  Problem Signature 01:    soundpackager.exe
  Problem Signature 02:    1.0.0.0
  Problem Signature 03:    49909bcd
  Problem Signature 04:    System.Drawing
  Problem Signature 05:    2.0.0.0
  Problem Signature 06:    4a275e83
  Problem Signature 07:    7af
  Problem Signature 08:    6c
  Problem Signature 09:    System.ArgumentException
  OS Version:    6.1.7600.2.0.0.256.1
  Locale ID:    1033



So i tried uninstalling soundpackager, ran ccleaner, rebooted, reinstalled and now sound packager wont even open again, just crashes on start up once again. here's the error codes from it now when it wants to crash immediately when i try to open it:


Problem signature:
  Problem Event Name:    BEX
  Application Name:    SoundPackager.exe
  Application Version:    1.0.0.0
  Application Timestamp:    49909bcd
  Fault Module Name:    KERNEL32.dll
  Fault Module Version:    6.1.7600.16385
  Fault Module Timestamp:    4a5bdbde
  Exception Offset:    000111b0
  Exception Code:    c0000005
  Exception Data:    00000008
  OS Version:    6.1.7600.2.0.0.256.1
  Locale ID:    1033



I only get these issues on 64 bit windows 7.



UPDATE


its got to be windows blind that's somehow causing these issues. I set windows blinds to aero default and low and behold sound packager works again. I wonder if it could somehow be from a corrupt windows blind package that i might have installed.

Reply #18 Top

Well, I'm glad you solved it by yourself cause I honestly don't know what to make of the error :P

Reply #20 Top

wow, that did it, deleting the wbocx32.ocx file!  i've been trying to get soundpackager to run with no luck since Vista x64.  It ran for a while on Win 7 x64 but quit.  Thanks!!!!!!!!!

Reply #23 Top

Could someone please tell me how to get the sound packager window to maximize?  I can get the sound packager window to open now that I followed this fix, but the window only shows about 3/4 of the contents with no scrollbar and no max button.  HELP!

Reply #24 Top

the window only shows about 3/4 of the contents with no scrollbar and no max button.

Have you changed your dpi settings? That has caused this problem with other apps.

Reply #25 Top

THANKS. Wokrs for me now too!