ever since i reimaged my pc with new windows 10 pro with a new m2 intel drive i keep hearing this chime sound every so often it is the sound that occurs when windows either signs off or shuts down but i am doing neither it just occurs at a certain interval not sure which. anyone else have this issue?
You can check under "sounds" in control panel. Check which action has Chime sound associated.
I checked that end of it there is no chime sound available under windows default sound scheme, what can i do to track this down so annoying.
By default there is no Windows Logoff or Shutdown sound defined in Windows 10.
To confirm this, check the following registry location:
Code:HKEY_CURRENT_USER\AppEvents\Schemes\Apps\.Default\WindowsLogoff\.Default
So, first you need to identify the exact sound you are hearing. If it's a built-in sound it will be stored under %windir%\media - for example, in the C:\Windows\Media folder.
Play the sounds one-by-one, perhaps beginning with the ones starting with 'Windows', for example Windows Shutdown.wav. Once the exact sound is identified then the next step is to identify the process using the sound.
If you cannot identify the sound manually then an alternative method is to use something like Sysinternals/Technet's Process Monitor (ProcMon), filtered to look for sounds being played or the filepath to the sounds. That's a little more complex so try the manual method above first of all.
Hope this helps...
As it must be associated with a certain process, and you say it occurs at intervals, either it's a scheduled task, or some background process generating it periodically.it just occurs at a certain interval
You can start to try to isolate this latter with a clean boot. If it still occurs, check to see what else you could stop running.
Then you can turn to scheduled tasks and examine these.
One way to get a linear list is to use Taskschedulerview by Nirsoft.
Note that the actual sound file being played may be one of the system sounds, or it could be one associated with a particular program.
Using Procmon as RickC suggests seems about the only analytical approach, but it's technically daunting as the log includes everything from registry access to running processes.
You could also try creating a new user, logging in as that user, and see if it still occurs. If not, you have a starting point for comparison.
checking all items. thank you will let you know what i find.. also i might do a video so we all know the sound.
Quote
