No sounds after upgrade to Windows 11

Quicken Windows Other Member

My wife has consistently used Quicken 2011 for our personal financial records since - well, 2011 (amazing eh?) and won't "give it up" despite my efforts to keep this old program alive since Windows 7, and Windows 8, and Windows 10 (etc etc). But most importantly for her, when this happened with Windows 10 'upgrade', I even got it fully functional with what she likes when operating it: mainly having the sound associated with opening the program and the sound associated when confirming an entry to the 'checkbook', both actions have associated sounds within the System Sounds applet.

BUT… now that we've upgraded her PC to Windows 11, no Quicken sounds function any longer, and of course, all these many sounds are stored inside the Quicken program folder under the "sounds" folder, but not only will they not function in the program, they will not play in the Windows System Sounds applet where these sounds are 'associated' with a file action in Quicken. Now I should note that, I CAN associate a Windows-specific sound file from a 'sound scheme' that is a 'default' sound for one of the some other unrelated action in Windows (all of which are .wav files), and by assigning these and saving this configuration to these two functions, this seems to work, but now I am on the hunt to find out WHY the "action associated" sounds from Quicken 2011 (… now 'upgraded to Quicken 2013 during my troubleshooting), and NONE of these files will play in an associated action in Quicken but 'default' system sounds do. What I now notice when I examine these by examining "Properties', none of the Quicken files have a 'digital signature' while all 'usual' system sounds DO have a digital signature. Could this be the issue with all Quicken sounds?

Oh, and BTW: all of these Quicken associated files CAN be played via Windows Media Player or other sound apps (ie: VLC player, etc.) and the ONLY places this does not work is in 'system sounds' (where one might associate a sound file with an 'action' in Quicken 2011/2013) and thus, while using the Quicken program itself. This is what has lead me to surmise it is because there is no 'digital signature' and Windows simply will not allow the sound to be played (Windows security related, possibly...?). If this could be the case, then how would one /create' or add a digital signature that Windows would 'trust'? By "editing" the file in a sound editor (like I once did in my older Roxio sound editor YEARS ago to create a cell phone sound that did not otherwise exist - to my knowledge..) and which might then give a sound file the required 'digital signature' that met Windows 11 security requirements?

Or maybe.. Intuit/Quicken support personnel might 'edit' these Quicken sound files and potentially give them a 'digital signature' and then maybe post them someplace where the 'anal-retentive' (like me) could download these and place them in the proper locations so these sounds can be properly associated once again..

Hey… ALL of this is just a thought… y'know (?)

Welcome!

It looks like you're new here. Sign in or register to get started.

Comments

  • Quicken Windows Other Member
    edited February 3

    Or am I just crazy in addition to being 'anal-retentive'… 🙄

  • Quicken Windows Other Member

    Well… insofar as I am inherently impatient (in addition to being 'anal-retentive') I did an experiment to see what I could try.. And it worked.

    I loaded up my old Roxio NXT8 software (well.. at least enough to get the Sound Editor, anyway) and imported the two sounds she wanted (qopen99.wav and qrecord.wav - which would not playback in either System Sounds applet or Quicken program), I then assigned some data to these files related to 'artist', album (none), track number, yadda-yadda- whatever…whatever else I could think of to lend it some 'credence' in Windows 11… then 'exported' the file to a 'safe' location in my user account (ie: Music - sounds) with a related title that made sense (in this instance, "qrecord.wav" became "quicken_record.wav" and "qopen99.wav" became "quicken_open_99.wav") copied the altered .wav files to BOTH Quicken2013/sounds folder and System Sounds, and then assigned the two newly altered files to their corresponding file actions in System Sounds…. And behold! they now work.

    See, told ya being 'anal-retentive' ain't necessarily all that bad… so there…

  • Quicken Mac Subscription Moderator mod

    Hello @HerHusband,

    Thank you for coming back to share the troubleshooting steps that you took. I am happy to hear that you were able to get the sounds working again!

    -Quicken Jasmine

    Make sure to sign up for the email digest to see a round-up of your top posts.

This discussion has been closed.