David369
23 discussion posts
After returning home, and returning my laptop to my multiple monitor setup, I've as always started having my taskbar, now either displaced or erroneously duplicated (which didn't happen before)...
Finally I decided to just hit 'Reset All Taskbars', in hopes of this helping perhaps, being well sure I could restore it through the backup before... but lo and behold, after the taskbar is reset, IT IS GONE FOREVER!! I've tried re-installing, re-installing with Revo, and... nothing... The taskbar icons neatly arranged on my 5 monitors — now gone forever. Why on Earth is this possible? And why does one's prior backup (of settings) not return them?? It just makes zero sense, and a dire, dire world of frustration and disappointment. There should at the very least then be a warning "You will lose all your taskbar icons forever with no way of ever getting them back. Do you want to proceed? Y/N"
May 22, 2023 (modified May 22, 2023)
•
#1
David369
23 discussion posts
After a couple of glasses of scotch to calm the tortured senses, it dawned on me to restore an earlier version of the .reg file (settings) through Dropbox (the subscription for it paying off big time here) — which luckily restored my precious little taskbar icons. But it seems then that the new settings export functionality is perhaps somewhat gimped then? Because if the old export (the one I restored through Dropbox, thank God 666) worked and the new one didn't, then something isn't right. Especially when they are the same size, with the new export a bit larger than the old. Just don't make much sense.
May 22, 2023 (modified May 22, 2023)
•
#2
Could you send me over the backup that's failing?
David369
23 discussion posts
Quote:
Could you send me over the backup that's failing?
Sure thing
• Attachment [protected]: DisplayFusion.reg [858,790 bytes]
Thanks for sending that over. There's a bug in 10.0 with the file path, if you do a find and replace on that file to search for "CurrentUser" and replace it with "HKEY_CURRENT_USER", it should fix that up.
This issue is also fixed up in our latest beta version.
Thanks!