New
#11
You are pointing to the wrong file. We are concerned with Windows Startup.wav down at the bottom of this folder. Try playing it and you get a sound very similar to Windows Navigation Start.wav.
Read this interesting thread on how to change the default Windows Startup sound to another sound.
Startup Sound - Change in Windows 7
This may be the thread Slartybart (here) was looking for but it doesn't appear to deal with the problem of not being able to play the Startup sound but in how to change the sound so I have not fully read or considered it.
However this is where it sounds to me that the actual Startup.wav actually resides in or part of this .dll
imageres.dll
See what you think if I used one of these procedures to fix this mess? Heck, I'm going to go search for this .dll right now. Maybe it is missing for all I know?
Last edited by Ratsneve; 02 Oct 2013 at 00:19.
Sounds (pardon the pun) as though you didn't complete the test.
Drat...this had no affect on bringing the Startup sound back. Sure makes the desktop look like puke too.
1) turn off areo theme and untick startup sound - presume this is done bc your desktop is not pretty
2) turn on (tick checkbox) startup sound - not sure if you did this
3) reset desktop theme to your preference - I don't think you did this
anyway, I couldn't find what I thought was out there.
if imageres.dll isn't there you'd know it - it contains all the system icons.
Sorry changing the theme didn't resolve the issue.
good luck
Bill
I saw that - but I had a question about the existence of the file that Process Monitor pointed to. I should have quoted your post and added to the discussion from there.
Process Monitor shows that RunDLL32 checked (opened - got info - closed) that file when I toggled the setting named "Play Windows Startup Sound" in the Sound Control Panel applet.
I had the Sound Scheme set to "No Sounds" so that Sound Control Panel applet would not set the WAV file info for each event in a scheme. This meant the Process Monitor was only recording what happens behind the scenes when the user changes that setting named "Play Windows Startup Sound". I have no idea why W7 checks that file... I just thought that I would ask if you had it.
Also - the Sound Control Panel applet does not always check that file when the setting named "Play Windows Startup Sound" is changed. Sometimes there are no WAV files checked. I don't like things that don't repeat. It makes it that much harder to document and understand.
I read the link about the DLL - I don't understand it, but I read it![]()
Thanks
Ok, I figured you would complete the list... bc your desktop wasn't pretty.
4 imageres.dll is fine (x86 & x64 = 2 + Winsxs versions of same = 4).
To see if it's just a timing issue, try a clean boot: Troubleshoot Application Conflicts by Performing a Clean Startup
I'm going to perform this clean boot when I get back from the store but I wanted to get out this other/related question first... Does this windows startup sound involve any Services? This is because I sometimes (but don't recall the last time) meddle with a Service I don't think I need. If there is a Service related/needed for this startup sound I might have deactivated it thinking it was stopping something unrelated that I knew I didn't need? :) Thank you for continuing your interest.
That would be Windows Audio and should be on auto start. Check in msconfig to see if you unchecked it.
Yippy! YIPPY! Cool! Thank you for pointing me via the tutorial process right to the problem. Following the instructions. I ended up running all my Startup items and all the MS Services but with all the non-MS Services remaining unchecked discovered the stupid Startup sound playing away consistently each time I restarted the machine. It was then a simple matter of checking these non-MS Services one at a time. In the order I took I actually guessed to within the last two remaining Services too! My Windows Startup problem boils down to...tada...
'NVIDIA Streamer Service -- Running'
Checked -- no startup sound
Unchecked -- startup sound plays like it should.
Will call NVIDIA back up who will be very interested in this and likely very helpful on what to do next--like resolving/solving the conflict, why it happens, and how to prevent it from happening again.
I'll post at least one more time to wrap up this thread.