While looking into Hyper-V socket implementation for using it within a service from vm, I have found out that implementation from HvSocketConn and HvSocketListener uses windows.Close to close a created socket, which calls windows.CloseHandle internally.

from "golang.org/x/sys/windows..

func Close(fd Handle) (err error) {
	return CloseHandle(fd)
}

However it is stated that in CloseHandle

Do not use the CloseHandle function to close a socket. Instead, use the closesocket function, which releases all resources associated with the socket including the handle to the socket object. For more information, see Socket Closure.

which makes this look like doing something like

// closeHandle closes the resources associated with a Win32 handle.
func (f *win32File) closeHandle() {
	f.wgLock.Lock()
	// Atomically set that we are closing, releasing the resources only once.
	if !f.closing.Swap(true) {
		f.wgLock.Unlock()
		// cancel all IO and wait for it to complete
		_ = cancelIoEx(f.handle, nil)
		f.wg.Wait()
		// at this point, no new IO can start
		if f.socket {
			windows.Closesocket(f.handle)
		} else {
			windows.Close(f.handle)
		}
		f.handle = 0
	} else {
		f.wgLock.Unlock()
	}
}

would be required to close a socket instead of a regular windows file?

Is using windows.CloseHandle a valid approach for closing a Hyper-V socket as it is not a common network socket or is this something needs to be fixed?