Microsoft Windows 8 Known Issues

This page contains known issues with Windows 8 and identifies workarounds when they have been identified.

ActiveSync and Built-in Exchange Apps

When configuring Exchange in the built-in Mail application with a Standard account (i.e., a non-Admin account), an error message prevents completion of the setup. The error message is displayed in the top bar of the Mail app as "To Sync [email], you'll need to change this PC's settings to match the mail server's security policy". More details shows: "To sync this account, you'll first need to make your Windows user account an administrator. Make these changes, and then try syncing again."

Example of Error message

This error is associated with non-domain-attached devices using non-admin accounts. Either adding the device to the domain or giving the user account administrative privledges will resolve the issue. However, an alternative workaround has been identified as well:

  1. Log in with an account with local Administrator priviledges and configure the mail app to sync with exchange. This will enforce the Exchange policies on the device.
  2. Log in with the regular user account and configure the mail app to sync with exchange.

Connecting to AirPennNet on Windows 8

Please note that XpressConnect is not necessary to connect to AirPennNet on devices running Windows 8 and above. To connect to AirPennNet:

  1. Open "Connect to a Network"
  2. Select "AirPennNet"
  3. Press "Connect"
  4. Enter your PennKey and Password, then press "OK"

Surface Pro and Surface Pro 2 Unable to Connect to AirPennNet (Resolved)

On Tuesday, March 11, 2014, Microsoft released a firmware update for the Surface Pro and Surface Pro 2 that resolved issues with connecting to wireless networks. Prior to the update, Surface Pro (and Pro 2) devices attempting to connect to AirPennNet received a 'Limited network connection' warning when connecting to AirPennNet. If you are experiencing issues connecting to AirPennNet on a Surface, make sure you have the latest firmware version and all software updates.

Junos Pulse Installation causes System Instability (Resolved)

On March 28, 2014, Juniper Networks released Junos Pulse 5.0.3, which resolves the issue outlined below (Junos Pulse 4.x installers have not been fixed). More information can be found in Juniper Network's Knowledbase article KB28571.

Installing Junos Pulse on Windows 8 devices with NDIS 6 drivers can result in unstable devices. As described in Juniper Network's Knowledbase article KB28571, installing Junos Pulse 4.0 on Microsoft Surface Pro, Microsoft Surface Pro 2, Dell Latitude 10, or Samsung Smart PC Pro Tablets results one or more of the following symptoms: several subsystems becoming unusable, a yellow warning icon appearing in the device manager list, network adapters becoming unusable, or the inability to log in/boot properly. In many cases, the only way to remedy any of these symptoms is a full system refresh. 

According to the Junos article, a permanent fix is expected with the next release of the Junos Pulse Client. Until then, follow the resolution steps from the Junos article, copied below:

A workaround has been identified is outlined below.  The following procedure should be performed after Pulse is installed but before rebooting the device:

  1. Install Pulse.
  2. Download the nvspbind package from the following site:
    Note: There are different versions of the utility.
    - For 64 bit OS, download Microsoft_Nvspbind_package.EXE
    - For 32 bit OS, download 32bit_Nvspbind_package.EXE
  3. Run the appropriate Nvspbind_package.EXE. It will prompt for a target folder to extract the package contents.
  4. Open a command prompt (run as administrator).
  5. cd to the folder where the Nvspbind_package.EXE is installed.
  6. Run the following command: nvspbind.exe -d * jnprna
  7. Run the following command: nvspbind.exe -e "Microsoft Wi-Fi Direct Virtual Adapter" jnprna

After a reboot, the tablet should run properly.

The Cisco AnyConnect Client is the new Cisco VPN that is supported Windows 8/8.1. Cisco VPN Client v5.0.07.0440 is not supported, but a workaround has been identified:

  1. Download the Citrix Deterministic Network Enhancer 
  2. Edit the Registry Key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\CVirtA.  Select the Display Name to modify and remove the leading characters from the data value.  Example: Change “oem8.inf,%CVirtA_Desc%;Cisco Systems VPN Adapter” to “Cisco Systems VPN Adapter”
  3. Users will now be able to access the Cisco VPN Client v5.0.07.0440.
Print This Page Share:
Date Posted: March 11, 2014 Tags: Windows 8

Was this information helpful?

Login with PennKey to view and post comments