Forums before death by AOL, social media and spammers... "We can't have nice things"
|    alt.comp.freeware    |    Generic free software discussions    |    39,996 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 38,604 of 39,996    |
|    Marion to All    |
|    Summary to solve re-occurring Epic Priva    |
|    15 Jun 25 18:46:46    |
      XPost: alt.comp.os.windows-10, alt.comp.os.windows-11, alt.comp.       icrosoft.windows       From: marion@facts.com              Summary to solve re-occurring Epic Privacy Browser launch issues              Recurring Problem:       Epic Privacy Browser will suddenly, inexplicably, simply fail to launch       (wouldn't start from existing shortcut, not running in Task Manager/Process       Explorer, no error messages and a reboot doesn't help but a re-install always       fixes the recurring problem        which happens sporadically, about once every few months).              Successful Solution (20250615):       I deleted the %localappdata%\Epic Privacy Browser\User Data\Default folder.       Result: Epic launched successfully from the shortcut that previously stopped       working.              This happens about once every few months.       I don't know why.              The assumption is "something" got corrupted.       But what?              Lessons Learned / Recommended Targeted Approach for Next Time:              Before deleting anything, ALWAYS BACK UP:        a. %localappdata%\Epic Privacy Browser\User Data\Default\Bookmarks (Your       saved bookmarks)        b. %localappdata%\Epic Privacy Browser\User Data\Default\Login Data (Saved       passwords)        c. %localappdata%\Epic Privacy Browser\User Data\Default\Preferences (Core       browser settings)        Note: These are files within the Default folder, copy them before deleting       Default or specific sub-elements.        Copy them back later after restarting & immediately killing Epic, which       re-creates the Default folder.              Once you've copied those files, then you can attempt a targeted deletion of       suspected corrupted elements (one by one, testing launch after each deletion),       attempting to restart Epic after each targeted deletion.              Most likely culprits (in order of likelihood):       1. Delete the file containing Epic's core configuration. Then test.        %localappdata%\Epic Privacy Browser\User Data\Default\Local State              2. Delete the folder containing session data for open tabs/windows. Then test.        %localappdata%\Epic Privacy Browser\User Data\Default\Session Storage              3. Delete the session data folder, often alongside Session Storage. Then test.        %localappdata%\Epic Privacy Browser\User Data\Default\Sessions              If those don't work, then try these far-less-likely possibilities:       A. Delete the folder for web content cache. Then test.        %localappdata%\Epic Privacy Browser\User Data\Default\Cache              B. Delete the folder for compiled JavaScript. Then test.        %localappdata%\Epic Privacy Browser\User Data\Default\Code Cache              C. Delete the folder for extension data. Then test.        Note: This will likely require re-enabling/re-logging into extensions.        %localappdata%\Epic Privacy Browser\User Data\Default\Extensions              D. Delete the folder for offline web app data. Then test.        %localappdata%\Epic Privacy Browser\User Data\Default\IndexedDB              If targeted deletions fail, delete the entire Default folder.       Then restore backed-up data. This always works.              If you know of a better solution, please let the team know as we're all more       powerful together than we are all alone.              --- SoupGate-DOS v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca