Posts made by otcpharm

@a4pacific Thanks, will go check.

@a4pacific Because Edge isn't Opera. Pretty simple. Nobody said it's "bad." Very clearly says Opera has disabled it, and gives their reason.

Extension is disabled.

"We've identified this extension as malicious and have blacklisted it. This means it can no longer cause any damage to your machine. You can leave it as is, or remove it."

Well, that seems to have taken care of it. 2nd day and it’s still running strong.

I can conclude that it’s not PC specific or hardware related, because it did the exact same thing on my work PC (8 month old HP desktop, Roaming folder on secondary HDD) the very next day after it crashed out on my home PC (2 year old Toshiba laptop, Roaming folder on primary SSD) - 4 crashes with 3 automatic restart attempts. The only thing they have in common is the version of Opera installed and the version of Windows they’re running. I repeated the same clean/reinstall steps on my work PC, with no changes to ownership/permissions of the profile folder, and it’s working fine now, too.

Thank God, because 1) I was dreading the possibility of having to migrate back to PaleMoon, and 2) after dealing with other people’s PC problems all day, I REALLY don’t like having to mess with mine.

@otcpharm said in opera won't open after windows 10 feature update:

OK, I'm up to 2 hours without a crash on this 2nd repair attempt.

Temp profile was not needed this time. Saved a copy of the Roaming "opera software" folder, uninstalled Opera normally, deleted both Local and Roaming 'Opera Software' folders, deleted the Opera folder left in Program Files, then ccleaned the registry - it removed a lot of dead stuff with Opera's name on it.

OK, I'm up to 2 hours without a crash on this 2nd repair attempt.

Temp profile was not needed this time. Saved a copy of the Roaming "opera software" folder, uninstalled Opera normally, deleted both Local and Roaming 'Opera Software' folders, deleted the Opera folder left in Program Files, then ccleaned the registry - it removed a lot of dead stuff with Opera's name on it.

Rebooted then reinstalled Opera normally. Copied bookmark files from the previously copied Roaming folder into the new Roaming folder, and it seems to be solid with extensions added back in.

I guess we'll see how it holds up for the rest of the day.

@otcpharm said in opera won't open after windows 10 feature update:

And that lasted a whole 30 minutes, then crashed again. Now it's back to open/crash/open/crash/open/crash/open/crash. Always 4 times, after the initial open, it crashes followed by three automatic recovery attempts that each crash. Then it gives up.

Now here's the fun part - if I go back to the temp profile I created earlier and run the original (was crashing, and is now crashing again after being "fixed") install of Opera, it starts and runs just fine.

Guys...what's going on?

And that lasted a whole 30 minutes, then crashed again. Now it's back to open/crash/open/crash/open/crash/open/crash. Always 4 times, after the initial open, it crashes followed by three automatic recovery attempts that each crash. Then it gives up.

Now here's the fun part - if I go back to the temp profile I created earlier and run the original (was crashing, and is now crashing again after being "fixed") install of Opera, it starts and runs just fine.

Guys...what's going on?

@otcpharm said in opera won't open after windows 10 feature update:

@burnout426

Same issue as coolusername. Created new admin profile, installed Opera in a separate folder using new profile, verified proper function - everything normal.

Cliff notes version - something in the profile folder is indeed hosed.

What's disappointing here is that Opera seems to have become sensitive to the point that a simple Windows feature update can randomly cause Opera to eat its own profile, killing the browser. Not cool.

@burnout426

Same issue as coolusername. Created new admin profile, installed Opera in a separate folder using new profile, verified proper function - everything normal. Gave the primary user profile Full Access rights to the Opera profile folder, returned to the primary profile and copied the new profile folder contents over the existing (crashing) profile folder (except for bookmarks). Verified proper function - now normal - and returned to the temporary profile to uninstall that discrete instance of Opera. Now have a single, fully functioning installation again. So far, it looks like all I lost is my speed dial pages and my history. I'm sure more will turn up, but right now it's rolling again.

Cliff notes version - something in the profile folder is indeed hosed.

What's disappointing here is that Opera seems to have become sensitive to the point that a simple Windows feature update can randomly cause Opera to eat its own profile, killing the browser. Not cool.