Skip to main content
pro256
Known Participant
September 21, 2017
Answered

Local Settings Manager won't retain settings

  • September 21, 2017
  • 4 replies
  • 7073 views

Environment Windows 7 Professional SP1 64-bit

Internet Explorer 11

Flash Player 27.0.0.130

Issue:

We are rolling out Flash Player 27.0.0.130.  We noticed that after upgrading to Flash Player 27.0.0.130 from Flash Player 26.0.0.151 our Local Settings won't "stick".  We haven't had this problem in the past with upgrades.  We've had this happen on several machines, so we've stopped our rollout until we understand what's going on.

The machines were functioning perfectly before the upgrade.

For example, on the Storage tab we set "Block all sites from storing information on this computer".  Camera and Microphone settings are set to "Block all sites from using the camera and microphone".   Peer-assisted networking is set to "Block all sites from using peer-assisted networking".

After opening-closing IE, we return to the Local Settings Manager UI in Control Panel.   All of the above settings are set back to their default Allow (Storage), or Ask (Camera and Microphone, Peer-assisted networking) settings.

We've tried a clean install by using the Adobe uninstaller and removing all traces of Flash from our system without fixing the issue.  Flash installs successfully.  IE is set to automatically delete cookies when it is closed.

Any ideas?

This topic has been closed for replies.
Correct answer jeromiec83223024

We identified the offending change this afternoon and rolled it back out.  We're in the endgame for this release, so there's no opportunity to land it in a beta, but it will be fixed in the next release.

4 replies

jeromiec83223024
Community Manager
Community Manager
April 9, 2018

Given the age of the thread and the fact that this has been fixed for months, I'm locking it so that the participants don't get spammed about new, unrelated issues that might share these symptoms.

jeromiec83223024
Community Manager
Community Manager
September 25, 2017

Thanks for the repro steps, that was exactly what I needed.

I'll get a bug open momentarily.

pro256
pro256Author
Known Participant
September 25, 2017

@jeromiec83223024 - Thanks for opening a bug report for us.  Please let us know the resolution.  In the meantime, we'll stick with 26.0.0.151.

@noikon - Thanks for confirming.  We've already regressed back to 26.0.0.151.  We were reasonably confident that it was a bug, but had to perform more testing to find the trigger.  It's always a good idea to function check new versions of any software.

jeromiec83223024
Community Manager
jeromiec83223024Community ManagerCorrect answer
Community Manager
September 25, 2017

We identified the offending change this afternoon and rolled it back out.  We're in the endgame for this release, so there's no opportunity to land it in a beta, but it will be fixed in the next release.

jeromiec83223024
Community Manager
Community Manager
September 21, 2017

The settings are typically stored in C:\<user>\AppData\Roaming\Macromedia\Flash Player\macromedia.com\support\flashplayer\sys\settings.sol.

That the settings revert to default each time Flash Player loads indicates that they're either not being read or written.  When I see this, it's generally a permission or group policy thing that prevents the client from accessing settings.sol.

(edit: You explicitly stated you're upgrading from a recent version, so this probably isn't applicable, but it might help someone else)

If you're upgrading from a really old version of Flash (<14), and you're storing the user's Windows profile on a network share, you might have a look at the description for the EnableInsecureJunctionBehavior flag in mms.cfg.  Details are on pp. 39 of the System Administrator's guide, here: Adobe Flash Player Administration Guide for Flash Player | Adobe Developer Connection

pro256
pro256Author
Known Participant
September 21, 2017

We're upgrading from 26.0.0.151 to 27.0.0.130.    The user's Windows profile is stored on the local machine.

We noticed this behavior if we install before the September Windows maintenance and also if we install after the Windows maintenance.  This is a real puzzler - we're experienced techs.  Have had very few problems with Flash Player in the past.  We've tried all of the usual - uninstall, delete any remaining Adobe files as in Uninstall Flash Player for Windows and How do I do a clean install of Flash Player - Windows?

These are production machines.  They have been working fine and are updated on a routine basis.  We haven't had any permissions issues in past installs.  26.0.0.151 was installed during our August maintenance cycle.

We haven't tried deleting settings.sol in C:\<user>\AppData\Roaming\Macromedia\Flash Player\macromedia.com\support\flashplayer\.  We're assuming that doing the clean install took care of that.

Is it possible that something changed in 27.0.0.130?   We've seen postings about new audio settings -  maybe the other settings were affected somehow.

jeromiec83223024
Community Manager
Community Manager
September 22, 2017

I just double-checked my Win7 x64 machine, and I'm definitely able to get settings to persist.  This is also the only complaint I've seen about this, and the release has been in the field for ~9 days at this point.  I'd expect a much higher volume of complaints.

I'm not sure what we would've broken that would cause this to happen in such a limited way.  I'm not ruling it out, but it seems like it's going to be nuanced bug if that's the case.

If you delete settings.sol then re-launch Flash Player, we should recreate it with default settings.  Do the settings persist after that?  If so,  I'm wondering if we're corrupting the file.  If that's the case, I'd be really interested in comparing a copy of settings.sol pre and post upgrade on a system where the settings now fail to persist. 

It seems unlikely that we would break the config file itself, since I seriously doubt that we modified the classes through which those settings are stored and retrieved, but I'd definitely like to rule it out.

Have you changed anything with IE11, like tightening the rules around IE's protected mode?  I did notice that I had to authorize the native control panel to launch from IE when I chose Global Settings from our context menu.


It might also be helpful for you to articulate some exact repro steps.  I'm making assumptions about what you're doing that might not be valid.

_maria_
Community Manager
Community Manager
September 21, 2017

This is close to a duplicate of mms.cfg settings​, as such, locking.

_maria_
Community Manager
Community Manager
September 21, 2017

Actually, unblocking to investigate the settings not sticking issue.