Forum Discussion
Help! Dev updated from 87 to 88 after an OS update comp restart, lost session, local storage
Previous Edge Dev on my laptop was apparently 87.0.658.0. On Nov 12 around 2:30am or so my time, even though I had put my laptop to sleep W10 decided to force restart after an update was downloaded, ...
I'm pretty sure those sync options are turned on for me, as when my Surface updated to Edge Chromium it brought over all of that. It did not bring over local storage, however, and I want to stress that local storage is the thing I want to recover most here.
If your Surface received the update to replace Edge legacy with the new Edge, you have the Edge stable, and it doesn't currently have History and Open tabs sync, it's still in Dev and Canary channels, the next version of Edge, version 88, will most likely bring those last remaining sync features to Edge stable.
your local storage resides in Edge's profile directory, you can get it from here:
edge://version/ in the "Profile path:"
I still don't know how your computer was sleep for a month, Edge Dev 87 is very old. like I said next one will probably be 89. and it usually takes 1.5 month between each version.
about your restart, use Windows 10 latest version, then go to Settings =>update & security => Windows update => Advanced options => make sure this is off "restart this device as soon as ...."
your local storage resides in Edge's profile directory, you can get it from here:
edge://version/ in the "Profile path:"
I still don't know how your computer was sleep for a month, Edge Dev 87 is very old. like I said next one will probably be 89. and it usually takes 1.5 month between each version.
about your restart, use Windows 10 latest version, then go to Settings =>update & security => Windows update => Advanced options => make sure this is off "restart this device as soon as ...."
- I held off on manually restarting Edge Dev when the v88 update first came in, mainly because I was actually using the browser for stuff and I didn't want to deal with the usual "out-of-graphics-memory when trying to reopen my windows" in the middle of me trying to be productive. Since maybe v84 this has been a regular occurrence when restarting while having 10 windows of almost 800 tabs total open, but that's a separate issue entirely from the local storage problem I'm trying to solve.
Found the "Local Storage" folder in the profile path but like I said it doesn't have the data that was in v87, and the Snapshot of v87 doesn't have a Local Storage folder at all, just Sessions (which is how I was able to get the last session which I'm still in the process of recovering).- Well, I don't think there is any way to recover it unless you have a backup of your C drive from a previous time. not sure with you mean by "snapshot of v87"
these problems are normal in Dev/Canary channels and expected to happen, less common in Beta channel and so on.
Try not to keep browser open for long periods of time. Chromium browsers aren't supposed to be like that. (Edge, Chrome etc) they all receive important security updates regularly, apart from maintenance and feature updates, and for updates to be applied browser needs to be restarted.
History and Open tabs sync are enabled at the moment for majority of Edge Dev/Canary users, (v88 and v89). the truth is, if you had upgraded your Edge dev update on time, you would have received these sync features and your history, session, open tabs would be available on the cloud.- Re "snapshot of v87" - I found that when it updates, some data of the previous version is stored in a folder called Snapshots in the profile folder. Unfortunately, Local Storage is not among them.
Re sync - I'm less concerned with sync features right now because I found the session file and can parse it programmatically to get what I need right now.
I understand very clearly that there were a lot of things I could have done in hindsight to avoid this problem. That being said, it's obvious I didn't do them, but local storage was still deleted during the restart+update process and I disagree with the program's choice to not even attempt to retain a backup of it with the other data.