Hi, i got:
- Windows 10 Home 64-bit
- Internet Explorer 11.371.16299.0
- Flash Player 184.108.40.206
whenever i play a game .swf it never save my progress: i checked on C:\users\admin\AppData\Roaming\Macromedia\FlashPlayer\#SharedObjects\(numbersandletters)\#localwithnet but there is a save data for a game only and if i plays it never update
I tried other games but i didn't get the .sol files
Someone can help me?
Do you have the "Delete History on Exit" setting checked in IE? It will delete all of your SOLs on every exit.
It's was already disabled. The problem is not solved.
My guess is that the file and/or permissions is corrupt and we can't write to it.
You can check the filesystem and repair any errors with chkdsk:
Check your hard disk for errors - Windows 7:
At that point, you can try just deleting the offending file. It should get recreated, although you'll lose any game progress.
No errors detected. I trashed all .sol files but fp don't save.
It seems like a situation where we can't write. That's usually disk corruption or a permissions problem.
If you want to rule out the possibility that it's something to do with running the file off the local filesystem, you could try running a local webserver like WAMP and accessing it that way. If it's saving that way and not when you run from the local filesystem, that would be interesting, but I'm not currently aware of a problem like that in the field.
Using a different browser flash player saves but with explorer don't saves. What's wrong with explorer? Really because i have removed the other browser and want continue to use explorer.
The problem is not solved, someone can help me?
Have you actually tried the things I recommended?
Yes, when Wamp is running it saves but when is off it don't save
That's helpful, thanks. We're able to reproduce this. It looks like a bug.
In general, the browsers are making it harder to run files locally. When developing Flash content, I find that running WAMP is much better than developing off the local filesystem, simply because you get the same security behaviors.
I don't think there's a better workaround than what you're already doing at this point.
How can be solved this situation?
We'll have to fix the bug and push it out in a future release, assuming that the change was unintentional. In the meantime, you can run it under WAMP as a workaround.