It’s been a long time coming, but there finally seems to be light at the end of the tunnel…
I’ve been using the Surface Pro 3 at the office since December of 2014. Prior to that, I used a Surface Pro 1 for a couple of years. It was the best and easiest way to really organize work at the office; and I say this to any and everyone who asks why I use it:
- It’s the best digital notepad (with OneNote) I’ve ever been to find and use
- With OneNote on the web and/ or OneNote’s sync capabilities, you have access to your notes nearly everywhere you have a device with internet access
- Paper notepads, notebooks and portfolios get lost. You’re never going to leave a tablet in a conference or meeting room (they’re too expensive to forget)
It’s a nearly flawless system, and it’s one of the best out there. Other software and hardware tools just don’t have the same capabilities or use cases due to one limitation or another.
When the Surface Pro 3 was released, I knew it was worth the upgrade from my Surface Pro 1, so off it went toGazelle, and over to the Microsoft Store I went. While Windows 8.1 wasn’t as optimal a notebook experience as I wanted, and while (in my opinion) Windows still doesn’t know if it wants to be a desktop or tablet OS (even with Windows 10); with either Windows 8.1 or Windows 10 (and the right utilities, like Start8 from Stardock Software) it can still be a very productive tool in either an corporate or academic setting.
Until, however, you move to Windows 10 and you bump into the problems I mentioned in March of 2015. The Disappearing Ink Bug is a huge problem for users of the Surface Pro 3.
It completely negates nearly all the value out of the device.
The reliability of the inking system is nearly gone. You never know when you’re going to lose anything you’ve written down, as the bug is completely random, and in end, you’re left with two very real choices – downgrade from Windows 10 to Windows 8.1 or take your chances with Windows 10, the bug, and maybe you lose some notes or maybe you don’t.
Well, I have a bit of an update for you. There appears to be, what may be, a final fix for this problem. There are two very active threads on this issue over at the Microsoft Support Community (here and here).
Microsoft has released KB3093266 in response to disappearing ink on the Surface Pro 3 running Windows 10. This cumulative update addresses not only disappearing ink, but tap becomes right click as well. Both of these issues were contributing factors to the conditions being experienced (where ink would vanish in OneNote on a Surface Pro 3 running Windows 10).
The cumulative update available via Windows Update on your Windows 10 PC, may take a while to appear on your Windows 10 PC. Like all Windows Updates, Microsoft rolls them out in batches.
Unfortunately, I haven’t had it show up for me yet.
“Can you possibly tell the Windows OS team to check with the surface team and tell the surface team to check with your team before releasing an Operating System which breaks core functionality of your Staple Devices?
I cannot in good conscious use a Surface (Pro or not) again because of the way this migration to Windows 10 was handled in lieu of Office 2016 and the Surface Pro 4.
I want to trust Windows, I want to depend on you guys for quality control and solutions my customers can trust. I just can’t…”
While it seems obvious, the reliability and trustability of Windows 10 for many users has greatly diminished. It’s not just this issue, there are still huge privacy, stability and (other) reliability concerns. You can check just about any and every Windows blog on the internet today and find at least 2-3 articles covering all that.
The cumulative update I mentioned may resolve the disappearing ink issue… it may not. KB3093266 is not the first fix that was released to address the issue. There were individual updates made to Windows 10, OneNote 2013/2016 as well as Office 2016 that failed to resolve the problems between May and September of 2015.
Results from those that have received this update have been generally positive, though somewhat mixed. Generally, it seems to be working; but like Dittman noted above, how much damage has TRULY occurred for the Windows and Surface Pro brands?
How easily Microsoft can recover from this is going to depend on a couple of things:
- Does the cumulative update truly resolve the bug for all users of both the Surface Pro 3 and the Surface 3 (its actually experienced on nearly all Surface Pro devices as well as the Surface 3)
- How well the Surface Pro 4 is received
- How well the bug stays resolved (especially on the Surface Pro 4)
Every time Microsoft releases a cumulative update or a new build, this issue is going to have to be retested. It’s very possible given the depth and severity of the problem(s) that Microsoft may resurrect the issue in future builds and updates. While that’s not ideal and certainly won’t be intentional, it does happen quite often with software development. It’s simply the nature of the beast – sometimes, it comes back.
The Surface Pro 4 has been anticipated for many months now. While there’s no real evidence that any industry pundit can provide regarding a credible rumor on the device’s ACTUAL existence, it is said that Microsoft will announce something next week (2015-10-05 to 2015-10-09) with an actual release date also rumored to be SOMETIME this month (October 2015). While it totally misses Back to School, it should hit the 2015 Holiday Buying Season, provided its already being manufactured.
Do you have a Surface Pro device (1, 2 or 3)? Do you have a Surface 3? Are you using OneNote and the Surface Pen to take notes? Are you experiencing issues with floating and disappearing ink? Have you been following any of the Microsoft support threads I mentioned (here or here)? Have you received the Windows 10 Cumulative Update (KB3093266) that I mentioned?
If you have, do, etc. and have received the update, I would REALLY appreciate hearing back from you on this. Please provide the appropriate comments and/ or information in the Discussion area, below, so that I can get your information back to Microsoft. This is a huge bug, and really needs to be resolved once and for all.