This article applies to the following ScreenBeam products:
The following is a list of known issues that you may encounter when using various features of ScreenBeam. This includes issues that affect client devices or other external factors. We are working to resolve these issues as quickly as possible, please follow this article if you would to be notified whenever we have updates on known issues or a new problem is discovered.
Open Issues
Firmware upgrade fails if Digital Signage is enabled (11.x.9.0)
Description
Firmware upgrade will fail to complete if Digital Signage is enabled on the receiver.
Affects
ScreenBeam 1000, 1100, and 1100 Plus on firmware version 11.0.9.0
Workaround
Follow the procedure below to perform an upgrade from 11.0.9.0:
- Login to the receiver LMI, or use CMS, and set Digital Signage to Disable
- Reboot the receiver
- Perform the firmware upgrade. The device will reboot after the process completes.
- After the firmware upgrade process is finished, re-enable Digital Signage
Resolution
We expect this issue to be resolved in a future firmware release.
Resolved Issues
Windows PC may auto-disconnect from a Miracast session unexpectedly
Description
Windows 10 PCs may unexpectedly disconnect from the ScreenBeam receiver during a Miracast session. This behavior can happen at any time during a session and may repeatedly occur for multiple sessions.
Affects
Certain PC systems running Windows 10 Build 1903, 1909 or 2004
Resolution
Patches have been released to address random Miracast disconnects. The patch to download and apply depends on the Windows 10 Build it is being applied to. Select the appropriate patch file for your system below.
- For Windows 10 Build 2004: Knowledgebase article - KB4571756. Download patch file here.
- For Windows 10 Build 1903/1909: Knowledgebase article - KB4586819. Download patch file here
Windows PC desktop may freeze or lock-up when connecting to ScreenBeam
Description
An issue may occur in Windows PCs where various desktop components freeze or lock up. This typically occurs when a reconnect to ScreenBeam is immediately initiated after a disconnect or failed connection attempt.
Affects
Certain PC systems running Windows 10 Build 1903, 1909 or 2004
Resolution
A fix has been released to address this issue and can be downloaded and applied to the Windows PCs to prevent this behavior from occurring again:
- Windows 10 Build 2004 – https://support.microsoft.com/en-us/help/4577063/windows-10-update-kb4577063
- Windows 10 Build 1903 or 1909 - https://support.microsoft.com/en-us/help/4577062/windows-10-update-kb4577062
Windows PC fails to discover receiver
Description
A Windows PC may open the Connect sidebar (Win + k) to connect to a ScreenBeam receiver but nothing appears on the scan list. This typically does not happen on the first time, but on subsequent launches of the Connect sidebar and the issue is then observed.
Affects
Windows PCs with Intel-based wireless adapters of the 9xxx, or AXxxx families.
Resolution
Apply the latest Intel wireless driver for your card. I recommend going to Intel's support page and getting the latest version of the driver for your laptop, you might not get the latest version from Windows update/onboard laptop utilities, but the support page will have a sufficient (21.110.x.x or newer) version available.
Comments
0 comments
Please sign in to leave a comment.