Assume that you run sp_configure stored procedure to change the PolyBase enabled status to '0 or 1' in SQL Server 2019. After changing PolyBase enabled status, when you query the PolyBase Dynamic Management Views (DMVs), you may get unexpected results.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
This issue is fixed in the following cumulative update 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: