Tray notification settings get reset...

Discussion in 'backup, imaging & disk mgmt' started by LittleDude, Mar 6, 2014.

Thread Status:
Not open for further replies.
  1. LittleDude

    LittleDude Registered Member

    Joined:
    Mar 22, 2008
    Posts:
    62
    Most of the time when I restore an image(using Drive Snapshot, Macrium and sometimes AX64) or rebooting from Shadow Defender, the Tray Notification settings get reset back to default. Is this common as I don't recall anyone mentioning it. A slight PITA but I have created a backup of the Tray Notification registry settings which I can restore, then exit and restart explorer.
    Any ideas on why this happens?
    Thanks :)
     
  2. Brian K

    Brian K Imaging Specialist

    Joined:
    Jan 28, 2005
    Posts:
    8,646
    Location:
    NSW, Australia
    LittleDude,

    Are you using VSS backups? VSS doesn't backup/restore "everything". Just a guess.
     
  3. LittleDude

    LittleDude Registered Member

    Joined:
    Mar 22, 2008
    Posts:
    62
    I'm not sure(I'm not as knowledgable about these things as most of the members here)...but the service is set to manual. I see Drive Snapshot has it enabled as default. I'll run a few tests in the weekend to see if it makes any difference.
    Thanks for your reply.
     
  4. Jim1cor13

    Jim1cor13 Registered Member

    Joined:
    Aug 4, 2012
    Posts:
    453
    Location:
    US
    Hi LittleDude :)

    Your issue is a registry issue in regards to the tray notifications. It is baffling as to how this can happen, but in the past, when I had tried to delete a few entries that were no longer installed, I found the registry key and the process in how to reset it as you also mentioned you found.

    I am reading more strange issues like this with various disk imagers and all I can say is it is very possible as BrianK mentioned it could be VSS issues, but if I were you, have you tried performing a COLD backup and restore in order to see if that takes care of this issue?

    I choose COLD imaging instead of HOT because in my experience, hot imaging CAN cause these issues that COLD imaging does not experience. I think there are certain parts of registry hives that some imagers using VSS simply cannot get a good or proper lock on while performing a hot image backup.

    Just my thoughts. Perhaps you could try a cold image backup then a restore to see if indeed it may be VSS related. :)

    Jim
     
Thread Status:
Not open for further replies.