Set "Enable Single-Store Mode" to Yes" in Stores -> Configuration -> General -> Single-Store Mode fieldset
Currency Symbol is set back to the default value
A success message is shown, but currency symbol is not changed back to the default value
Hi @sivaschenko. Thank you for your report.
To help us process this issue please make sure that you provided the following information:
Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:
@magento-engcom-team give me {$VERSION} instance
where {$VERSION} is version tags (starting from 2.2.0+) or develop branches (2.2-develop +).
For more details, please, review the Magento Contributor Assistant documentation.
@sivaschenko do you confirm that you was able to reproduce the issue on vanilla Magento instance following steps to reproduce?
@sivaschenko, thank you for your report.
You just need to flush cache.
@engcom-backlog-pb there is no cache involved in the admin panel. The issue is still actual and should be reopened.
@engcom-backlog-pb I wonder, who stands behind the answer about the cache.
Thank you! @miguelbalparda
@sivaschenko, thank you for your report.
We were not able to reproduce this issue by following the steps you provided. Please provide more detailed steps to reproduce or try to reproduce this issue on a clean installation or latest release.

@engcom-backlog-pb Sorry, I missed one important precondition: this is single-store mode issue. Title and description updated accordingly.
Here is a screen recording of what acvtually happens:

@sivaschenko, thank you for an update.
We've acknowledged the issue and added to our backlog.
Hi @sivaschenko. Thank you for your report.
The issue has been fixed in magento/magento2#17966 by @magently in 2.2-develop branch
Related commit(s):
The fix will be available with the upcoming 2.2.8 release.
Hi @sivaschenko. Thank you for your report.
The issue has been fixed in magento/magento2#18204 by @mage2pratik in 2.3-develop branch
Related commit(s):
The fix will be available with the upcoming 2.3.1 release.