The following are known issues with TypeWell running on Windows 8. If you are using Windows 10, please go to:
Known Issues with TypeWell on Windows 10
Fractional exponents
TypeWell Transcriber V6 (installed on a Windows 8 machine) may display an error and crash, if you or your team use fractional exponents.
Internal Linking may be disabled after a Windows update, due to Windows deprecating Soft AP
When Windows Update installs an updated network card driver, the "virtual hosted network" feature may become disabled. This is because Windows has deprecated the SoftAP feature that the TypeWell Internal Server program uses to create a hosted network.
Even if your Windows 8 or 10 computer previously supported Internal Linking, after installing a Windows Update, you may suddenly see an error message when you try to use Internal Linking.
See this report from a TypeWell user who was using Internal Linking just fine until the driver was updated during a Windows Update:
Internal Linking Issue - "Disabled because the Virtual AP is not available on your machine"
Another TypeWell user submitted this follow-up comment in March 2016:
I know it's been a week or two now, but I just wanted to follow up and thank you for your help with this! The information about the "VAP not available" issue was extremely helpful. Sure enough, I reinstalled the driver for the wifi adapter via device manager, and internal linking worked like a charm following a reboot. Very good to know as we're adding more Windows 10 machines to our inventory.
To determine whether Internal Linking is supported on your Windows 8 computer, open a Command Prompt and enter the following command:
netsh wlan show wirelesscapabilities
Look for the Soft AP entry. If it shows Not Supported, you might be able to restore this feature by rolling back to an older driver for your wireless device. For example, see this solution in Intel Community forum, where reverting to an older driver changes the IBSS from Not Supported to Supported.
Peer-to-peer (ad hoc) linking may be disabled after a Windows update, due to Windows deprecating IBSS
Ad hoc linking (i.e. IBSS, which is used for TypeWell's peer-to-peer linking) was deprecated starting with Windows 8.1. So, even if a Windows 8 or Windows 10 previously supported peer-to-peer linking, it may cease to work after Windows Update installs a newer network card driver.
To determine whether ad hoc linking is supported on your Windows 8 computer, open a Command Prompt and enter the following command:netsh wlan show wirelesscapabilities
Look for the IBSS entry. If it shows Not Supported, you might be able to restore this feature by rolling back to an older driver for your wireless device. For example, see this solution in Intel Community forum, where reverting to an older driver changes the IBSS from Not Supported to Supported.
Even if IBSS is supported on your Windows 8 or Windows 10 computer, you must have administrative privileges your computer in order to create an ad hoc (peer-to-peer) network. Please follow the steps in this article: Peer-to-Peer WiFi configuration (Windows 8 and 10).
We also suggest using Local Linking with a Virtual Hosted Network (Windows 8), which has the benefit of allowing simultaneous Internet access while the TypeWell computers are linked.
Read more about all of the Linking features that TypeWell supports.
