FIX: The "is_media_read_only" value remains unchanged for a SQL Server data file even though the media is no longer read-only

Applies to: SQL Server 2017 Developer on WindowsSQL Server 2017 Enterprise Core on WindowsSQL Server 2017 Enterprise on Windows

Symptoms


Assume that the is_media_read_only columnvalue is '1' for a data file in sys.database_files and sys.master_files in SQLServer 2016 or 2017. The column indicates that the underlying media hosting the datafile is read-only. The is_media_read_only valueremains unchanged even though the media is no longer read-only. Restoring orattaching the database that the file belongs to still may not change the columnvalue. Because of this issue, some operations will fail including enabling TDE on thedatabase. You may receive an error message that resembles the following:
Msg 33118, Level 16, State 2, Line LineNumber
Cannot enable or modify database encryptionon a database that is read-only, has read-only files or is not recovered.

Status


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. 

Resolution


This issue is fixed in the following cumulative updates for SQL Server:
About cumulative updates for SQL Server:
Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. Check out the latest cumulative updates for SQL Server:

References


Learn about the terminology that Microsoft uses to describe software updates.