SQL Server sys.dm_os_performance_counters cntr_values are all 0

I am having an issue whereby all the cntr_values from sys.dm_os_performance_counters are always 0

I have two SQL Server 2016 instances, one developer edition, and one standard edition. Both are sitting on SP1 CU8 and both are experiencing the same issue.

The standard edition was recently installed, and can see that its installation experienced no issues overall as seen in *\130\Setup Bootstrap\Log\Summary.txt. The instance was installed afresh with this patch level so there is only one set of logs to look through.

In *\130\Setup Bootstrap\Log\20180502_141120\Detail.txt though I found the below three exceptions, although am not sure what to make of them

(06) 2018-05-02 14:11:36 Slp: Exception type: Microsoft.SqlServer.Configuration.Sco.MonitorThreadInterruptedException
(06) 2018-05-02 14:11:36 Slp:     Message: 
(06) 2018-05-02 14:11:36 Slp:         The directory monitor thread is interrupted. Message: 'The directory monitor thread is interrupted due to a StopMonitor call.'
(06) 2018-05-02 14:11:36 Slp:     HResult : 0x86a40016
(06) 2018-05-02 14:11:36 Slp:         FacilityCode : 1700 (6a4)
(06) 2018-05-02 14:11:36 Slp:         ErrorCode : 22 (0016)
(06) 2018-05-02 14:11:36 Slp:     Data: 
(06) 2018-05-02 14:11:36 Slp:       ErrorMessage = The directory monitor thread is interrupted due to a StopMonitor call.
(06) 2018-05-02 14:11:36 Slp:       WatsonData = Microsoft.SqlServer.Configuration.Sco.MonitorThreadInterruptedException@22
(06) 2018-05-02 14:11:36 Slp:     Stack: 
(06) 2018-05-02 14:11:36 Slp:         at Microsoft.SqlServer.Configuration.Sco.DirectoryMonitor.Monitor()

(14) 2018-05-02 14:17:18 Slp: Exception type: Microsoft.SqlServer.Configuration.Sco.MonitorThreadInterruptedException
(14) 2018-05-02 14:17:18 Slp:     Message: 
(14) 2018-05-02 14:17:18 Slp:         The directory monitor thread is interrupted. Message: 'The directory monitor thread is interrupted due to a StopMonitor call.'
(14) 2018-05-02 14:17:18 Slp:     HResult : 0x86a40016
(14) 2018-05-02 14:17:18 Slp:         FacilityCode : 1700 (6a4)
(14) 2018-05-02 14:17:18 Slp:         ErrorCode : 22 (0016)
(14) 2018-05-02 14:17:18 Slp:     Data: 
(14) 2018-05-02 14:17:18 Slp:       ErrorMessage = The directory monitor thread is interrupted due to a StopMonitor call.
(17) 2018-05-02 14:17:18 Slp:       WatsonData = Microsoft.SqlServer.Configuration.Sco.MonitorThreadInterruptedException@22
(17) 2018-05-02 14:17:18 Slp:     Stack: 
(17) 2018-05-02 14:17:18 Slp:         at Microsoft.SqlServer.Configuration.Sco.DirectoryMonitor.Monitor()

(01) 2018-05-02 14:26:40 Slp: Exception type: Microsoft.SqlServer.Setup.Chainer.Workflow.NestedProcessExecutionCompletionException
(01) 2018-05-02 14:26:40 Slp:     Message: 
(01) 2018-05-02 14:26:40 Slp:         Aborting queue processing as the nested bootstrap program has completed with exit code 0.
(01) 2018-05-02 14:26:40 Slp:     HResult : 0x00000000
(01) 2018-05-02 14:26:40 Slp:         FacilityCode : 0 (000)
(01) 2018-05-02 14:26:40 Slp:         ErrorCode : 0 (0000)
(01) 2018-05-02 14:26:40 Slp:     Data: 
(01) 2018-05-02 14:26:40 Slp:       SQL.Setup.FailureCategory = ActionFailure
(01) 2018-05-02 14:26:40 Slp:     Stack: 
(01) 2018-05-02 14:26:40 Slp:         at Microsoft.SqlServer.Configuration.BootstrapExtension.LaunchBootstrapAction.ExecuteAction(String actionId)

I ran through the solution suggested at https://dba.stackexchange.com/questions/112371/zero-rows-return-on-querying-dmv-sys-dm-os-performance-counters but unfortunately had no luck. I then ran a repair against the developer edition instance and it fixed the issue but am looking for a less invasive solution for the standard edition instance.

How do I get the cntr_values to show the correct values without repairing the instance? Also how do I prevent this in the future and what is the cause?