Skip to content
Windows 10 Creators Update Annoyance
Got a problem with Viscosity or need help? Ask here!
Windows 10 version 1703 or Creators Update small annoyance:
When Viscosity is not connected, the Health Report under Device Performance & Health thinks there is something wrong with with the Viscosity Virtual Adapter's driver.
Eventually, it always returns after every reboot and I haven't seen any way to disable that particular false flag message.
Maybe this will be fixed in an upcoming version update?
When Viscosity is not connected, the Health Report under Device Performance & Health thinks there is something wrong with with the Viscosity Virtual Adapter's driver.
Eventually, it always returns after every reboot and I haven't seen any way to disable that particular false flag message.
Maybe this will be fixed in an upcoming version update?
Hi Zelroy,
Thanks for the report, we are investigating.
Regards,
Eric
Thanks for the report, we are investigating.
Regards,
Eric
Eric Thorpe
Viscosity Developer
Web: http://www.sparklabs.com
Support: http://www.sparklabs.com/support
Twitter: http://twitter.com/sparklabs
Viscosity Developer
Web: http://www.sparklabs.com
Support: http://www.sparklabs.com/support
Twitter: http://twitter.com/sparklabs
Hi Zelroy,
The issue being reported is that the adapters are disabled. There isn't anything we can do to fix this in a future release and have submitted feedback to Microsoft to at least allow a way to bypass this. We are actually getting the same error reported on one of our test laptops because the WiFi is disabled, something done on purpose.
We'll keep an eye on this regardless and see if there's anything we can do to bypass this warning.
Regards,
Eric
The issue being reported is that the adapters are disabled. There isn't anything we can do to fix this in a future release and have submitted feedback to Microsoft to at least allow a way to bypass this. We are actually getting the same error reported on one of our test laptops because the WiFi is disabled, something done on purpose.
We'll keep an eye on this regardless and see if there's anything we can do to bypass this warning.
Regards,
Eric
Eric Thorpe
Viscosity Developer
Web: http://www.sparklabs.com
Support: http://www.sparklabs.com/support
Twitter: http://twitter.com/sparklabs
Viscosity Developer
Web: http://www.sparklabs.com
Support: http://www.sparklabs.com/support
Twitter: http://twitter.com/sparklabs
4 posts
Page 1 of 1