"Cannot change thread mode after it is set." error when calling disk.IOCounters on Windows

[ericrange]

Describe the bug
Sometimes i get an error when i want to get the io counters. But just sometimes...
"Cannot change thread mode after it is set."

To Reproduce

        parts, err := disk.Partitions(false)
	for _, part := range parts {
		u, errUsage := disk.Usage(part.Mountpoint)
		if errUsage != nil {
			logger.Error.Println(errUsage)
			continue
		}

		counters, errIO := disk.IOCounters(part.Mountpoint)
		if errIO != nil {
		=>	logger.Error.Println(errIO)
                "Cannot change thread mode after it is set."
                ....

Expected behavior
[A clear and concise description of what you expected to happen.]

Environment (please complete the following information):

• Windows: [Windows Server 2012R2]
• Linux: [paste contents of /etc/os-release and the result of uname -a]
• Mac OS: [paste the result of sw_vers and uname -a
• FreeBSD: [paste the result of freebsd-version -k -r -u and uname -a]
• OpenBSD: [paste the result of uname -a]

[shirou]

I have created this gist.
https://gist.github.com/shirou/004b2a859ed5f33ca659e431b7378d17

• linux( 4.15.0-38-generic, go1.11.1) -> not error
• freebsd(11.2-RELEASE-p4, go1.11.1) -> not error

I have not digged the golang source code, but is it windows only?

[ericrange]

it seems that it is windows only. never got such an error for linux.
But as i said. it appears only "sometimes". Every 5 minutes, i guess.

[Lomanic]

Solution is probably to remove calls to WMI (see #692 (comment)), performance counters might be an option here but way less easy to request than wmi (thanks to stackexchange/wmi package). Here is an example in Python, here is a promising package in Go.

[Lomanic]

disk.IOCounters doesn't use WMI internally after #850 has been merged.