A new Windows 10 v1903 update block is in place, and this time is aimed at Zebra XSLATE B10 tablet users.

Lots of XSLATE B10 owners reported loss of touch after the update

Following many customer reports that signalled an issue with XSLATE B10 tablets, Microsoft decided to block Windows 10 v1903 and Windows 10 v1809 on these devices.

It seems that after updating to those specific versions, XSLATE B10 tablets lose the touch access:

If you’re in the same boat, you should know that the Redmond giant is aware of the problem and has a support page dedicated to it.

Zebra has received customer reports of an issue with XSLATE B10 tablets after Windows 10 upgrade or deployment. This issue potentially affects Windows 10 versions 1809, 1903 and 19H1. Upon rebooting the device (warm boot), the issue causes users to lose touch access.

Microsoft blocked the Windows 10 v1903 and 1809 on XSLATE B10 tablets

Also, Microsoft is working on a fix as soon as possible, but until one is released, the update block is in place to safeguard the update experience:

As explained by Microsoft in their support document, this is an incompatibility problem. Furthermore, the company recommends users to not manually update their devices.

To safeguard your update experience, we have applied a compatibility hold on these devices from installing or being offered Windows 10, version 1903 or Windows 10, version 1809.

This is another in a long list of update blocks for Windows 10 May update that will hopefully get resolved soon enough.

Have you experienced any issues with your Zebra XSLATE B10 tablet?

Share your experience in the comments section below.

If the advices above haven’t solved your issue, your PC may experience deeper Windows problems. We recommend downloading this PC Repair tool (rated Great on TrustPilot.com) to easily address them. After installation, simply click the Start Scan button and then press on Repair All.

Still having issues? Fix them with this tool:

SPONSORED

  • tabletWindows 10 May 2019 Updatewindows 10 upgrade

Email *

Commenting as . Not you?

Comment