Just for reference - I got the same problem again, this time isolated to location A (on 5G), after waking up from hibernation.
To repair the stuck state, executing some PowerShell commands (see below) was enough to get the driver out of what appears to be a stuck state.
(The Disable-Device, Enable-Device cmdlets were downloaded from TechNet Device Management PowerShell Cmdlets)
Note, BTW, that the driver itself seems to report that it is in a healthy state.
PS C:\Windows\system32> Get-Device | Where-Object -Property Name -like "Intel*Dual Band Wireless*"
Name : Intel(R) Dual Band Wireless-AC 3160
Capabilities : 0
ConfigurationFlags : 0
InstallState : InstallStateInstalled
NumaNode : 0
UINumber : 0
Characteristics : 0
Manufacturer :
HardwareIds : {PCI\VEN_8086&DEV_08B3&SUBSYS_81708086&REV_83, PCI\VEN_8086&DEV_08B3&SUBSYS_81708086,
PCI\VEN_8086&DEV_08B3&CC_028000, PCI\VEN_8086&DEV_08B3&CC_0280...}
LocationPaths : {PCIROOT(0)#PCI(1C02)#PCI(0000), ACPI(_SB_)#ACPI(PCI0)#ACPI(RP03)#ACPI(PXSX), , }
DriverVersion : 17.0.6.1
DriverProvider : Intel
DriverDescription : Intel(R) Dual Band Wireless-AC 3160
LocationInfo : PCI bus 2, device 0, function 0
InstanceId : PCI\VEN_8086&DEV_08B3&SUBSYS_81708086&REV_83\4&13C7D2&0&00E2
Service : NETwNb64
DeviceParent : PCI\VEN_8086&DEV_9C14&SUBSYS_00011179&REV_E4\3&11583659&1&E2
DeviceSiblings :
IsPresent : True
HasProblem : False
AvailableProperties : {[DEVPKEY_NAME, Intel(R) Dual Band Wireless-AC 3160 ], [DEVPKEY_Device_DeviceDesc, Intel(R) Dual
Band Wireless-AC 3160 ], [DEVPKEY_Device_HardwareIds, System.String[]],
[DEVPKEY_Device_CompatibleIds, System.String[]]...}
PS C:\Windows\system32> Get-Device | Where-Object -Property Name -like "Intel*Dual Band Wireless*" | Disable-Device
Device Disabled
PS C:\Windows\system32> Get-Device | Where-Object -Property Name -like "Intel*Dual Band Wireless*" | Enable-Device
Device Enabled
PS C:\Windows\system32>